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>
12 lines
423 B
HCL
12 lines
423 B
HCL
# Terraform state files can contain secrets, so we should always encrypt
|
|
# the bucket those are on. Encryption requires a KMS key, which is created here.
|
|
|
|
resource "aws_kms_key" "terraform_s3_kms" {
|
|
description = "KMS key for terraform state S3 bucket"
|
|
}
|
|
resource "aws_kms_alias" "terraform_s3_kms_alias" {
|
|
name = "alias/terraform_s3_kms"
|
|
target_key_id = aws_kms_key.terraform_s3_kms.key_id
|
|
}
|
|
|