1 回答
- 最新
- 投票最多
- 评论最多
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
相关内容
- AWS 官方已更新 2 年前
- AWS 官方已更新 3 年前
- AWS 官方已更新 1 年前
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