A company has deployed an application that consists of microservices running on AWS Lambda and Amazon Elastic Kubernetes Service (Amazon EKS). Separate teams support each microservice and the company uses multiple AWS accounts, giving each team its own account. A solutions architect must design service-to-service communication over HTTPS (port 443) and provide a service registry for discovery with the least administrative overhead. Which solution meets these requirements?

VPC Lattice is the most suitable solution because it simplifies service-to-service communication across multiple accounts and VPCs with minimal overhead. It provides a service network that automatically handles service discovery, traffic management, and access control for microservices over HTTPS. By associating microservices and VPCs with the service network, VPC Lattice ensures secure and efficient communication without complex networking configurations. The other options are less efficient or suitable: An inspection VPC with AWS Network Firewall adds significant administrative overhead for managing firewall rules and routing for every service-to-service interaction. Using Network Load Balancers and AWS PrivateLink for every microservice creates a high administrative burden due to the need to manage multiple NLBs, endpoint services, and interface endpoints. VPC peering connections require manual route table updates and security group management for every pair of VPCs, which becomes unmanageable with many microservices and accounts.