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

Add AWS support #848

Merged
merged 1 commit into from
May 10, 2022
Merged

Conversation

JaminB
Copy link
Contributor

@JaminB JaminB commented May 10, 2022

  • added aws.py adapted from here.
  • added corresponding aws.conf
  • updated requirements*

@JaminB
Copy link
Contributor Author

JaminB commented May 10, 2022

:)

@JaminB JaminB closed this May 10, 2022
@JaminB JaminB reopened this May 10, 2022
@JaminB JaminB mentioned this pull request May 10, 2022
@doomedraven doomedraven merged commit 32e4732 into kevoreilly:master May 10, 2022
@doomedraven
Copy link
Collaborator

thank you

@kevoreilly
Copy link
Owner

Thanks a lot.

Out of interest, how well does it work on AWS - does it scale well, any vm detection issues, etc?

@JaminB
Copy link
Contributor Author

JaminB commented May 10, 2022

I've done limited testing (only scaled up to 5 instances concurrently), but so far so good. I'll report back if I run into any issues as I scale up.

I haven't run into it personally, but if the cuckoo crashes during analysis you could be left in a situation where you have several orphaned EC2 instances running (as this module manages its own autoscaling internally) so suggest keeping the dynamic_machines_limit low or baby-sitting your EC2 environment until you feel confident your configuration is solid.

Only other kind of tricky part is the routing to get traffic back to the CAPE instance for packet-capture. All of that has to be done with routing tables inside your VPC. I eventually accomplished it by creating an AMI image always deploys inside the the same subnet, and then building an explicit routing table for that subnet that routes traffic to CAPE. After, that all of the per-analysis routing should be the same (although I have yet to implement it).

Will be sure to push any fixes if I find any bugs.

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