> 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/knowledge-base-articles/entry-settings/aws-dashboard.md).

# AWS dashboard

Configure AWS dashboard entries in Remote Desktop Manager, including access key or SSO authentication, region, account, role, and Quick Connect credentials.

This article details the settings and options available for ***AWS dashboard*** session entries in Remote Desktop Manager.

{% hint style="info" %}
See [Configure AWS dashboard entry](https://docs.devolutions.net/rdm/integrations/virtualization-cloud/amazon-web-services.md) for the steps to create the entry with an access key or with SSO.
{% endhint %}

<table data-header-hidden><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>SETTINGS</strong></td><td><strong>DESCRIPTION</strong></td></tr><tr><td><strong>Name</strong></td><td>The name of the entry.</td></tr><tr><td><strong>Folder</strong></td><td>The folder where the entry is located.</td></tr><tr><td><strong>Credentials</strong></td><td>Choose a credential mode. Read more on <a href="https://docs.devolutions.net/rdm/ribbon-menu-bar/edit/entry-credentials-options.md"><em><strong>credentials</strong></em> options</a>. With any mode other than <em><strong>Custom</strong></em>, such as <em><strong>Linked (vault)</strong></em>, the user name of the credentials is used as the <em><strong>Access key ID</strong></em> and the password as the <em><strong>Secret access key</strong></em>. Applies when <em><strong>Authentication type</strong></em> is set to <em><strong>Access key</strong></em>.</td></tr></tbody></table>

### General

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Authentication type</strong></td><td><p>How the entry authenticates with AWS:</p><ul><li><strong>Access key</strong> — authenticate with an access key ID and a secret access key.</li><li><strong>SSO</strong> — authenticate through an AWS SSO portal.</li></ul></td></tr><tr><td><strong>Access key ID</strong></td><td>The access key ID used to authenticate with AWS. Shown when <em><strong>Authentication type</strong></em> is set to <em><strong>Access key</strong></em>. Required when <em><strong>Credentials</strong></em> is set to <em><strong>Custom</strong></em>. Unavailable when the credentials come from another source.</td></tr><tr><td><strong>Secret access key</strong></td><td>The secret access key paired with the access key ID. Shown when <em><strong>Authentication type</strong></em> is set to <em><strong>Access key</strong></em>. Required when <em><strong>Credentials</strong></em> is set to <em><strong>Custom</strong></em>. Unavailable when the credentials come from another source, or when the <em><strong>Disable password saving in vaults</strong></em> system setting is enabled.</td></tr><tr><td><strong>Region</strong></td><td>The AWS region to connect to. Select a region from the list, or leave it on <em><strong>Default</strong></em>. Shown for both authentication types, and each authentication type keeps its own region. With <em><strong>SSO</strong></em>, the field appears under <em><strong>Portal URL</strong></em>.</td></tr><tr><td><strong>Portal URL</strong></td><td>The URL of the AWS SSO portal. Shown and required when <em><strong>Authentication type</strong></em> is set to <em><strong>SSO</strong></em>.</td></tr><tr><td><strong>Account</strong></td><td>The AWS account to use. Click the <em><strong>Browse</strong></em> button in the field to sign in to the SSO portal if needed and select an account from the list. The button is available once <em><strong>Portal URL</strong></em> is filled. Shown and required when <em><strong>Authentication type</strong></em> is set to <em><strong>SSO</strong></em>.</td></tr><tr><td><strong>Role name</strong></td><td>The role to use in the selected account. Click the <em><strong>Browse</strong></em> button in the field to select a role from the list. The button is available once an <em><strong>Account</strong></em> is selected. Shown and required when <em><strong>Authentication type</strong></em> is set to <em><strong>SSO</strong></em>.</td></tr></tbody></table>

### Credentials

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Credential Usage</strong></td><td><p>How the credentials used for Quick Connect are obtained:</p><ul><li><strong>Ask on Quick Connect</strong></li><li><strong>Stored credentials</strong> — use the credentials configured in the <em><strong>Custom</strong></em> and <em><strong>Private key</strong></em> tabs below.</li></ul></td></tr><tr><td><strong>Custom</strong></td><td>The credentials stored in the entry for Quick Connect. Select a credential mode from the list. Available when <em><strong>Credential Usage</strong></em> is set to <em><strong>Stored credentials</strong></em>.</td></tr><tr><td><strong>Private key</strong></td><td>The private key stored in the entry for Quick Connect. Available when <em><strong>Credential Usage</strong></em> is set to <em><strong>Stored credentials</strong></em>.</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://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/aws-dashboard.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.
