diff --git a/content/nginx/deployment-guides/amazon-web-services/ec2-instances-for-nginx.md b/content/nginx/deployment-guides/amazon-web-services/ec2-instances-for-nginx.md index 036dab9c6..e3b173ae4 100644 --- a/content/nginx/deployment-guides/amazon-web-services/ec2-instances-for-nginx.md +++ b/content/nginx/deployment-guides/amazon-web-services/ec2-instances-for-nginx.md @@ -1,186 +1,147 @@ --- +title: Create Amazon EC2 Instances for NGINX Open Source and NGINX Plus +weight: 600 description: Create Amazon Elastic Compute Cloud (EC2) instances for running NGINX Open Source and F5 NGINX Plus. -docs: DOCS-444 -doctypes: -- task -title: Creating Amazon EC2 Instances for NGINX Open Source and NGINX Plus toc: true -weight: 600 +type: how-to +product: NGINX+ +docs: DOCS-444 --- -These instructions explain how to create instances in the Amazon Elastic Compute Cloud (EC2) environment suitable for running NGINX Open Source and F5 NGINX Plus. +This guide explains how to create instances in the Amazon Elastic Compute Cloud (EC2) that can run NGINX Open Source and F5 NGINX Plus. -For NGINX Plus, a faster alternative is to purchase a prebuilt Amazon Machine Image (AMI) in the AWS Marketplace. Several operating systems are available, including Amazon Linux, Red Hat Enterprise Linux, and Ubuntu. For instructions, see [Installing NGINX Plus AMIs on Amazon EC2]({{< relref "../../admin-guide/installing-nginx/installing-nginx-plus-amazon-web-services.md" >}}). +For NGINX Plus, you can buy a prebuilt Amazon Machine Image (AMI) from the AWS Marketplace for a faster option. You can find AMIs for various operating systems, such as Amazon Linux, Red Hat Enterprise Linux, and Ubuntu. For instructions, see [Installing NGINX Plus AMIs on Amazon EC2]({{< relref "/nginx/admin-guide/installing-nginx/installing-nginx-plus-amazon-web-services.md" >}}). - -## Prerequisites +## Before you begin -These instructions assume you have: +To complete this guide, you need the following: - An [AWS account](http://docs.aws.amazon.com/AmazonSimpleDB/latest/DeveloperGuide/AboutAWSAccounts.html). -- If using the instructions in [Automating Installation with Ansible](#automate-ansible), basic Linux system administration skills, including installation of Linux software from vendor‑supplied packages, and file creation and editing. - -In addition, to install NGINX software by following the linked instructions, you need: - -- An NGINX Plus subscription, either paid or a [30‑day free trial](https://www.nginx.com/free-trial-request), if you plan to install that product. -- `root` privilege on the hosts where NGINX Open Source and NGINX Plus are to be installed. If appropriate for your environment, prefix commands with the `sudo` command. - - -## Creating an Amazon EC2 Instance - -1. Log into the [EC2 dashboard](https://console.aws.amazon.com/ec2/) in the AWS Management Console (****). - -2. In the left navigation bar, select **Instances**, then click the  Launch Instance  button. - - - -3. In the **Step 1: Choose an Amazon Machine Image (AMI)** window, click the  Select  button for the Linux distribution of your choice. - - - -4. In the **Step 2: Choose an Instance Type** window, click the radio button for the appropriate instance type. In the screenshot, we are selecting a t2.micro instance, which is normally selected by default and is sufficient for demo purposes. - - **Note:** At the time of publication of this guide, AWS gives you 750 hours of free usage per month with this instance type during the first year of your AWS account. Keep in mind, however, that if they run 24 hours a day, the sets of instances specified in the NGINX deployment guides use up the 750 hours in just a few days (just over 5 days for 6 instances, and just under 4 days for 8 instances). +- Basic Linux system administration skills, including installing software, managing files and folders, and using the command line, to follow the [Ansible instructions]({{< relref "#automate-ansible" >}}). +- A paid subscription or a [30-day free trial](https://www.nginx.com/free-trial-request) for NGINX Plus. +- Root privileges on the hosts where NGINX Open Source or NGINX Plus will be installed, with `sudo` access as needed. - Click the  Next: Configure Instance Details  button to continue to the next step. +## Create an Amazon EC2 Instance {#create-ec2-instances} - +1. Log in to the EC2 dashboard in the AWS Management Console: **[https://console.aws.amazon.com/ec2](https://console.aws.amazon.com/ec2)**. -5. In the **Step 3: Configure Instance Details** window, select the default subnet for your VPC in the **Subnet** field, then click the  Next: Add Storage  button. +1. In the left navigation bar, choose **Instances**. Then select **Launch Instances** in the top right corner. - +1. On the **Launch an Instance** page, give your new instance a name in the **Name and Tags** section. This name will show in the Name column of the summary table on the EC2 Instances dashboard. This guide is using "instance-name." -6. In the **Step 4: Add Storage** window, leave the defaults unchanged. Click the  Next: Add Tags  button. +1. In the **Application and OS Images (Amazon Machine Image)** section select the image of the Linux distribution of your choice. - + {{< img src="/img/aws/aws-nlb-instance-choose-ami.png" alt="Screenshot of AMI section on the EC2 Launch Instance page">}} -7. In the **Step 5: Add Tags** window, click the  Add Tag  button. Type Name in the **Key** field, and in the **Value** field type the instance name (the screenshot shows the result). This name is what will appear in the **Name** column of the summary table on the **Instances** tab of the EC2 dashboard (see the screenshot in Step 12, which shows one instance). +1. In the **Instance Type** section, choose an appropriate instance type. The screenshot shows the **t2.micro** instance type selected by default. This type is sufficient for demo purposes. - If you are following these instructions as directed by an NGINX deployment guide, the **Creating EC2 Instances and Installing the NGINX Software** section of the deployment guide specifies the instance names to use. + {{}}At the time of publication, AWS offered 750 hours of free usage each month for this instance type. This applies during your first year with an AWS account. Keep in mind, though, that several NGINX instances running all day will use the free 750 hours up quickly. For example, 6 instances will use them in just over 5 days. If you use 8 instances, you'll hit the limit in under 4 days.{{}} - Click the  Next: Configure Security Group  button to continue to the next step. + {{< img src="/img/aws/aws-nlb-instance-choose-type.png" alt="Screenshot of Instance Type on the EC2 Launch Instance page">}} - +1. In the **Key pair (login)** section, select an existing key pair or create a new one. If you choose **Create new key pair**, a window appears, allowing you to download the key pair. + {{}} It's best practice — and necessary in production — to create a separate key for each EC2 instance. This way, if a key is compromised, only that one instance is at risk.{{}} -8. In the **Step 6: Configure Security Group** window, select or enter the following values in the indicated fields: +1. Scroll to the **Network settings** section. You can keep the default **VPC** and **Subnet** settings. Under **Firewall (Security Groups),** either create a new security group or use an existing one. + - If this is your first setup, keep **Create security group** selected. + - Select **Allow HTTP traffic from the internet.** + - (Optional) Select **Allow HTTPS traffic from the internet** if needed. - - **Assign a security group** – - - If you are setting up a deployment with multiple instances (one in an NGINX deployment guide, for instance), and this is the first instance you are creating, select Create a **new** security group. - - For subsequent instances, select Select an **existing** security group instead (it makes sense for all instances in a deployment to use the same security group). - - **Security group name** – Name of the group. If you are following these instructions as directed by an NGINX deployment guide, the **Prerequisites and Required AWS Configuration** section of the deployment guide specifies the group name to use. - - **Description** – Description of the group; the group name is often used. + This creates the following inbound security group rules: - /nginx/images/aws-generic-instance-security-group.png + 1. Accept SSH connections from all sources + - **Type** – SSH + - **Protocol** – TCP + - **Port Range** – 22 + - **Source** – Custom `0.0.0.0/0` + 1. Accept unencrypted HTTP connections from all sources + - **Type** – HTTP + - **Protocol** – TCP + - **Port Range** – 80 + - **Source** – Custom `0.0.0.0/0` + 1. Accept encrypted HTTPS connections from all soruces (optional) + - **Type** – HTTPS + - **Protocol** – TCP + - **Port Range** – 443 + - **Source** – Custom `0.0.0.0/0` -9. In the table, modify the default rule for SSH connections, if necessary, by selecting or setting the following values. They allow inbound SSH connections from all sources (any IP address): + {{< img src="/img/aws/aws-generic-instance-details.png" alt="Screenshot of Network Settings on the EC2 Launch Instance page">}} - - **Type** – SSH - - **Protocol** – TCP - - **Port Range** – 22 - - **Source** – Custom 0.0.0.0/0 - - **Description** – Accept SSH connections from all sources + If you are deploying multiple instances, it makes sense to use the same security group for all. In that case, choose "Select existing security group." This will allow you to pick a security group from a list. -10. Create a rule that allows inbound HTTP connections from all sources, by clicking the  Add Rule  button and selecting or setting the following values in the new row: + {{< img src="/img/aws/aws-instance-select-sg.png" alt="Screenshot of Network Settings on the EC2 Launch Instance page with the option of selecting an existing security group">}} - - **Type** – HTTP - - **Protocol** – TCP - - **Port Range** – 80 - - **Source** – Custom 0.0.0.0/0 - - **Description** – Accept unencrypted HTTP connections from all sources +1. In the **Configure Storage** section, leave the defaults unchanged. - If appropriate, repeat this step to create a rule for HTTPS traffic. +1. In the right panel, verify the settings in the **Summary** section. If everything is correct, select **Launch Instance**. - When you've created all desired rules, click the  Review and Launch  button. + {{< img src="/img/aws/aws-instance-summary.png" alt="Screenshot of the Summary panel on the EC2 Launch Instance page with button to launch instance">}} -11. In the **Step 7: Review Instance Launch** window, verify the settings are correct. If so, click the  Launch  button in the lower‑right corner of the window. To change settings, click the  Previous  button to go back to earlier windows. +1. After launching the instance, you are redirected to a confirmation page with a success message. Select the instance ID to return to the **EC2 Instances** page. - + {{< img src="/img/aws/aws-instance-launch-success.png" alt="Screenshot of the Summary panel on the EC2 Launch Instance page with button to launch instance">}} -12. When you click the  Launch  button, a window pops up asking you to select an existing key pair or create a new key pair. Take the appropriate action for your use case, then click the  Launch Instances  button. +1. On the **EC2 Instances** page, you can view all your instances, including the new one. The following screenshot shows a single instance: - **Note:** It's a best practice – and essential in a production environment – to create a separate key for each EC2 instance, so that if a key is compromised only the single associated instance becomes vulnerable. + {{< img src="/img/aws/aws-generic-instance-display-first.png" alt="Screenshot of the EC2 Instances page with a single instance">}} - ![Screen of 'Select an existing key pair or create a new key pair' window during creation of Amazon EC2 instance](/nginx/images/aws-nlb-instance-key-pair.png) - - A **Launch Status** window pops up to confirm that your launch is underway. To confirm the details of your instance when the launch completes, click the  View Instances  button on that page. - - The instances you have created so far are listed on the **Instances** dashboard. The following screenshot shows a single instance. - - - -13. Finalize your security group rules. You need to do this only for the first instance in a given set, because all instances in a set can use the same security group. +1. Finalize your security group rules. You only need to do this for the first instance in a set. All other instances in that set can use the same security group. - In the left navigation bar, select **Security Groups**. - Select the security group by clicking its radio button in the leftmost column of the table. A panel opens in the lower part of the window displaying details about the group. - - Open the **Inbound** tab and verify that the rules you created in Steps 9 and 10 are listed. + - In the **Inbound** tab, verify that the rules you created in Step 7 are listed. + - Open the **Outbound** tab and select **Edit outbound rules** to create a rule for outbound traffic. The rules depend on the ports used for traffic handled by NGINX Open Source or NGINX Plus instances: - + - By default, AWS adds an outbound rule that allows all traffic to all destinations. You can remove this rule by selecting **Delete**. + - If you use port 80 for client traffic and health checks from a load balancer, like [AWS Network Load Balancer]({{< relref "high-availability-network-load-balancer.md" >}}), you only need one rule. + - If you set up different ports for various tasks, or if you use ports like 443 for HTTPS, adjust them accordingly. - - Open the **Outbound** tab and click the  Edit  button to create a rule for outbound traffic. The set of rules depends on which ports you have used for traffic handled by the NGINX Plus instances: + In the **Destination** field, start typing your security group's name or ID. It should appear under **Security Groups**. The example below shows **sg-0dd4d3c5284052f99**. - - If, for example, you have used port 80 both for client traffic and for health checks from a load balancer (for example, [AWS Network Load Balancer]({{< relref "high-availability-network-load-balancer.md" >}})), you need only one rule. - - If you have configured separate ports for different purposes, or ports other than 80 (such as 443 for HTTPS), make the appropriate adjustments. + {{< img src="/img/aws/aws-generic-instance-security-outbound.png" alt="Screenshot of the EC2 Security Group outbound rules page">}} - In the **Destination** field, type the security group's ID, which appears in the **Group ID** column in the upper table (here it's sg-3bdbf55d). +1. To install NGINX software on the instance, first [connect]({{< relref "#connect-to-an-ec2-instance" >}}) to it. Then follow the instructions in the NGINX Plus Admin Guide for [NGINX Open Source]({{< relref "/nginx/admin-guide/installing-nginx/installing-nginx-open-source#prebuilt" >}}) and [NGINX Plus]({{< relref "/nginx/admin-guide/installing-nginx/installing-nginx-plus.md" >}}). - - -14. To install NGINX software on the instance, [connect](#connect-to-instance) to it, and follow the instructions in the NGINX Plus Admin Guide for [NGINX Open Source]({{< relref "/nginx/admin-guide/installing-nginx/installing-nginx-open-source#prebuilt" >}} and [NGINX Plus]({{< relref "/nginx/admin-guide/installing-nginx/installing-nginx-plus.md" >}}). +--- - -## Connecting to an EC2 Instance -To install and configure NGINX Open Source or NGINX Plus on an instance, you need to open a terminal window and connect to the instance over SSH. +## Connect to an EC2 Instance +To install and configure NGINX Open Source or NGINX Plus on an instance, open a terminal window and connect to the instance over SSH. 1. Navigate to the **Instances** tab on the EC2 Dashboard if you are not there already. +1. Select the row for an instance to highlight it. +1. Select **Connect** above the list of instances. You are redirected to the **Connect to Instance** page, with the **SSH client** tab selected by default. +1. Follow the instructions on the page, which are customized for the selected instance. A sample `ssh` command includes the key file name and the instance hostname. + + {{< img src="/img/aws/aws-nlb-instance-connect.png" alt="Screenshot of the EC2 Instance Connect with SSH page">}} -2. Click the row for an instance to select it. In the screenshot **instance2** is selected. - - - -3. Click the  Connect  button above the list of instances. The **Connect To Your Instance** window pops up. -4. Follow the instructions in the pop‑up window, which are customized for the selected instance (here **instance2**) to provide the name of the key file in the steps and in the sample `ssh` command. - - ![Screenshot of 'Connect To Your Instance' pop-up window for Amazon EC2 instance](/nginx/images/aws-nlb-instance-connect.png) - - -## Installing NGINX Software - -Once you have established a connection with an instance, you can install the NGINX software on it. Follow the instructions in the NGINX Plus Admin Guide for NGINX Open Source and [NGINX Plus]({{< relref "../../admin-guide/installing-nginx/installing-nginx-plus.md" >}}). The [Admin Guide]({{< relref "/nginx/admin-guide/_index.md" >}}) also provides instructions for many maintenance tasks. +--- - -### Automating Installation with a Configuration Manager +## Install NGINX software -You can automate the installation of NGINX Open Source and NGINX Plus. Instructions for Ansible are provided below. For Chef and Puppet, see these articles on the NGINX, Inc. blog: +Once you have established a connection with an instance, you can install the NGINX software on it. Follow the instructions in the NGINX Plus Admin Guide for [NGINX Open Source]({{< relref "/nginx/admin-guide/installing-nginx/installing-nginx-open-source#prebuilt" >}}) and [NGINX Plus]({{< relref "/nginx/admin-guide/installing-nginx/installing-nginx-plus.md" >}}). The [Admin Guide]({{< relref "/nginx/admin-guide/_index.md" >}}) also provides instructions for many maintenance tasks. -- [Installing NGINX and NGINX Plus with Chef](https://www.nginx.com/blog/installing-nginx-nginx-plus-chef/) -- [Deploying NGINX Plus for High Availability with Chef](https://www.nginx.com/blog/nginx-plus-high-availability-chef/) -- [Installing NGINX and NGINX Plus with Puppet](https://www.nginx.com/blog/installing-nginx-nginx-plus-puppet/) +### Automate installation with a configuration manager - -#### Automating Installation with Ansible +You can automate the installation of NGINX Open Source and NGINX Plus. Instructions for Ansible are provided below. -NGINX, Inc. publishes a unified Ansible role for NGINX Open Source and NGINX Plus on [Ansible Galaxy](https://galaxy.ansible.com/nginxinc/nginx/) and [GitHub](https://github.com/nginxinc/ansible-role-nginx). Perform these steps to install and run it. +#### Automate installation with Ansible {#automate-ansible} -1. [Connect to the EC2 instance](#connect-instance). +NGINX, Inc. releases a combined Ansible role for NGINX Open Source and NGINX Plus on [Ansible Galaxy](https://galaxy.ansible.com/nginxinc/nginx/) and [GitHub](https://github.com/nginxinc/ansible-role-nginx). Perform these steps to install and run it. -2. Install Ansible. These commands are appropriate for Debian and Ubuntu systems: +1. [Connect to the EC2 instance]({{< relref "#connect-instance" >}}). - ```shell - apt update - apt install python-pip -y - pip install ansible - ``` +1. Install Ansible following the [instructions](https://docs.ansible.com/ansible/latest/installation_guide/installation_distros.html) for the operating system on your EC2 instance. -3. Install the official Ansible role from NGINX, Inc.: +1. Install the official Ansible role from NGINX: ```shell ansible-galaxy install nginxinc.nginx ``` -4. (NGINX Plus only) Copy the nginx-repo.key and nginx-repo.crt files provided by NGINX, Inc. to ~/.ssh/ngx-certs/. +1. (NGINX Plus only) Copy the **nginx-repo.key** and **nginx-repo.crt** files provided by NGINX, Inc. to **~/.ssh/ngx-certs/**. -5. Create a file called **playbook.yml** with the following contents: +1. Create a file called **playbook.yml** with the following contents: ```none --- @@ -190,36 +151,35 @@ NGINX, Inc. publishes a unified Ansible role for NGINX Open Source and NGINX P - role: nginxinc.nginx ``` -5. Run the playbook: +1. Run the playbook: ```shell ansible-playbook playbook.yml ``` - -## Optional: Creating an NGINX Open Source AMI +1. Confirm that NGINX is installed by running `nginx -v`. -To streamline the process of installing NGINX Open Source on multiple instances, you can create an AMI from an existing NGINX Open Source instance, and spin up additional instances of the AMI when needed. -1. Follow the instructions in [Creating Amazon EC2 Instances](#create-ec2-instances) and the NGINX Plus Admin Guide to create an instance and install NGINX Open Source on it, if you have not already. +## Optional: Create an NGINX Open Source AMI -2. Navigate to the **Instances** tab on the Amazon EC2 Dashboard. +To simplify installing NGINX Open Source on several instances, create an AMI from an existing NGINX instance. You can then create additional virtual instances based on the AMI. -3. Select the base instance by clicking its row in the table. In the screenshot, **instance2** is selected. +1. Follow the instructions in [Create Amazon EC2 Instance]({{< relref "#create-ec2-instances" >}}) and [Install NGINX software]({{< relref "#install-nginx-software" >}}). - +1. Go to the **Instances** tab on the Amazon EC2 Dashboard. -4. Click the  Actions  button and select Image > Create Image. +1. Select the base instance with NGINX installed by clicking its row in the table. - +1. Select **Actions**, then choose **Image and templates** > **Create Image**. -5. In the window that pops up, fill in the **Image name** and (optionally) **Image description** fields, then click the  Create image   button. + {{< img src="/img/aws/aws-generic-create-image-menu.png" alt="Screenshot of the EC2 Create Image button menu">}} - screenshot of 'Create Image' pop-up window for creating base AMI in Amazon EC2 +1. On the **Create Image** page, enter the **Image name** and optionally add an **Image description**. Then select **Create image**. You are returned to the **Instances** page with a green alert confirming that the image is being created. - A **Create Image** window pops up to confirm that the image‑creation request was received. To verify that the image was created, navigate to the **AMIs** tab. +1. To verify that the image was created, go to the **AMIs** tab and find the new image by its name. ### Revision History +- Version 3 (February 2025) - Update guide to match new AWS instance creation flow, update screenshots, and links. - Version 2 (July 2018) – Substitute links to NGINX Plus Admin Guide for sample installation instructions. - Version 1 (April 2018) – Initial version (NGINX Plus Release 14) diff --git a/static/img/aws/aws-generic-create-image-menu.png b/static/img/aws/aws-generic-create-image-menu.png new file mode 100644 index 000000000..2f21a8c16 Binary files /dev/null and b/static/img/aws/aws-generic-create-image-menu.png differ diff --git a/static/img/aws/aws-generic-instance-details.png b/static/img/aws/aws-generic-instance-details.png new file mode 100644 index 000000000..f9e40bed8 Binary files /dev/null and b/static/img/aws/aws-generic-instance-details.png differ diff --git a/static/img/aws/aws-generic-instance-display-first.png b/static/img/aws/aws-generic-instance-display-first.png new file mode 100644 index 000000000..6d5e04252 Binary files /dev/null and b/static/img/aws/aws-generic-instance-display-first.png differ diff --git a/static/img/aws/aws-generic-instance-security-outbound.png b/static/img/aws/aws-generic-instance-security-outbound.png new file mode 100644 index 000000000..bf84a7020 Binary files /dev/null and b/static/img/aws/aws-generic-instance-security-outbound.png differ diff --git a/static/img/aws/aws-instance-launch-success.png b/static/img/aws/aws-instance-launch-success.png new file mode 100644 index 000000000..294621ab1 Binary files /dev/null and b/static/img/aws/aws-instance-launch-success.png differ diff --git a/static/img/aws/aws-instance-select-sg.png b/static/img/aws/aws-instance-select-sg.png new file mode 100644 index 000000000..859fbf4d4 Binary files /dev/null and b/static/img/aws/aws-instance-select-sg.png differ diff --git a/static/img/aws/aws-instance-summary.png b/static/img/aws/aws-instance-summary.png new file mode 100644 index 000000000..0bbf920b0 Binary files /dev/null and b/static/img/aws/aws-instance-summary.png differ diff --git a/static/img/aws/aws-nlb-instance-choose-ami.png b/static/img/aws/aws-nlb-instance-choose-ami.png new file mode 100644 index 000000000..775a36c0c Binary files /dev/null and b/static/img/aws/aws-nlb-instance-choose-ami.png differ diff --git a/static/img/aws/aws-nlb-instance-choose-type.png b/static/img/aws/aws-nlb-instance-choose-type.png new file mode 100644 index 000000000..c74c9c38a Binary files /dev/null and b/static/img/aws/aws-nlb-instance-choose-type.png differ diff --git a/static/img/aws/aws-nlb-instance-connect.png b/static/img/aws/aws-nlb-instance-connect.png new file mode 100644 index 000000000..af7d79cd0 Binary files /dev/null and b/static/img/aws/aws-nlb-instance-connect.png differ diff --git a/static/nginx/images/aws-generic-create-image-menu.png b/static/nginx/images/aws-generic-create-image-menu.png deleted file mode 100644 index 97bdb97fa..000000000 Binary files a/static/nginx/images/aws-generic-create-image-menu.png and /dev/null differ diff --git a/static/nginx/images/aws-generic-create-image-popup.png b/static/nginx/images/aws-generic-create-image-popup.png deleted file mode 100644 index 3a5823f92..000000000 Binary files a/static/nginx/images/aws-generic-create-image-popup.png and /dev/null differ diff --git a/static/nginx/images/aws-generic-instance-details.png b/static/nginx/images/aws-generic-instance-details.png deleted file mode 100644 index 784cd3c81..000000000 Binary files a/static/nginx/images/aws-generic-instance-details.png and /dev/null differ diff --git a/static/nginx/images/aws-generic-instance-display-first.png b/static/nginx/images/aws-generic-instance-display-first.png deleted file mode 100644 index 1cbe08821..000000000 Binary files a/static/nginx/images/aws-generic-instance-display-first.png and /dev/null differ diff --git a/static/nginx/images/aws-generic-instance-launch.png b/static/nginx/images/aws-generic-instance-launch.png deleted file mode 100644 index 8b63f1fd1..000000000 Binary files a/static/nginx/images/aws-generic-instance-launch.png and /dev/null differ diff --git a/static/nginx/images/aws-generic-instance-review-launch.png b/static/nginx/images/aws-generic-instance-review-launch.png deleted file mode 100644 index f88086f85..000000000 Binary files a/static/nginx/images/aws-generic-instance-review-launch.png and /dev/null differ diff --git a/static/nginx/images/aws-generic-instance-security-group.png b/static/nginx/images/aws-generic-instance-security-group.png deleted file mode 100644 index 227626066..000000000 Binary files a/static/nginx/images/aws-generic-instance-security-group.png and /dev/null differ diff --git a/static/nginx/images/aws-generic-instance-security-inbound.png b/static/nginx/images/aws-generic-instance-security-inbound.png deleted file mode 100644 index 50c9889bd..000000000 Binary files a/static/nginx/images/aws-generic-instance-security-inbound.png and /dev/null differ diff --git a/static/nginx/images/aws-generic-instance-security-outbound.png b/static/nginx/images/aws-generic-instance-security-outbound.png deleted file mode 100644 index dac80f6e8..000000000 Binary files a/static/nginx/images/aws-generic-instance-security-outbound.png and /dev/null differ diff --git a/static/nginx/images/aws-generic-instance-select-one.png b/static/nginx/images/aws-generic-instance-select-one.png deleted file mode 100644 index b71e9bb28..000000000 Binary files a/static/nginx/images/aws-generic-instance-select-one.png and /dev/null differ diff --git a/static/nginx/images/aws-instance-add-tags-name.png b/static/nginx/images/aws-instance-add-tags-name.png deleted file mode 100644 index 414783a77..000000000 Binary files a/static/nginx/images/aws-instance-add-tags-name.png and /dev/null differ diff --git a/static/nginx/images/aws-nlb-instance-add-storage.png b/static/nginx/images/aws-nlb-instance-add-storage.png deleted file mode 100644 index 23a095258..000000000 Binary files a/static/nginx/images/aws-nlb-instance-add-storage.png and /dev/null differ diff --git a/static/nginx/images/aws-nlb-instance-choose-ami.png b/static/nginx/images/aws-nlb-instance-choose-ami.png deleted file mode 100644 index b630f6774..000000000 Binary files a/static/nginx/images/aws-nlb-instance-choose-ami.png and /dev/null differ diff --git a/static/nginx/images/aws-nlb-instance-choose-type.png b/static/nginx/images/aws-nlb-instance-choose-type.png deleted file mode 100644 index be139720f..000000000 Binary files a/static/nginx/images/aws-nlb-instance-choose-type.png and /dev/null differ