prebid-adpod-client v3.6.0
#Prebid S2S AdPod Client The client is responsible for the ad pod front-end interface and the Mongo record API.
###Deployment Bitbucket pipelines will run build, test, and upload to S3. Production release requires a manual confirmation in the Bitbucket UI.
####Settings #####Production
- CodeDeploy Application:
PrebidAdPodService - Deployment Group:
prebid-adpod-fe - EC2 Tag:
bitbucket-group: prebid-adpod-fe - EC2 IAM Role:
EC2Introspection-S3 - S3 Bucket:
beachfront-bitbucket - AWS User:
codedeploy-bitbucket - EC2 Instance
io-prebid-nodejs-{SUFFIX} - Target Group:
io-prebid-node - Load Balancer:
io-pod-alb
#####QA
- CodeDeploy Application:
PrebidAdPodService - QA Deployment Group:
prebid-adpod-fe-qa - QA EC2 Tag:
bitbucket-group: prebid-adpod-qa - EC2 IAM Role:
EC2Introspection-S3 - S3 Bucket:
beachfront-bitbucket - AWS User:
codedeploy-bitbucket - EC2 Instance
io-prebid-qa-ue1c1 - Target Group:
io-prebid-node-qa - Load Balancer:
io-pod-qa-alb
###Requirements
- Node v x.x.x
- NPM v x.x.x
###Local Development #####Environment
- Node v x.x.x
- NPM v x.x.x
- MongoDB v x.x.x running on 27017 with no authentication
#####Install, Build, and Run
Pipeline will kickoff when {BRANCH} receives a push. Final deployment step requires a manual confirmation in Bitbucket.
The following Repository vars must be set:
- NPM_TOKEN
- AWS_ACCESS_KEY
- AWS_SECRET_ACCESS_KEY
- ENV_REFRESH_SECRET
- ENV_JWT_KEY
###API Endpoints The API is secured with a JWT which requires a secret key.
###Production Deployment The application is deployed via Bitbucket Pipelines. Pushing to {{BRANCH}} will kickoff the deployment process.
Deployment stages are detailed in bitbucket-pipelines.yml and appspec.yml.
###Production Infrastructure
- MongoDB Host:
- AWS Application LB:
- EC2 Cluster Instances: