This process will require certain permissions to create a few resources in your Account. Ensure you are using a Role that has the ability to create the following resources
- IAM Role
- IAM Managed Policy
- VPC
- IGW
- Route tables
- Security Group
- NAT Gateway
- Elastic IP (EIP)
- EC2 Instance
- S3 Bucket
In addition to the IAM Permissions you will need to verify that you will not run into an issue with Service Quotas.
The best place to check is with the Service Quotas Console
You will be deploying the scripts from the GitHub page into this bucket.
The following guide can walk you through how to create an S3 bucket if you are not familiar. Make sure to note the name of the bucket that you create as we will need this in the next step.
Note
- You need to deploy the cloudformation template in the same region as the bucket that you create
Copy the uncompressed files from "CloudFormation-Templates" directory into your S3 bucket.
Note
you will need the S3 URL of the SelfServiceSec.yml file
- In the bucket that you just created and uploaded the files to, select the file name SelfServiceSec.yml
- In the resulting window at the bottom of the screen, copy the Object URL
Object URL
https://s3-us-west-2.amazonaws.com/Your-Bucket-Name-Here/SelfServiceSec.yml
Go to the CloudFormation console and select “Create Stack"
Select Amazon S3 URL as the source and copy and paste the S3 URL from the step above:
example:
https://s3-us-west-2.amazonaws.com/Your-Bucket-Name-Here/SelfServiceSec.yml
Enter a unique stack name
- This is just the name of the new bucket where you have placed the files from "CloudFormation-Templates".
Note
- This is ONLY the bucket name (e.g. your-bucket-name) not the full S3 bucket URL
- This will deploy several additional functions that can help you scan your environment for ransomware
Note
- We will be adding more modules to this over time
Use tags per your organizational tagging policy and guidance.
If applicable to your organization use the appropriate Role for CloudFormation here. Otherwise leave this blank, and CloudFormation will use the permissions that you currently have (this is the default behavior).
No Advanced Options are required.
On the next screen, before you select “Create Stack” be sure to check the two (2) check boxes
Once you have both report you can remove the files from the S3 Bucket.
Once the S3 Bucket is empty you can go to CloudFormation and delete the CloudFormation stack.
IF the S3 Bucket is not empty you will receive an error when CloudFormation attempts to delete the S3 Bucket.
Simply delete the object