There are a number of use cases where customer development teams need to rely on Network Engineering teams when working with cross dependencies of services across organizations. Each sub-team develops and manages services in its own VPC and carries out the release lifecycle. Network Engineering teams need to work with all teams to make sure teams are set up with the right controls and they are not using overlapping CIDRs, and connectivity is established using VPC Peering, AWS transit gateway, or AWS private link. Communication and dependency between teams increase significantly as the number of applications are migrated and needed to communicate. Upgrades of applications become complex as well.

With VPC Lattice, it helps to create a service network, that connects clients and services across different VPCs and accounts, taking away networking complexity and giving consistent experiences across instances, containers and serverless.

In the use case detailed here, we will show how to deploy shared services (Keycloak on EKS) in one VPC and how it can be accessed from another VPC leveraging VPC Lattice.