Pay as you go with no up-front fees. There is no minimum fee. The prices below apply to both MySQL-compatible and PostgreSQL-compatible editions of Amazon Aurora, except where noted.

Database Instances

Select "MySQL-Compatible Edition" or "PostgreSQL-Compatible Edition" to view database instance pricing.

  • MySQL-Compatible Edition

    Select to see details about MySQL-Compatible pricing options

    On-Demand Instance Pricing

    On-Demand Instances let you pay for your database by the hour with no long-term commitments or upfront fees. This frees you from the cost and complexity of planning and purchasing database capacity ahead of your needs. On-Demand pricing lets you pay as you go and is ideal for development, test and other short-lived workloads.

    Pricing is per DB instance-hour consumed, from the time a DB instance is launched until it is stopped or deleted. Partial DB instance-hours are billed in one-second increments with a 10 minute minimum charge following a billable status change such as creating, starting, or modifying the DB instance class.

    Instance pricing applies to both Primary instances, used for read-write workloads, and Amazon Aurora Replicas, used to scale reads and enhance failover. Amazon RDS Multi-AZ technology is used to failover to one of your Replicas if an outage occurs. The cost of Multi-AZ deployments is simply the cost of the primary instance plus the cost of each Amazon Aurora Replica. To maximize availability, we recommend placing at least one Replica in a different Availability Zone from the Primary instance.

    T3 CPU Credits

    Amazon Aurora T3 DB instances run in Unlimited mode, which means that you will be charged if your average CPU utilization over a rolling 24-hour period exceeds the baseline of the instance. CPU Credits are charged at $0.09 per vCPU-Hour. The CPU Credit pricing is the same for all T3 instance sizes across all regions and is not covered by Reserved Instances.

    Serverless Pricing

    With Amazon Aurora Serverless, there are no instances to manage. Your database capacity automatically scales up or down to meet your application workload needs and shuts down during periods of inactivity, saving you money and administration time. You pay for database storage, plus the database capacity and I/O your database consumes while it is active.

    Database capacity is measured in Aurora Capacity Units (ACUs). 1 ACU has approximately 2 GB of memory with corresponding CPU and networking, similar to what is used in Aurora user-provisioned instances.

    Reserved Instance Pricing

    Reserved Instances are appropriate for steady-state database workloads and offer significant savings over On-Demand. One Year Reserved Instances provide discounts up to 45% and Three Year Reserved Instances provide discounts of up to 66% over On-Demand. You commit to the entire duration of the Reserved Instance term and pay an upfront charge and a discounted hourly rate as shown below. You will be billed for each hour of the term regardless of whether any usage has occurred.

    You need to purchase a Reserved Instance for each database instance you plan to use, including Aurora Replicas.

    Reserved Instances provide size flexibility for the Amazon Aurora database engine. With size flexibility, your RI’s discounted rate will automatically apply to usage of any size in the same instance family (T2, R3, etc.).

    *This is the average monthly payment over the course of the Reserved Instance term. For each month, the actual monthly payment will equal the actual number of hours in that month multiplied by the hourly usage rate. The hourly usage rate is equivalent to the total average monthly payments over the term of the Reserved Instance divided by the total number of hours (based on a 365 day year) over the term of the Reserved Instance.

    **Effective hourly pricing is shown to help you calculate the amount of money that a Reserved Instance will save you over On-Demand pricing. When you purchase a Reserved Instance, you are billed for every hour during the entire Reserved Instance term that you select, regardless of whether the instance is running or not. The effective hourly price shows the amortized hourly cost of the instance (this takes the total cost of the Reserved Instance over the entire term, including any upfront payment, and spreads it out over each hour of the Reserved Instance term).

  • PostgreSQL-Compatible Edition

    Select to see details about PostgreSQL-Compatible pricing options

    On-Demand Instance Pricing

    On-Demand Instances let you pay for your database by the hour with no long-term commitments or upfront fees. This frees you from the cost and complexity of planning and purchasing database capacity ahead of your needs. On-Demand pricing lets you pay as you go and is ideal for development, test and other short-lived workloads.

    Pricing is per DB instance-hour consumed, from the time a DB instance is launched until it is stopped or deleted. Partial DB instance-hours are billed in one-second increments with a 10 minute minimum charge following a billable status change such as creating, starting, or modifying the DB instance class.

    Instance pricing applies to both the primary instance, used for read-write workloads, and any Amazon Aurora Replicas, used to scale reads and enhance failover. Amazon RDS Multi-AZ technology is used to failover to one of your Replicas if an outage occurs. The cost of Multi-AZ deployments is simply the cost of the primary instance plus the cost of each Amazon Aurora Replica. To maximize availability, we recommend placing at least one Replica in a different Availability Zone from the Primary instance.

    Reserved Instance Pricing

    Reserved Instances are appropriate for steady-state database workloads and offer significant savings over On-Demand. One Year Reserved Instances provide discounts up to 45% and Three Year Reserved Instances provide discounts of up to 66% over On-Demand. You commit to the entire duration of the Reserved Instance term and pay an upfront charge and a discounted hourly rate as shown below. You will be billed for each hour of the term regardless of whether any usage has occurred.

    You need to purchase a Reserved Instance for each database instance you plan to use, including Aurora Replicas.

    Reserved Instances provide size flexibility for the Amazon Aurora database engine. With size flexibility, your RI’s discounted rate will automatically apply to usage of any size in the same instance family (T2, R3, etc.).

    *This is the average monthly payment over the course of the Reserved Instance term. For each month, the actual monthly payment will equal the actual number of hours in that month multiplied by the hourly usage rate. The hourly usage rate is equivalent to the total average monthly payments over the term of the Reserved Instance divided by the total number of hours (based on a 365 day year) over the term of the Reserved Instance.

    **Effective hourly pricing is shown to help you calculate the amount of money that a Reserved Instance will save you over On-Demand pricing. When you purchase a Reserved Instance, you are billed for every hour during the entire Reserved Instance term that you select, regardless of whether the instance is running or not. The effective hourly price shows the amortized hourly cost of the instance (this takes the total cost of the Reserved Instance over the entire term, including any upfront payment, and spreads it out over each hour of the Reserved Instance term).

