❓ General Issue

The Question

When attempting to run CDK, if your AWS credentials are expired, CDK commands succeed, but take up to 161% more time to run. This happens for all cdk commands. Should CDK notify users if their credentials are expired? Should CDK run more quickly despite the expired credentials?

Environment

• CDK CLI Version: 1.70.0 (build c145314) (also tried 1.75.0)
• Module Version: (does not matter - create an empty TypeScript CDK app and run cdk synth on it with an expired or not present credential)
• Node.js Version: v15.3.0 (also tried LTS)
• OS: macOS Catalina 10.15.7
• Language (Version): typescript 3.9.7, Python 3.8.6

Other information

# with profile set:
> time cdk synth
cdk synth  2.59s user 0.42s system 152% cpu 1.966 total
> time cdk synth
cdk synth  2.67s user 0.41s system 154% cpu 1.996 total

# without profile set: 
> time cdk synth
cdk synth  2.77s user 0.44s system 16% cpu 18.896 total
> time cdk synth
cdk synth  2.81s user 0.44s system 25% cpu 12.685 total