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
Problem
More detailed instructions for deploying to AWS with explanations on what the commands do would be appreciated. I am currently getting the following error for step 1 of EKS setup:
AWS::EKS::Cluster/ControlPlane: CREATE_FAILED – "Resource handler returned message: \"Cannot create cluster 'papercups' because us-east-1e, the targeted availability zone, does not currently have sufficient capacity to support the cluster. Retry and choose from these availability zones: us-east-1a, us-east-1b, us-east-1c, us-east-1d, us-east-1f (Service: Eks, Status Code: 400, Request ID: eb7ba2e3-1d62-4102-9c39-0695bcecf3aa, Extended Request ID: null)\"
When I try to choose different availability zones, I get the following error:
Error: --vpc-private-subnets/--vpc-public-subnets and --zones cannot be used at the same time
As far as I know, if I remove the --vpc-private-subnets command then the rest of the setup will not work correctly.
Solution
I would like some more detailed instructions on deploying to AWS with some information on what each command does.
Describe alternatives you've considered
I've tried googling the error message but none of the results seem to match what I am looking for.
Problem
More detailed instructions for deploying to AWS with explanations on what the commands do would be appreciated. I am currently getting the following error for step 1 of EKS setup:
AWS::EKS::Cluster/ControlPlane: CREATE_FAILED – "Resource handler returned message: \"Cannot create cluster 'papercups' because us-east-1e, the targeted availability zone, does not currently have sufficient capacity to support the cluster. Retry and choose from these availability zones: us-east-1a, us-east-1b, us-east-1c, us-east-1d, us-east-1f (Service: Eks, Status Code: 400, Request ID: eb7ba2e3-1d62-4102-9c39-0695bcecf3aa, Extended Request ID: null)\"
When I try to choose different availability zones, I get the following error:
Error: --vpc-private-subnets/--vpc-public-subnets and --zones cannot be used at the same time
As far as I know, if I remove the --vpc-private-subnets command then the rest of the setup will not work correctly.
Solution
I would like some more detailed instructions on deploying to AWS with some information on what each command does.
Describe alternatives you've considered
I've tried googling the error message but none of the results seem to match what I am looking for.
Testing
Run step 1 of EKS Setup:
eksctl create cluster \ --name papercups \ --version=1.19 \ --enable-ssm \ --vpc-public-subnets=$(aws rds describe-db-subnet-groups --db-subnet-group-name "default" --query 'DBSubnetGroups[-1].Subnets[*].SubnetIdentifier' --output text | perl -pe 's/\h/,/g')
The text was updated successfully, but these errors were encountered: