How can I force Global-DataTransfer-Regional-Bytes to be Global-DataTransfer-Out-Bytes traffic?

Question

Hello everyone! Can I configure my server instance so that when it produces intra-region traffic (Global-DataTransfer-Regional-Bytes), it is counted as public internet traffic (Global-DataTransfer-Out-Bytes)? I'm curious if AWS supports such a configuration. It seems technically feasible to me, but if this is a pricing trap set by AWS, such an option might deliberately not be provided. My need for this arises because, in the free tier, the quota for Global-DataTransfer-Regional-Bytes is only 1GB, whereas the quota for Global-DataTransfer-Out-Bytes is 100GB, making the latter more cost-effective. I tried searching for an answer to this question, but most of the information I found discusses identifying the sources of Global-DataTransfer-Regional-Bytes to avoid producing this traffic. However, in my case, I am aware of the source of the traffic but still need to produce it. Therefore, I need to find a way to convert it to Global-DataTransfer-Out-Bytes. Technically, I could achieve this by setting up a public internet proxy server, but this is obviously not the ideal solution. Hence, I am wondering if AWS allows for such a conversion configuration.

Accepted Answer

You can't force traffic to route a particular way once it leaves your VPC. It will take the shortest/best path available to and from the destination. And in this case, the traffic will stay on the AWS private network as per the [VPC FAQ](https://aws.amazon.com/vpc/faqs/):

> **Does traffic go over the internet when two instances communicate using public IP addresses, or when instances communicate with a public AWS service endpoint?**
>
> No. When using public IP addresses, all communication between instances and services hosted in AWS use AWS's private network. Packets that originate from the AWS network with a destination on the AWS network stay on the AWS global network, except traffic to or from AWS China Regions.

So even though public IP addresses are being used, the traffic stays on the AWS network because that is the shortest (and best) path between AWS regions.

Answer

Well, based on the above answer, it seems that the traffic quota settings of the AWS Free Tier are not user-friendly. A limit of 1GB on intra-region traffic almost seems like a deliberate attempt to prevent users from utilizing intra-region traffic, while public internet traffic, on the other hand, has an adequate quota.

Answer

its good to follow

How can I force Global-DataTransfer-Regional-Bytes to be Global-DataTransfer-Out-Bytes traffic?

Relevant content