AWS Application Migration Service service quota limits
The following are the AWS MGN service quota limits:
| Name | Default | Description |
|---|---|---|
|
Concurrent jobs in progress |
Each supported AWS Region: 20 |
Launching a test or cutover instance, or a cleanup action is considered a "job". This parameter is the maximum number of Jobs that can be run concurrently. Jobs that are "completed" are not counted against this quota. |
|
Max active source servers |
Each supported AWS Region: 150 |
The maximum number of servers that can be actively replicating at any time. For larger migrations, contact Support. Learn more about requesting a quota increase. |
|
Max non-archived source servers |
Each supported AWS Region: 4,000 |
This parameter is used for agentless migrations. This is the max number of servers that can be managed by MGN, in non-archived state. This includes the servers that are actively replicating, as well as any servers whose replication has not yet started. The number of actively replicating servers is controlled by the parameter "Max active source servers". For larger migrations, contact Support. Learn more about requesting a quota increase |
| Max source servers in a single job |
Each supported AWS Region: 200 |
Launching a test or cutover instance, or a cleanup action is considered a "Job". If you select multiple servers, and perform one of these actions, they are grouped into a single Job. This is the maximum number of servers that can be grouped into a single Job. |
|
Max source servers in all jobs |
Each supported AWS Region: 200 |
Launching a test or cutover instance, or a cleanup action is considered a "job". This is the maximum total number of servers that can be configured in all active jobs. Jobs that are "completed" are not counted against this quota. |
| Max total source servers per AWS account |
Each supported AWS Region: 50,000 |
This parameter is the maximum total servers, both active and archived, that can be migrated in a single account in each AWS Region. Servers that are deleted, are not counted against this quota. |
|
Max concurrent jobs per source server |
Each supported AWS Region: 1 |
Launching a test or cutover instance, or a cleanup action is considered a "job". This is the maximum number of active jobs, that can be configured per server. Jobs that are "completed" are not counted against this quota. |
|
Max actions per source server |
Each supported AWS Region: 100 |
This parameter is the maximum amount of custom post-migration actions that can be associated with a specific source server. |
|
Max actions per account template |
Each supported AWS Region: 100 |
This parameter is the maximum amount of custom post-migration actions that can be associated with an account template. |
|
Max source servers per application |
Each supported AWS Region: 200 |
This parameter is the maximum total servers, both active and archived, that can be added to an application. |
|
Max active applications |
Each supported AWS Region: 200 |
This parameter is the maximum number of applications that are in an active status. |
|
Max archived applications |
Each supported AWS Region: 10,000 |
This parameter is the maximum number of applications that are in an archived status. |
|
Max applications per wave |
Each supported AWS Region: 1000 |
This parameter is the maximum total applications, both active and archived, that can be added to a wave. |
|
Max active waves |
Each supported AWS Region: 200 |
This parameter is the maximum number of waves that are in an active status. |
|
Max archived waves |
Each supported AWS Region: 10,000 |
This parameter is the maximum number of waves that are in an archived status. |
|
Global View - Max Managed Accounts |
5,000 |
This is the maximum number of member accounts that can be managed by a single management account. |
You can learn about the AWS MGN service limits in the AWS General Reference
