AWS Data Transfer Pricing Between Availability Zones
The below listed AWS services include some service-specific pricing related to cross Availability Zones data transfer:
Amazon Elastic Load Balancing:
Data which is being transferred between the following: EC2 instances and Amazon Classic and Application load balancers, with the use of private IPv4 addresses included in the exact same shared region is considered as free of charge.
Amazon RDS + Amazon Neptune:
- Data which gets transferred between differing availability zones for the sake of replication of Multi-AZ deployments is considered as free of charge.
- Regarding data which is being transferred between RDS or Neptune instance outside VPC and EC2 instance inside VPC, you are merely going to be charged for the data which gets transferred into or outside of EC2 instance only.
Amazon Aurora:
AWS Data Transfer Pricing Between Availability Zones – amazon aruora
Data being transferred between differing availability zones for the sake of replication of Multi-AZ deployments is considered as free of charge.
Amazon ElastiCache + Amazon Cloudsearch:
Regarding the data which gets transfer between Cloudsearch or ElastiCache nodes, and EC2 instances found in the exact same region, you will merely be charged for data which is transferred into and outside of the EC2 instances.
Amazon Elasticsearch:
Data which gets transferred between nodes located in the exactly same domain is considered as free of charge.
Amazon MSK:
AWS Data Transfer Pricing Between Availability Zones – amazon MSK
Data which is being transferred between brokers or Apache Zookeepers and brokers is considered as free of charge.
Keep in Mind
The costs of data transfer found and summarized in this document hold an explanation about the way that AWS services and AWS resources are going to charge you for your data transfers which also involve them.
In case an AWS service tends to use other AWS services or AWS resources, then in this case you are definitely going to incur extra added charges for your data transfer costs related to the other taken AWS services and resources.
For Example: In case you choose to configure your S3 bucket for having event notifications to an SQS queue and a Lambda function, then in this case you are going to incur some SQS and Lambda data transfer charges and costs.
For Example: There will not be any data transfer charge for the utilization of AWS Elastic Beanstalk. You will be paying for the data transfer costs related to the additional AWS resources that you later create for the sake of storing and running your chosen application.
Every single data which gets transferred because of the following reasons:
– Failed or timed out requests
– Responses to requests
– File or network traffic overhead
This transfer being made will be counted towards your data transfer usage and charges.
Some of those data transfer examples include:
(1) Any failed or timed out S3 object upload will be incurring some data transfer costs.
(2) Any response to SQS SendMessage API calls will be incurring specific data transfer costs, as well as the TCP re-transmits made at the network communication layer.
All data transfer costs related to the AWS services and resources might be added to the standard processing or routing charges for the data being transferred to them.
For example: In case you have in your possession an EC2 instance being routed to the Internet across a NAT gateway, then in this case you are going to incur region-specific data transfer charge for every single data being transferred through NAT gateway added to the region-specific NAT gateway data processing charge as well.
- You will not be charged at all for any Data Transfer occurring between EC2 and different Web Services located in the exact same region. For example: No charge for data transfers between EC2 US West region and S3 in US West region.
- Data which gets transferred between EC2 instances that are found in differing AZs, while remaining in similar Regions, are going to get charged with the Regional Data Transfer.
- Transferring Data between services, that are found in differing regions, is going to get charged as an Internet Data Transfer on both the destination and source sides.
Any other usage made from different Amazon Web Services is going to be charged for as a separate bill than that of EC2.
Data Transfer through Availability Zone: $0.00 per GB
All the data which is being transferred between EC2 instances that are found in the exactly same AZ through the utilization of a private IP address.
Data Transfer through Public & Elastic IP + Elastic Load Balancing: $0.01 per GB in or out
In the case that you decide to go for communication through utilizing a Public/Elastic IP address, otherwise an Elastic Load Balancer located within the EC2 network, you are going to have to pay your Regional Data Transfer rates, regardless of whether both those instances are found within the same AZ or not.
Data being transferred within an exactly same AZ, it’s possible for you to simply and quickly prevent getting charged for this fee, while ensuring yourself some more efficient network performance, all through the utilization of a private IP anytime it can be done.
Data Transfer through Regions: $0.01 per GB
All the data which is being transferred between EC2 instances that are located in differing AZs while remaining in the exact same AWS region.