Every time you add a new CIDR to your VPC - it's auto added to the Main route table and subsequent route tables you create with target being "local" - which you could only modify the target as mentioned earlier. For any other destination not in your VPC you should be able to remove it; you "can't" add a destination (routes outside your VPC) in your route table with target being "local" to begin with, since you will encounter an error. Please share an illustration of the routes in your table along with the CIDR of your VPC
You can only modify routes that you've added. The local routes (VPC CIDR) are auto added in the "Main" table, which you can't remove, but can change the destination to be instance GWLBe, Network Interface...
Hi Jules, thanks for your answer. I read similar explanations before, however that doesn't apply to this case. The route wasn't auto added, I added it myself after creating a new CIDR (in order to reproduce/clarify the effect/situation I have seen on another system).
Using Designer to connect a route table to a subnetAccepted Answerasked 5 months ago
How to get Subnet's associated Route Table ID in CloudFormation?Accepted Answerasked 2 years ago
TGW Route Table entriesAccepted Answerasked 2 years ago
Remove local target from AWS Route TableAccepted Answerasked a month ago
Understanding route table to NAT GatewayAccepted Answerasked 2 years ago
The route for the VPC not showing in iproute2 when a subnet has different maskAccepted Answerasked 6 months ago
how to enable route propagation in the routing tablesasked 2 months ago
Subnets associated with a route table show as not associated with any RTasked 3 years ago
What is the VPC subnet route priority when two targets have the same default 0.0.0.0/0 route as the destination?Accepted Answerasked 2 years ago
cloud-init not setting default route to NAT Gatewayasked 2 years ago