Format AWS envars

libremfg · Nov 4, 2024 · be66307 · be66307
1 parent 7b68d5e
commit be66307
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 6 deletions.
diff --git a/content/deploy/backup/binary.md b/content/deploy/backup/binary.md
@@ -37,9 +37,9 @@ To back up the database, follow these steps:
     kubectl logs {{< param application_name >}}-baas-baas-alpha-0 --tail=80
     ```
 1. Set the follow environmental variables:
-   - `AWS_ACCESS_KEY_ID` AWS access key with permissions to write to the destination bucket 
-   - `AWS_SECRET_ACCESS_KEY` AWS access key with permissions to write to the destination bucket
-   - `AWS_SESSION_TOKEN` AWS session token (if required)
+   - `AWS_ACCESS_KEY_ID` your AWS access key with permissions to write to the destination bucket 
+   - `AWS_SECRET_ACCESS_KEY` your AWS access key with permissions to write to the destination bucket
+   - `AWS_SESSION_TOKEN` your AWS session token (if required)
 
 1. Open a pod shell for one of the alpha pods. If you are using the terminal, run this command:
 

diff --git a/content/deploy/restore/binary.md b/content/deploy/restore/binary.md
@@ -25,9 +25,9 @@ Before you start, ensure you have the following:
 <!-- if procedure is very long, consider using h3s -->
 
 1. Set the follow environmental variables:
-   - `AWS_ACCESS_KEY_ID` AWS access key with permissions to write to the destination bucket
-   - `AWS_SECRET_ACCESS_KEY` AWS access key with permissions to write to the destination bucket
-   - `AWS_SESSION_TOKEN` AWS session token (if required)
+   - `AWS_ACCESS_KEY_ID` your AWS access key with permissions to write to the destination bucket
+   - `AWS_SECRET_ACCESS_KEY` your AWS access key with permissions to write to the destination bucket
+   - `AWS_SESSION_TOKEN` your AWS session token (if required)
 
 1. Confirm the cluster and namespace are correct.