> For the complete documentation index, see [llms.txt](https://upsolver.gitbook.io/content/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upsolver.gitbook.io/content/quickstarts-1/data-ingestion-wizard/using-the-wizard/target-set-up/aws-glue-data-catalog.md). # AWS Glue Data Catalog ## Step 1 - Connect to AWS Glue Data Catalog ### **Create a new connection** Click **Create a new connection**, if it is not already selected. In the **Name your connection** field, type in the name for this connection. Please note this connection will be available to other users in your organization. Set the storage location where target tables will be stored in the **S3 Target Bucket** field, using the format: `S3:///` Select the region where your AWS Glue Data Catalog is hosted in the **Catalog Region** select list.

Create a new connection to AWS Glue Data Catalog to use as the target for your ingestion job.

### Use an existing connection By default, if you have already created a connection, Upsolver selects **Use an existing connection**, and your AWS Glue Data Catalog connection is populated in the list. For organizations with multiple connections, select the target connection you want to use.

Select your AWS Glue Data Catalog to use as the target for your ingestion job.

## Step 2 - Configure AWS access In order for Upsolver to access the catalog and write to the target bucket, follow the AWS configuration assistant link. For the **Authentication Method**, we recommend to use **Role-based** access. Paste the ARN from the role you created in AWS IAM into the **Role ARN** field, as explained in the configuration guide. If using AccessKey/Secret Key, ensure the user provided to Upsolver has the necessary permissions to access AWS Glue Data Catalog and Amazon S3, as explained in the configuration guide. ## Step 3 - Select table format Choose the target format to stored your data: * **Upsolver managed Iceberg** * **Upsolver managed Hive (compatibility mode)** ## Step 4 - Select where to ingest the data In this step, you need to configure the mapping of source schemas to target schemas. Upsolver will automatically create new tables in the selected target schemas. Firstly, define a default target schema. This will be the schema to which all tables from all schemas will be replicated, unless specific manual mappings are defined. When ingesting multiple source schemas into the AWS Glue Data Catalog, you have the following options: 1. Ingest all tables into a single AWS Glue Data Catalog schema and prepend the source schema name to every new table created in the AWS Glue Data Catalog. Use the prefix `{source\_schema}\_` for this purpose. 2. Map each source schema to a corresponding target schema in the AWS Glue Data Catalog. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://upsolver.gitbook.io/content/quickstarts-1/data-ingestion-wizard/using-the-wizard/target-set-up/aws-glue-data-catalog.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.