> For the complete documentation index, see [llms.txt](https://docs.openiam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openiam.com/installation/rpm/cloud.md).

# On AWS and Azure

What changes when you build OpenIAM on AWS or Azure, what stays the same, and which services you hand to the provider.

**The installation procedure does not change on a cloud provider.** Both RPM shapes build the same way on an EC2 instance or an Azure VM as on a machine in your own data centre: the same package, the same `openiam-cli init`, the same verification. What changes is what you provision before you start, and what you hand to the provider instead of running yourself.

These pages cover that difference. Follow the build path for your shape and use the page for your provider alongside it.

## What you hand to the provider

<table><thead><tr><th width="194.80001831054688">Component</th><th>On a cloud provider</th></tr></thead><tbody><tr><td><strong>Database</strong></td><td><strong>Use the provider's managed service.</strong> This is the one component with a supported managed path for an RPM deployment, and the one worth using — it brings backups, patching, failover and monitoring you would otherwise build. <a href="/installation/rpm/cloud/managed-databases.md"><em>Managed databases</em></a> covers it</td></tr><tr><td><strong>Load balancer</strong></td><td>The provider's — an Application Load Balancer on AWS, a Load Balancer or Application Gateway on Azure. <a href="/installation/rpm/rpm-ha/load-balancer.md"><em>Configure the load balancer</em></a> has the requirements; the provider pages have the settings</td></tr><tr><td><strong>TLS certificates</strong></td><td>The provider's certificate service, terminated at the load balancer. <a href="/installation/rpm/rpm-single-node/enable-https.md"><em>Enable HTTPS</em></a> covers terminating on the hosts instead</td></tr><tr><td><strong>Backups and snapshots</strong></td><td>Volume snapshots complement, rather than replace, the platform backup in <a href="/installation/rpm/rpm-single-node/back-up-and-restore.md"><em>Back up and restore</em></a></td></tr></tbody></table>

## What OpenIAM runs on the instances

Everything else: the application services and interfaces, the message broker, the cache, the graph and search tiers, the secret store and its backend, and the reverse proxy. **The installation provisions, configures and clusters all of them for you**, and offers no option to substitute a managed service for any of them. An OpenIAM deployment on a cloud provider therefore needs one managed service — the database — and nothing else beyond compute, storage and networking.

That is deliberate. It keeps the deployment portable between providers and your own data centre, keeps the cluster's failover behaviour under the platform's control rather than a provider's, and means the shape you prove in one environment is the shape you run in the next.

Container deployments have a wider set of managed options — the database and the cache. See [*Kubernetes*](/installation/kubernetes.md).

## The two shapes on a cloud provider

| Shape           | What you provision                                                        |
| --------------- | ------------------------------------------------------------------------- |
| **Single node** | One instance, one managed database, one public entry point                |
| **Three nodes** | Three identical instances, one managed database, a load balancer in front |

Sizing does not change: every instance meets [*System requirements*](/installation/system-requirements.md) in full. A cloud instance is not smaller because it is virtual.

## The pages

<table><thead><tr><th width="193.19998168945312">Page</th><th>Covers</th></tr></thead><tbody><tr><td><a href="/installation/rpm/cloud/aws.md"><em>AWS</em></a></td><td>Instance types, storage, images, security groups and the load balancer, for both RPM shapes</td></tr><tr><td><a href="/installation/rpm/cloud/azure.md"><em>Azure</em></a></td><td>The same, for Azure VMs</td></tr><tr><td><a href="/installation/rpm/cloud/managed-databases.md"><em>Managed databases</em></a></td><td>Which engines are supported on each provider, the parameters to set before you install, and how to answer the installation's prompts</td></tr></tbody></table>

**Deploying to Kubernetes instead?** [*Amazon EKS*](/installation/kubernetes/amazon-eks.md) and [*Azure AKS*](/installation/kubernetes/azure-aks.md) cover the cluster side; the managed database page applies unchanged.

## Before you start

Read the build path for your shape first — [*RPM, single node*](/installation/rpm/rpm-single-node.md) or [*RPM, three nodes*](/installation/rpm/rpm-ha.md). The provider pages assume you know what you are building; they tell you how to provision for it.

## Related

* [*Choose your route*](/installation/choose-your-route.md)
* [*Scope and availability*](/installation/scope-and-availability.md) — all cloud deployments in this release are single-zone
* [*Managed databases*](/installation/rpm/cloud/managed-databases.md)

*Applies to OpenIAM 2026.8.1.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openiam.com/installation/rpm/cloud.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.