We have added two new options to our “Copy AMI Images” action:
Copy Image Permissions
Launch permissions can be added to an AMI image to allow other AWS accounts to launch EC2 instances from your AMI image. If you have added launch permissions to your AMI, then those permissions can be copied to the target AMI image with this option enabled.
Copy Snapshot Permissions
Similarly, “Create Volume” permissions can be added to EBS snapshots that allow other AWS accounts access to EBS snapshots. If you have added permissions to the EBS snapshots associated with your AMI images, then those permissions can be copied to the target snapshots.
Allows the Target AMI to be Launchable
If your source AMI image is launchable by other AWS accounts, then enabling the “Copy Image Permissions” option will allow the target AMI image to be launchable by the same AWS accounts. Otherwise, the target AMI image will be private.
Allows the Target AMI to be Copied
If your source AMI image has appropriate permissions set on the AMI image and the associated EBS snapshots to permit the AMI to be copied to another AWS account, then enabling the “Copy Snapshot Permissions” option will allow the target AMI image to be copyable by the same AWS accounts.
These new options do not need to be enabled to allow Skeddly to copy your AMI images between AWS accounts. When this is happening, Skeddly will automatically add and remove permissions as needed.
Only when the original AMI image has permissions previously added that should be preserved on the target AMI image will the new options be applicable.
Sign-up for our 30 day free trial or sign-in to your Skeddly account and use Skeddly to implement your disaster recovery strategy today.