IPv6 addressing with Amazon Redshift

December 18, 2025

5

As we witness the gradual transition from IPv4 to IPv6, Amazon Internet Companies (AWS) continues to broaden its help for dual-stack networking throughout its service portfolio. On this put up, we present how one can migrate your Amazon Redshift Serverless workgroup from IPv4-only to dual-stack mode, so you can also make your knowledge warehouse future prepared.

An IP tackle serves as a digital id for units linked to the web. This distinctive numerical identifier allows units to speak throughout IP-based networks, facilitating the alternate of knowledge packets between supply and vacation spot.

In the present day’s web operates on two IP variations:

IPv4 – The standard 32-bit addressing system (reminiscent of 192.168.0.22) that has powered web communications for over three many years. With roughly 4 billion doable addresses (2³²), IPv4’s limitations have change into more and more obvious as our digital surroundings expands.
IPv6 – The following-generation 128-bit addressing system (reminiscent of 2606:4700::6810:787f) presents an astronomical variety of distinctive addresses (340 undecillion or 2¹²⁸). This nearly limitless tackle area is designed to accommodate the explosive development of internet-connected units.

Within the case of Amazon Redshift, dual-stack networking permits Redshift workgroups to speak over each IPv4 and IPv6 protocols concurrently. This networking structure permits Redshift workgroups to be accessible utilizing each IPv4 and IPv6 addresses, offering larger flexibility and future-proofing for community communications. Twin-stack networking gives the next benefits:

Future-proofing – Facilitates compatibility with each IPv4 methods and fashionable IPv6 networks
Enhanced connectivity – Supplies extra versatile networking choices for various shopper functions

Allow dual-stack networking for Amazon Redshift

An Amazon Redshift workgroup working in dual-stack mode has each IPv4 and IPv6 addresses related to the database endpoints. We’ve launched a brand new API subject known as ipAddressTypewithin the Amazon Redshift API that offers you direct management over your workgroup’s community configuration. Now you can particularly select whether or not your Amazon Redshift occasion operates in IPv4-only mode or dual-stack mode. For full implementation particulars, seek advice from the ipAddressType parameter within the Amazon Redshift API Reference.

Greatest apply

When implementing dual-stack networking in Amazon Redshift, deploy your workgroups in non-public subnets with digital non-public cloud (VPC) endpoints for optimum safety and compatibility. This method aligns with the present Amazon Redshift help mannequin, which requires dual-stack databases to function in non-public mode solely. Amazon Redshift doesn’t at present help databases with IPv6-only endpoints or publicly accessible dual-stack situations.

Conditions

To implement dual-stack networking in Amazon Redshift, you’ll want to have the next stipulations:

An current Amazon Redshift serverless workgroups working in IPv4-only mode that you simply wish to convert to dual-stack mode
Administrative permissions to switch Amazon Redshift workgroup community configurations
VPC with each IPv4 and IPv6 CIDR blocks assigned

Allow IPv6 help in your VPC subnets

Earlier than migrating your Amazon Redshift Serverless workgroup to dual-stack mode, you have to first ensure your VPC subnets help IPv6 addressing. On this part, we stroll by way of the method of enabling IPv6 CIDR blocks to your VPC.

Current VPC Subnets

To allow dual-stack mode in your current VPC comply with these 5 high-level steps:

Entry the VPC dashboard
Navigate to the subnet settings
Add the IPv6 CIDR block
Repeat for the required subnets
Confirm IPv6 CIDR affiliation

To entry the VPC dashboard:

Sign up to your account on the AWS Administration Console
Within the search bar on the prime, kind VPC
Select VPC from the dropdown checklist to navigate to the Amazon Digital Personal Cloud (Amazon VPC) dashboard

To navigate to subnet settings:

Within the left navigation panel underneath Digital non-public cloud, select Subnets
From the subnet checklist, determine and choose the subnet(s) that your Amazon Redshift Serverless workgroup makes use of or will use

So as to add the IPv6 CIDR block:

Along with your subnet chosen, select Actions within the dropdown checklist
Select Edit IPv6 CIDRs from the obtainable choices
Within the configuration panel that seems, select Add IPv6 CIDR
The system will mechanically recommend an acceptable IPv6 CIDR block allocation
Select Save to use the modifications

Repeat for the required subnets. You have to modify the subnets throughout the VPC that might be utilized by your Amazon Redshift assets. Repeat high-level steps 2–3 for every subnet in your Amazon Redshift subnet group.

Confirm the IPv6 CIDR affiliation. After finishing the configuration, confirm that every subnet shows each IPv4 and IPv6 CIDR blocks within the subnet particulars. Your subnet particulars ought to present one thing like the next snippet:IPv4 CIDR: 10.0.0.0/24IPv6 CIDR: 2600:1f16:c72:9d00::/64

After you’ve efficiently configured IPv6 CIDR blocks for the related subnets, you’re able to proceed with enabling dual-stack mode in your Amazon Redshift Serverless workgroup.

New VPC Subnets

To allow dual-stack mode in a brand new VPC, comply with these steps:

To create a dual-stack VPC, add the --amazon-provided-ipv6-cidr-block possibility so as to add an Amazon supplied IPv6 CIDR block, as proven within the following instance:
```
aws ec2 create-vpc --cidr-block 10.0.0.0/24 
--amazon-provided-ipv6-cidr-block 
--query Vpc.VpcId 
--output textual content
```
[Dual stack VPC] Get the IPv6 CIDR block that’s related together with your VPC through the use of the next describe-vpcs command:
```
aws ec2 describe-vpcs --vpc-id vpcxxxxx 
--query Vpcs[].Ipv6CidrBlockAssociationSet[].Ipv6CidrBlock 
--output textual content
```

