External gRPC clients carry JWTs, but Amazon VPC Lattice trusts SigV4 signatures. This post shows how to build an ingress layer where an Application Load Balancer validates JWTs and an Amazon ECS proxy translates that identity into SigV4, enforcing per-service authorization with VPC Lattice auth policies while preserving gRPC over HTTP/2 end-to-end.