AWS Application Migration Service

Name: AWS Application Migration Service API
Brand: AWS Application Migration Service
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputehmac61 EndpointsREST

For Agents

Migrate physical, virtual, and cloud servers to AWS through continuous block-level replication and orchestrated EC2 cutovers.

Quickstart

Get started with AWS Application Migration Service in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"launch a migration test"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with AWS Application Migration Service API.

Group source servers into applications and waves to coordinate migration phases

Configure replication templates that govern staging area, instance, and bandwidth defaults

Configure launch templates that define target EC2 instance type, OS licensing, and disks

Run test launches to validate cutover readiness without disrupting production

GET STARTED

Start building with AWS Application Migration Service API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for AWS Application Migration Service, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for AWS Application Migration Service, keeping it validated and agent-ready. Application Migration Service (MGN) is AWS's lift-and-shift service for migrating physical, virtual, and cloud servers onto AWS. It continuously replicates source servers into a staging area in the target AWS account and orchestrates cutover and test launches into EC2. The control plane covers source servers, applications, waves, replication and launch configuration templates, post-launch actions, and lifecycle state changes such as archive, disconnect, and finalize cutover.

Use Cases

Patterns agents use AWS Application Migration Service API for, with concrete tasks.

★ Datacenter Lift-and-Shift Migration

Enterprises moving from on-premises VMware to AWS install MGN agents on each source server, group servers into applications and waves, and run continuous block-level replication into a staging area. Test launches validate that each wave boots and connects to dependencies; cutover launches replace those test instances with the final production EC2 instances. The whole flow is orchestrated through this control-plane API.

Call CreateApplication for app 'erp-prod', associate the relevant source servers via AssociateSourceServers, then run StartTest for that application and inspect the resulting Job

Cross-Cloud Migration Programs

Organisations migrating from another cloud (Azure, GCP) to AWS use MGN's continuous replication so source workloads remain online while replication catches up. ListSourceServers and ListApplications surface the current migration state to dashboards; UpdateLaunchConfiguration tunes target EC2 sizing per server before cutover; PostLaunchActions run SSM documents post-boot to install agents or rotate credentials.

Call UpdateLaunchConfiguration on a source server with TargetInstanceTypeRightSizingMethod=BASIC and Licensing.OsByol=true, then call StartTest to validate the new sizing

Migration Wave Orchestration

Programme managers coordinate hundreds of servers per migration window using waves: a wave groups applications that cut over together. CreateWave, AssociateApplications, and StartCutover sequenced over weeks let large programmes prove out test launches, hold a freeze period, and finally cut all wave members over in a coordinated event. ArchiveWave records the completed wave for audit.

Call CreateWave for 'Q3-wave-3', associate the applications in scope via AssociateApplications, then call StartCutover for the wave once test launches are signed off

AI Agent Migration Operations

Migration agents call MGN through Jentic to track replication lag across servers, trigger scheduled test launches, and flag servers stuck in REPLICATION_FAILED state. Jentic isolates the AWS access keys and exposes the source server, application, wave, and template operations as discoverable tools, so the agent can answer 'launch a test for tonight's wave' without learning the AWS SDK.

Search Jentic for 'launch a migration test', load the StartTest operation, and execute it with the array of SourceServerIDs in tonight's wave

Key Endpoints

61 endpoints — jentic publishes the only available openapi specification for aws application migration service, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/CreateApplication

Create a logical application grouping source servers

POST

/CreateWave

Create a migration wave

POST

/AssociateSourceServers

Associate source servers with an application

POST

/CreateLaunchConfigurationTemplate

Create a launch configuration template

POST

/CreateReplicationConfigurationTemplate

Create a replication configuration template

POST

/ChangeServerLifeCycleState

Change a source server's lifecycle state

POST

/ArchiveApplication

Archive an application after migration

POST

/CreateApplication

Create a logical application grouping source servers

POST

/CreateWave

Create a migration wave

POST

/AssociateSourceServers

Associate source servers with an application

POST

/CreateLaunchConfigurationTemplate

Create a launch configuration template

POST

/CreateReplicationConfigurationTemplate

Create a replication configuration template

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS keys are stored encrypted in the Jentic vault. Each MGN call is signed with Signature Version 4 server-side, and IAM scoping restricts the agent to the migration actions you grant — replication, jobs, and templates — without granting broader EC2 control.

Intent-based discovery

Agents search by intent (e.g. 'launch a migration test' or 'list replicating source servers') and Jentic returns matching MGN operations such as StartTest, StartCutover, and DescribeSourceServers with their input schemas.

Time to first call

Direct integration: 2-5 days for IAM, replication and launch templates, and orchestration scripting. Through Jentic: under an hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

AWS Migration Hub

Migration Hub aggregates progress across migration tools including MGN

Use Migration Hub when the agent needs a portfolio-wide view of migrations across MGN, DMS, and partner tools; use MGN for the underlying replication and cutover.

Complementary

AWS Database Migration Service

DMS migrates databases while MGN migrates servers

Use DMS for relational and NoSQL database migration; use MGN for full server lift-and-shift. They commonly run side-by-side on the same workload.

Complementary

AWS Migration Hub Config

Migration Hub Config manages the home region MGN reports into

Use Migration Hub Config first to set the migration home region; MGN and other migration tools then aggregate status into that region.

FAQs

Specific to using AWS Application Migration Service API through Jentic.

Why is there no official OpenAPI spec for AWS Application Migration Service?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS Application Migration Service via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the AWS Application Migration Service API use?

MGN uses AWS Signature Version 4 (HMAC) with an access key ID and secret access key scoped via IAM. The service also assumes IAM roles to provision target EC2 instances and manage the staging area. Through Jentic, the access keys live in the encrypted vault and Jentic signs each request server-side.

Can I orchestrate test launches and cutovers with the AWS MGN API?

Yes. POST /StartTest creates test EC2 instances from replicated volumes for a list of SourceServerIDs without affecting production. POST /StartCutover finalises the migration by launching production instances. POST /FinalizeCutover archives the source server entries once you confirm the cutover is successful.

What are the rate limits for the AWS MGN API?

AWS does not document hard request-per-second limits for MGN control-plane operations in this spec. Soft quotas apply to source servers, applications, waves, and concurrent jobs per region — see the AWS service quotas console for current values.

How do I run a test launch through Jentic?

Search Jentic for 'launch a migration test' to surface POST /StartTest. Load the schema with the Jentic SDK (pip install jentic), execute it with the array of SourceServerIDs in scope and any tags you want applied to the resulting Job, and poll DescribeJobs to track per-server progress.

Is AWS Application Migration Service free?

MGN itself is free for the first 90 days per source server, after which a per-server-per-hour charge applies during replication. EC2, EBS, and data transfer charges for the staging area and cutover instances are billed separately at standard rates.