Is there a way to change the default route which points to l

Question

Is there a way to change the default route which points to local of a route table with Pulumi This is something which is possible in the API but i get errors when trying to do this with RouteTable and Route disappointed

little-cartoon-10569 · Answer

Yes but iirc you need to import the default route so you can t do it with just a single `up`

strong-helmet-83704 · Answer

ooof that is an unfortunate state of affairs if this is the only available option

little-cartoon-10569 · Answer

Yes pretty much anything where AWS knows best and creates extra resources doesn t play well with IaC

little-cartoon-10569 · Answer

It s not a Pulumi specific problem

little-cartoon-10569 · Answer

However it s safe to always ignore the default route and create a managed route to local with higher priority which sidesteps the problem

strong-helmet-83704 · Answer

I need to use the same CIDR as the default route but want it to go elsewhere

little-cartoon-10569 · Answer

Same as default VPC default NACL etc Just ignore the defaults and manage your own ones

little-cartoon-10569 · Answer

I don t think that ll be a problem

strong-helmet-83704 · Answer

can i deploy a route table and instruct it to not produce a route at all

little-cartoon-10569 · Answer

Just set up the Route and RouteTableAssociation in the normal way as if the default route wasn t there

little-cartoon-10569 · Answer

Not sure thinking face

little-cartoon-10569 · Answer

The default route doesn t have a CIDR does it Other than 0 0 0 0

strong-helmet-83704 · Answer

I might be able to deploy more specific targets but that only sidesteps the problem

strong-helmet-83704 · Answer

yea it has the same cidr as the vpc by default

little-cartoon-10569 · Answer

Ah you said default route you mean default RouteTable

little-cartoon-10569 · Answer

Don t use the default RouteTable Ignore it Don t associate it with any subnets This is a standard rule for all IaC

strong-helmet-83704 · Answer

uhh yes route inside the routetable when its generated

little-cartoon-10569 · Answer

Just don t use that RouteTable Create your own ones

strong-helmet-83704 · Answer

hmmm ok we may have gotten confused

little-cartoon-10569 · Answer

The default RouteTable isn t used by anything except the default subnet and you shouldn t be using that

strong-helmet-83704 · Answer

i am generating a brand new route table it comes with a local route i can t seem to update that route

little-cartoon-10569 · Answer

I think I m missing something Checking my own Pulumi created resources

strong-helmet-83704 · Answer

```error creating Route in Route Table rtb x with destination 10 1 130 0 24 RouteAlreadyExists The route identified by 10 1 130 0 24 already exists ```

strong-helmet-83704 · Answer

I think you were right when you said that Pulumi is not aware of the local route created when the route table is created

strong-helmet-83704 · Answer

perhaps we can perform an inline import of that route and then replace it

little-cartoon-10569 · Answer

No I don t think so You can use the AWS SDK to make the change after Pulumi has finished doing its thing

little-cartoon-10569 · Answer

You can also create another RouteTable with the correct route defined inline rather than via Route RouteTableAssoication not certain that d work but it might

little-cartoon-10569 · Answer

I ve been looking through the AWS SDK to see if there s a different API for the default route but there isn t It s just a regular route that s set up by AWS

little-cartoon-10569 · Answer

Grr

strong-helmet-83704 · Answer

Tested that same error RouteAlreadyExists

little-cartoon-10569 · Answer

In fact it s a documented feature that if you create a RouteTable with inline routes then set up Route RouteTableAssociation routes then all the inline routes are overwritten you might be able to make that work to your advantage just define a dummy useless inline route then set up all the real routes using Route <https www pulumi com registry packages aws api docs ec2 routetable > gt NOTE on Route Tables and Routes This provider currently provides both a standalone Route resource and a Route Table resource with routes defined in line At this time you cannot use a Route Table with in line routes in conjunction with any Route resources Doing so will cause a conflict of rule settings and will overwrite rules

strong-helmet-83704 · Answer

I can try

little-cartoon-10569 · Answer

I have a question about why you d want this though normally if you want to redirect traffic through a VPC to another one you d set up either a virtual gateway or peering Would either of those options be better

strong-helmet-83704 · Answer

this is for an igw which sits in front of a firewall All local traffic coming back from the igw should be sent back to the vpce firewall

strong-helmet-83704 · Answer

i THINK with my architecture i m gonna need to use more specific subnet routes to redirect traffic to respective AZ s anyhow So that will be a good workaround

little-cartoon-10569 · Answer

Is the VPCE not inside a subnet You shouldn t need to bother with the default route if the device is in an AWS subnet right

strong-helmet-83704 · Answer

the igw exists only at the vpc level It needs a route table edge association to send traffic specifically back to the vpce