Data Egress

Data egress means data leaving a defined boundary. That boundary might be a virtual machine, a virtual network, a cloud Region, or the provider's infrastructure. Downloading an object from cloud storage to a laptop is egress from the cloud. Copying a dataset between Regions is egress from the source Region and ingress into the destination Region, even though the data stays with the same provider.

Cloud pricing distinguishes data transfer from compute, storage, and request charges. A workload can have inexpensive storage but substantial transfer costs if users repeatedly download large files. To estimate cost, identify the source, destination, direction, volume, and route of each transfer. Apply the relevant rates and allowances, then account separately for services that process or transport the traffic.

On AWS, data transfer into AWS from the internet is generally free of data transfer charges. This does not make the entire upload operation free: storage requests, acceleration features, or network processing can still incur charges. Data transfer from AWS to the internet is commonly charged by volume, subject to applicable free allowances, pricing tiers, and service-specific exceptions. Do not assume incoming and outgoing traffic have symmetrical prices.

Transfers between AWS Regions generally incur inter-Region data transfer charges, commonly associated with the source service's outgoing transfer. Replication can also create destination storage, request, and service-specific charges. For example, copying backups to another Region improves geographic resilience but introduces recurring transfer and storage costs. Check the pricing rules for the participating services rather than applying an internet egress rate to every outbound transfer.

Within one Region, charges depend on the services, Availability Zones, and connection path. Traffic between EC2 instances using private IP addresses in the same Availability Zone is generally free of data transfer charges. EC2 traffic across Availability Zones generally incurs regional data transfer charges, potentially on both sides, although service-specific exceptions exist. Some same-Region service paths, such as transfers between Amazon S3 and EC2, have no data transfer charge. Being in the same Region, VPC, or account does not by itself guarantee free traffic.

The network route can add costs independently of egress pricing. An EC2 instance downloading internet data through a NAT gateway may incur NAT gateway processing charges even when incoming data transfer is free. Similarly, a private connection does not automatically eliminate transfer charges. Separate per-gigabyte transfer charges from gateway processing, endpoint, connection, and hourly charges when estimating the complete path.

Engineers reduce unnecessary egress by compressing responses, filtering data before export, caching frequently requested objects, and placing compute near its datasets. A content delivery network can reduce repeated origin transfers, but it has its own delivery and request pricing. Locality can reduce cost and latency, while multi-AZ and multi-Region designs can improve availability and recovery. Optimize avoidable traffic without sacrificing required resilience, and validate estimates against billing data and actual traffic patterns.