Stack creation failures
The two most common stack creation failures customers see are a result of either bad parameters specified within the CloudFormation template or deploying in a non-supported region.
- Virtual Private Cloud (VPC) ID
- Subnet A ID
- Subnet B ID
- Console Security Group CIDR Block
- Email
Ensure that the subnets you select for Subnet A and Subnet B are unique (to each other) and both are a part of the VPC you selected.
Rules have been added to ensure you select these values correctly.
Ensure the CIDR range is a value that you can access. Specify a network range that represents the specific network you will be accessing from (i.e. your work network) or open it up to everyone with a value of
0.0.0.0/0.Using
0.0.0.0/0 will make it accessible to the outside world. SSL based authentication is in place, but you still may want to consider whether "wide open" is the strategy you want to take.Antivirus for Amazon S3 uses many native AWS services. Not all AWS services are supported in all AWS regions. Cognito is a service leveraged for authentication and user management, but it is not supported in all regions.
Below you will find a list of supported regions. Please deploy the console to one of these regions.
- us-east-1 (N. Virginia)
- us-east-2 (Ohio)
- us-west-1 (California)
- us-west-2 (Oregon)
- ap-south-1 (Mumbai)
- ap-northeast-2 (Seoul)
- ap-southeast-1 (Singapore)
- ap-southeast-2 (Sydney)
- ap-northeast-1 (Tokyo)
- ca-central-1 (Canada)
- eu-central-1 (Frankfurt)
- eu-west-1 (Ireland)
- eu-west-2 (London)
- eu-west-3 (Paris)
- eu-north-1 (Stockholm)
- me-south-1 (Bahrain)
- sa-east-1 (Sao Paulo)
- GovCloud (West) AWS regions
Missing regions in this list are due to Amazon Cognito not being supported in those regions.
The scanning agent will run in any region that supports Amazon ECS Fargate.
Last modified 3mo ago