metadata-ingestion/docs/sources/mongodb/mongodb_post.md
Use the Important Capabilities table above as the source of truth for supported features and whether additional configuration is required.
By default the connector emits all ingested entities under the mongodb data platform, regardless of whether the underlying source is MongoDB or AWS DocumentDB. To surface DocumentDB clusters as their own platform, set platform: documentdb. This requires hostingEnvironment to be AWS_DOCUMENTDB; any other hosting environment is rejected at config validation time.
Switching an existing recipe to platform: documentdb will generate new documentdb dataset and container URNs; the previously emitted mongodb URNs will need to be cleaned up via stateful ingestion (if enabled) or manually soft-deleted.
Module behavior is constrained by source APIs, permissions, and metadata exposed by the platform. Refer to capability notes for unsupported or conditional features.
If ingestion fails, validate credentials, permissions, connectivity, and scope filters first. Then review ingestion logs for source-specific errors and adjust configuration accordingly.