Skip to Content
Cloud Engineering Academy
4. API Development & Integration

Module 4 cheat sheet

One-page revision summary for API Development & Integration: services, Azure mapping, CLI commands, limits, decision rules, exam traps and cost traps.

DVA-C03SAA-C03SCS-C03

Assumes: AWS CLI v2 · AWS SDK for .NET v4 · .NET 10 · Microsoft.Extensions.Http.Resilience · Region us-east-1 · facts as stated in the Module 4 lessons; items marked VERIFY there are not repeated as certain here. Verified against official sources on 2026-11-18.

A printable summary of Module 4. Each row links back to the lesson with the detail.

Key services

ServiceWhat it is for
API Gateway REST APIFull feature set: WAF, API keys and usage plans, caching, request validation, private endpoints, response streaming
API Gateway HTTP APICheaper and simpler: JWT authorizers, Lambda and private integrations; no WAF, keys or request validation
API Gateway WebSocket APIServer push over persistent connections
Amazon Cognito user poolsIssues OIDC/OAuth 2.0 tokens; resource servers define custom scopes
Lambda authorizerCustom credential checks; returns a cached IAM policy and context
IAM + SigV4, mTLSMachine identity: IAM inside AWS, client certificates for outside partners
VPC link (V2)Private route from API Gateway to ALB/NLB and ECS tasks
AWS WAFManaged rules and rate-based rules in front of REST APIs, ALB, CloudFront
DynamoDB + TTLIdempotency store using conditional writes
SQS + DLQAcknowledge webhooks fast, process later
Transfer FamilyManaged SFTP into S3 for partner files
Amazon MQLegacy JMS/AMQP protocol compatibility (not IBM MQ)

.NET / Azure → AWS

Microsoft / AzureAWS
Azure API ManagementAPI Gateway (REST / HTTP / WebSocket)
APIM rate-limit policyStage/method throttling, usage plans, WAF rate rules
Entra ID / B2CCognito user pools
[Authorize] JWT bearerGateway JWT/Cognito authorizer plus ASP.NET Core policies
Managed identity calling AzureIAM role + SigV4 (SDK signs for you)
Private EndpointPrivate REST API, VPC link, PrivateLink
Front Door WAFAWS WAF web ACL
Polly / HttpClientFactoryMicrosoft.Extensions.Http.Resilience (unchanged)
Service Bus bridgeSQS, Amazon MQ
Blob SFTPTransfer Family

Most useful CLI commands

TaskCommand
Who am I?aws sts get-caller-identity --profile learn-sandbox
Find HTTP APIsaws apigatewayv2 get-apis
Stage throttlingaws apigateway update-stage --rest-api-id ID --stage-name learn --patch-operations ...
Gateway error shapesaws apigateway put-gateway-response ...
Redeploy after changesaws apigateway create-deployment --rest-api-id ID --stage-name learn
Idempotency TTLaws dynamodb update-time-to-live --table-name NAME --time-to-live-specification Enabled=true,AttributeName=expiresAt
Let API Gateway invoke Lambdaaws lambda add-permission ...
Log retentionaws logs put-retention-policy --log-group-name NAME --retention-in-days 14
Delete a REST APIaws apigateway delete-rest-api --rest-api-id ID
Anything left over?aws resourcegroupstaggingapi get-resources --tag-filters Key=Project,Values=cea-lab

Key limits and defaults

ItemValueLesson
Integration timeout29 seconds by default for REST (Regional/private can request more); streaming lifts itAPI Gateway
Payload size10 MB REST and HTTP; WebSocket 128 KB per message, 32 KB per frameAPI Gateway
Account throttle (us-east-1)10,000 requests per second steady, 5,000 burst, shared by all API typesKeys and throttling
Throttling modelToken bucket; empty bucket returns 429Keys and throttling
REST quotas10,000 API keys (fixed), 300 usage plans, 10 plans per keyKeys and throttling
Lambda authorizer cache300 s default, 3,600 s maximum, per identity sourceLambda authorizers
Resource policy size8,192 characters by default; REST onlyIAM, SigV4 and mTLS
mTLSRegional custom domain, TLS 1.2 policy, truststore (PEM) in S3IAM, SigV4 and mTLS
Pricing, us-east-1HTTP API about USD 1.00 and REST USD 3.50 per million requestsAPI Gateway
Lambda payload formatREST = 1.0, HTTP = 2.0Lambda integrations
Cognito EssentialsFree to 10,000 MAU; M2M token requests billed from the firstCognito
Webhook timestamp toleranceAbout five minutes, HMAC-SHA256 over id.timestamp.bodyWebhooks
Idempotency outcomesReplay 200 · different body 422 · in flight 409 · missing 400Idempotency keys
REST modelsJSON Schema draft 4Validation and CORS

Decision rules

If…Then…
Need WAF, keys, caching or validation at the gatewayREST API
Cost and simplicity matter, JWT auth is enoughHTTP API (front with CloudFront plus WAF if WAF is needed)
Customer or partner is a person or app with a Cognito loginAuthorization code + PKCE, Cognito/JWT authorizer
Machine caller inside AWSIAM + SigV4, no secrets
Partner outside AWS with certificatesmTLS on a Regional custom domain
Custom credential or lookupLambda authorizer; keep ownership checks in the backend
Backend is private ECS/ALBVPC link V2
POST must survive retriesIdempotency key plus domain uniqueness
Partner calls youVerify HMAC on the raw body, acknowledge fast, process via SQS
Calling a partnerFixed egress, one resilience handler, retry only idempotent transient failures
Long download over 29 s or 10 MBResponse streaming or pre-signed S3 URL
Core banking write timed outUnknown outcome: query by idempotency key, never blindly retry
New WAF rulesCount mode first, read logs, then Block

Common exam traps

  • API keys are not authentication. They identify a plan for throttling and quotas.
  • WAF attaches to REST APIs, not HTTP APIs.
  • A Deny policy returns 403; Unauthorized returns 401; any other authorizer error returns 500.
  • Cached authorizer policies apply to later requests with the same identity source: use wildcard resources.
  • Cognito access tokens have no aud by default; check client_id and token_use.
  • Custom scopes come from OAuth endpoints, not SDK sign-in.
  • A JWT is signed, not encrypted. APIs accept access tokens, not ID tokens.
  • Token validity is not object ownership (OWASP API1): return 404 for others' objects.
  • API Gateway does not health-check targets; the load balancer does.
  • Lambda timeout must be below the gateway timeout, and the function keeps running after the client gives up.
  • CORS is browser enforcement; it does not protect the API from other callers.
  • Parameter validation checks presence only and is absent on HTTP APIs.

Cost traps

TrapAvoid it by
Transfer Family endpoint left running (about USD 0.30 per protocol-hour)Delete the server after the lab; stopping is not enough
Load balancer and NAT gateway behind a VPC linkDeploy and destroy within the session
WAF web ACL and rule feesAttach, test, delete the same day
Amazon MQ brokerUse RabbitMQ or ActiveMQ in Docker locally
Cognito M2M token requestsCache tokens in the client until near expiry
Verbose access logs and X-Ray tracesSet retention, sample traces
Lambda retries and duplicate webhooksIdempotent handlers and a DLQ

Independent learning resource — not affiliated with, endorsed or sponsored by Amazon Web Services. AWS and related marks are trademarks of Amazon.com, Inc. or its affiliates. All banking data in examples is fictional. Sample architectures are for learning and are not automatically compliant with GDPR, PCI DSS or any banking regulation.

On this page