AWS VPC无法将路由规则删除到不存在的IP范围

我一直在研究整个上午,但是这似乎超出了我对AWS VPC的了解。

我们拥有一个带有一系列VPC的旧AWS账户。这些是几年前创建的。我担心的VPC可能很老,只有6岁。现有的VPC为:

eu-west-1 (Ireland)

  • I1: 172.31.0.0/16
  • I2: 172.102.0.0/16
  • I3: 172.201.0.0/16
  • I4: 192.168.96.0/20

us-west-2 (Oregon)

  • O1: 192.168.0.144/20

The VPC I'm working with is I1: 172.31.0.0/16.

I1 and O1 Are peered.

正确,我现在有了一个新帐户,在俄勒冈州创建了一个新的VPC。叫它吧

  • NO1: 10.1.0.0/20

I have peered O1 and NO1. Peering works fine and the route tables do too.

The issue comes when I peered I1 and NO1.

  • Creating the peered connection was fine.
  • Adding rules to the NO1 route table worked fine.

My concern is the following: when I go to modify the route table for I1 I see the following rules.

  • 172.31.0.0/16 local active (that's the IP range set for this VPC, expected)
  • 10.0.0.0/8 local active (This is my issue)
  • 0.0.0.0/0 inet active
  • Some other existing rules...

I don't understand the 10.0.0.0/8 rule. The full IP range is being routed internally and:

  • 这不在VPC的IP范围内
  • 万一我丢失了某些东西,我检查了所有可以找到的VPC和子网。该IP范围没有任何内容。

When I went to modify the route table the 172.31.0.0/16 and the 10.0.0.0/8 rules cannot be deleted so I can only assume they were created by default.

My question is, how can this rule be active when the IP range is "non-existent"? Why I cannot delete this? I've never seen this range being added by default to a route table, is this something maybe AWS used to do ages ago?

I've added a rule 10.1.0.0/20 routing traffic to my peered VPC. I'm hoping since it's more specific it will work fine. Am I right to think that?