​
Overview

Stacks are fundamental to the network-level isolation of your resources. Each Stack is hosted in a specific region and is comprised of environments. Aptible offers two types of Stacks: Shared Stacks (non-isolated) and Dedicated Stacks (isolated). Resources in different Stacks can only connect with each other with a network integration. For example: Databases and Internal Endpoints deployed in a given Stack are not accessible from Apps deployed in other Stacks.
The underlying virtualized infrastructure (EC2 instances, private network, etc.), which provides network-level isolation of resources.

​
Shared Stacks (Non-Isolated)

Stacks shared across many customers are called Shared Stacks. Use Shared Stacks for development, testing, and staging Environments.
You can not host sensitive or regulated data with shared stacks.

​
Dedicated Stacks (Isolated)

Dedicated Stacks are only available on Production and Enterprise plans.
Dedicated stacks are built for production environments, are dedicated to a single customer, and provide four significant benefits:
  • Tenancy - Dedicated stacks are isolated from other Aptible customers, and you can also use multiple Dedicated Stacks to architect the isolation you require within your organization.
  • Availability - Aptible’s Service Level Agreement applies only to Environments hosted on a Dedicated stack.
  • Regulatory - Aptible will sign a HIPAA Business Associate Agreement (BAA) to cover information processing in Environments hosted on a Dedicated stack.
  • Connectivity - Integrations, such as VPN and VPC Peering connections, are available only to Dedicated stacks.
  • Security - Dedicated stacks automatically come with a suite of security features, including encryption, DDoS protection, host hardening, intrusion detection, and vulnerability scanning — alleviating the need to worry about security best practices.

​
Supported Regions

RegionAvailable on Shared StacksAvailable on Dedicated Stacks
us-east-1 / US East (N. Virginia)✔️✔️
us-east-2 / US East (Ohio)✔️
us-west-1 / US West (N. California)✔️✔️
us-west-2 / US West (Oregon)✔️
eu-central-1 / Europe (Frankfurt)✔️✔️
sa-east-1 / South America (São Paulo)✔️
eu-west-1 / Europe (Ireland)✔️
eu-west-2 / Europe (London)✔️
eu-west-3 / Europe (Paris)✔️
ca-central-1 / Canada (Central)✔️✔️
ap-south-1 / Asia Pacific (Mumbai)✔️✔️
ap-southeast-2 / Asia Pacific (Sydney)✔️✔️
ap-northeast-1 / Asia Pacific (Tokyo)✔️
ap-southeast-1 / Asia Pacific (Singapore)✔️
A Stack’s Region will affect the latency of customer connections based on proximity. For VPC Peering, deploy the Aptible Stack in the same region as the AWS VPC for both latency and DNS concerns.

​
FAQ