A company runs EC2 instances in a private subnet and Lambda functions that need direct network access to those EC2 instances. The application will run for at least 1 year, and the number of Lambda functions is expected to grow. The company wants to maximize savings across application resources and keep network latency low. Which solution meets these requirements?

The correct option maximizes savings and meets connectivity requirements. A Compute Savings Plan offers the most flexibility and cost savings for both EC2 instances and Lambda functions, which are explicitly mentioned as growing and running for a year. Optimizing Lambda's duration, memory, invocations, and data transfer directly reduces costs. Connecting Lambda to the private subnet ensures direct, low-latency network access to the EC2 instances without exposing them to the internet. Incorrect options: An EC2 Instance Savings Plan only covers EC2, not Lambda, missing potential savings. Connecting Lambda to a public subnet is incorrect because the EC2 instances are in a private subnet, and Lambda needs direct access to them. Keeping Lambda in the Lambda service VPC prevents direct network access to the EC2 instances in the company's VPC.