Skip to content

Commit 32b7f39

Browse files
committed
Clarify that the cortex bucket is intended for the cluster's use only
1 parent 93032e2 commit 32b7f39

File tree

2 files changed

+6
-1
lines changed

2 files changed

+6
-1
lines changed

docs/cluster-management/config.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,9 +23,10 @@ cluster_name: cortex
2323
region: us-west-2
2424

2525
# S3 bucket (default: <cluster_name>-<RANDOM_ID>)
26+
# note: your cortex cluster uses this bucket for metadata storage, and it should not be accessed directly (a separate bucket should be used for your models)
2627
bucket: # cortex-<RANDOM_ID>
2728

28-
# List of availability zones for your region (default: 3 random availability zones from the specified region)
29+
# list of availability zones for your region (default: 3 random availability zones from the specified region)
2930
availability_zones: # e.g. [us-west-2a, us-west-2b, us-west-2c]
3031

3132
# instance type

docs/cluster-management/uninstall.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,10 @@ If you modified your bash profile, you may wish to remove `source <(cortex compl
2424

2525
## Cleaning up AWS
2626

27+
Since you may wish to have access to your data after spinning down your cluster, Cortex's bucket and log groups are not automatically deleted when running `cortex cluster down`.
28+
29+
To delete them:
30+
2731
```bash
2832
# set AWS credentials
2933
export AWS_ACCESS_KEY_ID=***

0 commit comments

Comments
 (0)