#AWS SECRETS MANAGER HOW TO#

If the administrator of the account to which the role belongs provided you with an external ID, then enter that value.įor more information, go to How to Use an External ID When Granting Access to Your AWS Resources to a Third Party in the AWS documentation. This role is an IAM role in the target deployment AWS account. Role ARN Įnter the Amazon Resource Name (ARN) of the role that you want to assume. Refer to Secret Name Prefix and Region explained above to add these details. Typically, you use AssumeRole within your account or for AWS cross-account access. This option uses the AWS Security Token Service (STS) feature. Option: Assume Role Using STS on Delegate You can select a Delegate using a Delegate Selector. If you select this option, Harness will authenticate using the IAM role assigned to the AWS host running the Delegate you select. Select the AWS Region for the secret manager. For example, devops will result in secrets like devops/mysecret. All the secrets under this secret manager would have this prefix. Secret Name Prefix Įnter Secret Name Prefix. You can either create a new Secret with your Access Key ID's secret key as its Value or use an existing secret. The AWS Access Key is the AWS Access Key ID for the IAM user you want to use to connect to secret manager. In the secret settings dialog, you can create/select a Secret and enter your AWS Access Key as it's value. Gather AWS - Access Key ID and AWS - Secret Access Key from the JSON for the Key Policy, or in the AWS IAM console, under Encryption keys.įor more information, go to Finding the Key ID and ARN from Amazon. You can select the following options in Credential Type for authenticating with AWS: For more information, go to Entity Identifier Reference.Įnter a Description for your secret manager. You can choose to update the ID or let it be the same as your secret manager's name. For information on restrictions on names and maximum quotas, go to Quotas for AWS Secrets Manager.

Aws secrets manager