AWS deployment design study

Status: unimplemented. No AWS resources, Infrastructure as Code, deployment pipeline, or test evidence for this design are present in the public repositories.

Learning objective

Explore how the small keyword-based /analyze API could be deployed after it has automated tests, a documented contract, and basic operational controls.

Option A: serverless experiment

User → API Gateway → Lambda → intent rules → response
                                  ↘ CloudWatch logs

Option B: container experiment

User → load balancer → containerized API → response
                                             ↘ logs and metrics

Not currently implemented

Asterisk, SBC, SIP/RTP handling, recording storage, redundancy, disaster recovery, authentication, rate limiting, AWS networking, and monitoring remain outside the implemented scope.

Evidence required to call this a prototype

Deployable Infrastructure as Code
Automated API tests
Deployment and teardown instructions
Cost and security notes
Observed logs or metrics from a test deployment

Return to LABP-Stack