1-Click CloudFormation Deploy

Deploy the Cloud Spectra Gateway

Pick a tier, configure every stack parameter on this one clean page -- with a live architecture diagram that updates as you go -- then launch straight into the AWS CloudFormation console in the region you choose, settings pre-filled.

1

Subscribe to the AMI

Subscribe to your Cloud Spectra tier on the AWS Marketplace (one-time, per account).

2

Configure below

Choose a tier and region, then fill the grouped form. Sensible defaults are pre-set.

3

Launch to AWS

Click Launch in CloudFormation. You land on the AWS quick-create page, pre-filled.

4

Create stack

Review on AWS, check the IAM box, click Create stack. Live in ~10 minutes.

Configure your deployment

Parameters are grouped by function. Green groups are the essentials; purple are optional features (off by default). Hover any ?Help tooltips like this explain each parameter, including its underlying CloudFormation parameter name. for details. You always finish and submit on the AWS console.

Essentialstier, target, network, placement, compute
Marketplace version used to resolve the AMI. "latest" resolves to the newest image at instance launch.
EC2 on-demand1x
On-demand premium~$83/mo
Annual (-25%)~$62/mo
Cloud Spectra premium per instance (est., c6in.large, US East on-demand) on top of your EC2 cost. See full pricing ->
The matching AMI for your tier and version is selected automatically per region.
Becomes part of every resource name. Use a different name per stack in the same account/region.
VPC mode ?Create a brand-new VPC, or wire Cloud Spectra into an existing one. With "Existing", Cloud Spectra adds its own subnets, route tables and ENIs to the VPC you select. newOrExistingVpc

CloudFormation always requires a VPC reference. In create-new mode you can leave "Existing VPC ID" blank here -- on the AWS console page, just pick any VPC from the dropdown. It is ignored, and a brand-new VPC is created from the CIDR below.

A /16 gives plenty of room for per-AZ subnets. Must not overlap VPCs you intend to peer with.
For production, restrict this to your admin network rather than 0.0.0.0/0.
Restrict to specific spoke VPC CIDRs to tighten the transit security group.
1024-65535. Keep 9443 unless you have a specific reason to change it.
💡

Each enabled AZ gets its own subnet, ENI, route table and Auto Scaling Group -- an independent gateway. Add zones for high availability. Subnet CIDR accepts an explicit block (10.0.0.0/28), a prefix length (24) for auto-selection, or empty for an auto /28.

Availability Zone 1 * ?AZ for slot 1 (required). A bare letter like "a" or a full AZ name like "us-east-1a". availabilityZone1 / subnet1CidrBlock
Left: zone letter. Right: subnet CIDR (optional).
Availability Zone 2 ?AZ for slot 2. Leave empty (--) to disable this zone. availabilityZone2 / subnet2CidrBlock
Availability Zone 3 ?AZ for slot 3. Leave empty (--) to disable this zone. availabilityZone3 / subnet3CidrBlock
Availability Zone 4 ?AZ for slot 4. Leave empty (--) to disable this zone. availabilityZone4 / subnet4CidrBlock
Availability Zone 5 ?AZ for slot 5. Leave empty (--) to disable this zone. availabilityZone5 / subnet5CidrBlock
Availability Zone 6 ?AZ for slot 6. Leave empty (--) to disable this zone. availabilityZone6 / subnet6CidrBlock
Blank = auto-resolved from your Marketplace subscription (Tier + Version). Set an ami-xxxx to override.
Start small; resize later from the dashboard.
Min / Desired / Max per AZ ?Auto Scaling Group sizing per AZ. The stack supports 0 or 1 instance per AZ at deploy time; multi-instance-per-AZ is configured afterward from the Cloud Spectra dashboard or API. MinSize / DesiredCapacity / MaxSize
Min / Desired / Max (each 0-1). For multiple instances per AZ, scale from the dashboard after deploy.
Warm pool ?Pre-initialized standby instances per ASG for fast scale-out (~25s vs ~90s cold launch). Disabled by default. When enabled, choose how many standby instances and whether they are Stopped (cheapest) or Running (fastest). warmPoolDisabled / warmPoolMinSize / warmPoolState
Disabled / Enabled · min standby (0-10) · Stopped or Running.
Features (optional)off by default -- expand to enable
💡

When a port-forwarding rule is submitted with externalPort=0, the gateway auto-allocates a free port from this range and opens it in the security group -- ideal for WireGuard tunnels dialed in from on-prem sites behind NAT.

Leave empty to keep the dial-in range closed until you add sources later.
Leave empty to skip firewall sync at deploy time.
Ingress HTTP / HTTPS ports ?Ports for the K8s ingress controller HTTP and HTTPS traffic. kubernetesIngressHttpPort / kubernetesIngressHttpsPort
Left: HTTP. Right: HTTPS.
Operations & Advancedupgrades, admin, developer, marketplace
Leave empty to pin to the AMI's built-in version.
Keep the default unless you self-host the release bucket.
🔑

For your security, the admin password is never placed in a launch URL. Leave it blank to auto-generate a strong initial password (retrievable via SSH), or set one in the masked adminPassword field on the AWS console page. Plaintext rules: 8-128 chars with upper, lower, digit and special; or paste a bcrypt hash.

Production deployments must leave this empty.
📦

These default to Cloud Spectra's public releases bucket. AWS Marketplace sets them automatically at publish time. Change only if self-hosting the Lambda artifacts.

Ready to launch
Opens the AWS CloudFormation quick-create page with your settings pre-filled. You review and click Create stack on AWS.
Show the generated launch URL

Template: latest/cloudspectra_gateway_asg.yaml. You must be signed in to the AWS console for the chosen region. The final Create-stack step (including the IAM capabilities acknowledgement) always happens on AWS -- this page never touches your account.