Skip to content

Updated README.md with instructions to URL-encode AWS <secret_access_key> #80

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
percona-ysorokin merged 1 commit into from
Dec 9, 2025
Merged

Updated README.md with instructions to URL-encode AWS <secret_access_key> #80

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -316,6 +316,8 @@ In case of `AWS S3`, the URIs must have the following format.
- `<region>` - the name of the AWS region (e.g. `us-east-1`) where this bucket was created (optional, if omitted, it will be auto-detected),
- `<path>` - a virtual path (key prefix) inside the bucket under which all the binary log files will be stored.

Note: your `<secret_access_key>` along with alphanumeric characters (`[a-zA-Z0-9]`) may also include `+` and `/` and because it needs to be inserted into the `userinfo` part of the URI, it is necessary to perform URL-encoding of selected special characters: `/` needs to be transformed into `%2F`, `+` can be left as is.

In case of `S3`-compatible service with custom endpoint, the URIs must have the following format.
`http[s]://[<access_key_id>:<secret_access_key>@]<host>[:<port>]/<bucket_name>/<path>`, where:
- `<host>` - either a host name or an IP address of an `S3`-compatible server,
Expand Down