Breaking change in 1.1.3

[envatopoho]

This commit which made it into the 1.1.3 release introduces a dependency in AWS for the ec2:DescribeInstanceStatus permission on the role that is building AMI's.

This broke our pipelines which were previously working on 1.1.2. (We used the docker light image, which wasn't pinned so it automatically put us on the latest release).

Anyway, the new permission it should probably be documented at https://www.packer.io/docs/builders/amazon.html#using-an-iam-task-or-instance-role

[rickard-von-essen]

Thanks for bringing this to our attention.

[mwhooker]

Sorry about that, and thanks for the report! Definitely did not mean to break this in a patch release.

We've generally not done an excellent job of catching changes to the aws permissions we need. I'm going to investigate writing an acceptance test for these which will notify me of any permissions changes in the future.

In the meantime I'll update the docs

[mwhooker]

fixed in cba1a05

[envatopoho]

No worries @mwhooker!

[JasonScottSF]

Does it depend on the specific permission being there?
I'm trying it with this as my IAM policy and it's not working.
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "",
"Resource": ""
}
]
}

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.