-
Notifications
You must be signed in to change notification settings - Fork 431
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.
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
upload file stuck when I set AWS_SECRET_ACCESS_KEY to empty #1584
Comments
is it default to go to 169.254.169.254 server to request token if AWS_SECRET_ACCESS_KEY not set? |
what to do if |
Hi! If |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Database name
Wal-g provides support for many databases, please write down name of database you uses.
Issue description
Describe your problem
When I set AWS_SECRET_ACCESS_KEY to empty, and execute
wal-g wal-push
to upload file to S3 bucket, it stuck. I debug it and print the message, it show:I tested it in an offline network environment(can not access website)
so should
AWS_SECRET_ACCESS_KEY
must be set?Please provide steps to reproduce
// it can really help
Please add config and wal-g stdout/stderr logs for debug purpose
also you can use WALG_LOG_LEVEL=DEVEL for logs collecting
If you can, provide logs
```bash any logs here ```
The text was updated successfully, but these errors were encountered: