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.
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.
You can log in 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 |
For all API endpoints, mParticle routes the request to the appropriate region based on the authorization token.
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:
The following features require mParticle pod-dependent changes before data flows from an input into mParticle:
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 |
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.
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.
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:4422 , Hostname: sftp.us1.mparticle.com:4422 |
IP: 34.199.76.170 |
|
US2 | Hostname: sftp.us2.mparticle.com:4422 |
IP: 52.45.156.86 |
|
EU1 | Hostname: sftp.eu1.mparticle.com:4422 |
IP: 18.157.92.224 |
|
AU1 | Hostname: sftp.au1.mparticle.com:4422 |
IP: 13.55.216.94 |
The following features require mParticle pod-dependent changes for data flowing out of mParticle:
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 |
If you are using role-based authentication, create an S3 bucket with a custom bucket policy.
Use this link docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html#arn-syntax-s3 for information on S3 ARN Syntax.
To create the bucket and set the custom bucket policy:
Create an S3 Bucket. The bucket name must begin with mp-forwarding-
.
Create a New Policy from the AWS S3 Bucket Policy Template below and be sure to:
{bucket}
with the name of the S3 bucket created in step 1. {arn1}
and {arn2}
with the ARN details below.Assign Policy to Bucket. In the Bucket Policy Editor
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 |
{
"Version": "2012-10-17",
"Statement": [
{
"Action": [
"s3:PutObject",
"s3:PutObjectAcl"
],
"Effect": "Allow",
"Resource": "arn:aws:s3:::{bucket}/*",
"Principal": {
"AWS": [
"{arn1}"
]
}
},
{
"Action": [
"s3:PutObject",
"s3:PutObjectAcl"
],
"Effect": "Allow",
"Resource": "arn:aws:s3:::{bucket}/*",
"Principal": {
"AWS": [
"{arn2}"
]
}
}
]
}
Learn more about how to set your bucket policy here.
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?