Support for IPv6 with public runners
I am trying to run a IPv6 only VPC on AWS, when running a OpenTofu stack with Ansible stack, I am failing to connect to the EC2 instance.
- Workaround
I am trying to run a IPv6 only VPC on AWS, when running a OpenTofu stack with Ansible stack, I am failing to connect to the EC2 instance.
Log in to comment and vote
Comments1
Natalia Gazda
Aug 5, 2025
Hey there!
Thanks for sharing this use case.
I can see you're running into connectivity issues with IPv6-only VPCs when using our public runners. Good news is that Spacelift already has a solution for this: private worker pools!
Private workers run in your own infrastructure where you have complete control over the networking configuration, including full IPv6 support. This is actually the recommended approach for any specialized networking requirements since it gives you the flexibility to configure things exactly as your environment needs.
Since you've already found that provisioning a public IPv4 address works as a workaround, that's probably your quickest fix if you want to stick with public runners. But for a proper IPv6-only setup, private workers are definitely the way to go.
Here's our documentation on setting up private worker pools: https://docs.spacelift.io/concepts/worker-pools
We also have Terraform modules that make it super easy to deploy:
AWS: https://github.com/spacelift-io/terraform-aws-spacelift-workerpool-on-ec2
If you're using Kubernetes: https://docs.spacelift.io/concepts/worker-pools/kubernetes-workers
Would private workers work for your use case? Happy to help if you have any questions about getting them set up!