Skip to main content
Version: v3.4 print this page

Overview

Data Management in Amorphic Analytics Studio is designed to be largely automated, ensuring that the underlying infrastructure required for your analytics is managed seamlessly behind the scenes. While the application handles the creation and lifecycle of core data entities, this section outlines how Data Sources (QuickSight Data Sources) and Data Sets (QuickSight Data Sets) function within the ecosystem and how to maintain the necessary permissions via IAM Role updates.

For detailed guidance, see:

Update IAM Role Deprecated​

If a user is registered in Amorphic and has access to new datasets, they can select the Update IAM Role button from the Analytics Studio app Center to synchronize dataset access. This action updates the permissions on the custom IAM Role associated with the registered user to ensure all accessible datasets are correctly reflected in the Analytics Studio application.

Info

Legacy Feature: Previously, this button was used to manually update the custom IAM Role permissions when the application could not automatically reflect dataset access changes. While the button remains visible for backward compatibility, it is now deprecated as the system handles permission synchronization automatically in the current version.

note

IAM role policy and shared domains

When a domain is shared with a Analytics Studio user, Amorphic prefers a single domain/* wildcard in the user's IAM role policy over listing every dataset path, to keep the policy compact.

Because Iceberg datasets require a different IAM statement shape than non-Iceberg datasets, domain/* is only used when every dataset in the domain is of the same type:

  • Domain with all non-Iceberg datasets → policy uses domain/*
  • Domain with all Iceberg datasets → policy uses domain/* (under the Iceberg-shaped statement)
  • Domain with a mix of Iceberg and non-Iceberg datasets → policy falls back to individual domain_name/dataset_name/* entries, since the two statement shapes cannot share a single wildcard

If you want the shorter domain/* form on a domain that already contains an Iceberg dataset, every other dataset in that domain must also be Iceberg type. Mixing types forces the per-dataset expansion.

Next Steps​

  • Learn how to manage your assets - See Asset Management.
  • Familiarize yourself with data sources and datasets - See Assets.