Data flows and security pathways
This page documents the individual network flows between your environment and the Akka platform. Each flow lists the data carried, its source and destination, the connectivity used, and how it is authenticated. "Your …" denotes a resource in your own environment.
Connectivity terms used below:
-
Peering: a private network path between your environment and the Akka region.
-
Firewall, Federation Plane allowlisted: a customer-initiated outbound flow to the Federation Plane over the internet, from an allowlisted egress path.
-
Akka NAT gateway: a region-initiated egress flow. Akka can work with you to route these through your firewall instead.
-
Pre-authorized IP ranges: Federation-Plane-to-region flows over the internet. A private-connectivity option is available.
Private connectivity by cloud
Under BYOC, Akka can set up a private-connectivity option per cloud to keep region-to-internal traffic off the public internet: Transit Gateway on AWS, VPC Peering on GCP, and VNet Peering with Azure Firewall on Azure. See the BYOC on AWS, BYOC on Azure, and BYOC on GCP pages.