1 Answer
- Newest
- Most votes
- Most comments
0
Check to see if you have a policy or SCP in place that requires the Instance Metadata Service V2 that is being applied to the account you are running in. This can prevent starting any instances that are not at IMDS v2. This shows as a permissions error and is really hard to link back to a policy issue/change. https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html
Relevant content
- asked a year ago
- asked 10 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Thanks! I found it was a restriction with the SCP that did not allow starting instances on subnets with public IPs. Changing it to private ones solved the issue