-1

that should be simple, but I cannot figure that out

Amazon bills the real used storage amount for Aurora databases, not the allocated storage like for non-Aurora.

there is a metric VolumeBytesUsed - The amount of storage used by your Aurora DB instance. This metric applies to an entire Aurora DB cluster, not for instance. https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Monitoring.html

I have a cluster of 1 Arora Writer and 2 Readers. DB size is about 10 Gb and VolumeBytesUsed shows 10Gb. According to documentation, each Aurora node has its own data copy - https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Overview.html So if I have 10Gb DB - Aurora Writer and 2 Readers should be using 10x3 = 30 Gb of storage, but VolumeBytesUsed shows 10Gb

Will I be billed for 10 Gb or 30 Gb in that case?

2 Answers 2

1

From the Aurora MySQL FAQ, which I found linked from the pricing page.

Q: Amazon Aurora replicates each chunk of my database volume six ways across three Availability Zones. Does that mean that my effective storage price will be three or six times what is shown on the pricing page?

No. Amazon Aurora’s replication is bundled into the price. You are charged based on the storage your database consumes at the database layer, not the storage consumed in Amazon Aurora’s virtualized storage layer.

Based on what I know about AWS (quite a bit) and what I've read (not a lot) I think each database is charged once for storage. That means if you have a 10GB database service with two 10GB read replicas you'll be charged for 30GB of storage.

3
  • I can have up to 15 replicas, does that mean that all the replicas use the same database files? I doubt that replicas may use the same DB files. I see that all replicas are connected to the same volume. If I have 1Gb Writer and 15 replicas, I assume that each replica will have its own DB copy. will I be charged for 1Gb or for 16Gb
    – John
    Apr 1, 2021 at 18:59
  • Updated my answer.
    – Tim
    Apr 1, 2021 at 20:34
  • I finally got an answer from AWS Support: Aurora by design, is managed in a clustered format. Both writer and reader instances of aurora cluster are associated with same storage layer hence there will not be any extra charge for storage when you provision additional reader instance.
    – John
    Apr 5, 2021 at 13:35
1

here is what I got from support:

Aurora by design, is managed in a clustered format. Both writer and reader instances of aurora cluster are associated with same storage layer hence there will not be any extra charge for storage when you provision additional reader instance. The charges to aurora cluster are calculated on a cluster level so if you have one writer and one (or more) reader instance, you will be charged as below:

  1. Cost of DB instances (if you have one writer and one reader, you will be charged for two instances)

  2. Total storage on cluster level

  3. Total IO consumed on cluster level

  4. Charges for backtrack feature (if applicable)

  5. Charges for Snapshot export (if applicable)

  6. Charges for cross-AZ data transfer in same region (if applicable)

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .