Plan your deployment
This section describes the prerequisites, cost, configurations for ECS Auto Scaling, security, Region, deployment scenarios, and quota considerations for planning your deployment.
Supported AWS Regions
Prebid Server on AWS is supported in the following AWS Regions:
| Region name | |
|---|---|
|
US East (Ohio) |
Asia Pacific (Tokyo) |
|
US East (N. Virginia) |
Canada (Central) |
|
US West (Northern California) |
Europe (Frankfurt) |
|
US West (Oregon) |
Europe (Ireland) |
|
Asia Pacific (Mumbai) |
Europe (London) |
|
Asia Pacific (Osaka) |
Europe (Paris) |
|
Asia Pacific (Seoul) |
Europe (Stockholm) |
|
Asia Pacific (Singapore) |
South America (São Paulo) |
|
Asia Pacific (Sydney) |
Deployment scenarios
This solution supports multiple deployment modes depending on your connectivity requirements and whether you are deploying the optional bidder simulator. The following table summarizes the available scenarios and the corresponding deploy.sh flags.
| Scenario | Description | deploy.sh flags | Connectivity |
|---|---|---|---|
|
Prebid Server only |
Deploy the core Prebid Server stack without a bidder simulator. Bidders are reached via the public internet through NAT Gateways. |
|
Public internet (NAT Gateway) |
|
Prebid Server + Simulator (RTB Fabric) |
Deploy both stacks with RTB Fabric connectivity. The |
|
RTB Fabric (Requester Gateway → Fabric Link → Responder Gateway) |
|
Prebid Server + Simulator (VPC peering) |
Deploy both stacks with VPC peering connectivity. Use this mode in Regions where RTB Fabric is not available. |
|
VPC peering (direct network path) |
|
Pre-built container image |
Deploy using the pre-built container image from the repository instead of building from source. Requires Git LFS. |
|
Any (combine with other flags) |
Note
The --container-image flag can be combined with any other deployment scenario. When specified, the script loads the container tar.gz, pushes it to ECR, and uses it for the ECS task definition instead of building from the Dockerfile.
