#9340 Create egress only internet gateways for ipv6 traffic on AWS
Closed: Invalid 3 years ago by mobrien. Opened 3 years ago by mobrien.

Describe what you would like us to do:


Each VPC which wants to use ipv6 traffic needs an egress only internet gateway created and added to its route table. I don't have the permissions to create them and they are required for the following VPCs

VPC Region Name Region code Route Table
vpc-cd8a3faa Sinagpore ap-southeast-1 rtb-260e2541
vpc-bb5218d2 London eu-west-2 rtb-0a83a063
vpc-91c925f8 Mumbai ap-south-1 rtb-8432deed
vpc-f5ec089c CapeTown af-south-1 rtb-2dec0844
vpc-024f01aa49fca8b36 Soa paulo sa-east-1 rtb-08bf42410411b855b

Entries will need to be created in corresponding route tables once the gateways are created with the route ::/0 pointing to the new gateway.

This should stop all the alerts for proxies on the external nagios as they try to communicate over ipv6

When do you need this to be done by? (YYYY/MM/DD)


Whenever


Metadata Update from @mohanboddu:
- Issue assigned to kevin
- Issue tagged with: medium-gain, medium-trouble, ops

3 years ago

Don't we want a normal internet gateway? These proxies will be reachable by clients on ipv6 right?

I tried to get the ap-southeast-1 one working... without much luck. ;(

Perhaps tomorrow we could meet on irc and try and debug it further?

As usual kevin you are correct. I misdiagnosed the issue. I'm going to close this as invalid.

Metadata Update from @mobrien:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata
Boards 1
ops Status: Done