This repository was archived by the owner on Apr 26, 2021. It is now read-only.
Azure Machinery for Cuckoo#3120
Open
cccs-kevin wants to merge 64 commits intocuckoosandbox:masterfrom
Open
Conversation
…oo envs can exist in same resource group
…e other files to fit cloud application
|
Man this is brilliant, good work @cccs-kevin! |
…ng logging, adding ability to acquire by machine_id
…ixing ClientRequestError bug
…erent machine pools
…tching and concurrent operations
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Thanks for contributing! But first: did you read our community guidelines?
https://cuckoo.sh/docs/introduction/community.html
What I have added/changed is:
The goal of my change is:
Use cloud resources for malware detonation
What I have tested about my change is:
Functionality, but only by hand.
Things to NOTE:
The Azure API has rate limits to how often you can submit requests. So far the current implementation of this machinery hits the API limit if it process 400 files per hour (each file requires a new VM which is created using a network interface card and a managed disk -> 3 write calls). Azure doc
I'm currently working on a method that utilizes Azure Virtual Machine Scale Sets with Ephemeral disks which avoid hitting this API limit.