The AWS CLI inside the CloudGoat Docker image is currently broken due to a boto3 version upgrade.
Running any AWS CLI command results in the following error:
KeyError: 'opsworkscm'
Root Cause
This issue appears after boto3 was upgraded from:
1.37.15 → 1.42.72
The newer boto3 version introduces a mismatch with the AWS CLI dependencies (likely botocore/service definitions), causing the CLI to fail when loading available services.
Steps to Reproduce
Run the CloudGoat Docker image
Execute any AWS CLI command, e.g.:
aws sts get-caller-identity
Observe failure with:
KeyError: 'opsworkscm'
##Expected Behavior
AWS CLI commands should execute normally and return valid responses.
Actual Behavior
AWS CLI crashes with a KeyError related to opsworkscm.
Suggested Fix
Pin boto3 to a compatible version (e.g. 1.37.15), or
Align boto3, botocore, and AWS CLI versions to compatible releases
The AWS CLI inside the CloudGoat Docker image is currently broken due to a boto3 version upgrade.
Running any AWS CLI command results in the following error:
KeyError: 'opsworkscm'
Root Cause
This issue appears after boto3 was upgraded from:
1.37.15 → 1.42.72
The newer boto3 version introduces a mismatch with the AWS CLI dependencies (likely botocore/service definitions), causing the CLI to fail when loading available services.
Steps to Reproduce
Run the CloudGoat Docker image
Execute any AWS CLI command, e.g.:
aws sts get-caller-identity
Observe failure with:
KeyError: 'opsworkscm'
##Expected Behavior
AWS CLI commands should execute normally and return valid responses.
Actual Behavior
AWS CLI crashes with a KeyError related to opsworkscm.
Suggested Fix
Pin boto3 to a compatible version (e.g. 1.37.15), or
Align boto3, botocore, and AWS CLI versions to compatible releases