3 回答
- 最新
- 投票最多
- 评论最多
1
Hi,
Yes, you will incur costs as per https://aws.amazon.com/ec2/pricing/on-demand/#Data_Transfer
Data transferred "in" to and "out" from Amazon EC2, Amazon RDS, Amazon Redshift, Amazon
DynamoDB Accelerator (DAX), and Amazon ElastiCache instances, Elastic Network Interfaces
or VPC Peering connections across Availability Zones in the same AWS Region is charged at
$0.01/GB in each direction.
IPv4: Data transferred "in" to and "out" from public or Elastic IPv4 address is charged at
$0.01/GB in each direction.
IPv6: Data transferred "in" to and "out" from an IPv6 address in a different VPC is charged
at $0.01/GB in each direction.
Note: in you case, both ends will pay the fee in or out for a transfer.
Best,
Didier
0
If they were in the same AZ, then it's free. But you mention it is a 3-rd party. So there will be 2 different VPCs. How are you going to make the connection without VPC peering or Transit Gateway even they are in the same AZ?
The same way I communicate with any other IP address on the internet.
0
I wouldn't agree with "what was once free would then become chargeable". When data is downloaded from Azure, you would still pay data processing charge on the NAT Gateway.
I'm not using a NAT Gateway.
相关内容
AWS 官方已更新 1 年前- AWS 官方已更新 2 年前
- AWS 官方已更新 7 个月前
Thanks. So if I were downloading data from an instance on Azure, and that third party later moved their infrastructure to AWS eu-west-2, what was once free would then become chargeable?
If both instances were in the same AZ within the Region, it looks like these charges would not apply?
Might not be the same AZ, that would not be within my control.
Hi Triatic, on your point re. Azure, different rates apply: I was pointing you only to the section for traffic intra-AWS and cross-region. For communication with Azure, a different rate applies: it is the one described on same page that I linked but mentionning traffic with the Internet ("Data Transfer IN From Amazon EC2 To Internet" and "Data Transfer OUT From Amazon EC2 To Internet"). Thanks for accepting my answer!
Didier_Durand yes, it was just an example of how inbound data from a third-party on Azure would be free, whereas inbound data from a third-party on another AZ within my AWS region would not be free.