Update from Deployments with Managed and Unmanaged Agents
- OAuth 2.0 authentication for programmatic access to Cloud Manager is available as a Preview feature.
- The feature and the corresponding documentation might change at any time during the Preview period. To use OAuth 2.0 authentication, create a service account to use in your requests to the Cloud Manager Public API.
You have a project with automated MongoDB deployments that may include both Automation-managed and standalone Backup and Monitoring Agents. You want to update to the MongoDB Agent.
To update to the MongoDB Agent, use the following procedures:
For any standalone legacy Agents:
For those hosts where Automation manages Monitoring/Backup Agents:
Note
Review the Prerequisites First
If you want to start or continue using Automation to manage your MongoDB deployments, please review the MongoDB Agent Prerequisites before updating to the MongoDB Agent.
Procedure
Update automated hosts to MongoDB Agent.
If your project has hosts that use Automation, you can update the Agents on those hosts to the MongoDB Agent.
Click Update All.
Wait until all hosts show Updated.
Click Next.
All authentication SCRAM, LDAP, and Kerberos credentials from
legacy Agents are retained after the update. All .pem
key
files are retained as well.
The legacy Automation Agent credentials become the MongoDB Agent credentials used for Automation. These credentials should not need modification. However, if you need to modify them:
In MongoDB Cloud Manager, go to the Deployment page for your project.
If it is not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
If it's not already displayed, select your desired project from the Projects menu in the navigation bar.
If the Deployment page is not already displayed, click Deployment in the sidebar.
The Deployment page displays.
Go to the Security page.
Click the Security tab for your deployment.
Edit the settings.
Click Settings.
Click Edit Settings.
Next Steps
After the MongoDB Agent update completes: