> For the complete documentation index, see [llms.txt](https://help.cloudstoragesec.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cloudstoragesec.com/console-overview/access-management/linked-accounts.md).

# Manage Accounts

There are scenarios where it makes sense to centrally manage your security deployments.

![Linked Accounts](https://905555942-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlGcQw8I2CHyi1loKBlfi%2Fuploads%2FkXpBxzkEczv4XFxJxQud%2FScreenshot%202024-12-05%20at%2013.45.08.png?alt=media\&token=85422614-766d-49c2-8f1f-208063eddf5f)

Whether you just don't want to manage separate deployments across all of your AWS accounts or you want to follow an [AWS Landing Zone](https://aws.amazon.com/solutions/implementations/aws-landing-zone/) or an [AWS Control Tower](https://aws.amazon.com/controltower/) best practice implementation, the necessity to scan multiple accounts may be one of your requirements.

Cross account scanning is achieved by linking "remote accounts" (non-deployment accounts) through the console and then deploying a cross-account role within each remote account. This is a very simple process which will allow the console to see all of the buckets for the linked account as it would for the deployment account ("primary"). All aspects of management and protection and feedback are the same after these steps have been completed. Both event-based and retro-scanning fully work with linked accounts so you can scan both your go-forward data as well as any existing data. You can link as many accounts as desired.

Accounts can be linked and then added in stages as you want to roll them out. So feel free to link all of your remote accounts and then activate them singularly or in groups. And you can always deactivate / reactivate accounts later on as needed.

The same applies for linking Azure accounts, allowing you to scan Azure Blobs. Click one of the below links to learn more about linking accounts for each cloud provider.

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Linking an AWS Account</strong></td><td>Learn more about linking additional AWS accounts and ingesting the associated storage volumes.</td><td></td><td><a href="/console-overview/access-management/linked-accounts/linking-an-aws-account.md">Linking an AWS Account</a></td></tr><tr><td><strong>Linking an Azure Account</strong></td><td>Learn more about linking Azure accounts and ingesting associated Azure Blobs.</td><td></td><td><a href="/console-overview/access-management/linked-accounts/linking-an-azure-account.md">Linking an Azure Account</a></td></tr><tr><td><strong>Linking a GCP Account</strong></td><td>Learn more about linking GCP accounts and ingesting associated GCP Buckets.</td><td></td><td><a href="/console-overview/access-management/linked-accounts/linking-a-gcp-account.md">Linking a GCP Account</a></td></tr></tbody></table>


---

# 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://help.cloudstoragesec.com/console-overview/access-management/linked-accounts.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.