Repository files navigation

This demo uses Terraform to set up four instances on AWS and then provides a series of Ansible playbooks to install NGINX Plus, configure an NGINX Plus reverse proxy load balancing between a couple NGINX Plus web servers, and install NGINX App Protect and configure NGINX App Protect to secure the NGINX Plus reverse proxy.

A PDF containing accompanying slides for this demo can also be found under the name ofNGINX Better with Ansible.pdf.

This demo has been developed and tested with Terraform1.3.

Instructions on how to install Terraform can be found in theTerraform website.

This demo has been developed and tested with Ansible2.16 and Jinja23.1. Do note you will absolutely need to have Jinja23.1 installed to be able to run the demo.

Instructions on how to install Ansible can be found in theAnsible website.

You will also need to download the latest Ansible NGINX roles and the latest Ansible AWS collection (amazon.aws). To install the latest versions, you can use:

ansible-galaxy install -f -r ansible/requirements.yml

Finally, in order to use the Amazon AWS (amazon.aws) collection, you will also need to install theboto3 andbotocore Python packages.

If you wish to deploy the more advanced version of this demo, you will need to download an NGINX Plus and NGINX App Protect license from yourMyF5 portal before you run this script. Alternatively, a simplified NGINX Open Source version of the demo is also available.

To use the provided Terraform scripts, you need to:

1. Export your AWS credentials as environment variables (or alternatively, tweak the AWS provider interraform/provider.tf).
2. Set up default values for variables missing a value interraform/variables.tf (you can find example values commented out in the file). Alternatively, you can input those variables at runtime (beware of dictionary values if you do the latter).

Once you have configured your Terraform environment, you can either:

• Run./setup.sh to initialize the AWS Terraform provider and start a Terraform deployment on AWS:

./setup.sh

• Runterraform init andterraform apply

cd terraform&& terraform init&& terraform apply -auto-approve

And finally, once you are done playing with the demo, you can destroy the AWS infrastructure by either:

• Run./cleanup.sh to destroy your Terraform deployment:

./destroy.sh

• Runterraform destroy:

cd terraform&& terraform destroy -auto-approve&& rm -f terraform.tfstate terraform.tfstate.backup&& rm -rf .terraform

You will find a series of Ansible playbooks in theansible folder. Playbook zero is only used to verify that the AWS EC2 instances launched by Terraform can be successfully pinged from the Ansible host. There are two versions of playbook one. One installs NGINX Plus whilst the other installs NGINX Open Source. You will have to deploy playbook one,1-deploy-nginx.yml, before you attempt to deploy any other playbooks. Playbooks two through four can be deployed in any order, albeit the recommended order gradually configures a more advanced NGINX environment. Do note that if you decide to install NGINX Open Source, you will not be able to deploy playbooks four and five. If you are running the NGINX Plus playbook, you can either tweak thenginx_license variable in playbook one itself, or pass the variable at runtime using Ansible's extra vars (--extra-vars/-e) CLI command.

To execute a playbook, run:

ansible-playbook --private-key=</path/to/key> -i ansible/aws_ec2.yml ansible/1-deploy-nginx.yml

This demo includes the following playbooks:

Alessandro Fael Garcia