Amazon Neptune

Amazon Neptune is a managed graph database product published by Amazon.com. It is used as a web service and is part of Amazon Web Services (AWS). It was announced on November 29, 2017.[1] Amazon Neptune supports popular graph models property graph and W3C's RDF, and their respective query languages Apache TinkerPop's Gremlin,[2] openCypher,[3] and SPARQL,[4] including other Amazon Web Services products.

Amazon Neptune general availability (GA) was announced on May 30, 2018[5][6] and is currently available in 22 AWS regions. Neptune is HIPAA eligible.[7] On December 12, 2018, it was announced that Amazon Neptune was in-scope for Payment Card Industry Data Security Standard, and ISO compliance programs.[8]

History

[edit]

Amazon Neptune is based on Blazegraph. Amazon acquired the Blazegraph developers and the Blazegraph open source development was essentially stopped in April 2018.[9]

History of Amazon Neptune engine releases[10]
Release Change Date
1.0.2.2 Engine version 1.0.2.2 March 9, 2020
1.0.2.1 Engine version 1.0.2.1.R4 December 20, 2019
1.0.2.1 Engine version 1.0.2.1.R3 December 12, 2019
1.0.2.1 Engine version 1.0.2.1.R2 November 23, 2019
1.0.2.0 Engine version 1.0.2.0.R2 November 8, 2019
1.0.1.0 Engine version 1.0.1.0.200502.0 October 31, 2019
1.0.1.0 Engine version 1.0.1.0.200463.0 October 15, 2019
1.0.1.0 Engine version 1.0.1.0.200457.0 September 19, 2019
1.0.1.0 Engine version 1.0.1.0.200369.0 August 13, 2019
1.0.1.0 Engine version 1.0.1.0.200348.0 July 2, 2019
1.0.1.0 Engine version 1.0.1.0.200310.0 June 12, 2019
1.0.1.0 Engine version 1.0.1.0.200296.0 May 1, 2019
1.0.1.0 Engine version 1.0.1.0.200267.0 January 21, 2019
1.0.1.0 Engine version 1.0.1.0.200264.0 November 19, 2018
1.0.1.0 Engine version 1.0.1.0.200258.0 November 8, 2018
1.0.1.0 Engine version 1.0.1.0.200255.0 October 29, 2018
1.0.1.0 Engine version 1.0.1.0.200237.0 September 6, 2018
1.0.1.0 Engine version 1.0.1.0.200236.0 July 24, 2018
1.0.1.0 Engine version 1.0.1.0.200233.0 June 22, 2018
1.0.1.0 Amazon Neptune initial release May 30, 2018

Features

[edit]

External support

[edit]

Amazon Neptune supports the open source Apache TinkerPop Gremlin[2] graph traversal language, openCypher query language[3] for property graphs, and the W3C standard Resource Description Framework's (RDF) SPARQL[4] query language. All three can be used on the same Neptune instance, and allows the user to build queries to navigate highly connected data sets and provides high performance for both graph models. Neptune also uses other AWS product features such as those of Amazon S3, Amazon EC2 and Amazon CloudWatch.[11]

Security

[edit]

All Amazon Neptune database clusters are created and stored in an Amazon Virtual Private Cloud (VPC), which allows the user to isolate their database in their own private network. Using Neptune's VPC configuration, the user can configure firewall settings to their needs in order to control network access to database instances. Amazon Neptune is integrated with AWS Identity and Access Management (IAM), which allows the user to create AWS IAM groups and control the actions that the groups and other AWS IAM users can do. Neptune allows the user to encrypt databases using keys created through AWS Key Management Service (KMS). A database instance running with Neptune Encryption, encrypts all of the stored data, backups, snapshots and replicas in the same cluster. Amazon Neptune allows the user to use HTTPS to encrypt data during its transfer to and from clients or Neptune service endpoints using Transport Layer Security (TLS).[12]

Storage

[edit]

The data is stored in a cluster volume, a virtual volume utilizing SSD drives. These sizes of these volumes are dynamic, they increase depending how much data is stored in the database, with a maximum of 64 TB. The Amazon Neptune SLA policy is designed to offer a monthly uptime percentage greater that of 99.9%, increasing database performance and availability by integrating the engine with a virtual storage based on SSD drives, that are specially made for database workloads. Neptune maintains copies of the user's data in multiple Availability Zones. In case of failures, Neptune automatically detects any failed segments in a disk volume and repairs them.[13]

Availability

[edit]

Neptune is now generally available in the US East (N. Virginia), US East (Ohio), US West (Oregon), US West (N. California), Canada (Central),[14] AWS GovCloud (US-West),[15] AWS GovCloud (US-East),[16] Europe (Ireland), Europe (London),[17] Europe (Frankfurt),[18] Europe (Stockholm),[19] Europe (Paris),[20] South America (São Paulo), Asia Pacific (Singapore),[21] Asia Pacific (Sydney),[22] Asia Pacific (Tokyo),[23] Asia Pacific (Mumbai),[24] Asia Pacific (Seoul),[25] Asia Pacific (Hong Kong), China (Ningxia), China (Beijing), Operated by NWCD,[26] and Middle-East (Bahrain)[27] AWS regions.

Pricing

[edit]

Pricing is determined by AWS regions, with each region having different prices for the available services.

On-Demand Instance Pricing lets the user pay only for what instance they use by the hour instead of a fixed sum. The price also differs depending on the instance class. Similarly, the user only pays for the storage consumed by the database, with no payments in advance. The price is based on the storage rate and I/O rate, which are billed in GB per month and per million request increments respectively. This pricing model is beneficial to short-term and small-scale projects and is available in all AWS regions. The price for backup storage is also billed in per GB-month increments albeit at different rates. Data Transfer is priced in per GB increments, the amount depends on whether the data is transferred in or out of Amazon Neptune and how much data is transferred per month (TB per Month).[28]

