- 최신
- 최다 투표
- 가장 많은 댓글
The ModifyVpcPeeringConnectionOptions operation cannot be performed with the permissions available in the lab environment. This is a limitation of the Cloud Quest lab, not a bug.
The hint may be misleading; this operation is not required.
Correct solution: Edit the route table. All that is required for inter-VPC communication is adding a route to the route table.
The error message you're encountering indicates that the IAM role you're using in the Cloud Quest lab environment doesn't have the necessary permissions to perform the ec2:ModifyVpcPeeringConnectionOptions action. This is a permissions issue rather than a configuration problem with your VPC peering connection.
Since this is occurring within an AWS Cloud Quest lab environment, here are some steps to try:
-
Check the lab instructions carefully - The challenge may not actually require you to modify the VPC peering connection options. Instead, you might need to add routes to the route tables associated with each VPC to enable communication between them. The peering connection itself may already be properly configured.
-
Focus on route table modifications - For VPCs to communicate through a peering connection, you typically need to add routes in the route tables of both VPCs that point to each other's CIDR blocks via the peering connection. Try adding the appropriate routes rather than modifying the peering connection options.
-
Verify you're using the correct lab resources - Make sure you're working with the resources that the lab intends you to modify. Some resources in lab environments are intentionally restricted to guide you toward the correct solution path.
-
Reset or restart the lab - If you believe you should have these permissions and the lab isn't working as intended, try resetting the lab environment through the Cloud Quest interface. This will give you a fresh start with the proper permissions configured.
If the issue persists after trying these approaches, you may need to reach out to AWS Training and Certification support through the AWS Training portal, as they manage the Cloud Quest lab environments and can investigate permission issues specific to the training platform.
Sources
Troubleshoot explicit deny errors in AWS Organizations | AWS re:Post
Troubleshoot Amazon VPC CNI add-on issues for Amazon EKS | AWS re:Post
Thank you - I worked this out during my session and have now completed my recertification.