What is not working?
stratus fails to use was credentials
What OS are you using?
Ubuntu 18.04.5 x86_64
What is your Stratus Red Team version?
1.4.0
Full output?
./stratus warmup aws.exfiltration.ec2-security-group-open-port-22-ingress
2022/02/14 14:47:36 Checking your authentication against the AWS API
2022/02/14 14:47:36 You are not authenticated against AWS, or you have not set your region. Make sure you are authenticated against AWS, and you have a default region set in your AWS config or environment (export AWS_DEFAULT_REGION=us-east-1)
Files in $HOME/.stratus-red-team?
ls -altr /home/application/.stratus-red-team/
total 60620
drwxr--r-- 2 application application 4096 Feb 11 16:11 aws.persistence.iam-backdoor-user
-rwx------ 1 application application 61956096 Feb 11 16:11 terraform
drwxr--r-- 2 application application 4096 Feb 11 16:28 k8s.privilege-escalation.privileged-pod
drwxr--r-- 2 application application 4096 Feb 11 16:28 k8s.privilege-escalation.hostpath-volume
drwxr--r-- 2 application application 4096 Feb 11 16:28 k8s.persistence.create-admin-clusterrole
drwxr--r-- 2 application application 4096 Feb 11 16:28 k8s.credential-access.steal-serviceaccount-token
drwxr--r-- 2 application application 4096 Feb 11 16:28 aws.persistence.lambda-backdoor-function
drwxr--r-- 2 application application 4096 Feb 11 16:28 aws.persistence.iam-create-user-login-profile
drwxr--r-- 2 application application 4096 Feb 11 16:28 aws.persistence.iam-create-admin-user
drwxr--r-- 2 application application 4096 Feb 11 16:28 aws.persistence.iam-backdoor-role
drwxr--r-- 2 application application 4096 Feb 11 16:28 aws.exfiltration.s3-backdoor-bucket-policy
drwxr--r-- 2 application application 4096 Feb 11 16:28 aws.exfiltration.rds-share-snapshot
drwxr--r-- 2 application application 4096 Feb 11 16:28 aws.exfiltration.ec2-share-ebs-snapshot
drwxr--r-- 2 application application 4096 Feb 11 16:28 aws.exfiltration.ec2-share-ami
drwxr--r-- 2 application application 4096 Feb 11 16:28 aws.exfiltration.ec2-security-group-open-port-22-ingress
drwxr--r-- 2 application application 4096 Feb 11 16:28 aws.execution.ec2-user-data
drwxr--r-- 2 application application 4096 Feb 11 16:28 aws.discovery.ec2-enumerate-from-instance
drwxr--r-- 2 application application 4096 Feb 11 16:28 aws.discovery.ec2-download-user-data
drwxr--r-- 2 application application 4096 Feb 11 16:28 aws.defense-evasion.vpc-remove-flow-logs
drwxr--r-- 2 application application 4096 Feb 11 16:28 aws.defense-evasion.organizations-leave
drwxr--r-- 2 application application 4096 Feb 11 16:28 aws.defense-evasion.cloudtrail-stop
drwxr--r-- 2 application application 4096 Feb 11 16:28 aws.defense-evasion.cloudtrail-lifecycle-rule
drwxr--r-- 2 application application 4096 Feb 11 16:28 aws.defense-evasion.cloudtrail-event-selectors
drwxr--r-- 2 application application 4096 Feb 11 16:28 aws.defense-evasion.cloudtrail-delete
drwxr--r-- 2 application application 4096 Feb 11 16:28 aws.credential-access.ssm-retrieve-securestring-parameters
drwxr--r-- 2 application application 4096 Feb 11 16:28 aws.credential-access.secretsmanager-retrieve-secrets
drwxr--r-- 2 application application 4096 Feb 11 16:28 aws.credential-access.ec2-steal-instance-credentials
drwxr--r-- 2 application application 4096 Feb 11 16:28 aws.credential-access.ec2-get-password-data
drwxr--r-- 29 application application 4096 Feb 11 16:28 .
drwxr-xr-x 14 application application 4096 Feb 14 14:45 ..
It is also worth mentioning that running aws sts get-caller-identity
returns the User ID, Account, and role being used. AWS_REGION and AWS_DEFAULT_REGION are both correctly set.
kind/question status/triage