Friday, July 2, 2021

[rant] I'm getting so sick of cloud networking services that don't support basic networking functions. Advice for a Prisma <> AWS VPC connection?

The more I try and move into the cloud, the more I hate these cloud services. Everything gets abstracted away into a black box that inevitably doesn't have any of the capabilities you'd expect, and sometimes not even the capabilities they advertise in their slick marketing pitches.

Latest frustration is trying to get Prisma integrated into our environment; we're kinda hybrid with some servers on-prem and some on our AWS VPC. Remote users need to access both. Prisma says it supports service connections to AWS, and that it supports BGP, should be great right?

Not so fast. Prisma doesn't support any kind of BGP Route filtering, or metric tuning, path prepend, anything that you'd actually expect for a service that claims to support BGP. You have to either send ALL of the routes in your Prisma route table to AWS, or nothing. Their excuse is to just do static routing on the other side . . . but AWS doesn't support static routes to individual connections (only to the Virtual Gateway).

So now I'm in this situation of Prisma saying “We don’t support BGP route filtering, use static routes” and AWS saying “We don’t support static routes, use BGP route filtering”.

internal screaming

Motherfucking fuckitty fuck I just want a router that will actually do router things.



No comments:

Post a Comment