-
Notifications
You must be signed in to change notification settings - Fork 99
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
9b14a73
commit b492242
Showing
9 changed files
with
54 additions
and
21 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,54 @@ | ||
# Example: Standalone with AWS Aurora RDS | ||
|
||
## About this example | ||
|
||
This example for Terraform Enterprise creates a TFE installation with the | ||
following traits: | ||
|
||
- External mode | ||
- a small VM machine type (m5.xlarge) | ||
- Red Hat 7.9 as the VM image | ||
- a publicly accessible HTTP load balancer with TLS termination | ||
- an access key for accessing S3 | ||
- AWS Aurora RDS with one reader and writer instance. | ||
|
||
## Pre-requisites | ||
|
||
This test assumes the following resources already exist: | ||
|
||
- Valid DNS Zone managed in Route53 | ||
- Valid AWS ACM certificate | ||
- a TFE license on a filepath accessible by tests | ||
|
||
## How to Use This Module | ||
|
||
### Deployment | ||
|
||
1. Read the entire [README.md](../../README.md) of the root module. | ||
2. Ensure account meets module prerequisites from above. | ||
3. Clone repository. | ||
4. Change directory into desired example folder. | ||
5. Create a local `terraform.auto.tfvars` file and instantiate the required inputs as required in the respective `./examples/standalone-rhel-aurora/variables.tf` including the path to the license under the `license_file` variable value. | ||
6. Authenticate against the AWS provider. See [instructions](https://registry.terraform.io/providers/hashicorp/aws/latest/docs#authentication-and-configuration). | ||
7. Initialize terraform and apply the module configurations using the commands below: | ||
|
||
NOTE: `terraform plan` will print out the execution plan which describes the actions Terraform will take in order to build your infrastructure to match the module configuration. If anything in the plan seems incorrect or dangerous, it is safe to abort here and not proceed to `terraform apply`. | ||
|
||
``` | ||
terraform init | ||
terraform plan | ||
terraform apply | ||
``` | ||
## Post-deployment Tasks | ||
The build should take approximately 10-15 minutes to deploy. Once the module has completed, give the platform another 10 minutes or so prior to attempting to interact with it in order for all containers to start up. | ||
Unless amended, this example will not create an initial admin user using the IACT, but it does output the URL for your convenience. Follow the advice in this document to create the initial admin user, and log into the system using this user in order to configure it for use. | ||
### Connecting to the TFE Application | ||
1. Navigate to the URL supplied via the `login_url` Terraform output. (It may take several minutes for this to be available after initial deployment. You may monitor the progress of cloud init if desired on one of the instances) | ||
2. Enter a `username`, `email`, and `password` for the initial user. | ||
3. Click `Create an account`. | ||
4. After the initial user is created you may access the TFE Application normally using the URL supplied via `login_url` Terraform output. |
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
This file was deleted.
Oops, something went wrong.