us-west-2
Regions and Data Residency
Your Azul Intelligence Cloud instance runs in one region, and the JVM metadata your Forwarder sends stays in that region. If your organization operates under GDPR or a similar data protection framework, this page tells you where your data lives, which limited set of operational data crosses a region boundary, and which subprocessors Azul relies on.
For an overview of what your systems send to Azul, see What Info is Transmitted Between Your System and Azul Intelligence Cloud. This page covers where that data ends up.
Available Regions
Azul hosts Intelligence Cloud on Amazon Web Services in the following regions:
| Region | Location | AWS region |
|---|---|---|
US |
Oregon, United States |
|
EU |
Ireland |
|
AU |
Australia |
|
Azul assigns your region when creating your instance. To find the region of your instance, look at the API host that you use to configure your Forwarder, for example YOUR_INSTANCE.api.ic.azul.com. You can copy this host from the Web UI Forwarder setup screen, as described in Configuring Your Firewall. Contact your Azul representative if you need your instance in a different region.
What Stays in Your Region
Azul stores all customer data in the region of your instance and never copies it to another region. Customer data covers:
-
The JVM metadata that your runtimes and Forwarders report, as listed in What Info is Transmitted.
-
Code Inventory and JVM Inventory reports.
-
Artifacts that your runtimes upload, such as GC logs and JFR recordings.
-
User accounts, API keys, and the audit log of your instance.
Azul also sends notification and account emails from inside your region, using Amazon SES and Amazon Cognito. No external email provider handles these messages.
What Crosses Regions
Azul operates a single security monitoring pipeline for all regions, hosted in the United States (us-west-2). Application monitoring and system telemetry from every region flow into AWS CloudTrail and into Arctic Wolf, the security monitoring vendor of Azul.
These logs contain system data, not the JVM metadata of your applications. They do record the email addresses of users who sign in, and for users who sign in through SSO they can also record names. Azul needs this information to detect unauthorized access and to investigate security incidents.
Other External Services
Besides the AWS infrastructure that hosts your instance, Azul relies on a small number of external services to run and support Intelligence Cloud. The tables below list them in two groups: the subprocessors that process data as part of delivering the service, and the tools that Azul uses to monitor its infrastructure and to support you.
Subprocessors
Azul uses the following subprocessors to deliver Intelligence Cloud:
| Vendor | Purpose | Data residency |
|---|---|---|
Amazon Web Services |
Cloud hosting provider |
Region of your instance |
Amazon Web Services |
CloudTrail audit and monitoring logs |
US |
Model provider for AI features |
EU |
Support Tools
Azul uses the following support tools:
| Tool | Purpose | Data residency |
|---|---|---|
Arctic Wolf |
Security monitoring |
US |
Zendesk |
Support portal |
US |
SendSafely |
Exchange of support artifacts |
US |
Security Review Information
Three points matter for a security review:
-
Intelligence Cloud uses no application-level subprocessors. Only the vendors in the tables above process data.
-
Intelligence Cloud uses no email subprocessor, as described in What Stays in Your Region.
-
The Intelligence Cloud Web UI sets no external tracking cookies.
Azul updates this list when the set of subprocessors changes.