The following are best practices for setting up your production environments for both a custom augmentor and your custom bidding agent.
Beeswax is currently located out of US-EAST-1, US-WEST-2, EU-WEST-1, and AP-NORTHEAST-1 AWS data centers. When deploying your augmentor or your bidding agent, you should ensure it's located in the same data center as your Beeswax bidder instance for optimal performance. We additionally recommend that you look up which AZ (Zone Name) in your AWS account refers to the below Zone IDs and choose to deploy in that AZ (Zone Name):
The Zone Name to Zone ID table for your account can be found at the bottom of https://console.aws.amazon.com/ec2/v2/home
By default Beeswax will deploy your custom bidder instance in US-EAST-1 with the option of also deploying an additional bidder instances in the other regions. If you have a Bidding Agent or Augmentor in multiple data centers you will need to have an instance of your augmentor and/or bidding agent in each region as well.
In addition to ensuring your augmentor or your bidding agent is located in the same AWS region, we recommend the following high level set up:
- Utilize Amazon's Elastic Load Balancer (ELB) in front of your augmentor or bidding agent. Using a different load balancer may come with performance and cost risk
- Set up DNS on your ELB
- Deciding on an EC2 machine type is up to you, but we've found that M4.2XLarge machine types perform well for augmentor and bidding agent use cases
- Given that you have 10ms timeouts for your augmentor and bidding agent respectively, best practice is to do any lookups in your machine's local cache. Calling out to a separate in-memory data-store like Redis can also typically be done within the 10ms timeout
- The programming language you use to build your augmentor or bidding agent is up to you, the only requirement is that it meet the 10ms timeout
- Set your server to
Keep Connections Openso we don't try to reset connections at high rates
Updated 3 months ago