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
After migration to Concourse 7.12.0 we were unable to fetch images from ECR with the type of the resource docker-resource. Registry-image type worked same as in version 7.11.2.
It seems like the update to aws-sdk-go-v2 (ba8c089) in version 1.9.0 messed up the ECR implementation as we started to face issue with getting images from ECR repository. This was not a case in version 1.8.1
We provide aws_access_key_id, aws_secret_access_key but not aws_session_token. This was functioning in lower version Hovewer it seems like new version might require also aws_session_token.
Reproduction steps
Migration to new version of concourse 7.12.0 with the latest docker-image resource (1.9.0)
ECR Implementation for docker images
Run any pipeline with this resource type
...
Expected behavior
To be able to pull images from ECR without providing session token.
Additional context
No response
The text was updated successfully, but these errors were encountered:
I think this is the same issue I reported in #372. A fix is in master but a new image release has not yet been published. (We've pinned to image version 1.8.1 in the meantime.)
Describe the bug
After migration to Concourse 7.12.0 we were unable to fetch images from ECR with the type of the resource docker-resource. Registry-image type worked same as in version 7.11.2.
It seems like the update to aws-sdk-go-v2 (ba8c089) in version 1.9.0 messed up the ECR implementation as we started to face issue with getting images from ECR repository. This was not a case in version 1.8.1
We provide aws_access_key_id, aws_secret_access_key but not aws_session_token. This was functioning in lower version Hovewer it seems like new version might require also aws_session_token.
Reproduction steps
...
Expected behavior
To be able to pull images from ECR without providing session token.
Additional context
No response
The text was updated successfully, but these errors were encountered: