1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
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
Contenus pertinents
- demandé il y a un an
- demandé il y a 15 jours
- demandé il y a un mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 3 ans