AWS Secrets Manager expands support to MongoDB Atlas and Confluent Cloud

AWS Secrets Manager has announced the extension of its managed external secrets support to include MongoDB Atlas and Confluent Cloud. This development allows users to centrally manage and automatically rotate secrets for these external services directly through AWS Secrets Manager, eliminating the need for custom Lambda rotation functions.

The integration with MongoDB Atlas offers support for two types of secrets: database user secrets, which utilize username-password authentication via SCRAM, and service account secrets, which employ OAuth client ID and secret. For Confluent Cloud, the integration facilitates API key rotation for service accounts, with capabilities for both cluster-scoped and cloud resource management keys. These integrations come with automatic rotation enabled by default, thereby reducing the necessity for hardcoded secrets and minimizing the operational workload associated with managing secrets across diverse platforms.

With this feature, AWS Secrets Manager fully manages the secret rotation using rotation logic provided by its partners, without deploying any Lambda functions in the user’s account. For instance, organizations using a data pipeline that incorporates MongoDB Atlas and Confluent Kafka can now leverage AWS Secrets Manager to centralize secret management, enabling automatic rotation of database and streaming platform secrets without the need to alter application code or maintain separate rotation logic for each service.

The new integrations with MongoDB Atlas and Confluent Cloud for managed external secrets are available in all AWS Regions that support managed external secrets. These additions join the existing integrations with other services such as Salesforce, Snowflake, and BigID. For further information, users are encouraged to consult the AWS Secrets Manager managed external secrets documentation.