Hello, I am having a lot of issues with machine scoped egress-ip, which is now being deprecated. I was wondering if migrating to app-scoped will let us use the same IP class of 209.71.*.*
You can keep your existing machine-scoped egress IPs while migrating by following these instructions.
Okay, thank you very much for the answer. I’ll give it a shot.
If it’s possible, it would be probably useful if this were mentioned as well specifically in the docs that the app would maintain the same IP class as the machines.
I’m not sure what is meant by “the same IP class”. The docs already mention that it is possible to migrate a machine-scoped egress IP to app-scoped.
If you mean whether these IPs are from the same /16, then unfortunately no, there is no guarantee even within machine egress IPs that they’re all from the same /16. In practice most regions have only a number of /24s to allocate from (smaller regions may even only have a couple), but we can and will always add new blocks to regions when our pools run out.
Right now the third party is checking that the IP starts with 209.71, which means that anything in this range 209.71.*.* is fine for us. What I hope to accomplish by migrating to app-scoped is maintain the same ip addresses (or atleast in the 209.71 range) so that we would not run into issues.
if you migrate machine-scoped egress IPs to app-scoped, you keep the same IP address(es); that’s the point of migrating the IP you already have vs. deleting and recreating it.
Got it.
Thank you both for the support