Amazon Neptune

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Lua error in package.lua at line 80: module 'strict' not found. 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, and SPARQL,[3] including other Amazon Web Services products.

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

History

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

History of Amazon Neptune engine releases[9]
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

External support

Amazon Neptune supports the open source Apache TinkerPop Gremlin[2] graph traversal language, openCypher query language for property graphs, and the W3C standard Resource Description Framework's (RDF) SPARQL[3] 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.[10]

Security

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).[11]

Storage

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.[12]

Availability

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

Pricing

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).[27]

Application

On September 12, 2018, it was announced that Neptune achieved HIPAA eligibility[6] 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.[7] The user can use Amazon Neptune in applications that are subject to PCI compliance or require ISO certification.[28] On May 17, 2019, it was announced that Neptune achieved SSAE 16 eligibility [29]

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

Notable users

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

See also

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.

Further reading

  • Lua error in package.lua at line 80: module 'strict' not found.

External links