Transit VPC Architecture (AWS)
Separate mesh traffic into a dedicated Transit VPC to keep AWS multi-AZ firewall deployments highly available during AZ failover.
| Where Can I Use This? | What Do I Need? |
| Prisma AIRS - AI Runtime Security |
- Prisma AIRS license
- Access to Strata Cloud Manager
- A cloud account (AWS) connected to Strata Cloud Manager
|
Overview
The Transit VPC Architecture update enhances High Availability (HA) and fault tolerance for multi-Availability Zone (AZ) deployments running East-West inter-region or cross-VPC mesh traffic. By decoupling mesh network traffic into a dedicated Transit VPC, this feature resolves cross-AZ routing limitations and ensures seamless AZ failover.
The mesh interfaces are separated from the main Security VPC into a dedicated Transit VPC. Transit Gateway (TGW) Appliance Mode is leveraged to maintain symmetric traffic inspection within each AZ. This eliminates the single preferred endpoint dependency, allowing traffic to route through any available AZ seamlessly in case of an outage. The architecture is fully compatible with legacy single-VPC firewalls and cross-cloud environments.
Configure Transit VPC CIDR
When you deploy firewall infrastructure in the Strata Cloud Manager portal, you see the following VPC CIDR deployment options:
- Cloud Mesh: Enable the toggle switch to activate cross-region mesh connectivity.
- Transit VPC CIDR: Enter a non-overlapping CIDR block (for example, 10.108.0.0/16) specifically assigned to the Transit VPC.
- Security VPC CIDR: Specify the primary CIDR block (for example, 10.106.0.0/16) for management, public, and private/trust interfaces.
- Ensure that both the Security VPC CIDR and Transit VPC CIDR do not overlap with existing spoke VPCs or corporate networks.
- Prisma AIRS creates the Transit Gateway attachment associated with the Transit VPC and enables Appliance Mode on it by default. You don't need to enable it.
- Prisma AIRS doesn't support a managed migration or upgrade from the legacy Security VPC architecture to the Transit VPC Architecture. To move an existing deployment to the Transit VPC Architecture, tear down the deployment and redeploy it.
Supported Deployment Models
| Scenario | Supported Topology | Customer Impact |
| New Deployments | Transit VPC Architecture | Full AZ redundancy and fault tolerance enabled by default. |
| Legacy AWS Deployments | Legacy Security VPC | Remains fully supported; no mandatory migration required. Moving to the Transit VPC Architecture requires teardown and redeployment. |
| Hybrid Mesh Interop | Transit VPC ↔ Legacy VPC | Supported. Enables incremental upgrades without downtime. |
| Cross-Cloud (AWS to Azure or GCP) | AWS Transit VPC ↔ Azure VNet or GCP VPC | Supported. Maintains full inter-cloud security inspection. |