AWS Region Support – Customer-Hosted Deployment Model
1. Overview
This document demonstrates that the customer-hosted product is compatible with and fully supported in all AWS commercial regions where AWS Lambda has been generally available for more than 90 days. The architecture is designed to be region-agnostic, using AWS-native services and serverless components such as AWS Lambda, Amazon S3, Amazon DynamoDB, and AWS CloudWatch.
The system is deployed directly into the customer’s AWS account, giving the customer full control over the infrastructure and compliance with local regulations. The deployment is performed using infrastructure-as-code (IaC) tools, mainly AWS Serverless Application Model (AWS SAM) and AWS CloudFormation.
2. AWS Lambda Region Compatibility
The solution supports deployment in all public AWS regions where Lambda is available, including but not limited to:
|
Region Name |
Region Code |
|
US East (N. Virginia) |
us-east-1 |
|
US West (Oregon) |
us-west-2 |
|
South America (São Paulo) |
sa-east-1 |
|
Europe (Ireland) |
eu-west-1 |
|
Asia Pacific (Tokyo) |
ap-northeast-1 |
|
Asia Pacific (Singapore) |
ap-southeast-1 |
|
Africa (Cape Town) |
af-south-1 |
The system does not require deployment in AWS China regions, AWS GovCloud, or other non-standard partitions.
All services used by the solution—such as AWS Lambda, Amazon S3, Amazon DynamoDB, Amazon SNS, and Amazon CloudWatch—are generally available in these regions, and the solution was tested and validated in a multi-region deployment strategy.
3. Deployment Architecture and Services
The product uses the following AWS services:
- AWS Lambda – for serverless function execution
- Amazon S3 – for object storage (videos, subtitles, metadata)
- Amazon DynamoDB – for storing indexed metadata
- Amazon SNS – for notifications and event propagation
- Amazon CloudWatch – for logging, metrics, and alarms
- Amazon Transcribe (optional) – for automatic subtitle generation
- AWS Elemental MediaConvert (optional) – for transcoding videos
The solution components are decoupled and event-driven, making it easy to deploy and operate in any AWS Region with minimal adjustments.
4. Step-by-Step Deployment Guide
Step 1: Environment Setup
Before starting the deployment, ensure the following tools are installed and configured:
- AWS CLI
- Install: https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2.html
- Configure: aws configure (use AWS credentials with administrative privileges)
- AWS SAM CLI
- Git
- Used to clone the infrastructure repository
- Node.js (version 18 or higher)
- Required for building Lambda functions if using JavaScript/TypeScript
- IAM permissions
- Ensure the user has the following minimum IAM permissions:
- lambda:*
- cloudformation:*
- iam:*
- s3:*
- dynamodb:*
- logs:*
- Ensure the user has the following minimum IAM permissions:
Step 2: Clone the Infrastructure Repository
Clone the source code that contains the SAM templates, Lambda functions, and configurations.
bash
CopyEdit
git clone https://github.com/playprime/serverless-platform
cd serverless-platform
Step 3: Set Deployment Parameters
Edit the env.json file or create a .env file with the following example content:
json
CopyEdit
{
“Region”: “sa-east-1”,
“S3InputBucket”: “playprime-ingest-input”,
“S3OutputBucket”: “playprime-ingest-output”,
“DynamoTableName”: “MediaMetadata”
}
You can also pass these as parameters during the SAM deployment if preferred.
Step 4: Build the Application
This step uses the AWS SAM CLI to compile all Lambda function code and prepare dependencies.
bash
CopyEdit
sam build
This will create a .aws-sam folder containing compiled code and packaged dependencies.
Step 5: Deploy the Application
To deploy the application into your AWS account, use the guided deployment command:
bash
CopyEdit
sam deploy –guided
You will be prompted to specify:
- Stack name (e.g., PlayPrimeMediaStack)
- AWS Region (e.g., sa-east-1)
- Confirmation to allow creation of IAM roles
- Option to save the configuration to samconfig.toml
Once confirmed, the SAM CLI will:
- Package and upload Lambda code to an S3 bucket
- Create all specified resources using CloudFormation
- Deploy the stack and display function endpoints (if applicable)
Step 6: Post-Deployment Validation
After the deployment completes, validate the following:
- Open the AWS Lambda Console and verify that all functions have been created.
- Open Amazon S3 and confirm that the input/output buckets are active.
- Check CloudWatch Logs for Lambda execution logs.
- If your application includes API Gateway or event sources like S3 triggers, test them by:
- Uploading a file to the input bucket
- Observing Lambda processing
- Reviewing output in the S3 destination bucket and DynamoDB
5. Multi-Region Considerations
If deploying to multiple regions, repeat the deployment process using a different –region parameter or separate CI/CD configuration. All templates are region-agnostic and parameterized to support region-based deployments without modification.
6. Conclusion
This document demonstrates that the Partner product is fully compatible with all public AWS Regions where AWS Lambda has been available for over 90 days. Its infrastructure is packaged using AWS-native tools and supports customer-hosted, region-flexible deployment patterns for production-grade workloads.
The product is built to be modular, scalable, and secure by design—following AWS best practices across identity, permissions, fault isolation, and deployment pipelines.