2e3dfccc68
* setup GCP terraform structure for connector dev infra * fxes * Created aws terraform bootstrap infrastructure * Corrected path for S3 state file * Creating ssh tunnel testing infrastructure * Creating a bastion host * Docs * Created bastion host with airbyte unprivileged account for tunneling * Added yum updates * Create a private subnet and a postgres database within it * Identifier for db * Create postgres and bastion within a module. * Set up postgres infrastructure * Don't need this terraform wrapper when we run with tfenv * Dropped incomplete WIP from GCP setup for this PR. * Touchups to how to use terraform * Updated to resolve merge conflict * More separated top level structure to avoid monorepo problems with terraform destroy. * Clarifying directory structure * Migrated directory structure for testing infrastructure Co-authored-by: Jenny Brown <jenny@airbyte.io>
21 lines
656 B
HCL
21 lines
656 B
HCL
# Best Practice is to use a remote state file on S3 plus a dynamodb concurrency lock
|
|
# https://www.terraform.io/docs/language/state/remote.html
|
|
# https://www.terraform.io/docs/language/state/locking.html
|
|
|
|
# Create a dynamodb table for locking the state file during terraform apply.
|
|
# This can be reused by multiple terraform projects just by referencing the resource.
|
|
resource "aws_dynamodb_table" "dynamodb-terraform-state-lock" {
|
|
name = "terraform-state-lock-dynamo"
|
|
hash_key = "LockID"
|
|
read_capacity = 20
|
|
write_capacity = 20
|
|
attribute {
|
|
name = "LockID"
|
|
type = "S"
|
|
}
|
|
tags = {
|
|
Name = "DynamoDB Terraform State Lock Table"
|
|
}
|
|
}
|
|
|