You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! It would be awesome if the Readme could be extended with troubleshooting tips for permissions. I will provide two examples where I lost quite a while due to this.
Example 1: Bad keys
I have reused existing aws creds setup we had already for ECR
InvalidToken: The provided token is malformed or otherwise invalid. status code: 400
What would have helped me
I can fly -t myteam hijack -job=mypipeline/myjob and enter the S3 Docker for put but what next?
How can I see what credentials were supplied to the task? (in Don't hardcode AWS region #1 those would be empty, in Support S3 compatible / custom endpoint URL? #2 token would be ((dev-session-token) instead of the expected value) I do not have them since they come from Concourse variables (which I could likely look up in AWS Secrets Manager or where we have them), moreover I also need to see that they were passed correctly to the S3 resource
How can I manually check whether access to the bucket is allowed? I guess I could issue a few commands (which?) to install awscli and use that manually to try to upload - but again I'd need the credentials
Thank you!!!
The text was updated successfully, but these errors were encountered:
Hello! It would be awesome if the Readme could be extended with troubleshooting tips for permissions. I will provide two examples where I lost quite a while due to this.
Example 1: Bad keys
I have reused existing aws creds setup we had already for ECR
not noticing that S3 uses different keys. While
get
succeeded,put
failed withExample 2: Missing token due to a typo
I fixed the keys but made a typo, forgetting a
)
:Not it failed with clear but for my puzzling
What would have helped me
I can
fly -t myteam hijack -job=mypipeline/myjob
and enter the S3 Docker forput
but what next?((dev-session-token)
instead of the expected value) I do not have them since they come from Concourse variables (which I could likely look up in AWS Secrets Manager or where we have them), moreover I also need to see that they were passed correctly to the S3 resourceawscli
and use that manually to try to upload - but again I'd need the credentialsThank you!!!
The text was updated successfully, but these errors were encountered: