An open source guidance tool for the AWS environment. Click here for sample report.
Disclaimer: The generated report has to be hosted locally and MUST NOT be internet accessible
Service Screener is a tool that runs automated checks on AWS environments and provides recommendations based on AWS and community best practices.
AWS customers can use this tool on their own environments and use the recommendations to improve the Security, Reliability, Operational Excellence, Performance Efficiency and Cost Optimisation at the service level.
This tool aims to complement the AWS Well Architected Tool.
Service Screener uses AWS Cloudshell, a free serivce that provides a browser-based shell to run scripts using the AWS CLI. It runs multiple describe and get API calls to determine the configuration of your environment.
Running this tool is free as it is covered under the AWS Free Tier. If you have exceeded the free tier limits, each run will cost less than $0.01.
- Please review the DISCLAIMER before proceeding.
- You must have an existing AWS Account.
- You must have an IAM User with sufficient read permissions. Here is a sample policy. Additionally, the IAM User must also have the following permissions: a. AWSCloudShellFullAccess b. cloudformation:CreateStack c. cloudformation:DeleteStack
- Log in to your AWS account using the IAM User with sufficient permissions described above.
- Launch AWS CloudShell in any region.
Launch AWS Cloudshell Walkthrough
In the AWS CloudShell terminal, run this script this to install the dependencies:
python3 -m venv .
source bin/activate
python3 -m pip install --upgrade pip
rm -rf service-screener-v2
git clone https://github.com/aws-samples/service-screener-v2.git
cd service-screener-v2
pip install -r requirements.txt
alias screener="python3 $(pwd)/main.py"
Install Dependecies Walkthrough
When running Service Screener, you will need to specify the regions and services you would like it to run on. It currently supports Amazon Cloudfront, AWS Cloudtrail, Amazon Dynamodb, Amazon EC2, Amazon EFS, Amazon RDS, Amazon EKS, Amazon Elasticache, Amazon Guardduty, AWS IAM, Amazon Opensearch, AWS Lambda, and Amazon S3.
We recommend running it in all regions where you have deployed workloads in. Adjust the code samples below to suit your needs then copy and paste it into Cloudshell to run Service Screener.
Example 1: Run in the Singapore region, check all services
screener --regions ap-southeast-1
Example 2: Run in the Singapore region, check only Amazon S3
screener --regions ap-southeast-1 --services s3
Example 3: Run in the Singapore & North Virginia regions, check all services
screener --regions ap-southeast-1,us-east-1
Example 4: Run in the Singapore & North Virginia regions, check RDS and IAM
screener --regions ap-southeast-1,us-east-1 --services rds,iam
Example 5: Run in the Singapore region, filter resources based on tags (e.g: Name=env Values=prod and Name=department Values=hr,coe)
screener --regions ap-southeast-1 --tags env=prod%department=hr,coe
Example 6: Run in all regions and all services
screener --regions ALL
##mode
--mode api-full | api-raw | report
# api-full: give full results in JSON format
# api-raw: raw findings
# report: generate default web htmlGet Report Walkthrough
The output is generated as a ~/service-screener-v2/output.zip file. You can download the file in the CloudShell console by clicking the Download file button under the Actions menu on the top right of the Cloudshell console.
Download Output & Report Viewing Walkthrough
Once downloaded, unzip the file and open 'index.html' in your browser. You should see a page like this:
Ensure that you can see the service(s) run on listed on the left pane. You can navigate to the service(s) listed to see detailed findings on each service.
Sample Output Walkthrough
The report provides you an easy-to-navigate dashboard of the various best-practice checks that were run.
Use the left navigation bar to explore the checks for each service. Expand each check to read the description, find out which resources were highlighted, and get recommendations on how to remediate the findings.
We encourage public contributions! Please review CONTRIBUTING for details on our code of conduct and development process.
Please review CONTRIBUTING to raise any issues.
See CONTRIBUTING for more information.
This project is licensed under the Apache-2.0 License.