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
when running reverb-cli cdk:deploy it fails with this error:
Resource handler returned message: "Minimum 2 AZs are needed to be covered by subnets but found only 1 AZs, requested subnet 'subnet-0a56c47446004f5fb' is in an unsupported availability zone 'us-east-1b' (Service: AmazonRDS; Status Code: 400; Error Code: InvalidParameterCombination; Request ID: e27fb7b0-4106-4b96-a058-57205dbd7268; Proxy: null)" (RequestToken: ae9bc5c0-d3ac-f473-27a2-b6751334511e, HandlerErrorCode: GeneralServiceException)
What do I need to fix?
The text was updated successfully, but these errors were encountered:
The error likely comes from the availability zone us-east-1b being out of t3 small instances(for RDS). I just deployed and my RDS instance was placed in us-east-1b. Likely you were just unlucky and if you try again at a later time it will work.
If you don't want to wait to try again, there are a couple of things you could do.
Deploy to a different region by changing your default region in the aws cli: aws configure set region <region_name>
Set the context file for the CDK manually to other availability zones I havent tested this
So, to do 2, first you need to find where the CDK project was downloaded on your machine. On linux it should be in ~/.config/reverb-cli/reverb-infrastructure-master, while on windows it would be in %LOCALAPPDATA%/reverb-cli/reverb-infrastructure-master. Next you need to create a file cdk.context.json in this directory.
You will need your account id for this file, so run aws sts get-caller-identity --query 'Account' --output text which will output your account id. Next fill cdk.context.json like so:
Where <AccountId> is your id and the availability zones are from the region (us-east-1 has zones a through f), technically you could include all of them, just remove the one that the error stated wasn't correct.
Finally, before you try to deploy again, you might want to check CloudFormation on the AWS console as while the reverb-app should be deleted since deployment failed, cloudformation can hang and have part of the stack still up and you might need to force a deletion via the console. Usually doesn't happen, but good to check either way.
I hope this fixes your issue, please keep us updated.
when running reverb-cli cdk:deploy it fails with this error:
Resource handler returned message: "Minimum 2 AZs are needed to be covered by subnets but found only 1 AZs, requested subnet 'subnet-0a56c47446004f5fb' is in an unsupported availability zone 'us-east-1b' (Service: AmazonRDS; Status Code: 400; Error Code: InvalidParameterCombination; Request ID: e27fb7b0-4106-4b96-a058-57205dbd7268; Proxy: null)" (RequestToken: ae9bc5c0-d3ac-f473-27a2-b6751334511e, HandlerErrorCode: GeneralServiceException)
What do I need to fix?
The text was updated successfully, but these errors were encountered: