-
-
Notifications
You must be signed in to change notification settings - Fork 908
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
s3cmd is not working with AWS web identity token #1218
Comments
Same issue using gitlab/EKS in govcloud.
|
Is there any additional information we should provide? |
It seems to be available in the latest release I haven't tried yet. |
IRSA support works for me with GitLab 14.5.1. |
We are on Gitlab 14.5.0, let me update to 14.5.1 and confirm. Thanks. |
I still get the error: $ s3cmd --version
s3cmd version 2.2.0
$ s3cmd ls s3://my-bucket-name
ERROR: /home/git/.s3cfg: None
ERROR: Configuration file not available.
ERROR: Consider using --configure parameter to create one. Image: |
I configure
|
Can we get a new s3cmd release for this? GitLab is using the latest release (2.2.0) and so doesn't have this change. |
Should be fixed already, and the update 2.3.0 should be released with it today. |
Not fixed in 15.5.1 at least I get this during restore:
Despite backuping everything and storing to S3 works, all other services work with S3, just the restore.
However, I get also this warning:
Maybe the /home/git/.s3cfg is not correct ? What should be in there ? |
OK here is what did it for me: /home/git/.s3cfg contains only:
The IAM role to access the bucket got S3:* cause following permissions were not enough:
I would be very happy if somebody could point me to permission I was missing. Thanks. |
Image: registry.gitlab.com/gitlab-org/build/cng/gitlab-toolbox-ee:v14.4.1
s3cmd version: 2.2.0
Configuration file is available:
Environment variables are set:
$ env | grep AWS AWS_DEFAULT_REGION=eu-central-1 AWS_REGION=eu-central-1 AWS_ROLE_ARN=arn:aws:iam::123456789:role/my-iam-role AWS_WEB_IDENTITY_TOKEN_FILE=/var/run/secrets/eks.amazonaws.com/serviceaccount/toke
aws sts get-caller-identity
shows me the correct IAM role from the service account.The text was updated successfully, but these errors were encountered: