From e124ffac67e8456582cfcf5901c799da6426329f Mon Sep 17 00:00:00 2001 From: Robin Beck Date: Wed, 5 Feb 2025 17:58:45 +0000 Subject: [PATCH] backport of commit 82e01d822ef5c9db1dea33e2c49d01d1355c735f --- website/content/docs/concepts/host-discovery/aws.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/website/content/docs/concepts/host-discovery/aws.mdx b/website/content/docs/concepts/host-discovery/aws.mdx index 96e342d763..ca819f8530 100644 --- a/website/content/docs/concepts/host-discovery/aws.mdx +++ b/website/content/docs/concepts/host-discovery/aws.mdx @@ -15,10 +15,10 @@ fields needed for Boundary to authenticate with AWS. Boundary supports two methods of authenticating to AWS: -1. **Static credentials** using an IAM user and its access key. -1. **Dynamic credentials** using credentials generated by `AssumeRole`. +1. **Static credentials** using an IAM user and its access key +1. **Dynamic credentials** using credentials generated by `AssumeRole` -HashiCorp recommends using dynamic credentials when possible. Select a credential type to continue. +HashiCorp recommends using dynamic credentials when possible. Select a credential type to continue: @@ -74,7 +74,7 @@ To enable allow for static credential rotation, add the `iam:GetUser`, `iam:Crea -To set up a dynamic host catalog using an AWS role, a self-managed worker must assume the role. You must assign the role to the self-managed worker AWS instance, and then supply a worker filter that matches the AWS worker when setting up the dynamic host catalog. +To set up a dynamic host catalog using an AWS role, a self-managed worker must assume the role. You must assign the role to the self-managed worker AWS instance, and then supply a worker filter that matches the AWS worker when you set up the dynamic host catalog. Perform the following steps to set up a host catalog using [AssumeRole](https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html):