Revisit Amazon Web Services re:Invent 2024’s biggest moments and watch keynotes and innovation talks on demand
Neptune Database cluster configuration
With Neptune, you can configure your database clusters to run cost effectively, regardless of the scaling needs or evolving data access patterns of your applications. You have the flexibility to choose between the Amazon Neptune Standard and Amazon Neptune I/O-Optimized 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 learn more, visit Amazon Neptune storage and reliability.
Neptune Standard offers cost-effective pricing for the vast majority of applications running on Neptune with typical data access patterns and low to moderate I/O usage. With Neptune Standard, you pay for your database instances, storage, and pay-per-request I/O.
Neptune I/O-Optimized 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-Optimized. With Neptune I/O-Optimized, you only pay for your database instances and storage usage, and there are zero charges for read and write I/O operations. Neptune I/O-Optimized offers predictable pricing for all applications regardless of evolving data access patterns or I/O usage. Neptune I/O-Optimized eliminates variability in I/O spend.
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, 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.
Instances 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-Optimized configuration.
Region: China (Beijing)
Standard Instances | Neptune Standard | Neptune I/O-Optimized |
(Current Generation) | (Price Per Hour) | (Price Per Hour) |
db.t4g.medium | ¥ 0.6644 | ¥0.90 |
db.t3.medium | ¥0.70 | ¥0.95 |
Memory Optimized Instances (Current Generation) | Neptune Standard | Neptune I/O-Optimized |
db.r6g.large | ¥ 3.2776 | ¥4.42 |
db.r6g.xlarge | ¥ 6.5269 | ¥8.81 |
db.r6g.2xlarge | ¥ 13.083 | ¥17.66 |
db.r6g.4xlarge | ¥ 26.2588 | ¥35.45 |
db.r6g.8xlarge | ¥ 52.5229 | ¥70.91 |
db.r6g.12xlarge | ¥78.81 | ¥106.39 |
db.r6g.16xlarge | ¥105.08 | ¥141.86 |
db.r5.large | ¥ 3.470 | ¥4.68 |
db.r5.xlarge | ¥ 6.910 | ¥9.33 |
db.r5.2xlarge | ¥ 13.850 | ¥18.70 |
db.r5.4xlarge | ¥27.67 | ¥37.35 |
db.r5.8xlarge | ¥55.34 | ¥74.71 |
db.r5.12xlarge | ¥83.04 | ¥112.10 |
db.r5.16xlarge | ¥110.72 | ¥149.48 |
db.r5.24xlarge | ¥166.08 | ¥224.21 |
db.r5d.large | ¥3.97 | ¥4.68 |
db.r5d.xlarge | ¥7.90 | ¥10.66 |
db.r5d.2xlarge | ¥15.83 | ¥21.37 |
db.r5d.4xlarge | ¥ 31.6229 | ¥42.69 |
db.r5d.8xlarge | ¥63.25 | ¥85.39 |
db.r5d.12xlarge | ¥94.90 | ¥128.12 |
db.r5d.16xlarge | ¥126.54 | ¥170.83 |
db.r5d.24xlarge | ¥189.81 | ¥256.24 |
Region: China (Ningxia)
Standard Instances | Neptune Standard | Neptune I/O-Optimized |
(Current Generation) | (Price Per Hour) | (Price Per Hour) |
db.t4g.medium | ¥ 0.5505 | ¥0.74 |
db.t3.medium | ¥0.58 | ¥0.78 |
Memory Optimized Instances (Current Generation) | Neptune Standard | Neptune I/O-Optimized |
db.r6g.large | ¥ 2.7203 | ¥3.67 |
db.r6g.xlarge | ¥ 5.4313 | ¥7.33 |
db.r6g.2xlarge | ¥ 10.8632 | ¥14.67 |
db.r6g.4xlarge | ¥ 21.8174 | ¥29.45 |
db.r6g.8xlarge | ¥ 43.6362 | ¥58.91 |
db.r6g.12xlarge | ¥65.46 | ¥88.38 |
db.r6g.16xlarge | ¥87.28 | ¥117.83 |
db.r5.large | ¥ 2.880 | ¥3.89 |
db.r5.xlarge | ¥ 5.750 | ¥7.76 |
db.r5.2xlarge | ¥ 11.500 | ¥15.52 |
db.r5.4xlarge | ¥22.99 | ¥31.04 |
db.r5.8xlarge | ¥ 45.980 | ¥62.08 |
db.r5.12xlarge | ¥68.98 | ¥93.12 |
db.r5.16xlarge | ¥91.97 | ¥124.16 |
db.r5.24xlarge | ¥137.95 | ¥186.24 |
db.r5d.large | ¥3.29 | ¥4.44 |
db.r5d.xlarge | ¥6.57 | ¥8.87 |
db.r5d.2xlarge | ¥13.14 | ¥17.74 |
db.r5d.4xlarge | ¥26.27 | ¥35.47 |
db.r5d.8xlarge | ¥52.55 | ¥70.94 |
db.r5d.12xlarge | ¥78.83 | ¥106.43 |
db.r5d.16xlarge | ¥105.11 | ¥141.89 |
db.r5d.24xlarge | ¥157.66 | ¥212.84 |
T4g and T3 CPU Credits
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.
Database Storage and IOs
Neptune storage is billed in per GB-month increments at the rates shown in the following table for the Neptune Standard and Neptune I/O-Optimized configurations. With Neptune Standard, you pay for the storage and I/O operations that your Neptune database consumes. I/O charges may vary significantly depending on workload and database engine.
Region: China (Beijing)
Storage Rate | ¥ 0.67 per GB-month | ¥ 1.507 per GB-month |
I/O Rate | ¥ 1.330 per 1 million requests | Included |
Region: China (Ningxia)
Storage Rate | ¥ 0.596 per GB-month | ¥ 1.341 per GB-month |
I/O Rate | ¥ 1.192 per 1 million requests | Included |
Backup Storage
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.
- 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:
Region: China (Beijing)
Storage Snapshot Rate | ¥ 0.180 per GB-month |
Region: China (Ningxia)
Storage Snapshot Rate | ¥ 0.157 per GB-month |
Data Transfer
The pricing below is based on data transferred “in” and “out” of Amazon Neptune.
Region: China (Beijing)
Data Transfer IN | |
All data transfer in | ¥ 0.000 per GB |
Data Transfer OUT From Amazon Neptune To Internet | |
All data transfer out | ¥ 0.933 per GB (Promotional) |
Inter Region Data Transfer | |
Data transferred between the China (Beijing) and China (Ningxia) regions | ¥ 0.6003 per GB |
Region: China (Ningxia)
Data Transfer IN | |
All data transfer in | ¥ 0.000 per GB |
Data Transfer OUT From Amazon Neptune To Internet | |
All data transfer out | ¥ 0.933 per GB (Promotional) |
Inter Region Data Transfer | |
Data transferred between the China (Beijing) and China (Ningxia) regions | ¥ 0.6003 per GB |
- 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.
Amazon Neptune Workbench
Region: China (Beijing)
Notebook Instance Type | Price Per Hour |
ml.t2.medium | ¥ 0.5964 |
ml.t2.large | ¥1.19 |
ml.t2.xlarge | ¥2.37 |
ml.t2.2xlarge | ¥ 4.7488 |
ml.t3.medium | ¥ 0.3681 |
ml.t3.large | ¥0.74 |
ml.t3.xlarge | ¥ 1.4721 |
ml.t3.2xlarge | ¥2.94 |
Region: China (Ningxia)
Notebook Instance Type | Price Per Hour |
ml.t2.medium | ¥ 0.5291 |
ml.t2.large | ¥ 1.0581 |
ml.t2.xlarge | ¥ 2.1162 |
ml.t2.2xlarge | ¥ 4.2325 |
ml.t3.medium | ¥ 0.2684 |
ml.t3.large | ¥ 0.5368 |
ml.t3.xlarge | ¥ 1.0735 |
ml.t3.2xlarge | ¥ 2.1469 |
Pricing Examples
Pricing Example 1: Neptune Database Standard configuration
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
Pricing Example 2: Neptune Database I/O-Optimized configuration
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 450 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 I/O-Optimized instance is ¥ 4.684 per hour, so your monthly cost for the instance is ¥ 3,372.5 (¥ 4.684 * 24 * 30).
Storage charges
Your I/O-Optimized storage cost is ¥ 1.507 per GB-month, so for 50 GB storage your (30-day) monthly cost is ¥ 75.35 (¥ 1.507 * 50). 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 ¥ 0.0 per million request increments, so for 450 Million I/Os per month, your cost is ¥ 0.0 (¥ 0.0 * 450).
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:
¥ 3,372.5 instance charges
¥ 75.35 storage charges
¥ 9.0 backup storage charges
¥ 0.0 I/O charges
¥ 9.33 data transfer charges
Total = ¥ 3,466.18
Pricing Example 3: Neptune Workbench
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