Cloud concept · Updated

Data Egress - Data egress is the transfer of data out of a defined boundary, such as a cloud service, network, Region, or cloud provider.

In short

Data egress describes outgoing traffic relative to a specified source; the same transfer is ingress at its destination. Cloud providers often charge for outgoing transfers based on volume, destination, and network path, making data movement an important part of architecture and cost planning.

Cloud Concepts Hub →

5 key aspects of Data Egress

Egress planning combines directional traffic analysis, location-specific pricing, network-path costs, and architectural trade-offs.

01
Direction depends on the boundary

A transfer is outgoing at its source and incoming at its destination. Identify whether the relevant boundary is a service, Availability Zone, Region, or provider before classifying the traffic.

02
Ingress and egress have different pricing

Internet ingress into AWS is generally free of data transfer charges, while internet egress commonly has volume-based charges. Free transfer does not eliminate storage, request, or network processing charges.

03
Location and service determine the rate

Same-Zone, cross-Zone, inter-Region, and internet transfers can follow different pricing rules. Check the exact service pair and path rather than assuming all internal traffic is free.

04
Network processing is a separate cost

Gateways, endpoints, and private connectivity can introduce processing or hourly charges in addition to data transfer charges. Model every billable component along the route.

05
Traffic reduction has architectural trade-offs

Caching, compression, and processing near the data can reduce transferred bytes. Balance these savings against cache behavior, processing overhead, availability, and disaster recovery requirements.

Cloud services for Data Egress

EC2 and S3 commonly produce the data that leaves a cloud environment. CloudFront can serve cacheable content to viewers while reducing repeated origin retrievals, and VPC routing determines whether application traffic passes through chargeable gateways or endpoints. Direct Connect provides another path for transfers to external networks, with separate connection and transfer pricing. Estimate costs across the complete route: source service, geographic boundaries, network intermediaries, and delivery service. Evaluate transfer charges separately from storage, requests, processing, and hourly infrastructure charges.

Amazon EC2Amazon EC2

EC2 workloads can generate internet, cross-Availability-Zone, and inter-Region transfers. Pricing depends on the destination and path; private-IP traffic between EC2 instances in the same Availability Zone is generally free of data transfer charges.

Amazon S3Amazon S3

S3 illustrates the distinction between generally free incoming transfer and potentially chargeable downloads or cross-Region transfers. Transfers between S3 and EC2 in the same Region have no data transfer charge, although requests, storage, and applicable network processing remain separate.

Amazon CloudFrontAmazon CloudFront

CloudFront caches content near viewers, reducing repeated retrievals from an origin. Transfers from AWS origins to CloudFront are not charged for data transfer out, while CloudFront delivery and requests follow the applicable pricing plan.

Amazon VPCAmazon VPC

VPC routing determines whether traffic uses paths such as NAT gateways or VPC endpoints. These components can introduce separate charges; gateway endpoints for S3 can avoid NAT gateway processing for eligible S3 traffic.

AWS Direct ConnectAWS Direct Connect

Direct Connect provides dedicated connectivity between an external network and AWS, with its own data transfer out and connection pricing. It changes the delivery path and pricing model rather than making outbound traffic universally free.

Data Egress exam questions

Real practice exam questions on Data Egress, with the correct answer and its explanation. Answer them with every option in the exam simulator.

CLF-C02

A company uploads daily backups from its on-premises data center over the internet to an Amazon S3 bucket in us-east-1. It then copies the backups to another S3 bucket in eu-west-1 for disaster recovery. The company uses standard S3 endpoints without transfer acceleration. Excluding storage and request charges, which approach correctly estimates AWS data transfer charges under standard pricing?

Show answerCORRECT ANSWER

Budget for outgoing inter-Region transfer from the first bucket, but not the internet upload or incoming transfer to the second bucket.

Data transfer into Amazon S3 from the internet is generally free. Copying objects between these Regions incurs outgoing inter-Region data transfer charges at the source, while incoming transfer at the destination is free. Storage and request charges are separate.

SOA-C03

A company runs an EC2-based processing service in three Availability Zones in one VPC. Each Availability Zone contains processing workers and an identical, fully synchronized set of reference-data servers. Workers read several terabytes of reference data each day by using private IP addresses. A service registry currently returns a randomly selected healthy reference-data server from any of the three Availability Zones.

A billing review shows that worker-to-server traffic accounts for most of the application's cross-Availability Zone data transfer charges. Each Availability Zone has enough reference-data capacity to serve its local workers. The company must retain workers and data replicas in all three Availability Zones and allow workers to use another Availability Zone if their local data servers are unavailable.

Which change will reduce recurring network costs while meeting these requirements?

Show answerCORRECT ANSWER

Update server selection to prefer healthy reference-data servers in the worker's Availability Zone and use servers in other Availability Zones only as a fallback.

Availability Zone-aware server selection keeps normal reads between EC2 instances using private IP addresses in the same Availability Zone, avoiding the associated cross-Availability Zone transfer charges. Existing replicas remain available in all three Availability Zones, and fallback preserves access when local servers are unavailable.

SAP-C03

A pharmaceutical company stores clinical records in Amazon S3 in eu-central-1. Its research team uses an analytics platform hosted outside the European Union. A contractual requirement prohibits clinical records and patient-level query results from leaving eu-central-1. Only outputs produced by a compliance-approved aggregation process may be transferred to the external platform.

The aggregation process suppresses small cohorts and removes patient-level information. Researchers must be able to submit analysis parameters, but must not be able to modify the process or execute arbitrary code with its permissions. Temporary files and failed-job outputs can contain clinical records. Separate controls already prevent cross-Region replication and unauthorized infrastructure changes.

Which architecture meets these requirements?

Show answerCORRECT ANSWER

Run the approved aggregation process in eu-central-1 through a broker that accepts only validated analysis parameters. Keep source data and intermediate outputs in buckets inaccessible to the external platform. Publish only successfully validated aggregate outputs to a separate release bucket that the external platform can read.

This design places the release boundary after the approved aggregation and validation steps. Researchers cannot replace the processing logic or use its permissions for arbitrary execution. Raw records, temporary files, and failed-job outputs remain inaccessible to the external platform, while only approved aggregates can leave the Region.

Practice Data Egress in a full exam

Questions on Data Egress in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is Data Egress

2 min read

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.

Learn Data Egress in lessons

4 short lessons on Data Egress in 4 certification courses.

Open the lessons