Skip to content

Commit 88860a4

Browse files
committed
minor edits
1 parent a46a159 commit 88860a4

File tree

1 file changed

+9
-8
lines changed

1 file changed

+9
-8
lines changed

self-hosting/govern/external-secrets.mdx

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,9 @@ This guide explains how to integrate Plane with external secret management solut
77

88
## AWS Secrets Manager
99

10-
1. Create a dedicated IAM user (e.g., `external-secret-access-user`).
11-
2. Generate security credentials (no Console Access required).
12-
3. Note the user's ARN for later use.
10+
1. Create a dedicated IAM user (e.g., `external-secret-access-user`). You can uncheck **Console Access Required**.
11+
2. Generate `ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` and keep them handy.
12+
3. Note the user's ARN for later use (format: `arn:aws:iam::<account-id>:user/<user-name>`).
1313

1414
4. Create IAM policy (e.g., `external-secret-access-policy`) with the following JSON:
1515

@@ -52,9 +52,10 @@ This guide explains how to integrate Plane with external secret management solut
5252
```
5353

5454
Replace `<IAM-USER-ARN>` with the ARN of the user created in step 1.
55-
Attach the AWS IAM policy created in step 4 to this role.
5655

57-
6. Create secrets in AWS Secrets Manager with your Plane configuration values. For example, store RabbitMQ credentials with a name like `prod/secrets/rabbitmq`.
56+
6. Attach the AWS IAM policy created in step 4 to the IAM role.
57+
58+
7. Create secrets in AWS Secrets Manager with your Plane configuration values. For example, store RabbitMQ credentials with a name like `prod/secrets/rabbitmq`.
5859

5960
|Key|Value|
6061
|-------|--------|
@@ -63,15 +64,15 @@ This guide explains how to integrate Plane with external secret management solut
6364

6465
Follow this pattern to manage all the [environment variables](/self-hosting/methods/kubernetes#external-secrets-config) in AWS Secrets Manager.
6566

66-
7. Create a Kubernetes secret containing AWS credentials in your application namespace:
67+
8. Create a Kubernetes secret containing AWS credentials in your application namespace:
6768
```sh
6869
kubectl create secret generic aws-creds-secret \
6970
--from-literal=access-key=<AWS_ACCESS_KEY_ID> \
7071
--from-literal=secret-access-key=<AWS_SECRET_ACCESS_KEY> \
7172
-n <application_namespace>
7273
```
7374

74-
7. Apply the following YAML to create a ClusterSecretStore resource:
75+
9. Apply the following YAML to create a ClusterSecretStore resource:
7576
```yaml
7677
apiVersion: external-secrets.io/v1beta1
7778
kind: ClusterSecretStore
@@ -94,7 +95,7 @@ This guide explains how to integrate Plane with external secret management solut
9495
```
9596
Replace `<ACCOUNT-ID>` and `<IAM ROLE>` with your AWS account ID and the role name created in Step 5.
9697

97-
8. Create an ExternalSecret resource to fetch secrets from AWS and create a corresponding Kubernetes secret:
98+
10. Create an ExternalSecret resource to fetch secrets from AWS and create a corresponding Kubernetes secret:
9899
```yaml
99100
apiVersion: external-secrets.io/v1beta1
100101
kind: ExternalSecret

0 commit comments

Comments
 (0)