The document discusses the integration of API Gateway with internal Elastic Load Balancers (ELB) and addresses key considerations such as architecture, security, cost, and performance. It emphasizes that AWS Lambda allows for serverless execution of code, scaling automatically and billing only for compute used. Security aspects highlight that API Gateway requires explicit permissions to invoke Lambda functions, along with performance impacts on response times.

1. Integrating API Gateway and
internal ELB
Juan Cruz Díaz
DevOps @ DinoCloud

2. • Case architecture overview
• Problem context
• Proxying request from the world
• Security consideration
• Cost
• Performance concerns
• Demo
Agenda

3. Case architecture overview

4. Problem Context
• API Service, more than one service behind Api Gateway
• Not multi access point to same service
• IP source white list are not allowed
• AWS limitations? Api Gw + internal ELB is not possible

5. Case architecture overview

6. What is Lambda?
AWS Lambda lets you run code without provisioning or managing servers.
You pay only for the compute time you consume. There is no charge when
your code is not running.
Continuous Scaling. AWS Lambda automatically scales your application by
running code in response to each trigger. Your code runs in parallel and
processes each trigger individually, scaling precisely with the size of the
workload.

7. • Permissions for your Lambda function. It grants your Lambda function
access to particular AWS managed services or infrastructure (Create Logs,
Access DynamoDB, send SQS message etc.).
• Amazon API Gateway Lambda function invocation permission, API GW
cannot invoke your Lambda function without explicit permission to do that.
Security considerations

8. Cost

9. Performance concerns
20 % response time