Application

[edit]

On September 12, 2018, it was announced that Neptune achieved HIPAA eligibility[7] enabling it to process data sets containing protected health information (PHI). On December 12, 2018, it was announced that Amazon Neptune was in-scope for Payment Card Industry Data Security Standard, ISO 9001, ISO 27001, ISO 27017, and ISO 27018 compliance programs.[8] The user can use Amazon Neptune in applications that are subject to PCI compliance or require ISO certification.[29] On May 17, 2019, it was announced that Neptune achieved SSAE 16 eligibility [30]

Neptune powers graph use cases such as recommendation engines, fraud detection, knowledge graphs, drug discovery, network security, and social networking.[31]

Notable users

[edit]

Some notable customers of Amazon Neptune include, Samsung Electronics, Pearson, Intuit, Siemens, AstraZeneca, FINRA, LifeOmic, Blackfynn, and Amazon Alexa[32]

See also

[edit]

References

[edit]
  1. ^ "Amazon Neptune – A Fully Managed Graph Database Service - Amazon Web Services". Amazon Web Services. 29 November 2017.
  2. ^ a b "Accessing the Neptune Graph with Gremlin - Amazon Neptune". docs.aws.amazon.com. Retrieved 2019-05-12.
  3. ^ a b "Accessing the Neptune Graph with openCypher". docs.aws.amazon.com. Retrieved 2022-11-02.
  4. ^ a b "Accessing the Neptune Graph with SPARQL - Amazon Neptune". docs.aws.amazon.com. Retrieved 2019-05-12.
  5. ^ "AWS Announces General Availability of Amazon Neptune". Amazon Web Services. 30 May 2018.
  6. ^ "Amazon Neptune is now generally available to build fast, reliable graph applications". Amazon Web Services. 30 May 2018.
  7. ^ a b "Amazon Neptune Achieves HIPAA Eligibility". Amazon Web Services. 12 September 2018.
  8. ^ a b "Amazon Neptune Now In-Scope for PCI DSS and ISO Compliance Programs". Amazon Web Services. 12 December 2018.
  9. ^ "Blazegraph fork?". GitHub. 12 April 2018.
  10. ^ "Engine Releases for Amazon Neptune - Amazon Neptune". docs.aws.amazon.com. Retrieved 2019-04-29.
  11. ^ "Amazon Neptune Features". Amazon Web Services, Inc. Retrieved 2019-05-12.
  12. ^ "Configuring Security in Amazon Neptune - Amazon Neptune". docs.aws.amazon.com. Retrieved 2019-04-29.
  13. ^ "Amazon Neptune Storage - Amazon Neptune". docs.aws.amazon.com. Retrieved 2019-04-29.
  14. ^ "Amazon Neptune is Now Available in the Canada (Central) Region". Amazon Web Services. 30 October 2019.
  15. ^ "Amazon Neptune is Now Available in the AWS GovCloud (US-West) Region". Amazon Web Services. 14 August 2019.
  16. ^ "Amazon Neptune is Now Available in the AWS GovCloud (US-East) Region". Amazon Web Services. 21 August 2019.
  17. ^ "Amazon Neptune is Now Available in Europe (London)". Amazon Web Services. 3 October 2018.
  18. ^ "Amazon Neptune is Now Available in Europe (Frankfurt)". Amazon Web Services. 7 November 2018.
  19. ^ "Amazon Neptune is Now Available in Europe (Stockholm)". Amazon Web Services. 27 June 2019.
  20. ^ "Amazon Neptune is Now Available in Europe (Paris)". Amazon Web Services. 11 March 2020.
  21. ^ "Amazon Neptune is Now Available in Asia Pacific (Singapore)". Amazon Web Services. 13 December 2018.
  22. ^ "Amazon Neptune is Now Available in Asia Pacific (Sydney)". Amazon Web Services, Inc. Retrieved 2019-04-29.
  23. ^ "Amazon Neptune is Now Available in the Asia Pacific (Tokyo) Region". Amazon Web Services, Inc. Retrieved 2019-04-29.
  24. ^ "Amazon Neptune Now Available in Asia Pacific (Mumbai)". Amazon Web Services, Inc. Retrieved 2019-05-12.
  25. ^ "Amazon Neptune is Now Available in Asia Pacific (Seoul)". Amazon Web Services, Inc. Retrieved 2019-05-12.
  26. ^ "Amazon Neptune is now available in AWS China (Ningxia) Region, Operated by NWCD". Amazon Web Services, Inc. Retrieved 2020-01-15.
  27. ^ "Amazon Neptune is Now Available in the Middle East (Bahrain) Region". Amazon Web Services, Inc. Retrieved 2019-10-30.
  28. ^ "Amazon Neptune Pricing". Amazon Web Services, Inc. Retrieved 2019-04-29.
  29. ^ "Amazon Neptune Now In-Scope for PCI DSS and ISO Compliance Programs". Amazon Web Services, Inc. Retrieved 2019-05-12.
  30. ^ "Amazon Neptune Is Now SOC Compliant". Amazon Web Services, Inc. Retrieved 2019-05-17.
  31. ^ "Amazon Neptune - Fast, Reliable Graph Database built for the cloud". Amazon Web Services, Inc. Retrieved 2019-05-12.
  32. ^ "AWS Announces General Availability of Amazon Neptune". Amazon.com, Inc. - Press Room. 30 May 2018. Retrieved 2019-04-29.

Further reading

[edit]
[edit]