Database Storage and IOs

Storage consumed by your Amazon Aurora database is billed in per GB-month increments and IOs consumed are billed in per million request increments. You pay only for the storage and IOs your Amazon Aurora database consumes and do not need to provision in advance.

Global Database

Amazon Aurora Global Database is an optional feature that provides low-latency global reads and disaster recovery from region-wide outages. You pay for replicated write I/Os between the primary region and each secondary region. The number of replicated write I/Os to each secondary region is same as the number of in-region write I/Os performed by the primary region. Apart from replicated write I/Os, you pay standard Aurora rates for instances, storage, cross-region data transfer, backup storage, and Backtrack.

Backup Storage

Backup storage for Amazon Aurora is the storage associated with your automated database backups and any customer-initiated DB cluster snapshots. Increasing your backup retention period or taking DB cluster snapshots increases the backup storage consumed.

  • Backup storage is allocated by region. Total backup storage space is equivalent to the sum of the storage for all backups in that region.
  • Moving a DB cluster snapshot to another region increases allocated backup storage in the destination region.
  • There is no additional charge for backup storage of up to 100% of your total Aurora database storage for each Aurora DB cluster. There is also no additional charge for backup storage if your backup retention period is 1 day and you don’t have any snapshots beyond the retention period.
  • Backup storage, as well as snapshots you store after your DB cluster is deleted will be charged at the following rates:
 

Backtrack

Backtrack lets you quickly move an Aurora database to a prior point in time without needing to restore data from a backup. This lets you quickly recover from user errors, such as dropping the wrong table or deleting the wrong row. This feature is currently available for the MySQL-compatible edition of Aurora.

You need to specify how far in the past you want to be able to go (e.g. “up to 24 hours”). Aurora will retain logs, called Change Records, for the specified Backtrack duration. You pay a simple hourly rate for storing Change Records.

For example, suppose your Aurora database is generating 10,000 Change Records per hour – which you can see by reviewing your CloudWatch metrics – and you want to be able to use Backtrack up to 10 hours in the past. To support this, Aurora would need to store 10,000 Change Records/hour x 10 hours = 100,000 Change Records. Say the cost in the US East (N. Virginia) Region is $0.012/hour per 1 million Change Records. Then turning on Backtrack would increase your costs by $0.012 x (100,000 / 1,000,000) = $0.0012/hour.

When using Backtrack, you can review CloudWatch metrics in the AWS Console to see how many Change Records your database is generating per hour.

Data Transfer

The pricing below is based on data transferred “in” and “out” of Amazon Aurora.

  • Data transferred between Amazon Aurora and Amazon EC2 instances in the same Availability Zone is free.
  • Data transferred between Availability Zones for DB cluster replication is free.
  • For data transferred between an Amazon EC2 instance and Amazon Aurora DB instance in different Availability Zones of the same Region, Amazon EC2 Regional Data Transfer charges apply.
 

Except as otherwise noted, our prices are exclusive of applicable taxes and duties, including VAT and applicable sales tax. For customers with a Japanese billing address, use of AWS is subject to Japanese Consumption Tax. Learn more.

Additional pricing resources

TCO Calculator

Calculate your total cost of ownership (TCO)

Simple Monthly Calculator

Easily calculate your monthly costs with AWS

Economics Resource Center

Additional resources for switching to AWS

Learn how to get started with Amazon Aurora

Find resources to get started
Ready to build?
Get started with Amazon Aurora
Have more questions?
Contact us