MongoDB Atlas Portal

MongoDB Atlas is a fully-managed cloud database service that automates database administration tasks for MongoDB. It supports multiple cloud providers and offers advanced features like real-time analytics and security controls. Atlas simplifies database management, allowing organizations to focus on application development with a scalable, flexible database solution that adapts to changing needs and workloads.

Through this integration, Apono helps you securely manage access to your MongoDB Atlas UI Organizations and Projects.

---

Prerequisites

---

Create an API key

You must create an API key with the Organization User role for the Apono connector.

Follow these steps to create the API key:

1. In the Atlas CLI, create the API key. The following command will return the public and private API keys in the response.

   ⚠️

   Be sure to replace <ORGANIZATION_ID> with the organization ID of the MongoDB Atlas UI to integrate.

   Shell

   atlas organizations apiKeys create --role ORG_OWNER --desc apono_connector --orgId <ORGANIZATION_ID>
   

2. Using the keys from the previous step, create a secret for the MongoDB Atlas UI instance:

   • AWS
   • Azure
   • GCP
   • Kubernetes
   
   
   Shell

   // Replace #PUBLIC_KEY and #PRIVATE_KEY with the actual key values.
   
   "public_key": "#PUBLIC_KEY"
   "private_key": "#PRIVATE_KEY"
   

You can now integrate your MongoDB Atlas UI resources .

---

Integrate MongoDB Atlas UI

Follow these steps to complete the integration:

1. On the Catalog tab, click Mongo Atlas Portal. The Connect Integration page appears.
2. Under Discovery, click one or both resource types to sync with Apono.

   ℹ️

   Apono automatically discovers and syncs all the instances in the environment. After syncing, you can manage Access Flows to these resources.

3. Click Next. The Apono connector section expands.
4. From the dropdown menu, select a connector.

   💡

   If the desired connector is not listed, click + Add new connector and follow the instructions for creating a connector (AWS, Azure, GCP, Kubernetes).

5. Click Next. The Integration Config section expands.
6. Define the Integration Config settings.

   Setting	Description
   Integration Name	Unique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow
   Organization ID	ID of the organization of the MongoDB Atlas UI instance to connect

7. Click Next. The Secret Store section expands.
8. Associate the secret or credentials:
   • AWS
   • Azure
   • GCP
   • Kubernetes
   • Apono
9. Click Next. The Get more with Apono section expands.
10. Define the Get more with Apono settings.

    Setting	Description
    Credential Rotation	(Optional) Number of days after which the database credentials must be rotated
    Custom Access Details	(Optional) Instructions explaining how to access this integration's resources Upon accessing an integration, a message with these instructions will be displayed to end users in the User Portal. The message may include up to 400 characters. To view the message as it appears to end users, click Preview. NOTE: You can also add the custom_access_details parameter to the apono_integration schema using Terraform. For more information, learn how to integrate with Apono in the Terraform Registry.
    Integration Owner	(Optional) Fallback approver if no resource owner is found Follow these steps to define one or several integration owners: From the Attribute dropdown menu, select User or Group under the relevant identity provider (IdP) platform. From the Value dropdown menu, select one or multiple users or groups. NOTE: When Resource Owner is defined, an Integration Owner must be defined.
    Resource Owner	(Optional) Group or role responsible for managing access approvals or rejections for the resource Follow these steps to define one or several resource owners: Enter a Key name. This value is the name of the tag created in your cloud environment. From the Attribute dropdown menu, select an attribute under the IdP platform to which the key name is associated. Apono will use the value associated with the key (tag) to identify the resource owner. When you update the membership of the group or role in your IdP platform, this change is also reflected in Apono. NOTE: When this setting is defined, an Integration Owner must also be defined.

11. Click Confirm.

Now that you have completed this integration, you can create access flows that grant permission to your MongoDB Atlas UI Organizations and Projects.