A company is migrating an application from on-premises to Amazon Elastic Kubernetes Service (Amazon EKS). The company must assign pods to custom subnets in the company's VPC to meet compliance, and ensure pods can communicate securely within that VPC. Which solution meets these requirements?

The Amazon VPC CNI plugin for Kubernetes assigns an IP address from your VPC to each pod, allowing pods to communicate directly within the VPC as if they were EC2 instances. This enables the use of custom subnets for pods, fulfilling the compliance requirement for specific network segmentation and ensuring secure communication within the VPC. Incorrect options: AWS Transit Gateway is for connecting multiple VPCs and on-premises networks, not for assigning specific subnets to individual pods within a single EKS cluster. AWS Direct Connect provides a dedicated network connection from on-premises to AWS, but it doesn't manage pod subnet assignments within EKS or solve the internal VPC communication requirement. Kubernetes network policies control pod-to-pod communication and pod anti-affinity rules prevent pods from being scheduled on the same node, but neither directly assigns pods to specific custom subnets or ensures their IP addresses come from those subnets.