for people and machines? There are two types of identities you need to manage when approaching operating secure AWS workloads. Understanding the type of identity you need to manage and grant access helps you verify the right identities have access to the right resources under the right conditions. …
❤ ECS, EKS and Fargate ❤ Container Tooling 💔 Scale to zero is hard ❤ Most efficient and sustainable ❤ Little administration 💔 Tight coupling 💔 NAT GW + CW Logs
Serverless APIs High-throughput ingress Latency Higher Low Very low Cost $$$ $ (cheapest API GW) $ (best at scale) Routing Advanced Basic host/path Auth IAM, Cognito, custom IAM, JWT (OIDC) OIDC (limited) Transformations Full (VTL) Limited None Throttling Fine-grained Basic None Timeout Throttle quota per account, per Region across HTTP APIs, REST APIs, WebSocket APIs, and WebSocket callback APIs Up to 4k secs (+-1h) When to Choose API routing All you need is Lambda No “middle man”
Integration • Smart Infrastructure as Code, able to perform CloudFront Continuous Deployment and Multi-Tenant Distributions • Simple authentication and authorization for common OIDC Providers and Frameworks