https://github.com/turnerlabs/looker_stack_aws_ec2_tf
Terraform for Looker Stack
https://github.com/turnerlabs/looker_stack_aws_ec2_tf
aws looker terraform
Last synced: about 2 months ago
JSON representation
Terraform for Looker Stack
- Host: GitHub
- URL: https://github.com/turnerlabs/looker_stack_aws_ec2_tf
- Owner: turnerlabs
- License: gpl-3.0
- Created: 2019-12-04T21:39:25.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2020-04-03T14:37:54.000Z (over 6 years ago)
- Last Synced: 2025-01-24T01:51:12.600Z (over 1 year ago)
- Topics: aws, looker, terraform
- Language: HCL
- Size: 1.65 MB
- Stars: 2
- Watchers: 4
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# What is this?
This is the [terraform](https://www.terraform.io/) code to create the following Looker architecture(assuming all the VPC's / Subnets are already in place).
## Directories
* The [tf_s3_state](https://github.com/turnerlabs/looker_stack_aws_ec2_tf/tree/master/tf_s3_state) directory contains the terraform code to create an s3 bucket to store the terraform state for the terraform code in the other directory.
* The [tf_existing_network](https://github.com/turnerlabs/looker_stack_aws_ec2_tf/tree/master/tf_existing_network) directory contains the terraform code to create the complete AWS Looker stack using existing VPC's and Subnets.
## How do I migrate new Looker AMIs to the stack I created in tf_existing_network?
There are several steps required to migrate a new version of Looker.
### Assumptions
* You have followed the instructions [here](https://github.com/turnerlabs/looker_stack_aws_ec2_ami/blob/master/looker_node) to succesfully create a new Looker Node AMI.
* You have followed the instructions [here](https://github.com/turnerlabs/looker_stack_aws_ec2_tf/tree/master/tf_existing_network) to succesfully create a new Looker AWS Stack.
### Steps
1. Modify [asgLooker.tf](https://github.com/turnerlabs/looker_stack_aws_ec2_tf/blob/master/tf_existing_network/asgLooker.tf) setting the max-size, min-size, and desired -capacity to zero.
`max_size = "0"
min_size = "0"
desired_capacity = "0"`
2. Run `terraform apply ...` to apply the changes which will take down all your instances.
3. Delete the `resource "aws_autoscaling_group" "asg_looker" {...}` section in your [asgLooker.tf](https://github.com/turnerlabs/looker_stack_aws_ec2_tf/blob/master/tf_existing_network/asgLooker.tf) file.
4. Delete the `resource "aws_cloudwatch_metric_alarm" "looker_asg_looker_cpu_utilization_too_high" {..}` section from your [snsCloudwatch.tf](https://github.com/turnerlabs/looker_stack_aws_ec2_tf/blob/master/tf_existing_network/snsCloudwatch.tf) file.
5. Delete lines 28 - 48 that reference the autoscale group from your [cloudwatchDashboard.tf](https://github.com/turnerlabs/looker_stack_aws_ec2_tf/blob/master/tf_existing_network/cloudwatchDashboard.tf) file.
6. Run `terraform apply ...` to apply the changes and remove your auto scale group.
7. Run `git checkout asgLooker.tf snsCloudwatch.tf cloudwatchDashboard.tf` to undo your changes.
8. Run `terraform apply ...` again with the `-var 'looker_node_ami='` variable set to your new AMI to update the launch config(and the auto scale group as well) with the new AMI.
**To backout changes, do the same steps above replacing the `-var 'looker_node_ami='` section with the previous AMI's id**