A company runs its application by using Amazon EC2 instances and AWS Lambda functions. The EC2 instances run in private subnets of a VPC. The Lambda functions need direct network access to the EC2 instances for the application to work.
The application will run for 1 year. The number of Lambda functions that the application uses will increase during the 1-year period. The company must minimize costs on all application resources.
Which solution will meet these requirements?
To meet the requirement of minimizing costs while ensuring direct network access between Lambda functions and EC2 instances in private subnets, a Compute Savings Plan is the best solution. A Compute Savings Plan offers flexibility across different AWS services, including EC2 instances and Lambda functions, providing significant cost savings over on-demand pricing. Connecting the Lambda functions to the private subnets ensures direct access to the EC2 instances, maintaining security and avoiding potential egress costs.
Compute Savings Plan: This plan offers significant discounts on Lambda functions compared to on-demand pricing. Since the application will run for a year, a sustained use discount like Compute Savings Plan is ideal. Private Subnets: Lambda functions in private subnets can directly access EC2 instances within the VPC without needing internet access, reducing security risks and potential egress costs.
In this question has point out "access EC2 instances" within VPC,=> Lambda VPC to an ENI (Elastic network interface) in your account VPC.=>No charge. Therefore I stick with A, Not D.
I am sorry I mean C
AnswerD https://docs.aws.amazon.com/lambda/latest/dg/foundation-networking.html
I confuse this Question. Instance saving plan is cheaper than compute saving plan. https://aws.amazon.com/savingsplans/compute-pricing/
But composite saving plan discount Automatically applies to Lambda.
Sorry I mean Compute Savings Plan.