Should you created a dual-stack VPC, you need to use the --ipv6-cidr-block choice to create a twin stack subnet, as proven within the following command:

aws ec2 create-subnet --vpc-id vpc-xxx 
--cidr-block 10.0.1.0/20 
--ipv6-cidr-block 2600:1f13:cfe:3600::/64 
--availability-zone us-east-2a 
--query Subnet.SubnetId 
--output textual content

Migrate an current Amazon Redshift Serverless workgroup from IPv4 to IPv6

To allow dual-stack mode to your Amazon Redshift Serverless workgroup, comply with these 5 high-level steps:

Entry Amazon Redshift Serverless
Choose your workgroup
Entry community and safety settings
Allow dual-stack mode
Confirm the configuration

To entry Amazon Redshift Serverless:

Sign up to AWS Administration Console utilizing your credentials.
Within the search bar on the prime of the console, enter Redshift.
Select Amazon Redshift within the dropdown checklist. This may take you to the Amazon Redshift dashboard. Affirm Be sure to’re on the Redshift Serverless dashboard view

To pick your workgroup:

Within the Redshift Serverless dashboard, find the Workgroups part
Choose the title of the particular workgroup you wish to modify

To entry community and safety settings:

On the workgroup particulars web page, find the horizontal navigation tabs
Subsequent to the Question and database monitoring part, select the Information entry tab
Select Edit to entry the Edit community and safety web page

To allow dual-stack mode:

Within the community settings part, find the IP tackle kind choices
Select Twin-stack mode. This allows connectivity for each IPv4 and IPv6
Select Save modifications on the backside of the web page

To confirm the configuration:

After the modifications are utilized, you’ll be returned to the workgroup particulars web page. Affirm that your workgroup now shows Twin-stack mode in its community settings, as proven within the following screenshot.

Your Amazon Redshift Serverless workgroup is now configured to help each IPv4 and IPv6 site visitors. This configuration permits your Redshift Serverless workgroup to speak over each IPv4 and IPv6 protocols, offering larger flexibility to your community connectivity choices.

Entry Redshift dual-stack serverless workgroups

Redshift dual-stack workgroups keep the identical entry strategies no matter whether or not you’re connecting utilizing IPv4 or IPv6. Your current connection endpoints stay unchanged.

To entry a Redshift dual-stack workgroups from an Amazon Elastic Compute Cloud (Amazon EC2) occasion, comply with these steps:

Create an IPv4 EC2 occasion.
Add the related EC2 safety group to your Redshift workgroup’s safety group inbound guidelines.
Connect with your EC2 occasion. Log in to your EC2 occasion on the AWS console to put in the psql shopper to check the database connectivity. Enter the next instructions from the terminal window:
```
# Replace your system packages
sudo dnf replace -y
# Set up the PostgreSQL 15 repository
sudo dnf set up -y postgresql15
# Confirm the set up
psql –model
```
Connect with your Redshift workgroup utilizing software person
```
psql -h your-redshift-endpoint -U your-username -d your-database -p 5439
```
Enter password when prompted
Enter pattern queries, as proven within the following:
```
SELECT * FROM your_table LIMIT 10;
```

Validate the IPv4 connection utilizing the next SQL by changing your related IPv4 EC2 occasion IP tackle:

SELECT * FROM sys_connection_log the place user_name="admin" 
and remote_host like '%172.31.83.132%' order by record_time desc;

Execute an identical validation steps in your IPv6-enabled EC2 occasion to confirm that every one performance operates appropriately with the IPv6 protocol stack utilizing the previous instructions.

Create dual-stack mode in Amazon Redshift Serverless utilizing AWS CLI

You possibly can create a brand new dual-stack mode in Amazon Redshift Serverless utilizing AWS Command Line Interface (AWS CLI). Observe these high-level steps:

Create a namespace
Create a workgroup
Confirm the workgroup is about up in dual-stack mode

To create namespace, enter the next code:

export AWS_USE_DUALSTACK_ENDPOINT=true
aws redshift-serverless create-namespace 
--region us-east-1 
--namespace-name ipv6-demo 
--admin-username xxx  
--admin-user-password "yyyyyyy"

To create workgroup, enter the next code:

aws redshift-serverless create-workgroup 
--workgroup-name ipv6-demo-wg 
--namespace-name ipv6-demo 
--region us-east-1 
--subnet-ids subnet-ppppppp subnet-qqqqqq 
--ip-address-type dualstack

To confirm the workgroup is about up in dual-stack mode, seek advice from the steps within the earlier part.

Clear up

To wash up your assets, full the next steps:

On the Amazon Redshift Serverless console, delete the Amazon Redshift workgroups and namespaces
On the Amazon EC2 console, terminate the EC2 situations

Conclusion

On this put up, we’ve explored the potential of Amazon Redshift Serverless to help IPv6 addressing by way of dual-stack mode, marking a big development within the AWS knowledge warehouse networking flexibility.

We’ve walked by way of the whole migration journey, from making ready your VPC subnets with IPv6 CIDR blocks to configuring your Amazon Redshift Serverless workgroup for dual-stack operation. The method is easy. Though IPv6-only configurations aren’t but supported for Amazon Redshift, the dual-stack method gives a super transition path, sustaining compatibility with current IPv4 methods whereas introducing IPv6 capabilities. Do not forget that dual-stack configurations are at present restricted to personal entry mode, with public accessibility not but supported for dual-stack situations.

By migrating to dual-stack mode now, you can also make certain your Amazon Redshift surroundings stays optimally linked, addressable, and able to help your group’s knowledge analytics wants properly into the long run—no matter how web addressing protocols proceed to evolve.

In case you have questions or options on the content material lined on this put up, depart them within the feedback part.