Page-Illo_PricingCalculator_Wallet_1x

AWS Pricing Calculator

Calculate your Neptune and architecture cost in a single estimate. Create your customised estimate now »

Neptune database cluster configuration

You can choose between Neptune Standard and Neptune I/O-optimised configuration options to best match the price-performance and price-predictability requirements of your unique workload characteristics. Your database instance, storage and I/O charges will vary based on the option you choose. To find out more, visit Neptune storage and reliability.

Neptune Standard is ideal for the vast majority of applications with typical data-access patterns and low-to-moderate I/O usage. You pay for your database instances, storage and pay-per-request I/O. Neptune I/O-Optimised offers predictable pricing for all applications regardless of evolving data access patterns or I/O usage and removes variability in costs due to I/O fluctuations. It delivers improved price performance for I/O-intensive applications. If your I/O spend exceeds 25% of your total Neptune database spend, you can save up to 40% on costs for I/O-intensive workloads with Neptune I/O-optimised. You only pay for your database instances and storage usage, and there are zero charges for read and write I/O operations. 

Pricing by database instances

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 costs and complexities of planning, purchasing and maintaining hardware and transforms what are commonly large fixed costs into much smaller variable costs. Instance charges will vary based on the database cluster configuration you choose to best match the price-performance and price-predictability needs of your application. All instances in a database cluster will either be charged the price for the Neptune Standard or Neptune I/O-optimised configuration.

Instance pricing applies to both primary instances used for read-write workloads, and to Neptune replicas used to scale reads and enhance failover. Neptune uses Multi-Availability Zone (Multi-AZ) architecture 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 Neptune replica. To maximise availability, we recommend placing at least one replica in a different AZ from the primary instance.

Neptune Serverless

Neptune Serverless is only available for Neptune Database. With Neptune Serverless, your database capacity automatically scales up or down to meet your application workload needs, saving you money and administration time. You only pay for the database capacity and storage that your database consumes when it is active. Neptune Serverless measures database capacity in Neptune Capacity Units (NCUs) billed per second. 1 NCU has approximately two GB of memory with corresponding CPU and networking, similar to what is used in Neptune instances.

Scale-up latency

Automatic scaling to hundreds of thousands of transactions per second

Scale-down latency

<5 minute

Starting capacity

1 NCU

Capacity granularity

Fine-grained, with increments as small as 1 NCU

Read replicas

Up to 15 Neptune replicas for read scalability

Multi-AZ and SLA

Distribute read replicas in separate AZs for high availability. Refer to Neptune SLA for details.

Pricing by database storage and I/Os

Storage consumed by your Neptune Database is billed in per GB-month increments, and I/Os consumed are billed in per million request increments. You pay only for the storage and I/Os your Neptune Database consumes and do not need to provision in advance.

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. Find out more.

Back-up storage costs

Back-up storage pricing applies to both Neptune Database and Neptune Analytics, and it's the storage associated with your automated database backups and any customer-initiated database cluster snapshots. Increasing your back-up retention period or taking database cluster snapshots increases the back-up storage consumed. Back-up storage is allocated by region. Total back-up storage space is equivalent to the sum of the storage for all back-ups in that region. Moving a database snapshot to another region increases allocated back-up storage in the destination region.

There is no additional charge for back-up storage of up to 100% of your total Neptune storage for each Neptune cluster. There is also no additional charge for back-up storage if your back-up retention period is one day, and you don’t have any snapshots beyond the retention period. Back-up storage, as well as snapshots you store after your database cluster is deleted, will be charged at the above rates.

Pricing examples

Pricing example 1

Let’s say your Neptune Database is running on a db.r5.large instance (on demand) in US East (N. Virginia). You store 50 GB of data with 100 GB back-up, and you perform 200 million I/Os per month, with data transfer IN of 50 GB per month and data transfer OUT of 10 GB per month. Your charges are calculated as follows:

Instance charges
The on-demand pricing for db.7g.large instance is €0.3286 per hour, so your monthly cost for the instance is €236.59 (€0.3286 * 24 * 30).

Storage charges
Your storage cost is €0.1174 per GB-month, so for 50 GB storage your (30-day) monthly cost is €5.87 (€0.1174 * 50). There is no additional charge for the first 50 GB of back-up storage. The remaining 50 GB of back-up storage is €1.13 (€0.0226 * 50).

I/O charges
Your I/O cost is €0.253 per million request increments, so for 200 million I/Os per month, your cost is €50.6 (€0.253 * 200).

Data transfer charges
Your I/O cost is €0.253 per million request increments, so for 200 million I/Os per month, your cost is €50.6 (€0.253 * 200).

Total charges
€236.59 instance charges
€5.87 storage charges
€1.13 back-up storage charges
€50.6 I/O charges
Total = €294.19

Pricing example 2

Let’s say your Neptune Database is running on a db.r5.large instance (on demand) in US East (N. Virginia). You store 50 GB of data with 100 GB back-up, and you perform 450 million I/Os per month, with data transfer IN of 50 GB per month and data transfer OUT of 10 GB per month. Let’s compare your charges with a standard configuration compared to an I/O-optimised configuration:

Instance charges
The on-demand pricing with I/O-optimised db.r7g.large instance is €0.4436 per hour, so your monthly cost for the instance is €319.39 (€0.4436 * 24 * 30).

Storage charges
Your storage cost with I/O-optimised is €0.2634 per GB-month, so for 50 GB storage your (30-day) monthly cost is €13.17 (€0.2634 * 50). There is no additional charge for the first 50 GB of back-up storage. The remaining 50 GB of back-up storage is €1.13 (€0.0226 * 50).

I/O charges
There are no I/O charges with an I/O-optimised configuration.

Total charges
€319.39 instance charges
€13.17 storage charges
€1.13 back-up storage charges
€0 I/O charges
Total = €333.69