Error waiting for AMI: Failed with ResourceNotReady, but AMI is available on AWS console

[Amedee Van Gasse]

I have this log:

==> amazon-ebs: Creating AMI ... from instance i-01f6...

    amazon-ebs: AMI: ami-0226...

==> amazon-ebs: Waiting for AMI to become ready...

==> amazon-ebs: Error waiting for AMI: Failed with ResourceNotReady error, which can have a variety of causes. For help troubleshooting, check our docs: https://www.packer.io/docs/builders/amazon.html#resourcenotready-error

==> amazon-ebs: original error: ResourceNotReady: exceeded wait attempts

==> amazon-ebs: Provisioning step had errors: Running the cleanup provisioner, if present...

==> amazon-ebs: Terminating the source AWS instance...

==> amazon-ebs: Cleaning up any extra volumes...

==> amazon-ebs: No volumes to clean up, skipping

==> amazon-ebs: Deleting temporary keypair...

Build 'amazon-ebs' errored after 50 minutes 34 seconds: Error waiting for AMI: Failed with ResourceNotReady error, which can have a variety of causes. For help troubleshooting, check our docs: https://www.packer.io/docs/builders/amazon.html#resourcenotready-error

original error: ResourceNotReady: exceeded wait attempts

==> Wait completed after 50 minutes 34 seconds

==> Some builds didn't complete successfully and had errors:

--> amazon-ebs: Error waiting for AMI: Failed with ResourceNotReady error, which can have a variety of causes. For help troubleshooting, check our docs: https://www.packer.io/docs/builders/amazon.html#resourcenotready-error

original error: ResourceNotReady: exceeded wait attempts

==> Builds finished but no artifacts were created.

However, when I go to the AWS console, I do see an AMI ami-0226... with status available.