ingesting-into-data-lake
ingesting into data lake
What it does
- You MUST check whether AWS MCP tools or AWS CLI are available and inform the user if missing
- You MUST confirm target AWS region and verify credentials with aws sts get-caller-identity
- Database/namespace: Does a specific target database exist? Or should one be created?
- Table: Existing table (append/merge) or new table (delegate to creating-data-lake-table)?
- Format: S3 Tables (default), standard Iceberg, or raw Parquet?
- Account has an s3tablescatalog federated catalog and active table buckets: recommend S3 Tables
- Account has general-purpose buckets with Iceberg tables and no S3 Tables usage: recommend standard Iceberg on their existing bucket
Requirements & configuration
- Local files, S3 files, DynamoDB, and catalog migration do not need a Glue connection.
- S3 Tables requires Glue 5.1 or higher and --datalake-formats iceberg job argument
- DynamoDB does not need a Glue connection -- do not attempt to create one
Derived from the skill's own SKILL.md documentation · extracted 2026-07-23
ingesting-into-data-lake FAQ
What does the ingesting-into-data-lake skill do?
>- Import data into the AWS data lake from S3 files, local uploads, JDBC databases (Oracle, SQL Server, PostgreSQL, MySQL, RDS, Aurora), Amazon Redshift, Snowflake, BigQuery, DynamoDB, or existing Glue catalog tables (migration). Default target is S3 Tables; standard Iceberg on a general purpose bucket is supported where S3 Tables is not adopted. Handles one-time loads, recurring pipelines, migrations. Triggers on: import data, load data, ingest, sync database, migrate table, move data to AWS, set up pipeline, ETL, pull from Snowflake, query BigQuery into S3, export DynamoDB, CTAS, convert to Iceberg. Do NOT use for setting up or troubleshooting Glue connections (use connecting-to-data-source), creating empty tables (use creating-data-lake-table), running queries (use querying-data-lake), finding tables by fuzzy name (use finding-data-lake-assets), catalog audit (use exploring-data-catalog), or SaaS platforms like Salesforce, ServiceNow, SAP, MongoDB, Kafka. You MUST check whether AWS MCP tools or AWS CLI are available and inform the user if missing You MUST confirm target AWS region and verify credentials with aws sts get-caller-identity
What does ingesting-into-data-lake require?
Local files, S3 files, DynamoDB, and catalog migration do not need a Glue connection. S3 Tables requires Glue 5.1 or higher and --datalake-formats iceberg job argument DynamoDB does not need a Glue connection -- do not attempt to create one
How do I install ingesting-into-data-lake?
Run: npx -y skills add https://github.com/aws/agent-toolkit-for-aws --skill ingesting-into-data-lake --agent claude-code — the source lives at github.com/aws/agent-toolkit-for-aws.
Maintain ingesting-into-data-lake?
Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.
[ingesting-into-data-lake on getagentictools](https://getagentictools.com/skills/aws-agent-toolkit-for-aws-ingesting-into-data-lake?ref=badge) npx agentictools info skills/aws-agent-toolkit-for-aws-ingesting-into-data-lake The second line is the CLI lookup for this page — handy in READMEs and docs.