> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/security-and-compliance/access-control/cloud-account.md).
# Cloud Account
How the Cloud Account provides the maximum level of isolation
The cloud provider account is the greatest barrier, providing security and isolation.
* **Azure Subscription**: One DuploCloud portal can manage multiple Azure subscriptions. To add a subscription, click **Administrator** -> **CloudCredentials**, as shown in the figure below. You can use a managed identity or a service principle with keys
Cloud Credentials page in the DuploCloud Portal for Azure
* **AWS Account**: In AWS, you need one DuploCloud VM per AWS account, because in AWS, the account is the fundamental IAM construct. The AWS organizations and SCP are very lightweight and were more recently added in the AWS product lifespan, unlike Azure which uses Active Directory as the fundamental IAM construct. Originally DuploCloud used to manage multiple AWS accounts, but this support was removed after consistent feedback from customers and security experts. The best practice evolved to one VM agent per account, federated in a single pane, allowing you to switch accounts as needed, using the **Switch Account** list box.\
Switch Account list box in the DuploCloud Portal
Welcome screen, displaying a list of available DuploCloud portals
* **Google Project**: Multiple GCP projects can be added and managed by the same DuploCloud installation. To add a project, click **Administrator** -> **Cloud Credentials**, as shown in the figure below.
---
# 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.duplocloud.com/docs/automation-platform/security-and-compliance/access-control/cloud-account.md?ask=&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.
