search

konklone / oversight.garden

Bringing together the oversight community's work.
https://oversight.garden
Creative Commons Zero v1.0 Universal
26 stars 9 forks source link

IPv6 support #165

Closed divergentdave closed 7 years ago

divergentdave commented 7 years ago

EC2 will soon support IPv6! We should make oversight.garden support IPv6 when support hits us-east-1. (watch https://console.aws.amazon.com/vpc/home?region=us-east-1#vpcs:)

divergentdave commented 7 years ago

The game is afoot! https://aws.amazon.com/blogs/aws/aws-ipv6-update-global-support-spanning-15-regions-multiple-aws-services/

divergentdave commented 7 years ago

I've manually associated IPv6 subnets with the VPC and all subnets, assigned IPv6 addresses to the running instances, and added AAAA records in Route 53 for staging.oversight.garden. Next: testing

divergentdave commented 7 years ago

That didn't work. In addition to updating the Rake tasks, I also need to add listen [::]:80;/listen [::]:443; to the nginx configuration.

divergentdave commented 7 years ago

It turns out this and #175 are blocked on EC2 Autoscaling Groups. Right now, you can only specify in launch configurations that instances are automatically assigned IPv4 addresses, and when you spin it up, instances don't get assigned IPv6 addresses.

I have half a mind to ditch the autoscaling group setup, and just use a regular instance for the web server. We aren't reaping any benefits from this, it's a pain to deal with the API differences between EC2 and EC2 ASG, and we don't actually have an ELB in front of the whole group, just a DNS record that's updated at provision time. But that's all for another day. Maybe this could be my first Terraform project?

konklone commented 7 years ago

Maybe this could be my first Terraform project?

I haven't done a ton with it myself, but my colleagues have and it's supposed to be pretty damn straightforward.