3 Answers
- Newest
- Most votes
- Most comments
1
From document[1] , agc account active
creates vpc when you not specified --vpc option
So you may have to add permission about creating VPC like AmazonVPCFullAccess
0
Thanks _takahash. This indeed helps. But now I get:
Failed resources:
2023-06-01T16:31:27Z ✘ Agc-Core | 4:28:40 PM | CREATE_FAILED | AWS::EC2::InternetGateway | Vpc/IGW (VpcIGWD7BA715C) 1 validation error detected: Value 'You are not authorized to perform this operation. Encoded authorization failure message
2023-06-01T16:31:27Z ✘ Agc-Core | 4:28:40 PM | CREATE_FAILED | AWS::EC2::VPC | Vpc (Vpc8378EB38) 1 validation error detected: Value 'You are not authorized to perform this operation. Encoded authorization failure message
2023-06-01T16:31:27Z ✘ ❌ Agc-Core failed: Error: The stack named Agc-Core failed creation, it may need to be manually deleted from the AWS console: ROLLBACK_COMPLETE: 1 validation error detected: Value 'You are not authorized to perform this operation.
2023-06-01T16:31:27Z ✘ ❌ Deployment failed: Error: Stack Deployments Failed: Error: The stack named Agc-Core failed creation, it may need to be manually deleted from the AWS console: ROLLBACK_COMPLETE: 1 validation error detected: Value 'You are not authorized to perform this operation.
answered a year ago
0
Ensure the IAM role you're using with AGC has the necessary permissions to create resources in AWS. In this case, it appears that your IAM role might lack the ec2:CreateVpc and ec2:CreateInternetGateway permissions, which are required to create a VPC and an Internet Gateway in AWS. If your AWS account has restrictions, or if you're using an organizational account with Service Control Policies (SCPs), ensure that these restrictions or policies don't prevent you from creating VPCs and Internet Gateways.
Relevant content
- asked 2 months ago
- asked 2 years ago
- AWS OFFICIALUpdated 8 days ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated a month ago