1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
0
There does appear to be a difference in behavior between the AWS CLI and CDK when it comes to handling of the config and credentials files. I found a GitHub issue on the aws-cdk project that describes the same issue you seem to be facing here (1)
Some are reporting success by adding a source_profile
to their ~/.aws/credentials
file. Despite having the same name, it appears that CDK may not be looking at non-default credentials when supplied with a --profile
You may also find more details on the overall behavior of CDK by adding the --verbose
flag in your CDK commands
(1) https://github.com/aws/aws-cdk/issues/5053#issuecomment-770527518
관련 콘텐츠
- AWS 공식업데이트됨 10달 전
- AWS 공식업데이트됨 일 년 전
- AWS 공식업데이트됨 일 년 전