AWSApplicationMigrationMGHAccess

OperatorService roleActivePermissions reviewedShow on map Compare

Summary

This policy allows AWS Application Migration Service (MGN) to send meta-data about the progress of servers being migrated using MGN to AWS Migration Hub (MGH). MGN automatically creates an IAM role with this policy attached, and assumes this role. We do not recommend that you attach this policy to your IAM users or roles.

Permissions imported from the AWS Managed Policy Reference Guide; other sections pending editorial review.

Identity

ARN: arn:aws:iam::aws:policy/service-role/AWSApplicationMigrationMGHAccess
Default version: v1
Created: 2021-04-07
Last edited: 2021-04-07
Services: mgh

Control-plane actions (7)

By access level: 1 Read, 6 Write.

Control-plane actions by service
Service	Granted	Access levels and limits	Granted by
Migration Hub	7 of 46	1 Read, 6 Write; 0 restricted, 0 conditional	mgh:AssociateCreatedArtifact, mgh:CreateProgressUpdateStream, mgh:DisassociateCreatedArtifact, mgh:GetHomeRegion, mgh:ImportMigrationTask, mgh:NotifyMigrationTaskState, mgh:PutResourceAttributes

Migration Hub: 7 actions

mgh:AssociateCreatedArtifact (Write)
mgh:CreateProgressUpdateStream (Write)
mgh:DisassociateCreatedArtifact (Write)
mgh:GetHomeRegion (Read)
mgh:ImportMigrationTask (Write)
mgh:NotifyMigrationTaskState (Write)
mgh:PutResourceAttributes (Write)

Data-plane actions (0)

By access level: none.

This policy grants no actions in this plane.

Excluded and conditional actions

No patterns are excluded by NotAction or Deny statements.

Resource scope and attachment

Resource scope across granted actions: all-resources.

Can be attached: Yes, to users, groups and roles.

Why this tier

Grants 6 write, tagging or permissions-management actions, short of full control of any service.

Guidance

Pending editorial review. The permission data on this page comes straight from AWS; this section will be filled in once a reviewed guide exists.

Same service

Same domain

Frequently asked questions

Pending editorial review. The permission data on this page comes straight from AWS; this section will be filled in once a reviewed guide exists.

Policy JSON

Download policy.json

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "mgh:AssociateCreatedArtifact",
        "mgh:CreateProgressUpdateStream",
        "mgh:DisassociateCreatedArtifact",
        "mgh:GetHomeRegion",
        "mgh:ImportMigrationTask",
        "mgh:NotifyMigrationTaskState",
        "mgh:PutResourceAttributes"
      ],
      "Resource": "*"
    }
  ]
}

Version history

Current version v1, edited by AWS on 2021-04-07. Version history is recorded from 2026-11-11. Earlier versions are in the IAM console under Policy versions.

Attach snippets

AWS CLI

aws iam attach-role-policy --role-name ROLE_NAME --policy-arn arn:aws:iam::aws:policy/service-role/AWSApplicationMigrationMGHAccess
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/service-role/AWSApplicationMigrationMGHAccess
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/service-role/AWSApplicationMigrationMGHAccess

CloudFormation

Resources:
  ExampleRole:
    Type: AWS::IAM::Role
    Properties:
      AssumeRolePolicyDocument: {}  # replace with your trust policy
      ManagedPolicyArns:
        - arn:aws:iam::aws:policy/service-role/AWSApplicationMigrationMGHAccess

Terraform

resource "aws_iam_role_policy_attachment" "service_role_awsapplicationmigrationmghaccess" {
  role       = aws_iam_role.example.name
  policy_arn = "arn:aws:iam::aws:policy/service-role/AWSApplicationMigrationMGHAccess"
}

CDK (TypeScript)

role.addManagedPolicy(
  iam.ManagedPolicy.fromAwsManagedPolicyName("service-role/AWSApplicationMigrationMGHAccess"),
);

Sources

Pending editorial review. No editorial sources are listed yet.