--- title: "AWS Secrets Manager Credentials" description: "AWS Secrets Manager Credentials" product: "Guardian" edition: "Classic" type: "reference" url: "https://docs.cloudhouse.com/guardian/classic/what-s-new/1-current-release/monthly/aws-secrets-manager-credentials/" --- # AWS Secrets Manager Credentials Applies to: `Guardian Classic` | Included in Version | Release Date | | --- | --- | | V3.64.0 | [March 2026 Monthly Release](https://docs.cloudhouse.com/guardian/classic/what-s-new/1-current-release/monthly/march-2026/index.md) | To further enhance credential management in Guardian, you can now integrate your Guardian instance with AWS Secrets Manager to securely retrieve secrets from your organisation's existing AWS account and use them as the authentication method when adding a Windows, Linux or Network device node. This feature helps centralise credential storage, improve security, and reduce the need to manually manage credentials across multiple nodes. For more information on the new AWS Secrets Manager integration feature, see [AWS Secrets Manager Integration](https://docs.cloudhouse.com/guardian/classic/control/integrations/aws-secrets-manager-integration/index.md). !!! note This feature was introduced in [V3.64.0](https://docs.cloudhouse.com/guardian/classic/what-s-new/1-current-release/monthly/march-2026/index.md) of the Guardian Web application. This is an optional feature that must be enabled. For more information on how to enable it, contact your Cloudhouse Representative. ![Awssecretsmanager](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/whats-new/2026/march/awssecretsmanager.png) ## Use AWS Secrets Manager credentials To use AWS Secrets Manager credentials as the authentication method Guardian uses to access nodes, the following dependencies must be met: - **AWS account** – Configured with AWS credentials. - **AWS Secrets Manager integration** – Set up in Guardian, with the folder path(s) to your existing credentials defined. Once you add an AWS Secrets Manager integration, you will see the new **AWS Secrets Manager** radio button under the **Password** credential type when adding a [Windows Node](https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/add-a-single-node/agentless/windows-node/index.md), [Linux Node](https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/add-a-single-node/agentless/linux-node/index.md) or [Network Device Node](https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/add-a-single-node/agentless/network-device-node/index.md). For more information on how to use an AWS Secrets Manager credential when adding a node, see the sections below. !!! note The following image shows where the AWS Secrets Manager option appears when adding a Windows node. ![Awssecretsmanagerboxed](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/whats-new/2026/march/awssecretsmanagerboxed.png) !!! tip Additionally, the **Guardian Credentials Vault** and **Azure Key Vault** radio buttons are available for selection (if the Credentials and Azure Key Vault features have been enabled). For more information, see [Credential Vault](https://docs.cloudhouse.com/guardian/classic/what-s-new/3-archive/2024/quarterly-releases/q2/credential-vault/index.md) and [Azure Key Vault Credentials](https://docs.cloudhouse.com/guardian/classic/inventory/credentials/azure-key-vault-credentials/index.md). ### Linux or network device node Use your organisation's AWS Secrets Manager credentials to allow Guardian to authenticate access to Linux or network device nodes. To add a Linux or network device node using AWS Secrets Manager credentials, complete the following steps: 1. In the Guardian web application, navigate to the **Add Nodes** tab (**Inventory** > **Add Nodes**). The **Add Nodes** page is displayed. ![Add nodes tab](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/add-nodes/single-nodes/add-nodes-tab.png) 2. Type the node name in the search bar. 3. Select the node you want to add and click the **Go Agentless** button to proceed. The **Connect Agentlessly to [Node Type]** page is displayed. ![Linux node](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/add-nodes/single-nodes/linux-node.png) 4. Select the **Password** radio button to display the **AWS Secrets Manager** radio button. The **AWS Secrets Manager Items** drop-down list is displayed. ![Awssecretsmanagerlinux](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/whats-new/2026/march/awssecretsmanagerlinux.png) 5. Select credentials from the **AWS Secrets Manager** drop-down list. The secrets displayed are based on values from the credentials configured in the AWS Secrets Manager integration. For more information, see [AWS Integration](https://docs.cloudhouse.com/guardian/classic/control/integrations/aws-integration/index.md). 6. Finally, click to **Update** or **Scan Node**. By selecting a credential, you can securely authenticate Guardian's access to the node without manually entering credentials. ### Windows node Use your organisation's AWS Secrets Manager credentials to allow Guardian to authenticate access to Windows nodes without the need for manual credential entry. To add a Windows node using AWS Secrets Manager credentials, complete the following steps: 1. In the Guardian web application, navigate to the **Add Nodes** tab. The **Add Nodes** page is displayed. ![Add nodes tab](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/add-nodes/single-nodes/add-nodes-tab.png) 2. Type 'Windows' in the search bar. 3. Select the 'Windows' node type you want to add and click the **Go Agentless** button to proceed. The **Connect Agentlessly to [Node Type]** page is displayed. ![Go agentless windows](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/misc/go-agentless-windows.png) 4. Select **AWS Secrets Manager** from the list of Credentials radio buttons. ![Awssecretsmanagerboxed](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/whats-new/2026/march/awssecretsmanagerboxed.png) 5. Select credentials from the **AWS Secrets Manager** drop-down list. The credentials displayed are based on values from the credentials configured in the AWS Secrets Manager integration. For more information, see [AWS Integration](https://docs.cloudhouse.com/guardian/classic/control/integrations/aws-integration/index.md). 6. Finally, click to **Update** or **Scan Node**. By selecting a credential, you can securely authenticate Guardian's access to the node without manually entering credentials.