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.

By default, mParticle Organizations are hosted in the a Pod residing in the US region.

Data Localization

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

Our docs generally assume that your Organization is hosted in the default Pod (US1). As part of the onboarding process, your mParticle account manager will let you know which Pod your Organization resides in.

If your Organization is hosted in an alternative Pod, you will need to note a few key differences described below.

Logging into mParticle

You can login to your localized mParticle Pod using the following URLs:

Region Pod Login URL
United States US1 https://app.mparticle.com, https://app.us1.mparticle.com
United States US2 https://app.us2.mparticle.com
Europe EU1 https://app.eu1.mparticle.com
Australia AU1 https://app.au1.mparticle.com

Sending Data into mParticle

All of our SDKs will route data to your mParticle Pod automatically based on your API keys. The following features require mParticle Pod dependent changes for data flowing 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 https://s2s.mparticle.com/v2/events, https://s2s.us1.mparticle.com/v2/events
bulkevents https://s2s.mparticle.com/v2/bulkevents, https://s2s.us1.mparticle.com/v2/bulkevents
bulkevents/historical https://s2s.mparticle.com/v2/bulkevents/historical, https://s2s.us1.mparticle.com/v2/bulkevents/historical
US2 events https://s2s.us2.mparticle.com/v2/events
bulkevents https://s2s.us2.mparticle.com/v2/bulkevent
bulkevents/historical https://s2s.us2.mparticle.com/v2/bulkevents/historical
EU1 events https://s2s.eu1.mparticle.com/v2/events
bulkevents https://s2s.eu1.mparticle.com/v2/bulkevents
bulkevents/historical https://s2s.eu1.mparticle.com/v2/bulkevents/historical
AU1 events https://s2s.au1.mparticle.com/v2/events
bulkevents https://s2s.au1.mparticle.com/v2/bulkevents
bulkevents/historical https://s2s.au1.mparticle.com/v2/bulkevents/historical

Rules

ARN

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
arn:aws:lambda:us-east-1:999999999999:function:mprmylambdafunction:$LATEST
US2 arn:aws:lambda:us-east-1:999999999999:function:mprmylambdafunction:PROD
arn:aws:lambda:us-east-1:999999999999:function:mprmylambdafunction:$LATEST
EU1 arn:aws:lambda:eu-central-1:999999999999:function:mprmylambdafunction:PROD
arn:aws:lambda:eu-central-1:999999999999:function:mprmylambdafunction:$LATEST
AU1 arn:aws:lambda:ap-southeast-2:999999999999:function:mprmylambdafunction:PROD
arn:aws:lambda:ap-southeast-2:999999999999:function:mprmylambdafunction:$LATEST

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

IAM

When setting IAM permissions, specify the following resources:

Pod IAM Permissions
US1 arn:aws:logs:us-east-1:*:log-group:/aws/lambda/mpr*
arn:aws:lambda:us-east-1:*:function:mpr*
US2 arn:aws:logs:us-east-1:*:log-group:/aws/lambda/mpr*
arn:aws:lambda:us-east-1:*:function:mpr*
EU1 arn:aws:logs:eu-central-1:*:log-group:/aws/lambda/mpr*
arn:aws:lambda:eu-central-1:*:function:mpr*
AU1 arn:aws:logs:ap-southeast-2:*:log-group:/aws/lambda/mpr*
arn:aws:lambda:ap-southeast-2:*:function: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: sftp.mparticle.com, Hostname: sftp.us1.mparticle.com
IP: 34.199.76.170
US2 Hostname: sftp.us2.mparticle.com
IP: 52.45.156.86
EU1 Hostname: sftp.eu1.mparticle.com
IP: 18.157.92.224
AU1 Hostname: sftp.au1.mparticle.com
IP: 13.55.216.94

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

When setting up the AWS S3 bucket policy, use the following Principal:

Pod AWS S3 Bucket Policy Principal
US1 arn:aws:iam::338661164609:role/Prod-Role-DG12-Default
US2 arn:aws:iam::386705975570:role/Prod-Role-DG12-Default
EU1 arn:aws:iam::583371261087:role/Prod-Role-DG12-Default
AU1 arn:aws:iam::526464060896:role/Prod-Role-DG12-Default

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:

All https://api.mparticle.com/ip-ranges

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

Was this page helpful?