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

Rewrite running on AWS EC2 instance #4272

Merged
merged 4 commits into from
Aug 13, 2024

Conversation

ilija-lazoroski
Copy link
Contributor

@ilija-lazoroski ilija-lazoroski commented Aug 6, 2024

What does this PR do?

Issue #4209 .

Add any further explanations here.

PR Checklist

  • Have you added an explanation of what your changes do and why you'd like to include them?
  • Is the TravisCI build passing?
  • Was the CHANGELOG.md updated to reflect the changes?
  • Was the documentation framework updated to reflect the changes?
  • Have you checked that you haven't introduced any duplicate code?

Testing Checklist

  • Added relevant unit tests?
  • Do all unit tests pass?
  • Do all end-to-end tests pass?
  • Any other testing performed?

    Tested by {Running the Monkey locally with relevant config/running Island/...}

  • If applicable, add screenshots or log transcripts of the feature working
image

@ilija-lazoroski ilija-lazoroski force-pushed the 4209-aws-run-on-ec2-machine-feature branch from 60aa6a5 to 83b4f00 Compare August 6, 2024 10:10
docs/content/features/run_on_aws.md Outdated Show resolved Hide resolved
docs/content/features/run_on_aws.md Outdated Show resolved Hide resolved
docs/content/features/run_on_aws.md Outdated Show resolved Hide resolved
docs/content/features/run_on_aws.md Outdated Show resolved Hide resolved
docs/content/features/run_on_aws.md Outdated Show resolved Hide resolved
docs/content/features/run_on_aws.md Outdated Show resolved Hide resolved
docs/content/features/run_on_aws.md Outdated Show resolved Hide resolved
@ilija-lazoroski ilija-lazoroski force-pushed the 4209-aws-run-on-ec2-machine-feature branch 3 times, most recently from e3d1354 to ab38708 Compare August 6, 2024 10:52
Comment on lines 20 to 22
This feature lets you run Infection Monkey Agent on your chosen EC2
instances without the requirement of manual installation, enabling the simulation of
various attack scenarios across your AWS infrastructure.
Copy link
Collaborator

@mssalvatore mssalvatore Aug 12, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • "This feature" is somewhat ambiguous after reading the previous paragraph. What feature? The Amazon Message Delivery Service?
  • This standalone sentence should either have some supporting sentences or, itself, be a supporting sentence for something else.

Maybe we need a better/clearer name for this feature. It would improve some of the language in this doc.

Comment on lines 11 to 18
The Infection Monkey can run on AWS EC2 instances using the
[AWS Systems Manager (SSM) Agent](
https://docs.aws.amazon.com/systems-manager/latest/userguide/what-is-systems-manager.html).
Each EC2 instance has an [SSM Agent](
https://docs.aws.amazon.com/systems-manager/latest/userguide/ssm-agent.html)
installed for updating, managing, and configuring the instance.
It executes requests received from the AWS Systems Manager, and uses the Amazon
Message Delivery Service to report back status and execution details.
Copy link
Collaborator

@mssalvatore mssalvatore Aug 12, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This context is fantastic. Should we add links for AWS Systems Manager and AMDS? Or are they not important?

instances without the requirement of manual installation, enabling the simulation of
various attack scenarios across your AWS infrastructure.

EC2 instances must be configured with the SSM Agent and the necessary IAM roles
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
EC2 instances must be configured with the SSM Agent and the necessary IAM roles
In order to launch Infection Monkey Agents using the AWS SSM Agent, EC2 instances must be configured with the SSM Agent and the necessary IAM roles

What does it mean for an EC2 instance to be "configured with the SSM Agent". Do they need to "enable the SSM Agent on the EC2 instance?" Can we link to AWS's documentation that explains what steps they need to take?

Maybe we need a better/clearer name for this feature. It would improve some of the language in this doc.

Copy link
Contributor Author

@ilija-lazoroski ilija-lazoroski Aug 13, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There can be instances that don't have SSM Agent preinstalled. I may need to reword this a bit.

It will be definitely easier to have a concise name for the feature. Maybe "Infection Monkey AWS Execution" ?

@ilija-lazoroski ilija-lazoroski force-pushed the 4209-aws-run-on-ec2-machine-feature branch 2 times, most recently from c221bb6 to a6292e8 Compare August 13, 2024 07:56
@ilija-lazoroski ilija-lazoroski marked this pull request as ready for review August 13, 2024 08:09
docs/content/features/run_on_aws.md Outdated Show resolved Hide resolved
docs/content/features/run_on_aws.md Outdated Show resolved Hide resolved
docs/content/features/run_on_aws.md Outdated Show resolved Hide resolved
docs/content/features/run_on_aws.md Outdated Show resolved Hide resolved
docs/content/features/run_on_aws.md Outdated Show resolved Hide resolved
docs/content/features/run_on_aws.md Outdated Show resolved Hide resolved
docs/content/features/run_on_aws.md Outdated Show resolved Hide resolved
docs/content/features/run_on_aws.md Outdated Show resolved Hide resolved
docs/content/features/run_on_aws.md Outdated Show resolved Hide resolved
docs/content/features/run_on_aws.md Outdated Show resolved Hide resolved
Copy link
Contributor

@shreyamalviya shreyamalviya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please also take a look at the comments from my previous review that I unresolved. You missed a couple.

@ilija-lazoroski ilija-lazoroski force-pushed the 4209-aws-run-on-ec2-machine-feature branch 2 times, most recently from a1f50e9 to 362471f Compare August 13, 2024 11:49
docs/content/features/run_on_aws.md Outdated Show resolved Hide resolved
docs/content/features/run_on_aws.md Outdated Show resolved Hide resolved
docs/content/features/run_on_aws.md Outdated Show resolved Hide resolved
docs/content/features/run_on_aws.md Outdated Show resolved Hide resolved
docs/content/features/run_on_aws.md Outdated Show resolved Hide resolved
@ilija-lazoroski ilija-lazoroski force-pushed the 4209-aws-run-on-ec2-machine-feature branch from 362471f to e87d30d Compare August 13, 2024 12:07
@ilija-lazoroski ilija-lazoroski force-pushed the 4209-aws-run-on-ec2-machine-feature branch from e87d30d to 03ee861 Compare August 13, 2024 12:13
Comment on lines 27 to 30
1. Ensure that the SSM Agent is installed on the EC2 instance on which
Infection Monkey will run.
1. Ensure that the EC2 instance has the necessary IAM roles to allow
the SSM Agent to execute commands.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This starts to feel like a "how to".

@mssalvatore mssalvatore force-pushed the 4209-aws-run-on-ec2-machine-feature branch from 636b3a7 to cc07e43 Compare August 13, 2024 17:46
@mssalvatore mssalvatore force-pushed the 4209-aws-run-on-ec2-machine-feature branch from cc07e43 to 585cf13 Compare August 13, 2024 17:47
@mssalvatore mssalvatore merged commit 4ab0353 into develop Aug 13, 2024
@mssalvatore mssalvatore deleted the 4209-aws-run-on-ec2-machine-feature branch August 13, 2024 17:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants