5 ms·

Ummm... Quick back of the envelope [1] shows that the EC2 pricing is still only about 60% of the Aurora price, and something less than half of the RDS/PostgreS

Ummm... Quick back of the envelope [1] shows that the EC2 pricing is still only about 60% of the Aurora price, and something less than half of the RDS/PostgreSQL price, even counting the intra-region transfer. There may be some transfer patterns and database sizes that cause the Aurora implementation to end up less expensive, but I think under most use cases Aurora is _more_ expensive, and RDS _much more_ expensive. Just because the intra-region transfer isn't itemized doesn't mean that you aren't paying for it. Heck, the fact that the mark-up is so _low_ is pretty impressive, to be honest. [1] Assumptions: [db.]r6g.large, x3 for ec2 instances, 1 year reserved capacity with monthly payments, 100GB storage, 1TB of intra-region transfer/month.

22c 4y ago
Except the entire premise is not true... I am not sure what Corey has done to get to these numbers, but inter-AZ traffic within the same VPC is free. Perhaps the problem is that the pricing page is very confusing [1]. Probably the confusing part is that VPC peering between one VPC and another that crosses an AZ is not free, but you do not need to do that to compete with RDS availability. > The problem that I want to highlight today is that if I spin up MySQL myself on EC2 instances, I’ll have to pay 2¢ per GB that I replicate between AZs, whereas I will pay nothing if I use RDS. This sentence specifically, is not true. If your EC2 instances are in the same VPC but different AZs the data transfer is still free. There's a better blog post which explains what is and isn't free here [2]. [1] https://aws.amazon.com/ec2/pricing/on-demand/ https://aws.amazon.com/ec2/pricing/on-demand/ [2] https://aws.amazon.com/blogs/architecture/overview-of-data-transfer-costs-for-common-architectures/ https://aws.amazon.com/blogs/architecture/overview-of-data-t...
- deleted 4y ago
  [deleted]
- hodgesrm 4y ago
  > This sentence specifically, is not true. If your EC2 instances are in the same VPC but different AZs the data transfer is still free. Your assertion is not true. We run intra-VPC services across AZs and they are billed for network traffic. It's also shown as incurring cost in your second source. I had made this same comment then deleted it in order to check for sure. You are right that the Amazon docs are horribly confusing. The pricing page is up there with the descriptions of security on S3.
- scott00 4y ago
  This diagram within your source 2 seems to directly contradict what you're saying: https://d2908q01vomqb2.cloudfront.net/fc074d501302eb2b93e2554793fcaf50b3bf7291/2021/06/29/Figure-3.-Workload-components-across-Availability-Zones-2.jpg https://d2908q01vomqb2.cloudfront.net/fc074d501302eb2b93e255...
  - 22c 3y ago
    This diagram from a third party suggests that the traffic between different AZs in the same region is "No cost", but the written text suggests otherwise. https://www.cloudbolt.io/guide-to-aws-cost-optimization/aws-data-transfer-pricing/ https://www.cloudbolt.io/guide-to-aws-cost-optimization/aws-... Granted it is a third party website. I wonder if something has changed with their pricing.
- dilyevsky 4y ago
  I can tell you from experience of optimizing those bills that it’s very much NOT free in the same vpc for inter-az traffic. From the link you provided: > Data transferred between a Local Zone and an Availability Zone within the same AWS Region, “in” to and “out” from Amazon EC2 in the Local Zone Pricing Data transfer in $0.01 Data transfer out $0.01
  - 22c 3y ago
    A Local Zone is not the same as an Availability Zone, a Local Zone is an edge computing location.
    - dilyevsky 3y ago
      Hm actually you’re right about this one (and the fact it’s confusing af) but they do charge you for cross-az traffic as anyone who tried to run reasonably loaded multi-az kafka cluster will attest to
hodgesrm 4y ago
Intra-region markup just isn't that much anyway. It's typically $0.01 per GB across AZs. [0] If you ingest 1 TB of data (a lot of data) into a MySQL instance and replicate it to a replica in another AZ, that will run you $10.24 per month. That's why a lot of services don't call it out. [0] https://aws.amazon.com/ec2/pricing/on-demand/#Data_Transfer_within_the_same_AWS_Region https://aws.amazon.com/ec2/pricing/on-demand/#Data_Transfer_...

22c 4y ago

Except the entire premise is not true... I am not sure what Corey has done to get to these numbers, but inter-AZ traffic within the same VPC is free. Perhaps the problem is that the pricing page is very confusing [1]. Probably the confusing part is that VPC peering between one VPC and another that crosses an AZ is not free, but you do not need to do that to compete with RDS availability. > The problem that I want to highlight today is that if I spin up MySQL myself on EC2 instances, I’ll have to pay 2¢ per GB that I replicate between AZs, whereas I will pay nothing if I use RDS. This sentence specifically, is not true. If your EC2 instances are in the same VPC but different AZs the data transfer is still free. There's a better blog post which explains what is and isn't free here [2]. [1] https://aws.amazon.com/ec2/pricing/on-demand/ https://aws.amazon.com/ec2/pricing/on-demand/ [2] https://aws.amazon.com/blogs/architecture/overview-of-data-transfer-costs-for-common-architectures/ https://aws.amazon.com/blogs/architecture/overview-of-data-t...

deleted 4y ago
[deleted]
hodgesrm 4y ago
> This sentence specifically, is not true. If your EC2 instances are in the same VPC but different AZs the data transfer is still free. Your assertion is not true. We run intra-VPC services across AZs and they are billed for network traffic. It's also shown as incurring cost in your second source. I had made this same comment then deleted it in order to check for sure. You are right that the Amazon docs are horribly confusing. The pricing page is up there with the descriptions of security on S3.
scott00 4y ago
This diagram within your source 2 seems to directly contradict what you're saying: https://d2908q01vomqb2.cloudfront.net/fc074d501302eb2b93e2554793fcaf50b3bf7291/2021/06/29/Figure-3.-Workload-components-across-Availability-Zones-2.jpg https://d2908q01vomqb2.cloudfront.net/fc074d501302eb2b93e255...
- 22c 3y ago
  This diagram from a third party suggests that the traffic between different AZs in the same region is "No cost", but the written text suggests otherwise. https://www.cloudbolt.io/guide-to-aws-cost-optimization/aws-data-transfer-pricing/ https://www.cloudbolt.io/guide-to-aws-cost-optimization/aws-... Granted it is a third party website. I wonder if something has changed with their pricing.
dilyevsky 4y ago
I can tell you from experience of optimizing those bills that it’s very much NOT free in the same vpc for inter-az traffic. From the link you provided: > Data transferred between a Local Zone and an Availability Zone within the same AWS Region, “in” to and “out” from Amazon EC2 in the Local Zone Pricing Data transfer in $0.01 Data transfer out $0.01
- 22c 3y ago
  A Local Zone is not the same as an Availability Zone, a Local Zone is an edge computing location.
  - dilyevsky 3y ago
    Hm actually you’re right about this one (and the fact it’s confusing af) but they do charge you for cross-az traffic as anyone who tried to run reasonably loaded multi-az kafka cluster will attest to

hodgesrm 4y ago

Intra-region markup just isn't that much anyway. It's typically $0.01 per GB across AZs. [0] If you ingest 1 TB of data (a lot of data) into a MySQL instance and replicate it to a replica in another AZ, that will run you $10.24 per month. That's why a lot of services don't call it out. [0] https://aws.amazon.com/ec2/pricing/on-demand/#Data_Transfer_within_the_same_AWS_Region https://aws.amazon.com/ec2/pricing/on-demand/#Data_Transfer_...