Skip to content

Commit 0f536ab

Browse files
committed
Run formatter
1 parent cd36d3d commit 0f536ab

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

docs/docs/how-tos/nebari-aws.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,11 +66,12 @@ Below are two sets of minimal IAM permissions required to deploy and destroy Neb
6666
:::note
6767

6868
Make sure to replace the following placeholders in the policies with your own values:
69+
6970
- `REGION`: The AWS region where you want to deploy Nebari (e.g., `us-west-2`)
7071
- `ACCOUNT_ID`: Your AWS account ID (e.g., `123456789012`)
7172
- `PROJECT_NAME`: The name of your Nebari project, specified under the `project_name` field in your `nebari-config.yaml` file (e.g., `my-nebari-project`)
7273
- `NAMESPACE`: The namespace you want to use for your Nebari deployment, specified under the `namespace` field in your `nebari-config.yaml` file (e.g., `dev`)
73-
:::
74+
:::
7475

7576
As a [best practice](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#lock-away-credentials), do not use the AWS account `root` user for any task where it's not
7677
required. Instead, create a new IAM user for each person that requires administrator access. Then make those users administrators by placing them into an "Administrators" (or any other name) user group, to which you attach the policies outlined above.

0 commit comments

Comments
 (0)