Mongo Atlas - Infisical

import DynamicSecretUsernameTemplateParamField from "/snippets/documentation/platform/dynamic-secrets/dynamic-secret-username-template-field.mdx";

The Infisical Mongo Atlas dynamic secret allows you to generate Mongo Atlas Database credentials on demand based on configured role.

Prerequisite

Create a project scoped API Key with the required permission in your Mongo Atlas following the official doc.

<Info>The API Key must have permission to manage users in the project.</Info>

Set up Dynamic Secrets with Mongo Atlas

<Steps> <Step title="Open Secret Overview Dashboard"> Open the Secret Overview dashboard and select the environment in which you would like to add a dynamic secret. </Step> <Step title="Click on the 'Add Dynamic Secret' button"> ![Add Dynamic Secret Button](../../../images/platform/dynamic-secrets/add-dynamic-secret-button.png) </Step> <Step title="Select Mongo Atlas"> ![Dynamic Secret Modal](../../../images/platform/dynamic-secrets/dynamic-secret-atlas-modal.png) </Step> <Step title="Provide the inputs for dynamic secret parameters"> <ParamField path="Secret Name" type="string" required> Name by which you want the secret to be referenced </ParamField>

<ParamField path="Default TTL" type="string" required>
	Default time-to-live for a generated secret (it is possible to modify this value after a secret is generated)
</ParamField>

<ParamField path="Max TTL" type="string" required>
	Maximum time-to-live for a generated secret
</ParamField>

<ParamField path="Admin public key" type="string" required>
			The public key of your generated Atlas API Key. This acts as a username.
</ParamField>

<ParamField path="Admin private key" type="string" required>
			The private key of your generated Atlas API Key. This acts as a password.
</ParamField>

<ParamField path="Group ID" type="number" required>
			Unique 24-hexadecimal digit string that identifies your project. This is same as project id
</ParamField>

<ParamField path="Roles" type="string" required>
   List that provides the pairings of one role with one applicable database.
	 - **Database Name**: Database to which the user is granted access privileges.
	 - **Collection**: Collection on which this role applies.
	 - **Role Name**: Human-readable label that identifies a group of privileges assigned to a database user. This value can either be a built-in role or a custom role.
			- Enum: `atlasAdmin` `backup` `clusterMonitor` `dbAdmin` `dbAdminAnyDatabase` `enableSharding` `read` `readAnyDatabase` `readWrite` `readWriteAnyDatabase` `<a custom role name>`.
</ParamField>

![Dynamic Secret Setup Modal](../../../images/platform/dynamic-secrets/dynamic-secret-modal-atlas.png)

</Step> <Step title="(Optional) Modify Access Scope">

<DynamicSecretUsernameTemplateParamField />
<ParamField path="Customize Scope" type="string">

List that contains clusters, MongoDB Atlas Data Lakes, and MongoDB Atlas Streams Instances that this database user can access. If omitted, MongoDB Cloud grants the database user access to all the clusters, MongoDB Atlas Data Lakes, and MongoDB Atlas Streams Instances in the project.
		- **Label**: Human-readable label that identifies the cluster or MongoDB Atlas Data Lake that this database user can access.
		- **Type**: Category of resource that this database user can access.

</ParamField>

</Step> <Step title="Click 'Submit'"> After submitting the form, you will see a dynamic secret created in the dashboard.

<Note>
	If this step fails, you may have to add the CA certificate.
</Note>

![Dynamic Secret](../../../images/platform/dynamic-secrets/dynamic-secret.png)

</Step> <Step title="Generate dynamic secrets"> Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials. To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item. Alternatively, you can initiate the creation of a new lease by selecting 'New Lease' from the dynamic secret lease list section.

![Dynamic Secret](/images/platform/dynamic-secrets/dynamic-secret-generate.png)
![Dynamic Secret](/images/platform/dynamic-secrets/dynamic-secret-lease-empty.png)

When generating these secrets, it's important to specify a Time-to-Live (TTL) duration. This will dictate how long the credentials are valid for.

![Provision Lease](/images/platform/dynamic-secrets/provision-lease.png)

<Tip>
	Ensure that the TTL for the lease falls within the maximum TTL defined when configuring the dynamic secret.
</Tip>


Once you click the `Submit` button, a new secret lease will be generated and the credentials for it will be shown to you.

![Provision Lease](/images/platform/dynamic-secrets/lease-values.png)

</Step> </Steps>

Audit or Revoke Leases

Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard. This will allow you to see the expiration time of the lease or delete a lease before it's set time to live.

Renew Leases

To extend the life of the generated dynamic secret leases past its initial time to live, simply click on the Renew button as illustrated below.

<Warning> Lease renewals cannot exceed the maximum TTL set when configuring the dynamic secret </Warning>