Data Hosting Locations

Each mParticle customer tenant (aka “Organization”) exists in a specific segment (or “Pod”) of mParticle’s infrastructure. A pod is a self-contained instance of the entire mParticle service for a subset of organizations. Pods are completely independent of each other with redundancy built into each layer of the architecture, including the application servers, database, IaaS, and CDN to ensure maximum availability.

Data Localization

mParticle offers the option of hosting a pod in a localized data center outside the US, in particular in the Europe and Australia regions. For customers interested in data localization outside these regions, please contact us.

As part of the onboarding process, your mParticle account manager will let you know which pod your organization resides in.

Depending on the pod your organization is hosted in, you will need to note a few key differences described below.

Logging into mParticle

You can log in to your localized mParticle pod using the following URLs:

Region Pod Login URL
United States US1,
United States US2
Europe EU1
Australia AU1

For all API endpoints, mParticle routes the request to the appropriate region based on the authorization token.

Sending Data into mParticle

Most mParticle SDKs route data to your mParticle pod automatically based on your API keys. The following SDKs require that you configure your pod name:

  • Go
  • Java
  • Node
  • Python
  • Ruby

The following features require mParticle pod-dependent changes before data flows from an input into mParticle:

Events API

Our Events API has the following data center specific URLs. Learn more about our Events API here.

Pod API Endpoint
US1 events,
US2 events
EU1 events
AU1 events



When providing an Amazon Resource Number (ARN) for your Rule, follow these conventions:

Pod ARN Rule Convention
US1 arn:aws:lambda:us-east-1:999999999999:function:mprmylambdafunction:PROD
US2 arn:aws:lambda:us-east-1:999999999999:function:mprmylambdafunction:PROD
EU1 arn:aws:lambda:eu-central-1:999999999999:function:mprmylambdafunction:PROD
AU1 arn:aws:lambda:ap-southeast-2:999999999999:function:mprmylambdafunction:PROD

Learn more about how to set an ARN when hosting a Rule here.


When setting IAM permissions, specify the following resources:

Pod IAM Permissions
US1 arn:aws:logs:us-east-1:*:log-group:/aws/lambda/mpr*
US2 arn:aws:logs:us-east-1:*:log-group:/aws/lambda/mpr*
EU1 arn:aws:logs:eu-central-1:*:log-group:/aws/lambda/mpr*
AU1 arn:aws:logs:ap-southeast-2:*:log-group:/aws/lambda/mpr*

Learn more about how to set IAM permissions when hosting a Rule here.

SFTP Servers

When sending data to mParticle for file based integrations (Salesforce, Custom CSV, etc), the following hostname and IP should be used:

Pod Hostname and IP
US1 Hostname:, Hostname:
US2 Hostname:
EU1 Hostname:
AU1 Hostname:

Sending Data Out of mParticle

The following features require mParticle pod-dependent changes for data flowing out of mParticle:

AWS Regions

Create your downstream AWS services in the following AWS Regions aligned to your pod for optimal performance:

Pod AWS Region
US1 us-east-1
US2 us-east-1
EU1 eu-central-1
AU1 ap-southeast-2

Amazon S3 Bucket

If you are using role-based authentication, create an S3 bucket with a custom bucket policy.

Use this link for information on S3 ARN Syntax.

To create the bucket and set the custom bucket policy:

  1. Create an S3 Bucket. The bucket name must begin with mp-forwarding-.

  2. Create a New Policy from the AWS S3 Bucket Policy Template below and be sure to:

    1. Replace the word {bucket} with the name of the S3 bucket created in step 1.
    2. Replace {arn1} and {arn2} with the ARN details below.
  3. Assign Policy to Bucket. In the Bucket Policy Editor

    1. Click Properties.
    2. Click Permissions.
    3. Click Add bucket policy.
    4. Paste the JSON from step 2 above.

AWS S3 Bucket Policy Principal

Pod ARN # AWS S3 Bucket Policy Principal
US1 {arn1} arn:aws:iam::338661164609:role/Prod-Role-DG12-Default
{arn2} arn:aws:iam::338661164609:role/role-lambda-verifyrequest
US2 {arn1} arn:aws:iam::386705975570:role/Prod-Role-DG12-Default
{arn2} arn:aws:iam::386705975570:role/verifyrequest_lambda
EU1 {arn1} arn:aws:iam::583371261087:role/Prod-Role-DG12-Default
{arn2} arn:aws:iam::583371261087:role/verifyrequest_lambda
AU1 {arn1} arn:aws:iam::526464060896:role/Prod-Role-DG12-Default
{arn2} arn:aws:iam::526464060896:role/verifyrequest_lambda

AWS S3 Bucket Policy Template

    "Version": "2012-10-17",
    "Statement": [
            "Action": [
            "Effect": "Allow",
            "Resource": "arn:aws:s3:::{bucket}/*",
            "Principal": {
                "AWS": [
            "Action": [
            "Effect": "Allow",
            "Resource": "arn:aws:s3:::{bucket}/*",
            "Principal": {
                "AWS": [

Learn more about how to set your bucket policy here.

IP Whitelisting

If you want to whitelist data being sent from mParticle to an integration, use the following information:


Learn more about setting up IP Whitelisting for Redshift and Snowflake.

Was this page helpful?