Customize the CloudFormation Template
The following table provides guidance for required and optional parameters in the CloudFormation template provided. If you choose not to customize the provided template, use this table to guide you in creating the Commander environment.
You can also specify these parameters on the command line, rather than customizing the template itself.
The ID of an existing Virtual Private Cloud (VPC) where Commander will be deployed.
The specified VPC must have a minimum of three subnets.
The ID of the subnet to assign to the EC2 instance that will host Commander.
The subnet must reside in the specified VPC.
The name of an instance profile or a reference to an AWS::IAM::InstanceProfile resource. Specifies the IAM Instance Profile that the EC2 instance should run as.
Defaults to blank
Comma-separated list of IDs of the subnets to assign to the RDS instance that will host the Commander database.
Must specify a minimum of two IDs; must not specify the subnet used for the EC2 instance.
Name of an existing EC2 key pair to enable console access to the EC2 instance.
Username for connecting to the SQL Server database on the RDS instance.
Must begin with a letter, contain only alphanumeric characters and be between 1 and 16 characters in length. You must encrypt the credentials used to access the Commander database.
Password for connecting to the SQL Server database on the RDS instance.
Must begin with a letter, contain only alphanumeric characters and be between 8 and 30 characters in length. You must encrypt the credentials used to access the Commander database.
The size of the database (GB).
Defaults to 200. For guidance, see Hardware requirements below.
The instance type for the RDS instance that will host the Commander database.
Defaults to db.m4.large. For guidance, see Hardware Requirements below.
The instance type for the Amazon EC2 instance where Commander will be installed.
Defaults to t2.large. For guidance, see Hardware Requirements below.
The CIDR block (IP address range) that can be used to access the EC2 instance over HTTPS.
Defaults to 0.0.0.0/0
Amazon Resource Name (ARN) for an SSL certificate used by the load balancer.
To use an HTTPS listener, an SSL certificate is required. The load balancer uses this certificate to terminate the connection and then decrypt requests from clients before sending them to the targets.
A production deployment for static environments of fewer than 500 instances, supporting fewer than 10 concurrent users, with infrequent reporting.
EC2 Instance: t3.large
RDS Instance: db.m5.large
A production deployment for dynamic environments with fewer than 1500 instances, supporting fewer than 30 concurrent users, with frequent reporting.
EC2 Instance: m5.xlarge
RDS Instance: db.m5.xlarge
A production deployment for dynamic environments with more than 1500 instances, supporting more than 30 concurrent users, with frequent reporting.
EC2 Instance: m5.xlarge
RDS Instance: db.m5.2xlarge
The pricing models for the required EC2 and RDS instances are available here:
Snow Software does not own the third party trademarks, software, products, or tools (collectively, the “Third Party Products”) referenced herein. Third Party Product updates, including user interface updates, may not be reflected in this content.