AWS secondary CIDR on VPC ability to NAT to PAN in original CIDR

cancel
Showing results for 
Search instead for 
Did you mean: 

AWS secondary CIDR on VPC ability to NAT to PAN in original CIDR

Hey all,

It has finally happened and we ran out of IPv4 space on Primary CIDR block for our VPC. We created a new CIDR and associated it to the same VPC. However it appears that I can't associate an ENI in the new CIDR to our Palo Alto in the original CIDR. And we can't use the NAT ENI in the original because it hops to the original then out which AWS doesn't allow.

 

Has anyone tried this, or aware of how to work around this issue?  Thanks, Chad

1 REPLY 1

L0 Member

Hello everybody,I see that we have AWS secondary CIDR on VPC ability to NAT to PAN in original CIDR

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!