Skip to content
This repository has been archived by the owner on Apr 25, 2024. It is now read-only.

Minor typo worked nodes > worker nodes #588

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Minor typo worked nodes > worker nodes #588

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion 04-path-security-and-networking/401-configmaps-and-secrets/readme.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -685,7 +685,7 @@ AWS Secrets Manager enables you to easily rotate, manage, and retrieve database
=== Update the IAM role for EKS or `kops` Kubernetes Cluster

==== EKS Kubernetes Cluster
EC2 worker nodes use `NodeInstanceRole` created in Step 3 of the https://docs.aws.amazon.com/eks/latest/userguide/getting-started.html[EKS Getting Started guide]. This role must be updated to allow the worked nodes to read the secrets from Secrets Manager.
EC2 worker nodes use `NodeInstanceRole` created in Step 3 of the https://docs.aws.amazon.com/eks/latest/userguide/getting-started.html[EKS Getting Started guide]. This role must be updated to allow the worker nodes to read the secrets from Secrets Manager.

In the IAM Console, click `roles` and type `NodeInstanceRole` and click it. In the Permissions tab, expand the inline policy and click `Edit policy`. Add the `secretsManager:GetSecretValue` permission to the policy so the policy looks similar to the one below.

Expand Down