Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aws.execution.ec2-launch-unusual-instances working #387

Closed
agroyz opened this issue Jul 20, 2023 · 3 comments · Fixed by #390
Closed

aws.execution.ec2-launch-unusual-instances working #387

agroyz opened this issue Jul 20, 2023 · 3 comments · Fixed by #390
Assignees
Labels

Comments

@agroyz
Copy link

agroyz commented Jul 20, 2023

This is a new issue. This started with the latest build.

BTW, thanks for adding in this output. [DEBUG] Successfully assumed role! .

What is not working?
detonate aws.execution.ec2-launch-unusual-instances

Ubuntu 22.04.2 LTS

What is your Stratus Red Team version?
2.8.0

./stratus detonate aws.execution.ec2-launch-unusual-instances
2023/07/20 21:03:01 Checking your authentication against AWS
2023/07/20 21:03:01 Not warming up - aws.execution.ec2-launch-unusual-instances is already warm. Use --force to force
2023/07/20 21:03:01 [DEBUG] Successfully assumed role!
2023/07/20 21:03:01 Attempting to run up to 10 instances of type p2.xlarge
2023/07/20 21:03:02 Error while detonating attack technique aws.execution.ec2-launch-unusual-instances: expected ec2:RunInstances to return an access denied error, got instead: operation error EC2: RunInstances, https response error StatusCode: 403, RequestID: 993a3d41-5543-43ff-850e-dd3a79685bd5, api error UnauthorizedOperation: You are not authorized to perform this operation. Encoded authorization failure message: qoYeuy5DNQMk_k7JauWsrjPnqAi9h90gWITrdEQKpzKtUH4C4XeRuGX_uviYK9_27hWRbK5Pf9jBrs08Gsd23YlGh_1Df9onGQUbfcih720lVZzTMbVKIVJTFFxPLGEQHV-rFoSMAj3Q99K34ugMR00dIp_RWoySKoNNKilmkiwxep_aJ_pvimWGZgcisM3SkFh0Sx4FShxUw5Cff4AGrK9YkJIt2ScBA4SqoMpbkV9snWa8m00Y2ZnWBbNYi-thhu28GjtZ0p0VEZFQCxCuNIsxcZIgTVwe0GTeezjhEJC12Etmk_SEhlDVZ1w9G-1Mk_jbPNoi48X9_2YUTjxxIfCCZ_d5y8W9OYyBmozp33Q4wbL6xLRcCEh9lbcfnPHje2m9NPh5QrY94uFEiuih1DMTQTJCQEY0NjMaCf_U6j31tyECRo1xbAjOXSH-GslMH703sscMHYx0Ccz3iRTYEHw8FlTmhI9-l7ZpKEGN0tleGpOA5tRXYAnJfqxELlX16YnrpbV4JeK67kKmrVf4xOzkTBRKvNKgoCA9-IVxQyhF0dLMqn09IZfNNFy6K-4RukWcsD-M1Ym6LzhXba-FB7kkUiUx6R5h0R0lpjG4osiusgq3MNYswRSWxRNLK8ie97WOZ9JGbj4E6TxTti5DuPDWXjmaZ5Al8bV1TILXqkVTl8a3hm2fR1V6jhlVDaQMhpAMegiUR6Yp4TG2bFpOAnozHKwYmg

@christophetd
Copy link
Contributor

Thanks for reporting! Can you share a version number that does not have this issue? I'm currently unable to reproduce in my test AWS account on 2.8.0

@christophetd
Copy link
Contributor

Was actually able to reproduce

@christophetd
Copy link
Contributor

Fixed in #390 and will be shortly released in Stratus Red Team v2.8.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
2 participants