Skip to main content

Import Assets from S3
App

You can bulk import or update asset metadata in Atlan (connections, databases, schemas, tables, columns, etc.) using a CSV file stored in Amazon S3.

This guide shows you how to set up and run a workflow to import assets from S3 into Atlan.

Other options also exist

Refer to the reference for other options, if you prefer to use some other object store or even to upload your files directly to Atlan.

Prerequisites​

Before you begin, make sure you have:

  • Access to the Asset Import app. If you don’t have access, contact Atlan support or your Atlan customer team.
  • Permissions in Atlan to run workflows and edit asset metadata.
  • An S3 bucket containing your asset CSV file in the Assets CSV format.
  • AWS credentials (access key, secret key, and region) with permission to read from the bucket.

Setup workflow​

  1. In your Atlan workspace, go to the homepage and click New workflow in the top navigation bar.

  2. Search for Asset Import, and then select Set up workflow.

  3. In the Workflow name field, enter a descriptive name such as:

    AWS S3 Asset Import — Sales DB

  4. In the Import metadata from section, select Object storage, then choose S3. This loads your CSV directly from an S3 bucket. For alternatives (local file uploads and other object stores), see Import metadata from reference.

  5. In the AWS access key field, add your AWS access key. You can find this in the AWS Management Console → IAM → Users → Security credentials tab.

  6. In the AWS secret key field, add your AWS secret key, which pairs with the access key. This is visible only at creation time in IAM.

  7. In the Region field, enter the AWS region where your S3 bucket is located. You can find this in the S3 service dashboard when selecting your bucket.

  8. In the Bucket field, enter the name of the S3 bucket that contains your CSV file. This is shown in the S3 service dashboard.

Configure file and import options​

  1. In the Prefix (path) field, enter the folder path inside the S3 bucket where your CSV file is stored. Use forward slashes (/) for separators.

    imports/assets

    If left empty, Atlan searches from the root of the bucket.

  2. In the Object key (filename) field, enter the exact name of the CSV file to import, including the .csv extension. This property points to the specific file inside the prefix or bucket path.

    assets-sept.csv

    For more details, see Object key (filename) reference.

  3. In the Input handling section, select Create full. This creates any missing assets and updates existing ones in a single run. For details and alternatives, see the Input handling reference.

  4. In the Delta handling section, select Full replacement. With this configuration, if you update the file in S3 and rerun the app it automatically calculates which rows have been removed and deletes those assets from Atlan.

    Single connection only

    Note that this Full replacement mode only works when all assets in the file are in the same connection.

  5. In the Options section, select Default, which ignores blank fields, fails on invalid values, and is recommended for most asset imports. For details on using Advanced, see the Assets options reference.

  6. Click Run to start the workflow. After the import completes, review the workflow logs and verify a few sample assets in Atlan to confirm that all enrichments defined in the input CSV were applied as expected.

    This ensures asset metadata is updated consistently and any new assets from the CSV are created in Atlan.

Need help?​

If you run into issues while importing assets, contact Atlan support for assistance.

See also​