OMISE Thailand - July 7-10, 2026
3-Day Instructor-Led CourseCourse overview, logistics, instructor, agenda, resources
Cognito, JWT authorizers, federated identities, OAuth/OIDC
CloudFormation, CDK, SAM, Amplify Gen 2
Event-driven decoupling, pub/sub, filtering, routing
SQS, Kinesis, DynamoDB Streams, event source mappings
Lifecycle, best practices, concurrency, idempotency, Kiro
State machines, Task/Choice/Parallel/Map, error handling
CloudWatch Logs, X-Ray traces, metrics, EMF, Lambda Insights
Defense in depth, WAF, IAM, VPC, encryption, auditing
Concurrency, throttling, SQS/Kinesis scaling, enhanced fan-out
Pipelines, SAM deploy, canary, traffic shifting, rollbacks
🔗 Open Lab Environment (AWS Builder Labs)
Day 1 - Deploy with SAM, test API Gateway + Lambda + DynamoDB
Day 1 - Custom event bus, rules, multiple targets, filtering
Day 2 - Build state machine with Task, Choice, Parallel, Map states
Day 2 - CloudWatch Logs, X-Ray traces, metrics, alarms, dashboards
Day 3 - WAF, IAM least privilege, Secrets Manager, encryption
Day 3 - CodePipeline, SAM deploy, canary deployments, auto-rollback
Real-world serverless patterns applied to Omise payment transaction management.
When a customer makes a payment, the transaction flows through an event-driven pipeline: API Gateway receives the payment request, Lambda validates and processes it, EventBridge routes the event to multiple consumers (fraud detection, receipt generation, analytics).
When a customer disputes a charge, a Step Functions workflow orchestrates the resolution: gather evidence (Task), determine dispute type (Choice), notify merchant + bank in parallel (Parallel), wait for response with callback token, then resolve or escalate.
Kinesis Data Streams ingests real-time transaction data. Lambda consumers analyze patterns (velocity checks, geo-anomalies). CloudWatch custom metrics track transaction volume and fraud rates. X-Ray traces end-to-end latency. Alarms trigger when fraud rate exceeds threshold.
Payment APIs are protected with defense-in-depth: CloudFront + WAF blocks SQL injection and bots, API Gateway enforces JWT auth (merchant API keys) + rate limiting per client, Lambda uses least-privilege IAM to access encrypted DynamoDB. Secrets Manager rotates payment gateway credentials.
New merchant integrations deploy via automated SAM pipeline: CodeCommit triggers CodeBuild (lint + unit tests), deploys to staging account for integration testing, then canary-deploys to production with CloudWatch alarms that auto-rollback if error rate increases. Each merchant gets isolated Lambda functions with separate IAM roles.
Daily settlement files uploaded to S3 trigger a Step Functions Distributed Map that processes thousands of transactions in parallel. Each item is validated, fees calculated, and results written to DynamoDB. Failed items go to DLQ for manual review. Entire process is serverless - scales from 10 to 100,000 transactions with no infrastructure changes.