# Amazon Neptune Now Speaks IPv6 with Dual-Stack Mode!

Hey there, it's me! Today I've got a small but handy networking update for graph databases.

## What was announced?

[Amazon Neptune](https://aws.amazon.com/neptune/) now supports dual-stack mode! This was announced on the AWS What's New feed.

With dual-stack mode, your database cluster can accept connections over IPv4, IPv6, or both protocols at the same time.

## The story so far

Until now, Neptune assumed IPv4 connectivity. So if your org wanted to adopt IPv6, Neptune could be a little sticking point in the plan.

## What changes

Now you can adopt IPv6 while keeping your existing IPv4 deployments working. Clients connect using whichever protocol they prefer, and **no application changes are required**. It's a nice fit when you want to move toward IPv6 without breaking backward compatibility.

## Dive Deep

Dual-stack mode comes in two configurations:

- **Private dual-stack**: IPv6 endpoints that stay isolated from the internet, good for internal apps and private graph databases.
- **Public dual-stack**: IPv6 endpoints reachable from the internet, good for internet-facing apps and hybrid network environments.

It's available in all AWS Regions where Amazon Neptune is supported. For how to configure it, check the [Neptune setup documentation](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-setup.html).

## Wrap-up

- Amazon Neptune now supports dual-stack mode (connect over IPv4, IPv6, or both)
- Two configurations: Private dual-stack and Public dual-stack
- Clients connect with their preferred protocol, no app changes needed
- Available in all AWS Regions where Neptune is supported

This one is for the infra folks who are rolling out IPv6 or running mixed IPv4/IPv6 environments with Neptune!