Create an AWS EKS Instance - Advertising Agencies and Partners
Check the prerequisites before kicking-off the creation of a new Conversions API Gateway or Signals Gateway instance (also referred to collectively as the Gateway products).
An advertising agency can manage a Gateway product instance for multiple different businesses.
Note: If you are only managing an individual business account, then the Conversions API Gateway: Setup Guide or Signals Gateway: Setup Guide is recommended for the instance creation instead
Start by logging in to the AWS account. Access the AWS CloudFormation service and choose the region where the Gateway product for multiple accounts will be deployed in.
Best practice: Choose the region where the majority of the advertisers operate or where most of the user activity is expected.
AWS regions not supported for advertiser IP address preservation:
- China (Beijing, Ningxia)
- AWS GovCloud (US-East, US-West)
Click Create Stack and select With new resources.
- To create a Conversions API Gateway instance:
Paste the Conversions API Gateway CloudFormation template URL below in the Amazon S3 URL field CloudFormation template URL below in the Amazon S3 URL field:
https://conversions-api-gateway-release-production.s3.us-west-2.amazonaws.com/conversions-api-gateway.eks_multiaccount.yaml
- To create a Signals Gateway instance:
Paste the Signals Gateway CloudFormation template URL below in the Amazon S3 URL field:
https://signals-gateway-release-production.s3.us-west-2.amazonaws.com/signals-gateway.eks_sgw.yaml
Click Next. Provide the following parameters to create the stack:
- Stack name: The name of the stack, shown on the AWS CloudFormation dashboard. Best practice: Choose a meaningful name, to easily recall the instance.
- SystemHealthInformation: Opt-in to periodically send telemetry data to Meta for monitoring and troubleshooting. Activate to periodically send to Meta essential data for monitoring and troubleshooting your instance.
A Gateway instance only supports the m5.large instance type. You can find a rough monthly cost estimate here based on the AWS Cost calculator: $350 for m5.large. (This will vary depending on region). This cost is due to the minimum deployment, including instances across two availability zones. The default deployment has two instances, one in each availability zone and the Gateway products can deploy more instances to handle more traffic. We estimate the default pair of m5.large instances can handle 50 pixels and this will vary based on how much traffic each pixel is sending. The maximum number of instances to deploy can be set in the Auto scaling limits menu of the Admin UI.
Note: the following screenshots demonstrate how to provision a Conversions API Gateway instance from an AWS template link. The Signals Gateway provisioning steps will look similar to this example.
Click Next, then Next again, and then Create Stack. No action is needed on the second CloudFormation page.
It will take about 40 minutes for the stack creation and deployment to complete. The stack creation process will create in total 8 stacks, as described below.
Once stack creation and deployment terminates, access the Outputs tab of the main stack.
The Gateway product instance is now created. Click the link mentioned in the CapigSetupURL section to finalize its configuration.