CODEWITHSUNDEEP
amazon-ec2amazon-amiec2-ami
jackhao
jackhao

Reputation: 3837

Creating AMI takes so long

I'm creating an AMI for a server with 100G files. It's been like an hour and it's still not finished. (The AMI still says pending) Is there something wrong with it? What should I do?

Upvotes: 108

Views: 74585

Answers (3)

Sunny Adhya
Sunny Adhya

Reputation: 151

It fully depends on the disk size that is attached to the ec2 instance.

You can check the progress of the AMI backup job by checking the EBS snapshot, as it will also take a snapshot of the attached EBS. Once the snapshot is complete, it will show Available(100%), otherwise it will show Unavailable(X%). When it becomes Available(100%), the AMI backup will be completed.

Here are some image of the snapshot progress.

enter image description here

Upvotes: 15

jackhao
jackhao

Reputation: 3837

Just to let other people know, this process could take very, very long. My 100 GB AMI takes like 2.5 hours to create and the progress bar jumps from 0 to 100 directly after that. So don't worry.

Upvotes: 144

mattm
mattm

Reputation: 5949

This answer pertains to a retirement situation where there is potentially a hardware failure for an instance with a EBS root volume. In this situation, AWS recommends creating an AMI of the instance to be retired, and starting a new instance from this AMI. In my situation, the instance was not responding before starting the AMI creation process.

The AMI creation step failed to complete after >8 hours.

I next tried stopping the instance. This also failed to complete in >10 minutes, so I tried force stopping the instance (by issuing the stop command again). The force stop did complete after a few minutes. After the instance was stopped, the AMI creation succeeded in <10 minutes.

This AWS forum message seemed relevant to my case: https://forums.aws.amazon.com/thread.jspa?messageID=372982&#372982

Upvotes: 11

Related Questions