Officially Supported: AWS Deployment

We now have an AMI that you can use to deploy Dradis directly in AWS. No more manual converting of the OVA! The AMI is simply an AWS version of our VM image - nothing else has changed about Dradis in this AMI, except that the image's disk is not LUKS-encrypted, due to the cloud image creation process. To encrypt your AWS storage, follow the steps in AWS's EBS encryption guide.

Before we can share the AMI with you, we need to know the AWS ID of your account. If you need help figuring out your account ID, follow the official AWS guide.

The AWS procedure outlined above is the only process that is available to share the AMI with your team. If you're not able to use this process, you'll need to choose another deployment option.

Reach out to our support team with your AWS ID and we'll share the AMI with your account so that you can launch an instance using the image. Please make sure that you're launching a t2 instance and not another instance type otherwise it won't work! We recommend a t2.large at minimum to meet our base specs. Copy the AMI to your given Availability Zone and deploy the instance using normal AWS procedures.

Great job, you reached the end of the guide! Have you read all of them?

Seven Strategies To Differentiate Your Cybersecurity Consultancy

You don’t need to reinvent the wheel to stand out from other cybersecurity consultancies. Often, it's about doing the simple things better, and clearly communicating what sets you apart.

  • Tell your story better
  • Improve your testimonials and case studies
  • Build strategic partnerships

Your email is kept private. We don't do the spam thing.