Deployment Regions
Why use multiple regions?
There are several reasons you might choose to host Prismatic integrations in multiple regions:
- GDPR compliance requirements, ensuring EU-based customer data remains in the EU and US-based customer data remains in the US
- CJIS or ITAR compliance requirements necessitating customer data storage in GovCloud
- Ensuring low-latency between where your application is hosted and Prismatic
- Private cloud hosting to fulfill specific customer requirements
Regardless of the requirement, when hosting integrations across multiple Prismatic stacks, you must maintain component and integration synchronization between regions.
Logging in to additional regions
Prismatic's public regions are accessible through the following URLs:
| Region | App URL |
|---|---|
| US Commercial (Ohio) | https://app.prismatic.io |
| US GovCloud | https://app.us-gov-west-1.prismatic.io |
| Europe (Ireland) | https://app.eu-west-1.prismatic.io |
| Europe (London) | https://app.eu-west-2.prismatic.io |
| Canada (Central) | https://app.ca-central-1.prismatic.io |
| Australia (Sydney) | https://app.ap-southeast-2.prismatic.io |
| Africa (Cape Town) | https://app.af-south-1.prismatic.io |
If your email address is associated with multiple regions, you can switch between them by clicking the Tenant Picker on the left-hand sidebar after logging in.
If your tenant is hosted in a private cloud deployment, contact Prismatic support for your endpoint URL.
Prismatic IP allowlist (whitelist)
If your integration connects to an external application that restricts connections by IP address, add the following IPs to your allowlist:
| Region | App URL | IP Addresses |
|---|---|---|
| US Commercial (Ohio) | app.prismatic.io | 3.132.205.2043.139.185.169 |
| US GovCloud | app.us-gov-west-1.prismatic.io | 15.200.86.23015.205.78.158 |
| Australia (Sydney) | app.ap-southeast-2.prismatic.io | 52.65.181.7754.252.173.54 |
| Canada (Central) | app.ca-central-1.prismatic.io | 35.182.143.993.99.22.244 |
| Europe (Ireland) | app.eu-west-1.prismatic.io | 54.78.26.1954.246.201.85 |
| Europe (London) | app.eu-west-2.prismatic.io | 18.132.171.18518.134.91.207 |
| Africa (Cape Town) | app.af-south-1.prismatic.io | 13.245.178.813.247.255.128 |
For private cloud deployments, contact Prismatic support for the appropriate allowlist.
Note: Integrations in Prismatic send data from these IP addresses to third-party applications and services. Webhook URLs for invoking integrations use name-based routing (e.g., hooks.prismatic.io) and IPs are subject to change.
Private regions
For private cloud deployments, Prismatic's DevOps team will deploy a Prismatic stack in your AWS account within your chosen region. Contact support@prismatic.io for your endpoint URL and IP allowlist.
Multi-region user access
By default, new Prismatic accounts are provisioned in the US Commercial (Ohio) region, app.prismatic.io. Access to additional regions can be enabled by Prismatic for enterprise customers whose contracts include additional regions.
User authentication spans all regions, allowing you to use the same email and password across regions. However, user data is not shared between regions.
After Prismatic support enables your organization in an additional region, you must invite your team members to the new region for them to access your tenant there.
Using Prism CLI with multiple regions
The prism CLI tool interacts with the US Commercial region by default.
To interact with a different region, set the PRISMATIC_URL environment variable:
- bash
- powershell
$ export PRISMATIC_URL=https://app.eu-west-1.prismatic.io
$ prism login
Press any key to open prismatic.io in your default browser:
Login complete!
$ prism me
Name: John Doe
Email: john.doe@example.com
Organization: Example Corp - EU Region
Endpoint URL: https://app.eu-west-1.prismatic.io
To persist across sessions, add to your shell configuration file (.bashrc, .zshrc, etc.).
PS C:\> $env:PRISMATIC_URL="https://app.eu-west-1.prismatic.io"
PS C:\> prism login
Press any key to open prismatic.io in your default browser:
Login complete!
PS C:\> prism me
Name: John Doe
Email: john.doe@example.com
Organization: Example Corp - EU Region
Endpoint URL: https://app.eu-west-1.prismatic.io
When automating deployments across regions in CI/CD pipelines, use the PRISMATIC_URL and PRISMATIC_TENANT_ID environment variables to target specific regions and tenants.
See Headless prism Usage.