- Mais recentes
- Mais votos
- Mais comentários
Comment from this may help:
Ah, one more thing - if all instances are in the same AZ, are you using Public IP on them to communicate with each other? Like... Elastic IP for example? If so - this will be the cause of generated DataTransfer-Regional-Bytes charges. If instances are in the same AZ, and they communicate within private network (using private IPs) within AWS, then that traffic is free. However, if with the same setup you use public IP, you will likely see data transfer charges associated with those resources. Check one more thing in Cost Explorer - when you filter DataTransfer-Regional-Bytes usage type, can you group by API Operation? If the results will show the operations like "public IP" or something similar, then my last theory is right :)
https://repost.aws/questions/QU4KuYNjlWTqWrqMA1RyWLYQ/unexpected-datatransfer-regional-bytes-traffic
I have only one instance on EC2 that communicates with S3. But the volume of data is above the previous ones, is there a way to limit this daily transfer so as not to exceed 10 million?