Q: I'm experiencing errors and can't deploy from stackery. Everything works right up until I do the final deploy.
A: If your Amazon Web Services (AWS) account was created more than two years ago, you may have an issue with authentication to AWS. Specifically, new requests to create an AWS CloudFormation stack won't find a default configuration for your Virtual Private Cloud (VPC). The solution might be fairly easy, or might require you to get in touch with Amazon to get it resolved. Let's start with the easy fix:
create a default VPC
To create a default VPC using the Amazon VPC console
Open the Amazon VPC console at https://console.aws.amazon.com/vpc/.
In the navigation pane, choose 'Your VPCs'.
check the region drop-down at the top right that you're in the same region you selected for Stackery!
Choose Actions, 'Create Default VPC'.
Choose Create, don't modify the settings, then close the confirmation screen.
you should see a VPC listed as 'default VPC'
I can't create a default VPC (the option is greyed out)
If you can't select the 'create a default VPC' it means one of two things:
- you already have a default VPC (that's the issue with the screenshot below)
- your account is set up to support classic ec2 connections and you'll need to contact AWS support
Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.
In the navigation bar, use the region selector on the top right to select your region.
On the Amazon EC2 console dashboard, look for Supported Platforms under Account Attributes. If there are two values, EC2 and VPC, yours is an old account that's configured to support 'classic' EC2 and won't have a default VPC. If there is one value, VPC, then this configuration isn't the source of your problem.
You'll need to contact AWS support to fix this issue (it's common enough to be in the drop down for support issue)