Egress FireNet for GCP
| Parameter | Description | 
|---|---|
Name  | 
A name for the Transit FireNet  | 
Cloud (prepopulated if creating on an existing Transit gateway)  | 
GCP  | 
Account (pre-populated if creating on an existing Transit gateway)  | 
The cloud access account for creating the Transit FireNet Gateway.  | 
VPC/VNet  | 
The VPC or VNet in the selected region in which to create the Spoke Gateway.  | 
Instance Size  | 
Minimum Size: n1-standard_1 The minimum size may vary if HPE is enabled.  | 
High Performance Encryption (HPE)  | 
Turn On HPE for the FireNet deployment, for higher throughputs.  | 
Peer to Spoke Gateways (optional)  | 
Select pre-existing Spoke gateways to connect to the Transit FireNet gateway. Traffic from these Spoke gateways is sent to the Transit FireNet gateway for firewall inspection.  | 
Attach to Subnet  | 
FireNet is launched in this public subnet.  | 
Zone  | 
Zone in which to create the gateway.  | 
Public IP  | 
Allocate a new, static public IP address to the new Transit gateway.  | 
Gateway Load Balancer  | 
This toggle is On and disabled by default. Load balancers are created automatically after FireNet is added to the Transit gateway.  | 
Traffic Inspection  | 
Off by default. This means that only egress traffic will be inspected/routed to a firewall.  | 
Egress  | 
Egress (Internet-bound) traffic inspection is On and disabled by default.  |