hashicorp / hashicorp/packer-plugin-amazon

Exceeded max wait time for ImageAvailable waiter

Open
#642 4 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Go
Stars
91
Forks
141
Avg merge
2d 18h
Merged PRs (30d)
3

Description

#### Overview of the Issue

Since upgrading to 1.8.0, waiting for AMI to become ready times out too early. We have `AWS_MAX_ATTEMPTS=240` so I would expect 60 minutes. I have seen as short as 7 minutes.

This step regularly takes up to 30 minutes so every image build is timing out and failing. Downgrading to 1.7.1 and the issue is no longer present, Waiting for AMI to become ready took around 27 minutes.

#### Reproduction Steps

This is happening on every single one of our images when using v1.8.0 so I'm not sure what the minimal reproduction would be. We have Windows Server 2022 and Amazon Linux images.

### Plugin and Packer version

Packer v1.14.3
Plugin v1.8.0

### Simplified Packer Buildfile

n/a

### Operating system and Environment details

Running in Github Actions on standard runner Ubuntu 24.04.3
[Image release](https://github.com/actions/runner-images/releases/tag/ubuntu24%2F20251208.163)

### Log Fragments and crash.log files

```
Tue, 16 Dec 2025 11:30:11 GMT ==> ops-win-2022.amazon-ebs.ops: Waiting for AMI to become ready...
Tue, 16 Dec 2025 11:37:56 GMT ==> ops-win-2022.amazon-ebs.ops: Error waiting for AMI: exceeded max wait time for ImageAvailable waiter
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.