Bidirectional metadata sync
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 type | Metadata field |
|---|---|
| Projects | Description |
| Published Assets | Description, README, Glossary Terms |
| Published Asset Columns | Description |
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.
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.
- Supported assets only: Only Projects, Published Assets, and Published Asset Columns support reverse sync.
- README and Glossary Terms: README and Glossary Terms reverse sync is only supported for Published Assets.
See also
- Set up AWS SageMaker Unified Studio: Configure AWS authentication for SMUS integration
- Crawl AWS SageMaker Unified Studio: Configure and run the crawler to extract metadata from SMUS