Skip to main content

Bidirectional metadata sync

Connect docs via MCP

Atlan supports bidirectional metadata synchronization with AWS SageMaker Unified Studio (SMUS). This enables you to update asset metadata in Atlan and have those changes reflected back in SMUS.

Supported assets and metadata​

Bidirectional sync is currently supported for the following SMUS asset types and metadata fields:

Asset typeMetadata field
ProjectsDescription
Business GraphsName, Description
Business Graph TermsName, Description
Published AssetsDescription, README, Business Graph Terms
Published Asset ColumnsDescription

How it works​

When you update a supported metadata field for a supported asset type in the Atlan UI, the Atlan reverse sync pipeline detects the change and propagates it back to AWS SMUS source. This keeps metadata synchronized between Atlan and SMUS without manual intervention.

Atlan-originated Business Graphs and terms: When you create a new Business Graph or term in Atlan (outside the SMUS-mirror Business Graph) and attach the term to a SMUS published asset, Atlan creates the corresponding Business Graph (if missing in SMUS), the term with its description, and the term-asset association in SMUS. The attachment to a SMUS published asset is the trigger—without it, the Atlan-originated Business Graph and term remain in Atlan only.

Limitations​

  • Supported metadata only: Bidirectional sync is limited to the metadata fields listed in the preceding table. Other metadata fields are crawled from SMUS but not synced back.
  • README: README reverse sync is only supported for Published Assets.
  • Atlan-originated content requires asset association: New Atlan-native Business Graphs and terms only sync to SMUS when a term is attached to a SMUS published asset. Orphan terms with no asset association aren't synced.
  • Asset revisions: Updates from Atlan create asset revisions in SMUS. The asset owner must republish the asset in SMUS for the changes to be visible to downstream consumers.

See also​