Multi-cluster support for Cosmos DB - Atlan Release Notes

🎉 What's new

Atlan now supports crawling metadata from multiple MongoDB clusters for the Azure Cosmos DB for MongoDB connector! If you have multiple clusters across different subscriptions within the same Azure account, Atlan will now be able to connect and crawl metadata from both RU- and vCore-based deployments.

✨ Let's dig deeper

You can set up the Cosmos DB connector to:

Connect and crawl metadata from multiple clusters — Atlan now supports connecting to and crawling metadata from multiple MongoDB clusters.
- For each of your vCore-based clusters, you will need to authenticate with a connection string. Atlan will not be able to automatically discover and catalog metadata from your vCore-based clusters. You will need to manually register or remove connection strings as you create or remove clusters at source.
- For each of your RU-based clusters, Atlan supports service principal authentication, and requires you to assign the Cosmos DB Account Reader Role for each cluster to the service principal. As new RU-based clusters are added, they will automatically show up in Atlan. If removed, the cluster metadata will also be removed from Atlan.
Crawl metadata from a mix of vCore- and RU-based clusters — if your Microsoft Azure Cosmos DB deployment includes a mix of vCore- and RU-based accounts, you can configure both to fetch metadata. You can then use the vCore and RU deployment option to crawl your Microsoft Azure Cosmos DB assets.
Discover accounts — this newly supported asset type represents each cluster running across all subscriptions. This can help your group your databases by clusters. To view supported attributes, refer to our documentation. Note that most MongoDB cluster-level attributes are unavailable for vCore-based deployments. This is because these clusters do not support service principal authentication.

👏 Give it a shot

Ready to explore the revamped Cosmos DB connector? Integrate Cosmos DB and Atlan to explore more: