Does cdk support IAM profile

[nikhilbhoj]

Hi,

I tried to run the cdk ls -l and I have multiple profile set up in my credential file.

This commands just hangs and I assume that cdk does not support profile too, as I cannot find the details in the help of cdk command.

[rix0rrr]

That's right, we don't support them yet. We do have it on the roadmap though.

In the mean time, the workaround is to populate your shell with the appropriate credentials.

[RomainMuller]

You can actually try to select a profile using environment variables (AWS_PROFILE) before running cdk ls.

Also, we're using the AWS SDK for Javascript behind the scenes, and in some cases an attempt to call the EC2 Metadata Service can cause a very long pause. If you're not running on an EC2 instance, you could consider adding export AWS_EC2_METADATA_DISABLED=1 to your shell profile. This will disable the EC2 metadata service attempt that is built into the AWS SDK for Javascript, and consequentially this possible cause of a long pause.

[nikhilbhoj]

Hi @RomainMuller , I did following
export AWS_EC2_METADATA_DISABLED=1 (as I am running in non EC2 instance)
export AWS_PROFILE=myprofile

and then try run cdk ls -l, it is still not working and hanging.
However, aws s3 ls --profile myprofile works and output s3 buckets that I own. This was just to test if my profile is not corrupted.

Also, I did all this in EC2 instance of Amazon Linux AMI, and it worked perfectly. However, their I didn't have multiple profile.

[RomainMuller]

Hey @nikhilbhoj,

Okay. I was afraid of this but hoping it would work. It may help troubleshooting if you can collect the output of running cdk ls -l --verbose. That may contain information useful for us to understand what is going wrong.

[pchaganti]

👍

[nikhilbhoj]

Hey @RomainMuller , I did following as suggested by you. I hope this information may help.

vagrant@vagrant:/hello-cdk$ echo $AWS_EC2_METADATA_DISABLED
1
vagrant@vagrant:/hello-cdk$ echo $AWS_PROFILE
myprofile
vagrant@vagrant:~/hello-cdk$ aws s3 ls --profile myprofile
2018-04-17 02:17:32 XXXXXX-bucket
2018-05-22 12:13:37 terraform-state-bucket-112

vagrant@vagrant:~/hello-cdk$ cdk ls -l --verbose
Command line arguments: { _: [ 'ls' ],
trace: false,
strict: false,
'ignore-errors': false,
ignoreErrors: false,
json: false,
j: false,
verbose: true,
v: true,
'version-reporting': undefined,
versionReporting: undefined,
version: false,
help: false,
long: true,
l: true,
'$0': '/home/vagrant/.npm-global/bin/cdk',
app: undefined,
context: undefined,
plugin: undefined,
rename: undefined }
Defaults: {
"app": "node index.js"
}
Setting "aws:cdk:toolkit:default-region" context to ap-southeast-2
Resolving default credentials
Looking up default account ID from STS

It is getting stuck here.