Skip to content


In this workshop you will learn how to use the Amazon Inspector Network Reachability report to validate your network configuration without needing a deep background in networking. You will use this report to find misconfigurations that may result in unintended behaviors and unexpected vulnerabilities. You will finish the workshop by remediating these vulnerabilities by integrating the findings of Amazon Inspector with other AWS services.


  1. You will need an AWS account for this workshop and administrative credentials.
  2. You should be familiar with AWS core services such as Amazon EC2, Amazon VPC, and AWS CloudFormation. You should also be comfortable using the AWS console.
  3. The instructions are written with the understanding that the account is new or clean. We strongly recommend that you do not do these workshops in work or "production" accounts.
  4. You will incur charges for the AWS resources used in this workshop. The charges for some of the resources may be covered through the AWS Free Tier. The demo uses free tier choices wherever possible.
  5. If you are using an existing account with resources already deployed in a region, be aware of the soft limit of five VPCs per region.
  6. You must run this workshop in a region supported by Amazon Inspector ( We recommended using the us-east-1 region.
  7. You must have an [EC2 key pair] ( in the region you have selected.

Workshop Scenario

Example Corp. has been in AWS for a few months and is moving its first few workloads into AWS. The first workload to move was an external website with a database back end. Example Corp.’s security team insisted administrative access to servers must be through a set of bastion hosts in a separate VPC. Recently, a developer has created a public proof of concept for a new highly available web service and connected it to the environment without going through all the proper change management. The various IT stakeholders have been working off the following untested assumptions:

Assumption 1.> Instances in private subnets are not accessible from the internet

Assumption 2.> Putting servers in different Availability zones provides both failover and better reliability

Assumption 3.> Nothing can route through the bastion VPC

Assumption 4.> Access to the servers is limited according to the principle of least privilege

Assumption 5.> The bastion hosts can access all environments

Example Corp's IT team found the new configuration not because of controls, but from the increase in their AWS bill. As a result, the security and operations teams want to validate the right security is applied to both the new and existing environments using the Inspector Network Reachability report.


You will use AWS CloudFormation to build the environment

The CloudFormation template will build the following elements of the workshop in a single account and will not use any existing VPCs.

  • Three VPCs - VPC 1, 2, and 3. VPC 1 and VPC 2 are both peered to VPC 3.
  • VPC 1 (the Web Application VPC) spans two Availability Zones each of which contains one public subnet and two private subnets. The VPC also includes Application Load Balancers, web servers, and database servers.
  • VPC 2 (the Proof of Concept VPC) spans two Availability Zones each of which contains one public subnet and one private subnet. The VPC also includes two servers.
  • VPC 3 (the Bastion VPC) spans two Availability Zones each of which has one private subnet. The VPC also contains two bastion servers that offer SSH and RDP access to the environment.

This environment is shown below.

Here are the Route Tables and Security Groups for you to review as well.

Presentation Deck

Feel free to download the workshop presentation. You may find this helpful when doing the workshop yourself or in support of a group learning activity.

This site will note where the presentation material may be most useful.


Make sure you are in a region supported by Amazon Inspector ( We recommend using the us-east-1 region.


The workshop is broken up into the five modules below:

  1. Environment Build and Configuration
  2. Running the Inspector Report
  3. Evaluating Findings
  4. Integration and Remediation
  5. Cleanup