As a premium service, mParticle offers the option of hosting an instance of mParticle in a localized data center.
Our docs generally assume that your instance is hosted in the default location (US-East). If you are a customer using localized hosting, you will need to note a few key differences described below.
You can login to your mParticle instance in region-specific data centers at the following URLs:
| Australia | app.au1.mparticle.com |
| EU | app.eu1.mparticle.com |
| US | app.mparticle.com |
Interested in data localization outside of these regions? Contact us.
All of our SDKs will route data to your account’s data center automatically based on your API keys. The following features require data center dependent changes for data flowing into mParticle.
Our Events API has the following data center specific URLs:
| Australia | events | https://s2s.au1.mparticle.com/v2/events |
| bulkevent | https://s2s.au1.mparticle.com/v2/bulkevent |
|
| bulkevents/historical | https://s2s.au1.mparticle.com/v2/bulkevents/historical |
|
| EU | events | https://s2s.eu1.mparticle.com/v2/events |
| bulkevent | https://s2s.eu1.mparticle.com/v2/bulkevent |
|
| bulkevents/historical | https://s2s.eu1.mparticle.com/v2/bulkevents/historical |
|
| US | events | https://s2s.us1.mparticle.com/v2/events |
| bulkevent | https://s2s.us1.mparticle.com/v2/bulkevent |
|
| bulkevents/historical | https://s2s.us1.mparticle.com/v2/bulkevents/historical |
Learn more about our Events API here.
When providing an Amazon Resource Number (ARN) for your Rule, follow these conventions:
| Australia | arn:aws:lambda:ap-southeast-2:999999999999:function:mprmylambdafunction:PROD |
arn:aws:lambda:ap-southeast-2:999999999999:function:mprmylambdafunction:$LATEST |
|
| EU | arn:aws:lambda:eu-central-1:999999999999:function:mprmylambdafunction:PROD |
arn:aws:lambda:eu-central-1:999999999999:function:mprmylambdafunction:$LATEST |
|
| US | arn:aws:lambda:us-east-1:999999999999:function:mprmylambdafunction:PROD |
arn:aws:lambda:us-east-1: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:
| Australia | arn:aws:logs:ap-southeast-2:*:log-group:/aws/lambda/mpr* |
arn:aws:lambda:ap-southeast-2:*:function:mpr* |
|
| EU | arn:aws:logs:eu-central-1:*:log-group:/aws/lambda/mpr* |
arn:aws:lambda:eu-central-1:*:function:mpr* |
|
| US | arn:aws:logs:us-east-1:*:log-group:/aws/lambda/mpr* |
arn:aws:lambda:us-east-1:*:function:mpr* |
Learn more about how to set IAM permissions when hosting a Rule here.
The following features require data center dependent changes for data flowing out of mParticle.
Create your downstream AWS services in the following pods for optimal performance:
| Australia | ap-southeast-2 |
| EU | eu-central-1 |
| US | us-east-1 |
When setting up the AWS S3 bucket policy, use the following Principal:
| Australia | arn:aws:iam::526464060896:role/Prod-Role-DG12-Default |
| EU | arn:aws:iam::583371261087:role/Prod-Role-DG12-Default |
| US | arn:aws:iam::338661164609:role/Prod-Role-DG12-Default |
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:
| Australia, EU, US | https://api.mparticle.com/ip-ranges |
Learn more about setting up IP Whitelisting for Redshift and Snowflake.
Was this page helpful?