
ℹ️ Information: The Share AMI feature allows you to make your custom Amazon Machine Images available to other AWS accounts. This is useful when you need to distribute standardized environments to development teams or deploy workloads across multiple AWS accounts while maintaining consistent configurations and data.
⚠️ Warning: This lab requires at least 2 AWS accounts. If you only have one account, you can create a new account through AWS Organizations and use the Switch Role feature to access it. For detailed instructions, refer to the lab: Set Up Single Sign-On (AWS IAM Identity Center) for Organizations.
Sign in to your second AWS account:
Copy your 12-digit AWS account ID:

Return to your primary AWS account:
ami and select AMIs
Access the AMI sharing settings:

⚠️ Warning: If the AMI is in the Pending state, any attempt to update its permissions will fail. You must wait until the AMI status changes to Available before making updates.
Set the AMI visibility:
Add the target account:

Enter the account details:

Confirm your settings:
Sign in to your second AWS account:
ami and select AMIsChange the AMI filter:
Select the appropriate view:
Confirm access to the shared AMI:

🔒 Security Note: When sharing encrypted AMIs, you must also share the AWS KMS customer managed key (CMK) used for encryption. By default, EBS volumes and snapshots are encrypted using KMS. To learn more about managing encryption keys, refer to the lab: AWS Key Management Service.
💡 Pro Tip: Each AMI has a sharing quota of 1000 entities, which can include organizations, organizational units, and individual AWS accounts. Plan your sharing strategy accordingly for large-scale deployments.
Congratulations! You have successfully shared an AMI with another AWS account. You can now proceed to launch EC2 instances from this shared AMI in your second account.