Fix IAM trust policy example to reference EC2 instance role #319
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The trust policy example for the target IAM role incorrectly referenced itself as the principal instead of the EC2 instance role that should be allowed to assume it.
Changes:
pbm-ec2-instance-rolefor the EC2 instance role andpbm-target-rolefor the target rolePrincipal.AWSfield to reference the EC2 instance role ARN instead of the target role ARNBefore:
{ "Principal": { "AWS": "arn:aws:iam::EC2_ACCOUNT_ID:role/pbm-target-role" }, "Action": "sts:AssumeRole" }After:
{ "Principal": { "AWS": "arn:aws:iam::EC2_ACCOUNT_ID:role/pbm-ec2-instance-role" }, "Action": "sts:AssumeRole" }This corrects the IAM role assumption pattern: the trust policy attached to the target role must specify which role (the EC2 instance role) is permitted to assume it.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.