-
Notifications
You must be signed in to change notification settings - Fork 75
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
s3auth file doesn't work for provided credentials. #48
Comments
This is my working /etc/apt/s3.auth.conf file, note where values are quoted and where they are not quoted:
Yes, the "Token" parameter seems to be necessary, even if it's not being used. This is consistent with the "Region" parameter and not consistent with the "AccessKeyId" and "SecretAccessKey" parameters. |
Hello, I see that the next release addressing this issue has been tagged 7 days ago: However it doesn't appear to have been released since apt-get is still vending 2.0.0. |
It can be release in the next couple of days in here after a bit more testing by people, but it won't find it's way to Debian anytime soon as Debian is in deep freeze we're probably around a month from the release, so it will have to wait a bit before I'm going to upload it to Debian archive. |
Understood, thanks for the update! |
Hello, any updates on this release? |
@vorlock Bump |
When setting: AccessKeyId and SecretAccessKey in /etc/apt/s3auth.conf we are greeted with the following error:
I have validated the key(s) are valid and have access.
Now I've tried this with IAM permissions assigned to an EC2 instance and that works as expected, only when I set the keys in the config do things not work as expected.
Glancing through the code it doesn't appear as though the token never gets called/created in that particular scenario. In fact the only two ways I ever see the session token being assigned is when it's read from the ENV Var:
OR it's attempted to connect locally (when in AWS and IAM is assigned to the instance):
keep in mind my Python knowledge is minimal and this is from the best I can figure out, unless there is something I messed up on my end (possibly) however I'm just not finding out where exactly it's hung up.
Thanks,
Stephen
The text was updated successfully, but these errors were encountered: