-
Notifications
You must be signed in to change notification settings - Fork 29
Failed to copy AMI #38
Comments
Its is not intentional |
Atlgho the AMI is public, but the snapshot of the root volume is private |
Any way the snapshot can be made public as well? |
If this can't be fixed, is it possible to disclose which AMI this repo builds on, so we can build our own? |
@syuu1228 can you please help |
I actually cannot reproduce the issue, I able to copy ami-3ceac343 to ami-06a848a0e9177ba2f. |
@syuu1228 I suspect this is because you are using Scylla account. |
Tried again, not possible to copy the AMI using our account. The AMI is public, but the EBS snapshot for the AMI is not public. The snapshot for According to the docs, you can lookup this snapshot in the EC2 console, go to Actions > Modify Permissions and make it public. |
Works for me too, thank you for fixing this! |
It does not seem to be possible to copy
ami-3ceac343
. AWS returned the following error:Is this intentional? When running an AMI in production it is desired to copy the AMI to protect against it (perhaps unintentionally) disappearing. Copying an AMI is also required for EBS root encryption.
The text was updated successfully, but these errors were encountered: