You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following resource(s) failed to create: [NATGateway, K8sStack]. . Rollback requested by user.
10:48:46 UTC-0800
CREATE_FAILED
AWS::EC2::NatGateway
NATGateway
10:48:45 UTC-0800
CREATE_FAILED
AWS::CloudFormation::Stack
K8sStack
When I used your AWS QuickStart here - https://aws.amazon.com/quickstart/architecture/heptio-kubernetes/ , I needed to provide my "IAM Role" under Permission on the form. If not, I would be receiving the same error above. I suspect that I need to pass my "IAM Role" to the "aws cloudformation create-stack" CLI command. I will greatly appreciate if you could find out how.
Thanks,
Gilbert
The text was updated successfully, but these errors were encountered:
@gmflau My apologies for taking so long to respond to this issue. To assume a role with the aws command line utility you can follow these instructions.
I was following your instructions on README.md to deploy a K8 cluster. Here is what I passed to the CLI command:
$ aws cloudformation create-stack --region us-west-2 --stack-name Heptio-Kubernetes-GML --template-url https://quickstart-reference.s3.amazonaws.com/heptio/latest/templates/kubernetes-cluster-with-new-vpc.template --parameters ParameterKey=AvailabilityZone,ParameterValue=us-west-2a ParameterKey=KeyName,ParameterValue=dse-keypair-us-west-2 ParameterKey=AdminIngressLocation,ParameterValue=0.0.0.0/0 --capabilities=CAPABILITY_IAM
The error I received below:
When I used your AWS QuickStart here - https://aws.amazon.com/quickstart/architecture/heptio-kubernetes/ , I needed to provide my "IAM Role" under Permission on the form. If not, I would be receiving the same error above. I suspect that I need to pass my "IAM Role" to the "aws cloudformation create-stack" CLI command. I will greatly appreciate if you could find out how.
Thanks,
Gilbert
The text was updated successfully, but these errors were encountered: