pkgre.blogg.se - Amazon images

Deregister the AMI on the source account if you don't need to run any instances from it.

It's a best practice to use this copy to avoid complications after the source account deregisters the originally shared AMI.

Create a custom AMI from the target account instance.

Note: For Amazon Virtual Private Cloud (Amazon VPC) instances, the private IP address is different in the new account unless specifically set during launch. To import a key pair from a previous account, see Import your own public key to Amazon EC2.

Launch a new instance from the shared AMI on the target account.

From the target account, find the AMI using the EC2 console or the AWS CLI.

For instructions, see one of the following: User Guide for Windows Instances - Share an AMI with specific AWS accounts User Guide for Linux Instances - Share an AMI with specific AWS accounts Note: If you receive errors when running AWS CLI commands, make sure that you’re using the most recent version of the AWS CLI.

Share the AMI with the target account using either the Amazon EC2 console or the AWS Command Line Interface (AWS CLI).

This data won't be on the instance store volumes of the instances that you launch from the AMI. For instructions, see one of the following: Create a Windows AMI from a running instance Create a Linux AMI from an instance Note: Data stored on instance store volumes isn't preserved in AMIs. Be sure that the AMI doesn't have a static IP configuration, as this can result in connectivity issues. Be sure to include all required EBS data volumes in the AMI.

Create a custom AMI from the instance that you want to use as the source account.

Note: The following steps apply only to instances with unencrypted Amazon Elastic Block Store (Amazon EBS) volumes. Instead, you can manually migrate an EC2 image from one AWS account to another. It's not possible to transfer existing instances or AMIs between AWS accounts.