> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/configure-aws-dashboard-entry.md).

# Configure AWS dashboard entry

Configure an AWS Dashboard entry in Remote Desktop Manager to view IAM users, groups, and roles using access key or SSO login.

The AWS dashboard allows system administrators to securely connect to their AWS environment and visualize key IAM components directly within Remote Desktop Manager:

* IAM User groups and their memberships
* IAM Users and associated group policies
* IAM Roles and trust relationships

1. In Remote Desktop Manager, go to ***New Entry*** and select ***AWS Dashboard***.
2. In the ***Add*** – ***AWS Dashboard*** dialog, enter a ***Name*** for the entry.
3. Optionally, select a ***Folder*** to organize the entry.
4. Under the ***General*** tab, click the ***Authentication type*** dropdown.

#### Access key <a href="#access-key" id="access-key"></a>

1. Select ***Access key***.
2. Enter your ***Access key ID***.
3. Enter your ***Secret access key***.
4. Select a ***Region*** from the dropdown, or leave it as ***Default***.

#### SSO <a href="#sso" id="sso"></a>

1. Select ***SSO***.
2. Enter the ***Portal URL*** for your AWS SSO portal.
3. Select a ***Region***, or leave it as ***Default***.
4. Click ***...*** next to ***Account*** to select the AWS account.
5. Click ***...*** next to ***Role name*** to select the IAM role.
6. Click ***Add*** to save the entry.


---

# 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.devolutions.net/rdm/knowledge-base/how-to-articles/configure-aws-dashboard-entry.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.