How to integrate MongoDB with Apono to manage JIT access to Clusters, Databases and Collections
A document database used to build highly available and scalable internet applications
Self Service Access - Empower your developers to gain self-servable access to databases using Slack.
Automated Approval Workflows - Create approval workflows for specific sensitive databases/collections.
Restricted Third Party Access - Grant third-party (customer or vendor) time-based access to specific databases with MFA verification.
Review Access - View a detailed access audit of who was granted access to which databases with what permission level and why.
- Apono requires a project owner in the cluster's project so it can provision.
Creating an API Key with Project Owner role
Run the following Atlas CLI command:
Make sure to replace #PROJECT_ID
with the project-id that contains the cluster you want to integrate
Copy the Public and Private API Keys in the response
Storing the secret in your environment secret store.
Open Integrations Catalog
Click on MongoDB integration card
Select the Connector, this is the Connector which is installed in the same AWS account as the MongoDB Atlas instance
Type in a friendly name for the integration
Fill in the Project Id and Cluster Name
AWS Use the respective secret which was stored in AWS Secret Manager previously in this guide.
Select the secret from the Secret Manager according to the appropriate AWS account and region
Click Create
You've successfully integrated Apono with your MongoDB. You should now see the new integration in your Connected Integrations.
You can now use this integration in your existing or new Access Flow. Check this guide out for more information on creating access flows.