This section contains answers to questions about post-launch actions.
Topics
What operating systems
does the post-launch actions framework support?
Verify that your operating systems are supported by AWS Systems Manager.
What version of AWS Systems Manager Agent will be installed on my instance?
AWS Application Migration Service uses the latest AWS Systems Manager Agent version available in your instance's region.
Why is the AWS Systems Manager Agent not executing my post launch actions?
-
By default, AWS Systems Manager doesn't have permission to perform actions on your instances. Grant access by using an AWS Identity and Access Management (IAM) instance profile. You can create an instance profile for AWS Systems Manager by attaching one or more IAM policies that define the necessary permissions to a new role or to a role you already created. You can use the managed policy
AmazonSSMManagedInstanceCorewhich allows an instance to use AWS Systems Manager service core functionality or create a custom policy. For more information, see Create an IAM instance profile for AWS Systems Manager. -
The instances you connect to must also allow HTTPS (port 443) outbound traffic to the following endpoints:
ec2messages.<REGION>.amazonaws.com ssm.<REGION>.amazonaws.com ssmmessages.<REGION>.amazonaws.com.rproxy.goskope.comYou can connect to the required endpoints by using interface endpoints. For more information, see Creating VPC endpoints for AWS Systems Manager.
Alternatively, you can use public IP addresses for communication between your instances and the internet.
Another reason might be that the managed instance has limited available CPU or memory resources. Although your instance might otherwise be functional, if the instance doesn't have enough available resources, you can't establish a session. For more information, see Troubleshooting an unreachable instance.
