A company is modernizing a legacy application by refactoring its API into a serverless architecture using Amazon API Gateway and AWS Lambda. The backend will be accessed by Amazon EC2 instances residing in a private VPC subnet. The solutions architect must ensure that traffic between the EC2 instances and the API Gateway does not traverse the public internet, and that a sudden burst of requests to this specific Lambda function does not exhaust the regional concurrency pool, which would impact other critical workloads in the same AWS account. Which TWO configurations should the solutions architect implement to meet these requirements? (Select TWO.)
- Configure reserved concurrency for the AWS Lambda function.Cevap
- Create an interface VPC endpoint for Amazon API Gateway in the VPC.Cevap
- CConfigure provisioned concurrency for the AWS Lambda function.
- DRoute outbound API traffic from the private subnet through a single NAT Gateway in a public subnet.
- EEnable a Canary deployment strategy in AWS CodeDeploy for the Lambda function.
Cevap
Configuring reserved concurrency for the AWS Lambda function and creating an interface VPC endpoint for Amazon API Gateway in the VPC.
The correct configurations involve setting up an interface VPC endpoint for API Gateway to ensure traffic remains entirely within the AWS network without traversing the public internet, and configuring reserved concurrency on the Lambda function to cap its execution scale so that a burst in traffic does not deplete the account's shared regional concurrency limit.
Adım Adım Çözüm
Anahtar Kavram
Using AWS PrivateLink (interface VPC endpoints) for secure private API access, and AWS Lambda reserved concurrency to limit scaling and protect the AWS account's regional concurrency limit.