Cross-AZ Egress Charge

[terrencec51229]

Hi Folks,

I have worked on proposing VMCA to stakeholders for a while and luckily, the feedback I got so far was quite positive.

During the cost assessment, I noticed that the traffic between customer VPC and connected VPC would not be charged from VMware Cloud on AWS Egress Estimate Guide.

If my situation is that the VMCA will be provisioned in the existing VPC where all the front-end applications reside so that the Transit Connect will not be required; when one of the APIs in the VPC tries to connect any of the databases in the Stretched Cluster, the network transfer in between will not be charged albeit they reside in different AZs.

Is my understanding correct? If so, the VMCA offering is extremely fascinating because the whole cross-AZ transfer, including the vSAN replication (10 PB/month), is typically free.

Much appreciated for any feedback in advance.

[terrencec51229 · Accepted solution]

Apologise for noising.

When I look at the document in depth, the diagram seems does not match the content. Why it is free just because its cost is too low to be ignored. If the cross-AZ transfer over the ENI is 1 TB, the corresponding expenditure will be 1,024 GB x $0.02 = $20.48, which is still not too costly.