Amazon Neptune Database now supports Graviton3-based R7g and Graviton4-based R8g instances for Amazon Neptune engine versions 1.4.5 or above, in Asia Pacific (Hong Kong), Asia Pacific (Osaka), Asia Pacific (Singapore), Canada (Central) and US West (N. California). R7g and R8g instances are priced -16% vs R6g.
Graviton3-based R7g are the first AWS database instances to feature the latest DDR5 memory, enabling high-speed access to data in memory. R7g database instances offer up to 30Gbps enhanced networking bandwidth and up to 20 Gbps of bandwidth to the Amazon Elastic Block Store (Amazon EBS). Graviton4-based R8g instances offer larger instance sizes, up to 48xlarge and features an 8:1 ratio of memory to vCPU, and the latest DDR5 memory. AWS Graviton4 processors are up to 40% faster for databases than AWS Graviton3 processors.
You can launch R7g and R8g instances for Neptune using the AWS Management Console or using the AWS CLI. Upgrading a Neptune cluster to R7g or R8g instances requires a simple instance type modification for Neptune engine versions 1.4.5 or higher. For more information on pricing and regional availability, refer to the Amazon Neptune pricing page.
Categories: marketing:marchitecture/databases,general:products/amazon-neptune
Source: Amazon Web Services
Latest Posts
- Amazon Neptune Database now supports R7g and R8g instances in 5 additional regions

- Amazon EC2 X8aedz instances are now available in Asia Pacific (Mumbai, Seoul) regions

- (Updated) Consult and merge into a meeting or group call via Dual-Tone Multi-Frequency (DTMF) [MC1183611]
![(Updated) Consult and merge into a meeting or group call via Dual-Tone Multi-Frequency (DTMF) [MC1183611] 4 pexels mareefe 1638280](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)
- (Updated) Microsoft Teams: Channel agent orchestration with GitHub, Asana, and Jira via Model Context Protocol (MCP) [MC1182703]
![(Updated) Microsoft Teams: Channel agent orchestration with GitHub, Asana, and Jira via Model Context Protocol (MCP) [MC1182703] 5 pexels cottonbro 4904564](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)



![(Updated) Consult and merge into a meeting or group call via Dual-Tone Multi-Frequency (DTMF) [MC1183611] 4 pexels mareefe 1638280](https://mwpro.co.uk/wp-content/uploads/2025/06/pexels-mareefe-1638280-150x150.webp)
![(Updated) Microsoft Teams: Channel agent orchestration with GitHub, Asana, and Jira via Model Context Protocol (MCP) [MC1182703] 5 pexels cottonbro 4904564](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-cottonbro-4904564-150x150.webp)