Amazon Neptune 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, testing and other short-lived workloads.

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

Amazon Neptune T4g and T3 medium 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 ¥ 1.032 per vCPU-Hour. The CPU Credit pricing is the same for all T4g and T3 instance sizes across all regions. For more information on how unlimited burstable performance instances work and how it is priced, see Unlimited mode concepts.

Storage consumed by your Amazon Neptune 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 Neptune database consumes and do not need to provision in advance.

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

• There is no additional charge for backup storage of up to 100% of your total Neptune database storage for a region. (Based on our experience as database administrators, the vast majority of databases require less raw storage for a backup than for the primary dataset, meaning that most customers will never pay for backup storage.)
  
  • For example, if you have 2 active Neptune database clusters each with 300 GB-month of consumed database storage, we provide up to 600 GB-month of backup storage at no additional charge.

• Backup storage beyond this amount and backups stored after your database cluster is terminated are billed at storage rates in the table below:

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

• Data transferred between Amazon Neptune and Amazon EC2 Instances in the same Availability Zone is free.
• Data transferred between Availability Zones for replication of Multi-AZ deployments is free.
• Amazon Neptune database instances outside VPC: For data transferred between an Amazon EC2 instance and Amazon Neptune database instance in different Availability Zones of the same Region, there is no Data Transfer charge for traffic in or out of the Amazon Neptune database instance. You are only charged for the Data Transfer in or out of the Amazon EC2 instance, and standard Amazon EC2 Regional Data Transfer charges apply.
• Amazon Neptune database instances inside VPC: For data transferred between an Amazon EC2 instance and Amazon Neptune database instance in different Availability Zones of the same Region, Amazon EC2 Regional Data Transfer charges apply on both sides of transfer.

Assume that your Neptune database is running on a db.r5.large instance (on-demand), you store 50 GB of data with 100 GB backup, 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.

• The on-demand pricing for db.r5.large instance is ¥2.88 per hour, so your monthly cost for the instance will be ¥2073.6 (¥2.88 *24*30).
  
• Your storage cost will be ¥ 0.596 per GB-month, so for 50 GB storage, your (30-day) monthly cost will be ¥29.8 (¥ 0.596 *50). There will be no additional charge for the first 50GB of backup storage. The remaining 50 GB of backup storage will be ¥ 7.85 (¥ 0.157 * 50).
• Your I/O cost will be ¥ 1.192 per million request increments, so for your 200 Million I/Os per month, your cost will be ¥ 238.4 (¥ 1.192 *200).
• There is no charge for data transfer IN to your Neptune database. For the Data transfer OUT of 10 GB per month, the cost is ¥ 0.933 per GB. 
• Your cost for Data transfer OUT will be ¥ 8.397 (¥ 0.933 *9).

Your total monthly bill for Neptune for this example would be ¥ 2358.05 (¥2073.6 for instance + ¥29.8 for storage + ¥ 7.85 for backup storage + ¥ 238.4 for I/O + ¥ 8.397 for Data Transfer OUT).

Let’s say your Amazon Neptune database is running on a db.r5.large instance (on demand) in China (Beijing Region). You store 50 GB of data with 100 GB backup, 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.r5.large instance is  ¥ 3.47 per hour, so your monthly cost for the instance is  ¥ 2,498.4 (¥ 3.47 * 24 * 30).

Storage charges

Your storage cost is ¥ 0.67 per GB-month, so for 50 GB storage your (30-day) monthly cost is ¥ 33.5 (¥ 0.67 * 5 0). There is no additional charge for the first 50 GB of backup storage. The remaining 50 GB of backup storage is ¥ 9.0 (¥ 0.180 * 50).

I/O charges

Your I/O cost is ¥ 1.330 per million request increments, so for 200 Million I/Os per month, your cost is ¥ 266.0 (¥ 1.330 * 200).

Data transfer charges

There is no charge for data transfer IN to your Amazon Neptune database. All data transfer OUT, the cost is ¥ 0.933 per GB per month. Cost for data transfer Out is ¥ 9.33 (¥ 0.933 * 10).

Total charges:

¥ 2,498.4 instance charges
¥ 33.5 storage charges
¥ 9.0 backup storage charges
¥ 266.0 I/O charges
¥ 9.33 data transfer charges
Total = ¥ 2,816.23

Let’s say your Amazon Neptune database is running with one primary db.r5d.2xlarge instance (on-demand) and three replica r5d.2xlarge instances (on-demand) in China (Beijing Region). You also use the Neptune Workbench to run one ml.t3.xlarge notebook instance (on-demand) in the same region. You store 100 GB of data with 75 GB backup, and you perform 150 million I/Os per month. Your charges are calculated as follows:

Instance charges

The on-demand pricing for db.r5d.2xlarge is ¥ 15.8286 per hour. You have four instances in your cluster, so your 30-day month cost for the cluster is ¥ 11,396.592 (¥ 15.8286 * 24 * 30).

Storage charges

Your storage cost is ¥ 0.67 per GB-month so for 100 GB storage, your (30-day) monthly cost is ¥ 67 (¥ 0.67 * 100). There is no additional charge for backup storage of up to 100 percent of your total Neptune database storage for each Neptune cluster. Your backup cost is ¥0.00.

I/O charges

Your I/O cost is ¥ 1.330 per 1 million requests, so for 150 million I/Os per month, your cost is ¥ 199.5 (¥ 1.330 * 150).

Notebook charges

Notebooks are hosted and billed through Amazon SageMaker’s notebook service. Customers are charged for the notebook instance while the instance is in the Ready state. The on-demand pricing for ml.t3.xlarge is ¥ 1.4721 per hour, so your 30-day monthly cost for the notebook instance is ¥ 1,059.912 (¥ 1.4721 * 24 * 30).

Total charges:

¥ 11,396.592 database instance charges
¥ 67 storage charges
¥ 0.00 backup charges
¥ 199.5 I/O charges
¥ 1,059.912 notebook instance charges
Total = ¥ 12,723.004