Skip to content

Commit b4813c4

Browse files
authored
reformat to pass prettier --check
1 parent f5c0475 commit b4813c4

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/docs/explanations/advanced-provider-configuration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@ amazon_web_services:
101101
### EKS KMS ARN (Optional)
102102

103103
You can use AWS Key Management Service (KMS) to enhance security by encrypting Kubernetes secrets in
104-
Amazon Elastic Kubernetes Service (EKS). This approach adds an extra layer of protection for sensitive
104+
Amazon Elastic Kubernetes Service (EKS). This approach adds an extra layer of protection for sensitive
105105
information, like passwords, credentials, and TLS keys, by applying user-managed encryption keys to Kubernetes
106106
secrets, supporting a [defense-in-depth strategy](https://aws.amazon.com/blogs/containers/using-eks-encryption-provider-support-for-defense-in-depth/).
107107

@@ -135,7 +135,7 @@ Here is an example of how you would set KMS key ARN in `nebari-config.yaml`.
135135
```yaml
136136
amazon_web_services:
137137
# the arn for the AWS Key Management Service key
138-
eks_kms_arn: 'arn:aws:kms:us-west-2:01234567890:key/<aws-kms-key-id>'
138+
eks_kms_arn: "arn:aws:kms:us-west-2:01234567890:key/<aws-kms-key-id>"
139139
```
140140

141141
### Launch Templates (Optional)

0 commit comments

Comments
 (0)