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 Deployment guide to README.md #1982

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

Y4nush
Copy link
Contributor

@Y4nush Y4nush commented Feb 25, 2024

Hi, I noticed that there is no documentation on how to deploy to AWS, such as what you have for Azure. I have been working on a comprehensive guide that explains how to deploy CAPEv2 to AWS from scratch. I would appreciate it if you would agree to add it to the README or to another location in the repository. The source code of my website is available in that repository: https://github.com/Y4nush/y4nush.com.
Thank you!

@doomedraven
Copy link
Collaborator

doomedraven commented Feb 26, 2024

hello, readme is not a place for that, but if that is ok, i will copy your work to cape docs specially mentioning that is your work and link your writeup. let me know if that is ok for you. You can see how we did that with wireguard from external blogpost https://capev2.readthedocs.io/en/latest/installation/host/routing.html#setup-wireguard

PS thank you for blogpost, is always a help

@doomedraven
Copy link
Collaborator

FYI you not really to uncomment those, you only need to change ip/port if they are different from cuckoo.conf and tags shouldn't be empty or commented

Uncomment #options =
Uncomment #tags = and add tags = none
Uncomment # resultserver_ip = and add your server ip
Uncomment #resultserver_port = 2042

@doomedraven
Copy link
Collaborator

but so far, very good writeup for those who starts with CAPE on AWS

@Y4nush
Copy link
Contributor Author

Y4nush commented Feb 26, 2024

Hi, @doomedraven sure! that's okay from my side.
Thank you for the feedback. I will update the blog post accordingly.

@doomedraven
Copy link
Collaborator

cool thanks, i will show you PR once that is done before merge

Y4nush and others added 3 commits April 16, 2024 20:21
…ret keys on EC2.

Using access/secret keys directly on EC2 is considered a bad security practice. I have added the option for boto3 to perform authentication using the Instance Metadata 
Service and assume the role associated with the EC2 instance on which CAPEv2 is running on.
This does not cancel the original authentication method; it is used as a fallback in case users do not specify secret/access keys in aws.conf.
@doomedraven
Copy link
Collaborator

why do you remove it?

@Y4nush
Copy link
Contributor Author

Y4nush commented Apr 16, 2024

why do you remove it?

@Y4nush Y4nush reopened this Apr 16, 2024
@Y4nush
Copy link
Contributor Author

Y4nush commented Apr 16, 2024

Hi @doomedraven, I did that accidentally while I opened the IMDS pull request.

By the way, I would like to edit the blog post based on the IMDS authentication method. I will update once I complete that. Is that okay from your side?

@doomedraven
Copy link
Collaborator

yes, as you can see sadly those week not enough free time so i can't work on it, and the same will be at least for next 2w, but after that i hope to add it. so once you update the blog just let me know here plz, i keep this open to remember that i have to copy it to docs

@Y4nush
Copy link
Contributor Author

Y4nush commented Apr 20, 2024

Hi @doomedraven, I have updated the blog post, thanks!

@doomedraven
Copy link
Collaborator

thanks for headups and documenting this

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.

None yet

3 participants