This Terraform module has one subnet and deploys an EC2 instance representing a web server with postgress to a greenplum database. Allowing inbound HTTPS TCP traffic on port 443, and inbound RDP TCP traffic on port 3389 .
| In/Out | Type | Protocol | FromPort | To Port | TLS |
|---|---|---|---|---|---|
| INBOUND | RDP | TCP | 3389 | 3389 | TLS to External Tableau ELB |
| INBOUND | HTTPS | TCP | 443 | 443 | TLS to External Tableau ELB |
This repo controls the deployment of an application module.
It consists of the following core elements:
This file has the basic components for EC2 instances.
- Private subnet and route table association
- An EC2 instance using the connectivity tester module
- Security group for the EC2 instance
Input data for resources within this repo.
Code and resource tester with mock data. It can be expanded by adding further definitions to the unit.
This project currently depends on:
- drone v0.5+dev
- terraform v0.11.1+
- terragrunt v0.13.21+
- python v3.6.3+
Please ensure that you have the correct versions installed (it is not currently tested against the latest version of Drone)
To run tests using the tf testsuite:
drone exec --repo.trustedTo launch:
terragrunt plan
terragrunt applyIf the CI process appears to be stuck with a stale tf state then run the following command to force a refresh:
terragrunt refresh
If the CI process is still failing after a refresh look for errors about items no longer available in AWS - say something that was deleted manually via the AWS console or CLI.
To explicitly delete the stale resource from TF state use the following command below. Note:terragrunt state rm will not delete the resource from AWS it will unlink it from state only.
terragrunt state rm aws_resource_name