You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issues isn't the way to ask for account activation. Ping capesandbox in Twitter with your username
This is open source and you are getting free support so be friendly!
Prerequisites
Please answer the following questions for yourself before submitting an issue.
[ * ] I am running the latest version
[ * ] I did read the README!
[ * ] I checked the documentation and found no answer
[ * ] I checked to make sure that this issue has not already been filed
[ * ] I'm reporting the issue to the correct repository (for multi-repository projects)
[ * ] I have read and checked all configs (with all optional parts)
Expected Behavior
The aws.conf has enough configuration steps to look into what instance ID and snapshot ID to launch the correct machine. This means, whenever you run poetry run python3 cuckoo.py and it gets ready for analysis, uploading a binary to test from the web UI, it should turn off the specified instance, re-launch it, and do the analysis.
Current Behavior
Once poetry run python3 cuckoo.py is ran, CAPEv2 turns off the instance and readies it up for analysis. It awaits user input from the web UI, and once that's done, it crashes with an error saying that the AMI is not placed in aws.conf even though autoscale = no is configured and commented out.
Everything under [machine_name] for configuration is set where machines = machine_name is configured. It should follow up and use the snapshot, however, it gets stuck and throws this error: Failure in AnalysisManager.run: An error occurred (InvalidAMIID.Malformed) when calling the RunInstances operation: Invalid id: "ami-abcdefgh123456789" (expecting "ami-...")
Failure Information (for bugs)
There may be a configuration logic or parsing issue where it WANTS to create a new instance, regardless of autoscaling is turned off. So, it does not just turn on the existing EC2 with the hard coded instance ID, it just wants to make a new one for some reason due to the following error lines:
File "/opt/CAPEv2/lib/cuckoo/core/scheduler.py", line 355, in acquire_machine
machine = machinery.acquire(
File "/opt/CAPEv2/modules/machinery/aws.py", line 184, in acquire
self._start_or_create_machines() # prepare another machine
File "/opt/CAPEv2/modules/machinery/aws.py", line 208, in _start_or_create_machines
if not self._allocate_new_machine():
File "/opt/CAPEv2/modules/machinery/aws.py", line 139, in _allocate_new_machine
instance = self._create_instance(
File "/opt/CAPEv2/modules/machinery/aws.py", line 315, in _create_instance
response = self.ec2_resource.create_instances(
Steps to Reproduce
Configure aws.conf by placing the credentials in addition in ~/.aws/credentials
Turn off the autoscaling feature, or comment out the entire thing
Make sure that you have created your guest, and have made a snapshot out of it. Copy the Instance ID and snapshot ID
Place the info from step 3 in the appropriate locations, in addition to the private IP of the host, including the SG and subnets.
Make sure arch is also placed under the [machine_name] where machines = machine_name to force the arch to be seen by CAPE, otherwise, it does not, and is another issue.
Launch poetry run python3 cuckoo.py, it will turn off the machine, and await an entry.
Go to the web UI and upload a sample
CAPE will complain that there is no AMI ID placed, even though in this configuration, it is not needed
Note that I've tried placing the AMI ID, it did not work still. I'm assuming the source code of scheduler.py or aws.py need to be changed? I can look into it soon to see what I can do.
Context
Basic AWS setup, default Windows AMI and Ubuntu 22.04 images.
Hello, AWS is community driven machinery, we can't help with this, so wait till someone with AWS comes to rescue o you will find to figurate yourself, as error comes from aws related library not cape
About accounts on capesandbox.com
This is open source and you are getting free support so be friendly!
Prerequisites
Please answer the following questions for yourself before submitting an issue.
Expected Behavior
The
aws.conf
has enough configuration steps to look into what instance ID and snapshot ID to launch the correct machine. This means, whenever you runpoetry run python3 cuckoo.py
and it gets ready for analysis, uploading a binary to test from the web UI, it should turn off the specified instance, re-launch it, and do the analysis.Current Behavior
Once
poetry run python3 cuckoo.py
is ran, CAPEv2 turns off the instance and readies it up for analysis. It awaits user input from the web UI, and once that's done, it crashes with an error saying that the AMI is not placed inaws.conf
even thoughautoscale = no
is configured and commented out.Everything under
[machine_name]
for configuration is set wheremachines = machine_name
is configured. It should follow up and use the snapshot, however, it gets stuck and throws this error:Failure in AnalysisManager.run: An error occurred (InvalidAMIID.Malformed) when calling the RunInstances operation: Invalid id: "ami-abcdefgh123456789" (expecting "ami-...")
Failure Information (for bugs)
There may be a configuration logic or parsing issue where it WANTS to create a new instance, regardless of autoscaling is turned off. So, it does not just turn on the existing EC2 with the hard coded instance ID, it just wants to make a new one for some reason due to the following error lines:
Steps to Reproduce
aws.conf
by placing the credentials in addition in~/.aws/credentials
arch
is also placed under the[machine_name]
wheremachines = machine_name
to force thearch
to be seen by CAPE, otherwise, it does not, and is another issue.poetry run python3 cuckoo.py
, it will turn off the machine, and await an entry.Note that I've tried placing the AMI ID, it did not work still. I'm assuming the source code of
scheduler.py
oraws.py
need to be changed? I can look into it soon to see what I can do.Context
Basic AWS setup, default Windows AMI and Ubuntu 22.04 images.
Failure Logs
The text was updated successfully, but these errors were encountered: