Skip to content

Commit 0cc0d64

Browse files
committed
fix cr comments
1 parent 28d20ac commit 0cc0d64

File tree

1 file changed

+7
-10
lines changed

1 file changed

+7
-10
lines changed

docs/howto/garbage-collection/standalone-gc.md

+7-10
Original file line numberDiff line numberDiff line change
@@ -64,15 +64,6 @@ docker pull treeverse/lakefs-sgc:<tag>
6464

6565
## Setup
6666

67-
### Credentials
68-
69-
Standalone GC supports S3 and S3-compatible storage backends and relies on AWS credentials for authentication.
70-
71-
Currently, `lakefs-sgc` does not allow you to explicitly set AWS credentials within the tool itself. Instead, it reads
72-
credentials from the hosting machine’s environment. This means you must ensure the machine is properly configured with AWS credentials beforehand.
73-
74-
To set up credentials, follow AWS guidelines, such as those outlined in [this guide](https://docs.aws.amazon.com/cli/v1/userguide/cli-chap-configure.html).
75-
7667
### Permissions
7768

7869
To run `lakefs-sgc`, you need both AWS (or S3-compatible) storage and lakeFS user permissions as outlined below:
@@ -139,7 +130,13 @@ The minimum required permissions for lakeFS are:
139130
}
140131
```
141132

142-
#### Using S3-compatible clients
133+
### Credentials
134+
135+
Standalone GC supports S3 and S3-compatible storage backends and relies on AWS credentials for authentication. To set up
136+
credentials, follow AWS guidelines, such as those outlined in [this guide](https://docs.aws.amazon.com/cli/v1/userguide/cli-chap-configure.html).
137+
For details on how to pass credentials to `lakefs-sgc`, refer to the instructions in [How to Run Standalone GC](#how-to-run-standalone-gc).
138+
139+
### Using S3-compatible clients
143140

144141
`lakefs-sgc` leverages AWS credentials to work seamlessly with S3-compatible storage solutions, such as [MinIO](https://min.io/).
145142
Follow the steps below to set up and use `lakefs-sgc` with an S3-compatible client:

0 commit comments

Comments
 (0)