Closed Bug 1393241 Opened 7 years ago Closed 7 years ago

Roll the default VPC in each region over to a new, VPN enabled VPC

Categories

(Taskcluster :: Services, enhancement)

Product:
Taskcluster
Component:
Services
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: dustin, Assigned: dustin)

References

Details

Per https://bugzilla.mozilla.org/show_bug.cgi?id=1387540#c9 this will require draining and deleting the old VPC first. That will be trickier for some regions than others (e.g., we run docker cloud and a bunch of windows stuff in us-west-2).
I'm going to disable eu-central-1 in ALLOWED_REGIONS now and let it drain. There are no non-worker instances in this VPC, happily.
Worth noting, creating a default VPC creates the default subnets for you. Hopefully those will be suitable! Also, terraform can't create default VPCs, so it won't be any use to us.
A default VPC doesn't even let you set the IPv4 CIDR for it. This won't work. (I just tried it in Sao Paolo)
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Component: AWS-Provisioner → Services
You need to log in before you can comment on or make changes to this bug.