Change Deployment Models
On this page
Overview
You can change an existing App's deployment configuration to deploy it in a new model, region, and/or cloud provider. For example, you might switch your App from a global deployment to a specific local AWS region or switch an App deployed in the Eastern USA from AWS to Azure. For a list of all available options, see Deployment Models & Regions.
To move an existing App, you begin a Deployment Migration that automatically moves your App's data and configuration to the new configuration. The migration process is designed to be as seamless as possible but requires 5 to 30 minutes of downtime. You can monitor the migration status, but no requests will be processed until the migration is complete. For more information, see Deployment Migration Process.
Important
Contact MongoDB Support
We recommend that you contact MongoDB technical support if you are planning to change your deployment model for a production App. To learn how, visit the MongoDB Support portal.
Run a Deployment Migration
You can begin a deployment migration at any time. Only one migration may be in progress at a time for a single App. If you try to start a migration while another is in progress, the new migration does not run and fails with an error.
If you connect to your App from a Realm SDK, you must update your SDK to a version that supports changing deployment models. If your App's SDK version does not support changing deployment models, you'll need to reinstall your app. If you change deployment models before upgrading, the SDK will not be able to connect and requests will fail.
Minimum SDK version:
Realm C++ SDK v0.2.0
Realm Flutter SDK v1.2.0
Realm Kotlin SDK v1.10.0
Realm .NET SDK v11.1.0
Realm Node.js SDK v12.0.0 (pending release)
Realm React Native SDK v12.0.0 (pending release)
Realm Swift SDK v10.40.0
Before You Begin
Before changing deployment models, please note the following:
All logs and drafts will be lost.
Suspended Triggers will restart.
Any existing Private Endpoints will need to be recreated for the new region.
Triggers and Device Sync operations will be paused during the migration.
Important
Deployment Migration is Permanent
Changing your deployment model is not a draft. This change cannot be reversed after it is saved.
You will need the following to modify an App's deployment model in the Atlas UI:
A MongoDB Atlas account with Project Owner permissions. To learn how to sign up for a free account, see Get Started with Atlas.
You will need the following to modify an App's deployment model with the Admin API:
A MongoDB Atlas account with Project Owner permissions. To learn how to sign up for a free account, see Get Started with Atlas.
A MongoDB Atlas Admin API public/private key pair. The API key must have Project Owner permissions to work with App Services Admin API.
Your App's internal ObjectId hex string and the Project ID of the Atlas Project that contains your App. To learn how to find these, see Get App Metadata.
Procedure
Choose a Target Deployment Model and Region
You can migrate an App to any valid deployment configuration.
First, choose to migrate to either a specific LOCAL
region or a GLOBAL deployment distributed around the
world.
If you choose GLOBAL, choose one of the global regions
to host your App's configuration data.
If you choose LOCAL, choose a specific cloud provider
and region to deploy to. For a list of all available
options, see Deployment Models & Regions.
Start the Migration
Once you've specified your desired deployment configuration, click Continue. You should see a confirmation prompt with a checklist. Review and check each item in the list to confirm that you understand the impact of the migration.
Once you've reviewed the checklist, being the migration by clicking Change region.
Clean Up After the Migration
Some features and services will not continue to work after a migration and must be reconfigured. If you use any of these features, follow the clean up steps below to restore functionality:
Feature | Clean Up Steps |
|---|---|
VPC Private Endpoints are region-specific. After migrating to a new region, you must create new VPC Private Endpoints in the new region and update your application to use the new endpoints. You cannot use VPC Private Endpoints if you migrated to a global deployment or to a local region in Azure or GCP. | |
Sending Requests | Once migration is complete, you must send requests
using new URLs, if applicable. |
Choose a Target Deployment Model and Region
You can migrate an App to any valid deployment configuration.
First, choose to migrate to either a specific LOCAL
region or a GLOBAL deployment distributed around the
world.
If you choose GLOBAL, choose one of the global regions
to host your App's configuration data.
{ "deployment_model": "GLOBAL", "provider_region": "aws-us-east-1" }
If you choose LOCAL, choose a specific cloud provider
and region to deploy to. For a list of all available
options, see Deployment Models & Regions.
{ "deployment_model": "LOCAL", "provider_region": "azure-westus" }
Start the Migration
To start a migration, call the Create a Deployment Migration endpoint with the deployment model and region you want to migrate to in the request body.
curl -X PUT \ https://services.cloud.mongodb.com/api/admin/v3.0/groups/{groupId}/apps/{appId}/deployment_migration \ -H 'Content-Type: application/json' \ -H 'Authorization: Bearer <AccessToken>' \ -d '{ "deployment_model": "<DeploymentModel>", "provider_region": "<RegionID>" }'
Monitor the Migration Status
To get the current status of a deployment migration, call the Get a Deployment Migration endpoint.
curl -X GET \ https://services.cloud.mongodb.com/api/admin/v3.0/groups/<groupId>/apps/<appId>/deployment_migration \ -H 'Authorization: Bearer <AccessToken>'
Clean Up After the Migration
Some features and services will not continue to work after a migration and must be reconfigured. If you use any of these features, follow the clean up steps below to restore functionality:
Feature | Clean Up Steps |
|---|---|
VPC Private Endpoints are region-specific. After migrating to a new region, you must create new VPC Private Endpoints in the new region and update your application to use the new endpoints. You cannot use VPC Private Endpoints if you migrated to a global deployment or to a local region in Azure or GCP. | |
Sending Requests | Once migration is complete, you must send requests
using new URLs, if applicable. |
Deployment Migration Process
Deployment migrations move your App's data and configuration to one or more new regions in a series of stages. At each stage, the process migrates a portion of your App to the new model and cleans up any artifacts from the previous model.
A deployment migration moves through the following stages in order:
"started": the migration has been started"downtime": the App is unavailable while the migration is in progress"enabling_event_subscriptions": the App's Triggers and Device Sync translators are being enabled"cleanup": deployment artifacts are being cleaned upThe migration is complete and can be in one of two states:
"successful": the migration completed successfully"failed": the migration failed
Data Affected
The migration process does not affect any application data stored in a MongoDB Atlas cluster.
The migration process migrates the following components of your App:
User accounts
App configuration files
Triggers
API Services
Device Sync translators
The migration process does not migrate the following data:
Application logs
Deployment drafts
Data stored in a MongoDB Atlas cluster