Skip to content
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

aws cloudformation package issue in CodeBuild with latest version 2.16.210 #4371

Closed
sbraverman opened this issue Aug 2, 2019 · 8 comments
Closed

Comments

@sbraverman
Copy link

Problem

aws cloudformation package issue in CodeBuild with latest version 2.16.210

Error seen

[Container] 2019/08/02 21:40:44 Running command aws cloudformation package --template-file /tmp/packaged/sam.json --s3-bucket ${APP_S3_BUCKET} --output-template-file transformed.yaml 
 
Credential named assume-role-with-web-identity not found. 

Bandaid Solution

hard-code awscli to install previous version: 1.16.209

Let me know if more information is necessary.
I did already open a ticket in AWS Support over this: 097198515119

@2ps
Copy link

2ps commented Aug 3, 2019

I created case 6315544681 before I saw this. Thank you @sbraverman !

@WillLiu360
Copy link

WillLiu360 commented Aug 5, 2019

also having the same problem with aws s3 command.

@W-Ely
Copy link

W-Ely commented Aug 5, 2019

Experiencing the same s3 issue. Locking on previous version as bandaid works.

@trastle
Copy link

trastle commented Aug 6, 2019

I'm also seeing this error msg from an ECR login on 1.16.211
Issue was not present in 1.16.209

@JayCork
Copy link

JayCork commented Aug 6, 2019

Does Amazon not work on Mondays? Or is their revert button broken as well?

@tabasnett
Copy link

I'm not sure if this is the same problem that everyone else has been having, but we saw this same error yesterday with some of our python builds. It turned out that we were specifying an "old" version of botocore for those builds and it had got out of sync with aws-cli. Removing the reference to the botocore dependency so that the version of botocore installed with aws-cli was used, seems to have fixed our problem.

@barroca
Copy link

barroca commented Aug 6, 2019

Same problem here, we are using pip install awscli (on our Dockerfile) and it seems that this is an issue introduced with latest release.

@sbraverman
Copy link
Author

AWS support got back to me on this case, and suggested to update the botocore version to:
botocore==1.12.200
This latest version of awscli has a dependency on botocode 1.12.200.

I updated to botocore==1.12.201 and sure enough the error disappeared.
I think this issue can now be closed.
Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants