diff --git a/docs/courses.mdx b/docs/courses.mdx index 2f65b5569b..c3560de23d 100644 --- a/docs/courses.mdx +++ b/docs/courses.mdx @@ -58,5 +58,5 @@ Courses are offered through Teachable. Access is included with every Gruntwork s diff --git a/docs/guides/build-it-yourself/achieve-compliance/core-concepts/intro.md b/docs/guides/build-it-yourself/achieve-compliance/core-concepts/intro.md index 9a3219c90c..8d2e7d7583 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/core-concepts/intro.md +++ b/docs/guides/build-it-yourself/achieve-compliance/core-concepts/intro.md @@ -51,5 +51,5 @@ controls. diff --git a/docs/guides/build-it-yourself/achieve-compliance/core-concepts/recommendation-sections.md b/docs/guides/build-it-yourself/achieve-compliance/core-concepts/recommendation-sections.md index 65a6f87290..e6883df2c2 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/core-concepts/recommendation-sections.md +++ b/docs/guides/build-it-yourself/achieve-compliance/core-concepts/recommendation-sections.md @@ -58,5 +58,5 @@ suggest limiting routing for VPC peering connections based on [the principle of diff --git a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-an-iam-user-in-the-root-account.md b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-an-iam-user-in-the-root-account.md index 10c780e66f..fc8951ef48 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-an-iam-user-in-the-root-account.md +++ b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-an-iam-user-in-the-root-account.md @@ -14,5 +14,5 @@ IAM user manually by diff --git a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-the-root-account.md b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-the-root-account.md index ab7d26f990..a680f1d6db 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-the-root-account.md +++ b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-the-root-account.md @@ -9,5 +9,5 @@ The first step is to create your root account. This account will be the parent o diff --git a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-vpc-flow-logs.md b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-vpc-flow-logs.md index 081f56c810..ad64e23f53 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-vpc-flow-logs.md +++ b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-vpc-flow-logs.md @@ -155,5 +155,5 @@ default security groups from all VPCs in all regions. diff --git a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-app-to-logs-account.md b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-app-to-logs-account.md index c8e7db8bbc..9cf10908a5 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-app-to-logs-account.md +++ b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-app-to-logs-account.md @@ -279,5 +279,5 @@ On some operating systems, such as MacOS, you may also need to increase your ope diff --git a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-app-to-other-child-accounts.md b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-app-to-other-child-accounts.md index 856e0c737b..cfb8c6569e 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-app-to-other-child-accounts.md +++ b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-app-to-other-child-accounts.md @@ -309,5 +309,5 @@ the benchmark, v1.3.0; the AWS Security Hub does not support this version at the diff --git a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-root-to-root-account.md b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-root-to-root-account.md index 3560d159fb..cc7935d2ad 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-root-to-root-account.md +++ b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-root-to-root-account.md @@ -587,5 +587,5 @@ those root users again. diff --git a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-security-to-security-account.md b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-security-to-security-account.md index 59fb4c3274..2961ae2f4d 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-security-to-security-account.md +++ b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-security-to-security-account.md @@ -337,5 +337,5 @@ echo "" | base64 --decode | keybase pgp decrypt diff --git a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/enable-key-rotation-for-kms-keys.md b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/enable-key-rotation-for-kms-keys.md index 23cafe008d..c4a7c1eb59 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/enable-key-rotation-for-kms-keys.md +++ b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/enable-key-rotation-for-kms-keys.md @@ -6,5 +6,5 @@ to create KMS keys with key rotation enabled by default. diff --git a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-iam-best-practices.md b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-iam-best-practices.md index 7eeee08c64..7ec98de502 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-iam-best-practices.md +++ b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-iam-best-practices.md @@ -19,5 +19,5 @@ We conclude the IAM section with a few parting words of wisdom for maintaining c diff --git a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-logging-best-practices.md b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-logging-best-practices.md index 1f09a3f34a..2a34f61f60 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-logging-best-practices.md +++ b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-logging-best-practices.md @@ -4,5 +4,5 @@ The logging section of the Benchmark includes configurations for CloudTrail, AWS diff --git a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-storage-best-practices.md b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-storage-best-practices.md index cf8cb3c16e..67df44096d 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-storage-best-practices.md +++ b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-storage-best-practices.md @@ -18,5 +18,5 @@ the hood. diff --git a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/use-iam-roles-for-ec2-instances.md b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/use-iam-roles-for-ec2-instances.md index 9129b95692..ecf2396bb4 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/use-iam-roles-for-ec2-instances.md +++ b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/use-iam-roles-for-ec2-instances.md @@ -23,5 +23,5 @@ access to the AWS API. Using static API credentials should be avoided whenever p diff --git a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deployment-approach.md b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deployment-approach.md index 53dd560b53..b946b133e5 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deployment-approach.md +++ b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deployment-approach.md @@ -9,5 +9,5 @@ The standalone modules will follow the pattern of referencing the module and pro diff --git a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/lock-down-the-root-account-iam-users.md b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/lock-down-the-root-account-iam-users.md index 90b8efb127..207a8d0db2 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/lock-down-the-root-account-iam-users.md +++ b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/lock-down-the-root-account-iam-users.md @@ -32,5 +32,5 @@ so using a virtual or hardware MFA device is preferable; that said, MFA with SMS diff --git a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/lock-down-the-root-user.md b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/lock-down-the-root-user.md index b8712bf23d..311ab95be8 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/lock-down-the-root-user.md +++ b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/lock-down-the-root-user.md @@ -62,5 +62,5 @@ your credentials) or for the diff --git a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/pre-requisites.md b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/pre-requisites.md index 86446c2ba9..92f7bac092 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/pre-requisites.md +++ b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/pre-requisites.md @@ -55,5 +55,5 @@ automatically. diff --git a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/prepare-your-infrastructure-live-repository.md b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/prepare-your-infrastructure-live-repository.md index e450263adc..0fb349b3e9 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/prepare-your-infrastructure-live-repository.md +++ b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/prepare-your-infrastructure-live-repository.md @@ -9,5 +9,5 @@ We’ve previously described exactly how to prepare your repository in the diff --git a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/the-gruntwork-solution.md b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/the-gruntwork-solution.md index 18278310ce..c7210b59a6 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/the-gruntwork-solution.md +++ b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/the-gruntwork-solution.md @@ -59,5 +59,5 @@ our [Introduction to Gruntwork](/docs/intro/overview/intro-to-gruntwork) section diff --git a/docs/guides/build-it-yourself/achieve-compliance/index.md b/docs/guides/build-it-yourself/achieve-compliance/index.md index d29f1f06d5..3683998f6f 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/index.md +++ b/docs/guides/build-it-yourself/achieve-compliance/index.md @@ -69,5 +69,5 @@ walkthrough. diff --git a/docs/guides/build-it-yourself/achieve-compliance/next-steps.md b/docs/guides/build-it-yourself/achieve-compliance/next-steps.md index 2e883e8d87..5f7649e7cb 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/next-steps.md +++ b/docs/guides/build-it-yourself/achieve-compliance/next-steps.md @@ -13,5 +13,5 @@ Now it’s time to confirm that your configurations are correct and you didn’t diff --git a/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/identity-and-access-management.md b/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/identity-and-access-management.md index cd5c79a48c..fb5db08f46 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/identity-and-access-management.md +++ b/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/identity-and-access-management.md @@ -347,5 +347,5 @@ For further detail, follow the manual steps outlined in the CIS Benchmark docume diff --git a/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/intro.md b/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/intro.md index 8226f954a0..ff03c11046 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/intro.md +++ b/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/intro.md @@ -18,5 +18,5 @@ edition of Terraform Up & Running](https://blog.gruntwork.io/terraform-up-runnin diff --git a/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/logging.md b/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/logging.md index c280039836..6983977083 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/logging.md +++ b/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/logging.md @@ -148,5 +148,5 @@ the default VPCs which exist in all regions of the account. You can use the diff --git a/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/monitoring.md b/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/monitoring.md index d4085f9c80..fa72c64d30 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/monitoring.md +++ b/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/monitoring.md @@ -12,5 +12,5 @@ Terraform resources. diff --git a/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/networking.md b/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/networking.md index 8689e8da23..daa2f47203 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/networking.md +++ b/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/networking.md @@ -21,5 +21,5 @@ on the services running on those subnets. This can help to avoid exposing servic diff --git a/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/storage.md b/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/storage.md index 88df6a65a6..a98961aa3f 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/storage.md +++ b/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/storage.md @@ -138,5 +138,5 @@ explicit list of buckets per region, namely in the variable `buckets_to_analyze` diff --git a/docs/guides/build-it-yourself/achieve-compliance/traceability-matrix.md b/docs/guides/build-it-yourself/achieve-compliance/traceability-matrix.md index 5abd093b47..46abc4fcff 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/traceability-matrix.md +++ b/docs/guides/build-it-yourself/achieve-compliance/traceability-matrix.md @@ -734,5 +734,5 @@ sections above. diff --git a/docs/guides/build-it-yourself/index.md b/docs/guides/build-it-yourself/index.md index b4c11810c0..0d63f8993e 100644 --- a/docs/guides/build-it-yourself/index.md +++ b/docs/guides/build-it-yourself/index.md @@ -59,5 +59,5 @@ The Gruntwork IaC library empowers you to construct your own bespoke architectur diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/interacting-with-kubernetes.md b/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/interacting-with-kubernetes.md index 3be10a41b5..e316c4e985 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/interacting-with-kubernetes.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/interacting-with-kubernetes.md @@ -59,5 +59,5 @@ Terraform code anyway (e.g., execute a script). diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-access-control.md b/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-access-control.md index 570e029290..9e9cd00e06 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-access-control.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-access-control.md @@ -42,5 +42,5 @@ namespace), and associate those roles with the specific user and service account diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-architecture.md b/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-architecture.md index 34ff9dc437..4792aa947e 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-architecture.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-architecture.md @@ -106,5 +106,5 @@ used for Service Discovery within Kubernetes, a topic we’ll discuss later. diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-resources.md b/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-resources.md index 3634d9062e..9b82894900 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-resources.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-resources.md @@ -123,5 +123,5 @@ secrets unencrypted!). diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/options-for-running-kubernetes-in-aws.md b/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/options-for-running-kubernetes-in-aws.md index a5031a291b..4648f5a822 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/options-for-running-kubernetes-in-aws.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/options-for-running-kubernetes-in-aws.md @@ -36,5 +36,5 @@ still fairly new, so some functionality is missing or more complicated to use th diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/what-is-kubernetes.md b/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/what-is-kubernetes.md index 49ea0a8697..66b4974c77 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/what-is-kubernetes.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/what-is-kubernetes.md @@ -41,5 +41,5 @@ Provide containers with environment-specific configuration data and secrets. diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/why-kubernetes.md b/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/why-kubernetes.md index df880e7d68..f1c4482534 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/why-kubernetes.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/why-kubernetes.md @@ -38,5 +38,5 @@ continuously getting better. diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/10-try-out-the-cluster.md b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/10-try-out-the-cluster.md index b52d4566c4..9393e5923e 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/10-try-out-the-cluster.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/10-try-out-the-cluster.md @@ -19,5 +19,5 @@ kubectl get nodes diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/11-updating-the-worker-nodes.md b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/11-updating-the-worker-nodes.md index 32cfdbf4a2..1bff3425c2 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/11-updating-the-worker-nodes.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/11-updating-the-worker-nodes.md @@ -41,5 +41,5 @@ kubergrunt eks deploy --region --asg-name diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-access-to-the-control-plane-and-worker-nodes.md b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-access-to-the-control-plane-and-worker-nodes.md index 3d5514059a..da0e4148a3 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-access-to-the-control-plane-and-worker-nodes.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-access-to-the-control-plane-and-worker-nodes.md @@ -103,5 +103,5 @@ resource "aws_iam_role_policy" "ssh_grunt_permissions" { diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-logging-metrics-and-alarms-for-the-worker-nodes.md b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-logging-metrics-and-alarms-for-the-worker-nodes.md index 4a2560cc13..444025ae58 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-logging-metrics-and-alarms-for-the-worker-nodes.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-logging-metrics-and-alarms-for-the-worker-nodes.md @@ -95,5 +95,5 @@ data "terraform_remote_state" "sns_region" { diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-role-mapping.md b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-role-mapping.md index 713c00c88e..8eb80fa39f 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-role-mapping.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-role-mapping.md @@ -76,5 +76,5 @@ data "aws_eks_cluster_auth" "kubernetes_token" { diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-control-plane.md b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-control-plane.md index b727351cda..2a56526ea3 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-control-plane.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-control-plane.md @@ -129,5 +129,5 @@ variable "terraform_state_s3_bucket" { diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-worker-node-user-data-script.md b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-worker-node-user-data-script.md index 94187870a7..deb4e2fed3 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-worker-node-user-data-script.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-worker-node-user-data-script.md @@ -105,5 +105,5 @@ data "template_file" "user_data" { diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-worker-nodes.md b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-worker-nodes.md index 2963410763..e3bcd4688e 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-worker-nodes.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-worker-nodes.md @@ -74,5 +74,5 @@ variable "cluster_instance_keypair_name" { diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/create-the-worker-node-ami.md b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/create-the-worker-node-ami.md index 62bb0bfcba..490a0e2aa5 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/create-the-worker-node-ami.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/create-the-worker-node-ami.md @@ -137,5 +137,5 @@ guide. diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/deploy-the-eks-cluster.md b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/deploy-the-eks-cluster.md index 005aa49952..e41ef7da65 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/deploy-the-eks-cluster.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/deploy-the-eks-cluster.md @@ -124,5 +124,5 @@ terragrunt apply diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/deploy-the-vpc.md b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/deploy-the-vpc.md index abffcf30b0..8f3626def9 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/deploy-the-vpc.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/deploy-the-vpc.md @@ -149,5 +149,5 @@ terragrunt apply diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/pre-requisites.md b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/pre-requisites.md index f46d74e4fb..1a67c13ed2 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/pre-requisites.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/pre-requisites.md @@ -58,5 +58,5 @@ for instructions. diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/index.md b/docs/guides/build-it-yourself/kubernetes-cluster/index.md index 9123c2f590..8f9ec5bdb0 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/index.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/index.md @@ -50,5 +50,5 @@ This guide will walk you through the process of configuring a production-grade K diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/next-steps.md b/docs/guides/build-it-yourself/kubernetes-cluster/next-steps.md index 8d3d3922bd..13de85372c 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/next-steps.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/next-steps.md @@ -9,5 +9,5 @@ any data stores they depend on by using the following guides: diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/authenticate.md b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/authenticate.md index 6719a2af31..06621dd1eb 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/authenticate.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/authenticate.md @@ -71,5 +71,5 @@ this tool separately, so we are just recording this here for historical reasons. diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/control-plane.md b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/control-plane.md index 2b2310c930..5e05e1c0b9 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/control-plane.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/control-plane.md @@ -54,5 +54,5 @@ CloudWatch. diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/iam-role-mapping-and-rbac.md b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/iam-role-mapping-and-rbac.md index 9677c0b9da..3afb2ffeda 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/iam-role-mapping-and-rbac.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/iam-role-mapping-and-rbac.md @@ -45,5 +45,5 @@ assume those roles. diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/intro.md b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/intro.md index 5c2774d402..d4685919ac 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/intro.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/intro.md @@ -11,5 +11,5 @@ that looks something like this: diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/logging.md b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/logging.md index d2a8ec80f1..f30d5479a1 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/logging.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/logging.md @@ -27,5 +27,5 @@ the logs from the worker nodes (including all the pods on them) to CloudWatch. diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/protecting-pods.md b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/protecting-pods.md index ea3a56eb9d..9b1c74bfa1 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/protecting-pods.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/protecting-pods.md @@ -34,5 +34,5 @@ gives it permissions to talk solely to the other pods it should be able to acces diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/use-eks.md b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/use-eks.md index e870937bec..b16628c739 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/use-eks.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/use-eks.md @@ -8,5 +8,5 @@ solutions will most likely be eclipsed very quickly by future EKS releases. diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/vpc-configuration.md b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/vpc-configuration.md index c9ce2ba16f..d9f5b5aaad 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/vpc-configuration.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/vpc-configuration.md @@ -30,5 +30,5 @@ sure that remote VPC DNS resolution is enabled on both accepter and requester si diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/worker-nodes.md b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/worker-nodes.md index 00f0f642c0..495ca2500a 100644 --- a/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/worker-nodes.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/worker-nodes.md @@ -66,5 +66,5 @@ a secure base image (e.g., CIS hardened images), intrusion prevention (e.g., `fa diff --git a/docs/guides/build-it-yourself/landing-zone/core-concepts/aws-account.md b/docs/guides/build-it-yourself/landing-zone/core-concepts/aws-account.md index 929a600187..c12d4afeb3 100644 --- a/docs/guides/build-it-yourself/landing-zone/core-concepts/aws-account.md +++ b/docs/guides/build-it-yourself/landing-zone/core-concepts/aws-account.md @@ -12,5 +12,5 @@ to share it publicly on the Internet), and you will be logged into your new AWS diff --git a/docs/guides/build-it-yourself/landing-zone/core-concepts/aws-config.md b/docs/guides/build-it-yourself/landing-zone/core-concepts/aws-config.md index 36fce004f8..d9b1bd2a0c 100644 --- a/docs/guides/build-it-yourself/landing-zone/core-concepts/aws-config.md +++ b/docs/guides/build-it-yourself/landing-zone/core-concepts/aws-config.md @@ -19,5 +19,5 @@ but you can also author your own [custom rules](https://docs.aws.amazon.com/conf diff --git a/docs/guides/build-it-yourself/landing-zone/core-concepts/aws-organizations.md b/docs/guides/build-it-yourself/landing-zone/core-concepts/aws-organizations.md index 038026f95a..78cdf45d42 100644 --- a/docs/guides/build-it-yourself/landing-zone/core-concepts/aws-organizations.md +++ b/docs/guides/build-it-yourself/landing-zone/core-concepts/aws-organizations.md @@ -54,5 +54,5 @@ those regions or services do not meet your company’s compliance requirements ( diff --git a/docs/guides/build-it-yourself/landing-zone/core-concepts/cloud-trail.md b/docs/guides/build-it-yourself/landing-zone/core-concepts/cloud-trail.md index 58c52fb79b..08f29ff3e3 100644 --- a/docs/guides/build-it-yourself/landing-zone/core-concepts/cloud-trail.md +++ b/docs/guides/build-it-yourself/landing-zone/core-concepts/cloud-trail.md @@ -14,5 +14,5 @@ incidents, and maintaining audit logs for compliance. diff --git a/docs/guides/build-it-yourself/landing-zone/core-concepts/federated-authentication.md b/docs/guides/build-it-yourself/landing-zone/core-concepts/federated-authentication.md index a0b1f0b897..cbb8e2bc9d 100644 --- a/docs/guides/build-it-yourself/landing-zone/core-concepts/federated-authentication.md +++ b/docs/guides/build-it-yourself/landing-zone/core-concepts/federated-authentication.md @@ -34,5 +34,5 @@ requires multiple steps, including manually copy/pasting credentials. diff --git a/docs/guides/build-it-yourself/landing-zone/core-concepts/guard-duty.md b/docs/guides/build-it-yourself/landing-zone/core-concepts/guard-duty.md index 9cc826c887..4ccc6f9d84 100644 --- a/docs/guides/build-it-yourself/landing-zone/core-concepts/guard-duty.md +++ b/docs/guides/build-it-yourself/landing-zone/core-concepts/guard-duty.md @@ -11,5 +11,5 @@ intelligence to identify and prioritize potential threats. diff --git a/docs/guides/build-it-yourself/landing-zone/core-concepts/iam-groups.md b/docs/guides/build-it-yourself/landing-zone/core-concepts/iam-groups.md index 7840542a57..3feb2935e9 100644 --- a/docs/guides/build-it-yourself/landing-zone/core-concepts/iam-groups.md +++ b/docs/guides/build-it-yourself/landing-zone/core-concepts/iam-groups.md @@ -13,5 +13,5 @@ and assign each IAM user to the appropriate IAM groups. diff --git a/docs/guides/build-it-yourself/landing-zone/core-concepts/iam-policies.md b/docs/guides/build-it-yourself/landing-zone/core-concepts/iam-policies.md index b3a0ae9242..97bb76b0a3 100644 --- a/docs/guides/build-it-yourself/landing-zone/core-concepts/iam-policies.md +++ b/docs/guides/build-it-yourself/landing-zone/core-concepts/iam-policies.md @@ -70,5 +70,5 @@ S3 bucket. diff --git a/docs/guides/build-it-yourself/landing-zone/core-concepts/iam-roles.md b/docs/guides/build-it-yourself/landing-zone/core-concepts/iam-roles.md index a0ec4602cb..4a66d182c2 100644 --- a/docs/guides/build-it-yourself/landing-zone/core-concepts/iam-roles.md +++ b/docs/guides/build-it-yourself/landing-zone/core-concepts/iam-roles.md @@ -125,5 +125,5 @@ services permissions to access specific resources in your AWS account. diff --git a/docs/guides/build-it-yourself/landing-zone/core-concepts/iam-users.md b/docs/guides/build-it-yourself/landing-zone/core-concepts/iam-users.md index cb0e4d59d9..200bbb3693 100644 --- a/docs/guides/build-it-yourself/landing-zone/core-concepts/iam-users.md +++ b/docs/guides/build-it-yourself/landing-zone/core-concepts/iam-users.md @@ -70,5 +70,5 @@ user permissions, you will need to use IAM policies, which are the topic of the diff --git a/docs/guides/build-it-yourself/landing-zone/core-concepts/root-user.md b/docs/guides/build-it-yourself/landing-zone/core-concepts/root-user.md index cb5e078440..91c7d0870b 100644 --- a/docs/guides/build-it-yourself/landing-zone/core-concepts/root-user.md +++ b/docs/guides/build-it-yourself/landing-zone/core-concepts/root-user.md @@ -60,5 +60,5 @@ more limited permissions, and then you’ll likely never touch the root user acc diff --git a/docs/guides/build-it-yourself/landing-zone/core-concepts/what-is-an-aws-account-structure.md b/docs/guides/build-it-yourself/landing-zone/core-concepts/what-is-an-aws-account-structure.md index 2c0b6d142a..593f82753d 100644 --- a/docs/guides/build-it-yourself/landing-zone/core-concepts/what-is-an-aws-account-structure.md +++ b/docs/guides/build-it-yourself/landing-zone/core-concepts/what-is-an-aws-account-structure.md @@ -35,5 +35,5 @@ breakdowns by account, service, tag, etc. diff --git a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-logs-account.md b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-logs-account.md index f2c35f49c4..dc013482e0 100644 --- a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-logs-account.md +++ b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-logs-account.md @@ -153,5 +153,5 @@ On some operating systems, such as MacOS, you may also need to increase your ope diff --git a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-other-child-accounts.md b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-other-child-accounts.md index d4a0473881..4821d9529f 100644 --- a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-other-child-accounts.md +++ b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-other-child-accounts.md @@ -163,5 +163,5 @@ Remember to repeat this process in the other child accounts too (i.e., dev, prod diff --git a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-root-account.md b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-root-account.md index 04caa5d338..378b0419c0 100644 --- a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-root-account.md +++ b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-root-account.md @@ -81,5 +81,5 @@ echo "" | base64 --decode | keybase pgp decrypt diff --git a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-security-account.md b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-security-account.md index 012e0f2f41..77e8b38f1e 100644 --- a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-security-account.md +++ b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-security-account.md @@ -203,5 +203,5 @@ echo "" | base64 --decode | keybase pgp decrypt diff --git a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/configure-the-security-baseline-for-the-root-account.md b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/configure-the-security-baseline-for-the-root-account.md index c688c97d8b..cfd059dcab 100644 --- a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/configure-the-security-baseline-for-the-root-account.md +++ b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/configure-the-security-baseline-for-the-root-account.md @@ -173,5 +173,5 @@ and any other existing resources. diff --git a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/create-an-iam-user-in-the-root-account.md b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/create-an-iam-user-in-the-root-account.md index a39fb393b7..81605d97f2 100644 --- a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/create-an-iam-user-in-the-root-account.md +++ b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/create-an-iam-user-in-the-root-account.md @@ -18,5 +18,5 @@ IAM user manually by diff --git a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/create-the-root-account.md b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/create-the-root-account.md index c0e76a1b85..cfb602b40e 100644 --- a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/create-the-root-account.md +++ b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/create-the-root-account.md @@ -14,5 +14,5 @@ the central place where you manage billing. You create this initial account manu diff --git a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/import-existing-resources-from-the-root-account-into-terraform-state.md b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/import-existing-resources-from-the-root-account-into-terraform-state.md index 011146b0df..77c96f2e1f 100644 --- a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/import-existing-resources-from-the-root-account-into-terraform-state.md +++ b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/import-existing-resources-from-the-root-account-into-terraform-state.md @@ -145,5 +145,5 @@ rm -rf .terragrunt-cache diff --git a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/lock-down-the-root-account-iam-users.md b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/lock-down-the-root-account-iam-users.md index 74d46ffb44..b11c985088 100644 --- a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/lock-down-the-root-account-iam-users.md +++ b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/lock-down-the-root-account-iam-users.md @@ -35,5 +35,5 @@ so using a virtual or hardware MFA device is preferable; that said, MFA with SMS diff --git a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/lock-down-the-root-user-in-the-child-accounts.md b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/lock-down-the-root-user-in-the-child-accounts.md index f9d9c92da0..3619cbbbd5 100644 --- a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/lock-down-the-root-user-in-the-child-accounts.md +++ b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/lock-down-the-root-user-in-the-child-accounts.md @@ -6,5 +6,5 @@ those root users again. diff --git a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/lock-down-the-root-user.md b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/lock-down-the-root-user.md index 5fdc01ee2c..c7b63511aa 100644 --- a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/lock-down-the-root-user.md +++ b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/lock-down-the-root-user.md @@ -45,5 +45,5 @@ your credentials) or for the diff --git a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/pre-requisites.md b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/pre-requisites.md index 27381b8479..22e863f50d 100644 --- a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/pre-requisites.md +++ b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/pre-requisites.md @@ -56,5 +56,5 @@ automatically. diff --git a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/prepare-your-infrastructure-live-repository.md b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/prepare-your-infrastructure-live-repository.md index 1f124f0448..a9c13ecf98 100644 --- a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/prepare-your-infrastructure-live-repository.md +++ b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/prepare-your-infrastructure-live-repository.md @@ -176,5 +176,5 @@ locals { diff --git a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/reset-the-root-user-password-in-each-child-account.md b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/reset-the-root-user-password-in-each-child-account.md index 0cc5bd495a..67c5da2f9f 100644 --- a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/reset-the-root-user-password-in-each-child-account.md +++ b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/reset-the-root-user-password-in-each-child-account.md @@ -13,5 +13,5 @@ Use this process to reset the password for the root user of each child account y diff --git a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/try-authenticating-as-an-iam-user-to-the-child-accounts.md b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/try-authenticating-as-an-iam-user-to-the-child-accounts.md index 5f0e889a4b..b65bf1f111 100644 --- a/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/try-authenticating-as-an-iam-user-to-the-child-accounts.md +++ b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/try-authenticating-as-an-iam-user-to-the-child-accounts.md @@ -25,5 +25,5 @@ authenticating: diff --git a/docs/guides/build-it-yourself/landing-zone/index.md b/docs/guides/build-it-yourself/landing-zone/index.md index c04549509f..0feeb496c5 100644 --- a/docs/guides/build-it-yourself/landing-zone/index.md +++ b/docs/guides/build-it-yourself/landing-zone/index.md @@ -97,5 +97,5 @@ Feel free to read this guide from start to finish or skip around to whatever sec diff --git a/docs/guides/build-it-yourself/landing-zone/next-steps.md b/docs/guides/build-it-yourself/landing-zone/next-steps.md index 902171f9ea..dfe090accd 100644 --- a/docs/guides/build-it-yourself/landing-zone/next-steps.md +++ b/docs/guides/build-it-yourself/landing-zone/next-steps.md @@ -6,5 +6,5 @@ accounts! Usually, the best starting point is to configure your network topology diff --git a/docs/guides/build-it-yourself/landing-zone/production-grade-design/aws-config.md b/docs/guides/build-it-yourself/landing-zone/production-grade-design/aws-config.md index c14bff7b5b..e27160bff1 100644 --- a/docs/guides/build-it-yourself/landing-zone/production-grade-design/aws-config.md +++ b/docs/guides/build-it-yourself/landing-zone/production-grade-design/aws-config.md @@ -17,5 +17,5 @@ We typically recommend that you aggregate AWS Config data in the logs account. T diff --git a/docs/guides/build-it-yourself/landing-zone/production-grade-design/child-accounts.md b/docs/guides/build-it-yourself/landing-zone/production-grade-design/child-accounts.md index 1fbbb5c7d5..472e58208f 100644 --- a/docs/guides/build-it-yourself/landing-zone/production-grade-design/child-accounts.md +++ b/docs/guides/build-it-yourself/landing-zone/production-grade-design/child-accounts.md @@ -70,5 +70,5 @@ for large organizations to have dozens or even hundreds of AWS accounts. diff --git a/docs/guides/build-it-yourself/landing-zone/production-grade-design/cloud-trail.md b/docs/guides/build-it-yourself/landing-zone/production-grade-design/cloud-trail.md index 1607ebf183..eddb1528a1 100644 --- a/docs/guides/build-it-yourself/landing-zone/production-grade-design/cloud-trail.md +++ b/docs/guides/build-it-yourself/landing-zone/production-grade-design/cloud-trail.md @@ -18,5 +18,5 @@ happening in the account. We typically recommend that you aggregate these logs i diff --git a/docs/guides/build-it-yourself/landing-zone/production-grade-design/federated-auth.md b/docs/guides/build-it-yourself/landing-zone/production-grade-design/federated-auth.md index d8e41e3e62..fdec53c4cd 100644 --- a/docs/guides/build-it-yourself/landing-zone/production-grade-design/federated-auth.md +++ b/docs/guides/build-it-yourself/landing-zone/production-grade-design/federated-auth.md @@ -52,5 +52,5 @@ so if you want to require MFA, you need to do that in the IdP itself (i.e., in G diff --git a/docs/guides/build-it-yourself/landing-zone/production-grade-design/guard-duty.md b/docs/guides/build-it-yourself/landing-zone/production-grade-design/guard-duty.md index 8a63c352ba..4c2c38254b 100644 --- a/docs/guides/build-it-yourself/landing-zone/production-grade-design/guard-duty.md +++ b/docs/guides/build-it-yourself/landing-zone/production-grade-design/guard-duty.md @@ -8,5 +8,5 @@ publishing GuardDuty’s findings to a dedicated Amazon SNS topic. diff --git a/docs/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-services.md b/docs/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-services.md index 85e905f232..45bbdd2f5c 100644 --- a/docs/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-services.md +++ b/docs/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-services.md @@ -136,5 +136,5 @@ sensitive machine user access keys. diff --git a/docs/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-users.md b/docs/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-users.md index 41483bb4b4..86a981f3fe 100644 --- a/docs/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-users.md +++ b/docs/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-users.md @@ -56,5 +56,5 @@ server and allows developers with access to these IAM roles to request VPN certi diff --git a/docs/guides/build-it-yourself/landing-zone/production-grade-design/iam-users-and-groups.md b/docs/guides/build-it-yourself/landing-zone/production-grade-design/iam-users-and-groups.md index 5c19bd9904..79cc327862 100644 --- a/docs/guides/build-it-yourself/landing-zone/production-grade-design/iam-users-and-groups.md +++ b/docs/guides/build-it-yourself/landing-zone/production-grade-design/iam-users-and-groups.md @@ -45,5 +45,5 @@ You must be a Gruntwork subscriber to diff --git a/docs/guides/build-it-yourself/landing-zone/production-grade-design/intro.md b/docs/guides/build-it-yourself/landing-zone/production-grade-design/intro.md index 7835e9c3a4..e376ec6fb6 100644 --- a/docs/guides/build-it-yourself/landing-zone/production-grade-design/intro.md +++ b/docs/guides/build-it-yourself/landing-zone/production-grade-design/intro.md @@ -13,5 +13,5 @@ we'll break it down piece by piece in the next few sections. diff --git a/docs/guides/build-it-yourself/landing-zone/production-grade-design/mfa-policy.md b/docs/guides/build-it-yourself/landing-zone/production-grade-design/mfa-policy.md index 40fca43ae4..4ebfaac10f 100644 --- a/docs/guides/build-it-yourself/landing-zone/production-grade-design/mfa-policy.md +++ b/docs/guides/build-it-yourself/landing-zone/production-grade-design/mfa-policy.md @@ -35,5 +35,5 @@ place. diff --git a/docs/guides/build-it-yourself/landing-zone/production-grade-design/password-policy.md b/docs/guides/build-it-yourself/landing-zone/production-grade-design/password-policy.md index 0d1c9a950f..c1327adf10 100644 --- a/docs/guides/build-it-yourself/landing-zone/production-grade-design/password-policy.md +++ b/docs/guides/build-it-yourself/landing-zone/production-grade-design/password-policy.md @@ -7,5 +7,5 @@ certain compliance requirements may force you to use a specific password policy) diff --git a/docs/guides/build-it-yourself/landing-zone/production-grade-design/the-root-account.md b/docs/guides/build-it-yourself/landing-zone/production-grade-design/the-root-account.md index 1d026b1ed4..8580fcabbc 100644 --- a/docs/guides/build-it-yourself/landing-zone/production-grade-design/the-root-account.md +++ b/docs/guides/build-it-yourself/landing-zone/production-grade-design/the-root-account.md @@ -12,5 +12,5 @@ IAM group that gives the finance team access to the billing details. diff --git a/docs/guides/build-it-yourself/pipelines/core-concepts/ci-cd-platforms.md b/docs/guides/build-it-yourself/pipelines/core-concepts/ci-cd-platforms.md index 35bf1c8a79..23bdbee5ff 100644 --- a/docs/guides/build-it-yourself/pipelines/core-concepts/ci-cd-platforms.md +++ b/docs/guides/build-it-yourself/pipelines/core-concepts/ci-cd-platforms.md @@ -131,5 +131,5 @@ provides, as well as how they mitigate the threat model that we cover: diff --git a/docs/guides/build-it-yourself/pipelines/core-concepts/ci-cd-workflows.md b/docs/guides/build-it-yourself/pipelines/core-concepts/ci-cd-workflows.md index 7def6e10a5..74b3865ff3 100644 --- a/docs/guides/build-it-yourself/pipelines/core-concepts/ci-cd-workflows.md +++ b/docs/guides/build-it-yourself/pipelines/core-concepts/ci-cd-workflows.md @@ -440,5 +440,5 @@ for this type of workflow. diff --git a/docs/guides/build-it-yourself/pipelines/core-concepts/threat-model-of-ci-cd.md b/docs/guides/build-it-yourself/pipelines/core-concepts/threat-model-of-ci-cd.md index 9c99a74740..420297012d 100644 --- a/docs/guides/build-it-yourself/pipelines/core-concepts/threat-model-of-ci-cd.md +++ b/docs/guides/build-it-yourself/pipelines/core-concepts/threat-model-of-ci-cd.md @@ -48,5 +48,5 @@ With this threat model in mind, let’s take a look at the different CI/CD platf diff --git a/docs/guides/build-it-yourself/pipelines/core-concepts/trunk-based-development-model.md b/docs/guides/build-it-yourself/pipelines/core-concepts/trunk-based-development-model.md index 0f801ef07d..aaf9267e7e 100644 --- a/docs/guides/build-it-yourself/pipelines/core-concepts/trunk-based-development-model.md +++ b/docs/guides/build-it-yourself/pipelines/core-concepts/trunk-based-development-model.md @@ -56,5 +56,5 @@ infrastructure code. diff --git a/docs/guides/build-it-yourself/pipelines/core-concepts/types-of-infrastructure-code.md b/docs/guides/build-it-yourself/pipelines/core-concepts/types-of-infrastructure-code.md index 5e23bf7fcc..4619f4ab80 100644 --- a/docs/guides/build-it-yourself/pipelines/core-concepts/types-of-infrastructure-code.md +++ b/docs/guides/build-it-yourself/pipelines/core-concepts/types-of-infrastructure-code.md @@ -36,5 +36,5 @@ infrastructure modules, and live infrastructure configuration. diff --git a/docs/guides/build-it-yourself/pipelines/core-concepts/what-is-continuous-integration-and-continuous-delivery.md b/docs/guides/build-it-yourself/pipelines/core-concepts/what-is-continuous-integration-and-continuous-delivery.md index ae869ef322..3f6e435b88 100644 --- a/docs/guides/build-it-yourself/pipelines/core-concepts/what-is-continuous-integration-and-continuous-delivery.md +++ b/docs/guides/build-it-yourself/pipelines/core-concepts/what-is-continuous-integration-and-continuous-delivery.md @@ -14,5 +14,5 @@ of a production-ready CI/CD pipeline for infrastructure code. diff --git a/docs/guides/build-it-yourself/pipelines/core-concepts/why-is-it-important-to-have-ci-cd.md b/docs/guides/build-it-yourself/pipelines/core-concepts/why-is-it-important-to-have-ci-cd.md index ae784a92d1..862bd612a1 100644 --- a/docs/guides/build-it-yourself/pipelines/core-concepts/why-is-it-important-to-have-ci-cd.md +++ b/docs/guides/build-it-yourself/pipelines/core-concepts/why-is-it-important-to-have-ci-cd.md @@ -38,5 +38,5 @@ ensuring that there is ample time for improvements and corrections. diff --git a/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/configure-ci-server.md b/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/configure-ci-server.md index 072489c93d..d14718af99 100644 --- a/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/configure-ci-server.md +++ b/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/configure-ci-server.md @@ -39,5 +39,5 @@ events! diff --git a/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/define-pipeline-as-code.md b/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/define-pipeline-as-code.md index a6647b0911..84979e750b 100644 --- a/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/define-pipeline-as-code.md +++ b/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/define-pipeline-as-code.md @@ -473,5 +473,5 @@ jobs: diff --git a/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/deploy-a-vpc.md b/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/deploy-a-vpc.md index a35be79740..6d962f72f1 100644 --- a/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/deploy-a-vpc.md +++ b/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/deploy-a-vpc.md @@ -37,5 +37,5 @@ infrastructure-live diff --git a/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/deploy-the-ecs-deploy-runner.md b/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/deploy-the-ecs-deploy-runner.md index b102d71f47..81785d6803 100644 --- a/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/deploy-the-ecs-deploy-runner.md +++ b/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/deploy-the-ecs-deploy-runner.md @@ -751,5 +751,5 @@ Repeat for each environment that you want to support the ECS Deploy Runner stack diff --git a/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/pre-requisites.md b/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/pre-requisites.md index 67941b7d4e..81e5c7fd0f 100644 --- a/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/pre-requisites.md +++ b/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/pre-requisites.md @@ -67,5 +67,5 @@ on alternative options, such as how to diff --git a/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/try-out-the-ecs-deploy-runner.md b/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/try-out-the-ecs-deploy-runner.md index f0a8c3eba4..5443c32f16 100644 --- a/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/try-out-the-ecs-deploy-runner.md +++ b/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/try-out-the-ecs-deploy-runner.md @@ -50,5 +50,5 @@ Running this command will provide output similar to below: diff --git a/docs/guides/build-it-yourself/pipelines/index.md b/docs/guides/build-it-yourself/pipelines/index.md index f3748e5f54..c9e8eeec54 100644 --- a/docs/guides/build-it-yourself/pipelines/index.md +++ b/docs/guides/build-it-yourself/pipelines/index.md @@ -90,5 +90,5 @@ Feel free to read this guide from start to finish or skip around to whatever sec diff --git a/docs/guides/build-it-yourself/pipelines/next-steps.md b/docs/guides/build-it-yourself/pipelines/next-steps.md index 1552bd78ae..b0aec7b41c 100644 --- a/docs/guides/build-it-yourself/pipelines/next-steps.md +++ b/docs/guides/build-it-yourself/pipelines/next-steps.md @@ -9,5 +9,5 @@ Now that you have a CI/CD pipeline for your infrastructure code, test it out by diff --git a/docs/guides/build-it-yourself/pipelines/production-grade-design/intro.md b/docs/guides/build-it-yourself/pipelines/production-grade-design/intro.md index fd01956113..3dddcafebd 100644 --- a/docs/guides/build-it-yourself/pipelines/production-grade-design/intro.md +++ b/docs/guides/build-it-yourself/pipelines/production-grade-design/intro.md @@ -12,5 +12,5 @@ infrastructure code, using a platform that looks something like this: diff --git a/docs/guides/build-it-yourself/pipelines/production-grade-design/limit-triggers-for-deploy-server.md b/docs/guides/build-it-yourself/pipelines/production-grade-design/limit-triggers-for-deploy-server.md index 0ce0e97e2f..db21a3e1eb 100644 --- a/docs/guides/build-it-yourself/pipelines/production-grade-design/limit-triggers-for-deploy-server.md +++ b/docs/guides/build-it-yourself/pipelines/production-grade-design/limit-triggers-for-deploy-server.md @@ -19,5 +19,5 @@ You can find similar mechanisms for limiting deployments in the various deploy s diff --git a/docs/guides/build-it-yourself/pipelines/production-grade-design/lock-down-vcs-systems.md b/docs/guides/build-it-yourself/pipelines/production-grade-design/lock-down-vcs-systems.md index 0138885f6a..406fe44bb8 100644 --- a/docs/guides/build-it-yourself/pipelines/production-grade-design/lock-down-vcs-systems.md +++ b/docs/guides/build-it-yourself/pipelines/production-grade-design/lock-down-vcs-systems.md @@ -38,5 +38,5 @@ internal environment variables or show infrastructure secrets using external dat diff --git a/docs/guides/build-it-yourself/pipelines/production-grade-design/options-for-deploy-server.md b/docs/guides/build-it-yourself/pipelines/production-grade-design/options-for-deploy-server.md index fd3038f0c5..343c13aa9e 100644 --- a/docs/guides/build-it-yourself/pipelines/production-grade-design/options-for-deploy-server.md +++ b/docs/guides/build-it-yourself/pipelines/production-grade-design/options-for-deploy-server.md @@ -38,5 +38,5 @@ cover it, the design is compatible with using Terraform Enterprise as the deploy diff --git a/docs/guides/build-it-yourself/pipelines/production-grade-design/summary-of-deployment-sequence.md b/docs/guides/build-it-yourself/pipelines/production-grade-design/summary-of-deployment-sequence.md index cf55e09f61..f63e8c4121 100644 --- a/docs/guides/build-it-yourself/pipelines/production-grade-design/summary-of-deployment-sequence.md +++ b/docs/guides/build-it-yourself/pipelines/production-grade-design/summary-of-deployment-sequence.md @@ -6,5 +6,5 @@ To put it all together, the following sequence diagram shows how all the various diff --git a/docs/guides/build-it-yourself/pipelines/production-grade-design/summary-of-mitigations.md b/docs/guides/build-it-yourself/pipelines/production-grade-design/summary-of-mitigations.md index a2020c7888..8768ab5489 100644 --- a/docs/guides/build-it-yourself/pipelines/production-grade-design/summary-of-mitigations.md +++ b/docs/guides/build-it-yourself/pipelines/production-grade-design/summary-of-mitigations.md @@ -94,5 +94,5 @@ with the `sensitive` keyword so that terraform will mask the outputs. diff --git a/docs/guides/build-it-yourself/pipelines/production-grade-design/use-a-vpc-to-lock-down-deploy-server.md b/docs/guides/build-it-yourself/pipelines/production-grade-design/use-a-vpc-to-lock-down-deploy-server.md index 703c547b55..de9c0f1b35 100644 --- a/docs/guides/build-it-yourself/pipelines/production-grade-design/use-a-vpc-to-lock-down-deploy-server.md +++ b/docs/guides/build-it-yourself/pipelines/production-grade-design/use-a-vpc-to-lock-down-deploy-server.md @@ -7,5 +7,5 @@ outbound access except for the minimum required (e.g, allow access to AWS APIs). diff --git a/docs/guides/build-it-yourself/pipelines/production-grade-design/use-approval-flows.md b/docs/guides/build-it-yourself/pipelines/production-grade-design/use-approval-flows.md index 40f6e5d505..a741047ebc 100644 --- a/docs/guides/build-it-yourself/pipelines/production-grade-design/use-approval-flows.md +++ b/docs/guides/build-it-yourself/pipelines/production-grade-design/use-approval-flows.md @@ -12,5 +12,5 @@ can approve the workflow. diff --git a/docs/guides/build-it-yourself/pipelines/production-grade-design/use-generic-ci-cd-platforms-as-a-workflow-engine-but-run-infrastructure-deployments-from-within-your-account.md b/docs/guides/build-it-yourself/pipelines/production-grade-design/use-generic-ci-cd-platforms-as-a-workflow-engine-but-run-infrastructure-deployments-from-within-your-account.md index 11bf37ac47..4bb8e7be2d 100644 --- a/docs/guides/build-it-yourself/pipelines/production-grade-design/use-generic-ci-cd-platforms-as-a-workflow-engine-but-run-infrastructure-deployments-from-within-your-account.md +++ b/docs/guides/build-it-yourself/pipelines/production-grade-design/use-generic-ci-cd-platforms-as-a-workflow-engine-but-run-infrastructure-deployments-from-within-your-account.md @@ -28,5 +28,5 @@ builds on existing code, but they don’t get arbitrary admin access. diff --git a/docs/guides/build-it-yourself/pipelines/production-grade-design/use-minimal-iam-permissions-for-a-deployment.md b/docs/guides/build-it-yourself/pipelines/production-grade-design/use-minimal-iam-permissions-for-a-deployment.md index bd6b369cf7..3c8d816a8f 100644 --- a/docs/guides/build-it-yourself/pipelines/production-grade-design/use-minimal-iam-permissions-for-a-deployment.md +++ b/docs/guides/build-it-yourself/pipelines/production-grade-design/use-minimal-iam-permissions-for-a-deployment.md @@ -9,5 +9,5 @@ which has more access to the environments. diff --git a/docs/guides/build-it-yourself/vpc/core-concepts/cidr-notation.md b/docs/guides/build-it-yourself/vpc/core-concepts/cidr-notation.md index b51493453f..29d1721bb9 100644 --- a/docs/guides/build-it-yourself/vpc/core-concepts/cidr-notation.md +++ b/docs/guides/build-it-yourself/vpc/core-concepts/cidr-notation.md @@ -42,5 +42,5 @@ CIDR notation for just one IP, `4.4.4.4`. diff --git a/docs/guides/build-it-yourself/vpc/core-concepts/default-vp-cs-and-custom-vp-cs.md b/docs/guides/build-it-yourself/vpc/core-concepts/default-vp-cs-and-custom-vp-cs.md index 0ee8ae47bf..5443efb64f 100644 --- a/docs/guides/build-it-yourself/vpc/core-concepts/default-vp-cs-and-custom-vp-cs.md +++ b/docs/guides/build-it-yourself/vpc/core-concepts/default-vp-cs-and-custom-vp-cs.md @@ -54,5 +54,5 @@ over how to configure a VPC with the kind of security, scalability, and high ava diff --git a/docs/guides/build-it-yourself/vpc/core-concepts/internet-gateways-public-subnets-and-private-subnets.md b/docs/guides/build-it-yourself/vpc/core-concepts/internet-gateways-public-subnets-and-private-subnets.md index 1e97f80874..695fe7c823 100644 --- a/docs/guides/build-it-yourself/vpc/core-concepts/internet-gateways-public-subnets-and-private-subnets.md +++ b/docs/guides/build-it-yourself/vpc/core-concepts/internet-gateways-public-subnets-and-private-subnets.md @@ -11,5 +11,5 @@ the VPC. diff --git a/docs/guides/build-it-yourself/vpc/core-concepts/nat-gateways.md b/docs/guides/build-it-yourself/vpc/core-concepts/nat-gateways.md index 6bd27f6bd3..f7b4c974ff 100644 --- a/docs/guides/build-it-yourself/vpc/core-concepts/nat-gateways.md +++ b/docs/guides/build-it-yourself/vpc/core-concepts/nat-gateways.md @@ -37,5 +37,5 @@ the traffic for all other IPs, `0.0.0.0/0`, to a NAT Gateway with ID `nat-67890` diff --git a/docs/guides/build-it-yourself/vpc/core-concepts/network-ac-ls.md b/docs/guides/build-it-yourself/vpc/core-concepts/network-ac-ls.md index 190d4f61f4..bad87ac95c 100644 --- a/docs/guides/build-it-yourself/vpc/core-concepts/network-ac-ls.md +++ b/docs/guides/build-it-yourself/vpc/core-concepts/network-ac-ls.md @@ -37,5 +37,5 @@ locking down source/destination IP addresses. diff --git a/docs/guides/build-it-yourself/vpc/core-concepts/regions-and-availability-zones.md b/docs/guides/build-it-yourself/vpc/core-concepts/regions-and-availability-zones.md index 24ab6d360b..54ec2a331c 100644 --- a/docs/guides/build-it-yourself/vpc/core-concepts/regions-and-availability-zones.md +++ b/docs/guides/build-it-yourself/vpc/core-concepts/regions-and-availability-zones.md @@ -22,5 +22,5 @@ as starting points. diff --git a/docs/guides/build-it-yourself/vpc/core-concepts/route-tables.md b/docs/guides/build-it-yourself/vpc/core-concepts/route-tables.md index 210668f5d1..cc640c1cb3 100644 --- a/docs/guides/build-it-yourself/vpc/core-concepts/route-tables.md +++ b/docs/guides/build-it-yourself/vpc/core-concepts/route-tables.md @@ -34,5 +34,5 @@ will be automatically routed within the subnet by AWS. This table then adds a fa diff --git a/docs/guides/build-it-yourself/vpc/core-concepts/security-groups.md b/docs/guides/build-it-yourself/vpc/core-concepts/security-groups.md index 5208031ca8..f5b8692956 100644 --- a/docs/guides/build-it-yourself/vpc/core-concepts/security-groups.md +++ b/docs/guides/build-it-yourself/vpc/core-concepts/security-groups.md @@ -76,5 +76,5 @@ custom security group with rules that exactly match your use case, rather than r diff --git a/docs/guides/build-it-yourself/vpc/core-concepts/subnets.md b/docs/guides/build-it-yourself/vpc/core-concepts/subnets.md index e099dd1acd..39b2da01a0 100644 --- a/docs/guides/build-it-yourself/vpc/core-concepts/subnets.md +++ b/docs/guides/build-it-yourself/vpc/core-concepts/subnets.md @@ -11,5 +11,5 @@ ranges. diff --git a/docs/guides/build-it-yourself/vpc/core-concepts/vpc-endpoints.md b/docs/guides/build-it-yourself/vpc/core-concepts/vpc-endpoints.md index f6526a1131..7fd1fc8c2c 100644 --- a/docs/guides/build-it-yourself/vpc/core-concepts/vpc-endpoints.md +++ b/docs/guides/build-it-yourself/vpc/core-concepts/vpc-endpoints.md @@ -33,5 +33,5 @@ a paid service, and includes support for CloudTrail, Secrets Manager, EC2, SNS, diff --git a/docs/guides/build-it-yourself/vpc/core-concepts/vpc-ip-addresses.md b/docs/guides/build-it-yourself/vpc/core-concepts/vpc-ip-addresses.md index 0f8748cac2..a8f89e61b9 100644 --- a/docs/guides/build-it-yourself/vpc/core-concepts/vpc-ip-addresses.md +++ b/docs/guides/build-it-yourself/vpc/core-concepts/vpc-ip-addresses.md @@ -31,5 +31,5 @@ while another instance might get the private IP address `172.31.5.3` and the pub diff --git a/docs/guides/build-it-yourself/vpc/core-concepts/vpc-peering.md b/docs/guides/build-it-yourself/vpc/core-concepts/vpc-peering.md index 74118f778a..31a131342c 100644 --- a/docs/guides/build-it-yourself/vpc/core-concepts/vpc-peering.md +++ b/docs/guides/build-it-yourself/vpc/core-concepts/vpc-peering.md @@ -26,5 +26,5 @@ connections total) can quickly become impractical. In this case, you should look diff --git a/docs/guides/build-it-yourself/vpc/core-concepts/what-is-a-vpc.md b/docs/guides/build-it-yourself/vpc/core-concepts/what-is-a-vpc.md index 47e8a23e5a..6d8d9fa940 100644 --- a/docs/guides/build-it-yourself/vpc/core-concepts/what-is-a-vpc.md +++ b/docs/guides/build-it-yourself/vpc/core-concepts/what-is-a-vpc.md @@ -31,5 +31,5 @@ your office and all the resources in your AWS account can access the same IPs an diff --git a/docs/guides/build-it-yourself/vpc/deployment-walkthrough/clean-up-default-vp-cs-and-security-groups.md b/docs/guides/build-it-yourself/vpc/deployment-walkthrough/clean-up-default-vp-cs-and-security-groups.md index 53ee3bae63..3c7dadb340 100644 --- a/docs/guides/build-it-yourself/vpc/deployment-walkthrough/clean-up-default-vp-cs-and-security-groups.md +++ b/docs/guides/build-it-yourself/vpc/deployment-walkthrough/clean-up-default-vp-cs-and-security-groups.md @@ -9,5 +9,5 @@ cloud-nuke defaults-aws diff --git a/docs/guides/build-it-yourself/vpc/deployment-walkthrough/deploy-a-bastion-host.md b/docs/guides/build-it-yourself/vpc/deployment-walkthrough/deploy-a-bastion-host.md index 9763babc5d..b785046d82 100644 --- a/docs/guides/build-it-yourself/vpc/deployment-walkthrough/deploy-a-bastion-host.md +++ b/docs/guides/build-it-yourself/vpc/deployment-walkthrough/deploy-a-bastion-host.md @@ -4,5 +4,5 @@ Please check out our [Bastion Host](https://github.com/gruntwork-io/terraform-aw diff --git a/docs/guides/build-it-yourself/vpc/deployment-walkthrough/deploy-a-management-vpc.md b/docs/guides/build-it-yourself/vpc/deployment-walkthrough/deploy-a-management-vpc.md index 6a30b10f32..b3b0b20260 100644 --- a/docs/guides/build-it-yourself/vpc/deployment-walkthrough/deploy-a-management-vpc.md +++ b/docs/guides/build-it-yourself/vpc/deployment-walkthrough/deploy-a-management-vpc.md @@ -214,5 +214,5 @@ terragrunt apply diff --git a/docs/guides/build-it-yourself/vpc/deployment-walkthrough/deploy-application-vp-cs.md b/docs/guides/build-it-yourself/vpc/deployment-walkthrough/deploy-application-vp-cs.md index b78c5e889e..3f7d2286c5 100644 --- a/docs/guides/build-it-yourself/vpc/deployment-walkthrough/deploy-application-vp-cs.md +++ b/docs/guides/build-it-yourself/vpc/deployment-walkthrough/deploy-application-vp-cs.md @@ -245,5 +245,5 @@ terragrunt apply diff --git a/docs/guides/build-it-yourself/vpc/deployment-walkthrough/pre-requisites.md b/docs/guides/build-it-yourself/vpc/deployment-walkthrough/pre-requisites.md index a4406a7a53..dc17e265af 100644 --- a/docs/guides/build-it-yourself/vpc/deployment-walkthrough/pre-requisites.md +++ b/docs/guides/build-it-yourself/vpc/deployment-walkthrough/pre-requisites.md @@ -43,5 +43,5 @@ for instructions. diff --git a/docs/guides/build-it-yourself/vpc/index.md b/docs/guides/build-it-yourself/vpc/index.md index 440e32e0d1..a5c04f62af 100644 --- a/docs/guides/build-it-yourself/vpc/index.md +++ b/docs/guides/build-it-yourself/vpc/index.md @@ -47,5 +47,5 @@ Feel free to read this guide from start to finish or skip around to whatever sec diff --git a/docs/guides/build-it-yourself/vpc/next-steps.md b/docs/guides/build-it-yourself/vpc/next-steps.md index cf8768bb06..be83834fa6 100644 --- a/docs/guides/build-it-yourself/vpc/next-steps.md +++ b/docs/guides/build-it-yourself/vpc/next-steps.md @@ -13,5 +13,5 @@ If you’re not sure which of these options to use, check out the `Server Cluste diff --git a/docs/guides/build-it-yourself/vpc/production-grade-design/bastion-host.md b/docs/guides/build-it-yourself/vpc/production-grade-design/bastion-host.md index 445c6a8726..0df0138120 100644 --- a/docs/guides/build-it-yourself/vpc/production-grade-design/bastion-host.md +++ b/docs/guides/build-it-yourself/vpc/production-grade-design/bastion-host.md @@ -20,5 +20,5 @@ allow you to manage and connect to EC2 Instances via a custom protocol managed b diff --git a/docs/guides/build-it-yourself/vpc/production-grade-design/defense-in-depth.md b/docs/guides/build-it-yourself/vpc/production-grade-design/defense-in-depth.md index 5f8919f648..5dffb90d03 100644 --- a/docs/guides/build-it-yourself/vpc/production-grade-design/defense-in-depth.md +++ b/docs/guides/build-it-yourself/vpc/production-grade-design/defense-in-depth.md @@ -15,5 +15,5 @@ described in the next few sections. diff --git a/docs/guides/build-it-yourself/vpc/production-grade-design/internet-gateways-and-nat-gateways.md b/docs/guides/build-it-yourself/vpc/production-grade-design/internet-gateways-and-nat-gateways.md index b3c2cf1226..d49330dbb3 100644 --- a/docs/guides/build-it-yourself/vpc/production-grade-design/internet-gateways-and-nat-gateways.md +++ b/docs/guides/build-it-yourself/vpc/production-grade-design/internet-gateways-and-nat-gateways.md @@ -27,5 +27,5 @@ availability zone as the subnet itself). diff --git a/docs/guides/build-it-yourself/vpc/production-grade-design/intro.md b/docs/guides/build-it-yourself/vpc/production-grade-design/intro.md index 8681826b43..b842efd515 100644 --- a/docs/guides/build-it-yourself/vpc/production-grade-design/intro.md +++ b/docs/guides/build-it-yourself/vpc/production-grade-design/intro.md @@ -11,5 +11,5 @@ something like this: diff --git a/docs/guides/build-it-yourself/vpc/production-grade-design/multiple-aws-accounts.md b/docs/guides/build-it-yourself/vpc/production-grade-design/multiple-aws-accounts.md index d3640ba578..ba5944d569 100644 --- a/docs/guides/build-it-yourself/vpc/production-grade-design/multiple-aws-accounts.md +++ b/docs/guides/build-it-yourself/vpc/production-grade-design/multiple-aws-accounts.md @@ -16,5 +16,5 @@ guide for instructions. diff --git a/docs/guides/build-it-yourself/vpc/production-grade-design/multiple-subnet-tiers.md b/docs/guides/build-it-yourself/vpc/production-grade-design/multiple-subnet-tiers.md index ab62a8fc24..c2cfd750b9 100644 --- a/docs/guides/build-it-yourself/vpc/production-grade-design/multiple-subnet-tiers.md +++ b/docs/guides/build-it-yourself/vpc/production-grade-design/multiple-subnet-tiers.md @@ -37,5 +37,5 @@ discussed in the next section. diff --git a/docs/guides/build-it-yourself/vpc/production-grade-design/multiple-vp-cs.md b/docs/guides/build-it-yourself/vpc/production-grade-design/multiple-vp-cs.md index 4fcd801de7..64b4a83812 100644 --- a/docs/guides/build-it-yourself/vpc/production-grade-design/multiple-vp-cs.md +++ b/docs/guides/build-it-yourself/vpc/production-grade-design/multiple-vp-cs.md @@ -54,5 +54,5 @@ your corporate intranet via site-to-site VPN connections. diff --git a/docs/guides/build-it-yourself/vpc/production-grade-design/security-groups-and-nac-ls.md b/docs/guides/build-it-yourself/vpc/production-grade-design/security-groups-and-nac-ls.md index 24fea5ddbc..77f2de6a30 100644 --- a/docs/guides/build-it-yourself/vpc/production-grade-design/security-groups-and-nac-ls.md +++ b/docs/guides/build-it-yourself/vpc/production-grade-design/security-groups-and-nac-ls.md @@ -33,5 +33,5 @@ environment. diff --git a/docs/guides/index.md b/docs/guides/index.md index 10506dc68b..f826d74c8e 100644 --- a/docs/guides/index.md +++ b/docs/guides/index.md @@ -22,5 +22,5 @@ We present a comprehensive model to help you establish a robust infrastructure p diff --git a/docs/guides/production-framework/gruntwork-solutions/index.md b/docs/guides/production-framework/gruntwork-solutions/index.md index bd3f6bec44..818af2f41d 100644 --- a/docs/guides/production-framework/gruntwork-solutions/index.md +++ b/docs/guides/production-framework/gruntwork-solutions/index.md @@ -42,5 +42,5 @@ questions, please [contact sales](https://gruntwork.io/contact/). diff --git a/docs/guides/production-framework/index.md b/docs/guides/production-framework/index.md index 20ca26f1cf..124e09cd8d 100644 --- a/docs/guides/production-framework/index.md +++ b/docs/guides/production-framework/index.md @@ -178,5 +178,5 @@ Gruntwork to help you implement this framework. diff --git a/docs/guides/production-framework/ingredients/automatic-updates/auto-update-features.md b/docs/guides/production-framework/ingredients/automatic-updates/auto-update-features.md index 00e69f64a1..39eee0ef1c 100644 --- a/docs/guides/production-framework/ingredients/automatic-updates/auto-update-features.md +++ b/docs/guides/production-framework/ingredients/automatic-updates/auto-update-features.md @@ -19,5 +19,5 @@ Your auto update solution should automatically check that none of your dependenc diff --git a/docs/guides/production-framework/ingredients/automatic-updates/how-auto-update-should-work.md b/docs/guides/production-framework/ingredients/automatic-updates/how-auto-update-should-work.md index 9d94fb33f6..88e4172741 100644 --- a/docs/guides/production-framework/ingredients/automatic-updates/how-auto-update-should-work.md +++ b/docs/guides/production-framework/ingredients/automatic-updates/how-auto-update-should-work.md @@ -19,5 +19,5 @@ Once the update is merged, the CI / CD pipeline again kicks in, and automaticall diff --git a/docs/guides/production-framework/ingredients/automatic-updates/index.md b/docs/guides/production-framework/ingredients/automatic-updates/index.md index 6c655cd591..f6a5e39136 100644 --- a/docs/guides/production-framework/ingredients/automatic-updates/index.md +++ b/docs/guides/production-framework/ingredients/automatic-updates/index.md @@ -13,5 +13,5 @@ everything up-to-date, so that all your hard work doesn't turn into tech debt. diff --git a/docs/guides/production-framework/ingredients/ci-cd-pipeline/ci-cd-features.md b/docs/guides/production-framework/ingredients/ci-cd-pipeline/ci-cd-features.md index 02b1028adf..7146a73162 100644 --- a/docs/guides/production-framework/ingredients/ci-cd-pipeline/ci-cd-features.md +++ b/docs/guides/production-framework/ingredients/ci-cd-pipeline/ci-cd-features.md @@ -39,5 +39,5 @@ AWS](https://docs.gruntwork.io/docs/guides/build-it-yourself/landing-zone/). diff --git a/docs/guides/production-framework/ingredients/ci-cd-pipeline/ci-cd-only-path-to-prod.md b/docs/guides/production-framework/ingredients/ci-cd-pipeline/ci-cd-only-path-to-prod.md index 1a6de47678..9e731de169 100644 --- a/docs/guides/production-framework/ingredients/ci-cd-pipeline/ci-cd-only-path-to-prod.md +++ b/docs/guides/production-framework/ingredients/ci-cd-pipeline/ci-cd-only-path-to-prod.md @@ -16,5 +16,5 @@ It's a bad idea to have give your CI server (e.g., Jenkins)—which your entire diff --git a/docs/guides/production-framework/ingredients/ci-cd-pipeline/index.md b/docs/guides/production-framework/ingredients/ci-cd-pipeline/index.md index c38ae26dd3..31c2797c73 100644 --- a/docs/guides/production-framework/ingredients/ci-cd-pipeline/index.md +++ b/docs/guides/production-framework/ingredients/ci-cd-pipeline/index.md @@ -8,5 +8,5 @@ pipeline) to automate their build, test, and deployment processes. diff --git a/docs/guides/production-framework/ingredients/index.md b/docs/guides/production-framework/ingredients/index.md index 439ccd4b9a..af2383636d 100644 --- a/docs/guides/production-framework/ingredients/index.md +++ b/docs/guides/production-framework/ingredients/index.md @@ -8,5 +8,5 @@ cloud effectively. diff --git a/docs/guides/production-framework/ingredients/landing-zone/account-vending-machine.md b/docs/guides/production-framework/ingredients/landing-zone/account-vending-machine.md index 373d5f0c6e..af1333e4c7 100644 --- a/docs/guides/production-framework/ingredients/landing-zone/account-vending-machine.md +++ b/docs/guides/production-framework/ingredients/landing-zone/account-vending-machine.md @@ -22,5 +22,5 @@ As part of the account provisioning process, the Account Vending Machine should diff --git a/docs/guides/production-framework/ingredients/landing-zone/index.md b/docs/guides/production-framework/ingredients/landing-zone/index.md index 68dfac79aa..10f2a0fe2f 100644 --- a/docs/guides/production-framework/ingredients/landing-zone/index.md +++ b/docs/guides/production-framework/ingredients/landing-zone/index.md @@ -13,5 +13,5 @@ harder than setting up the proper controls in the first place. diff --git a/docs/guides/production-framework/ingredients/landing-zone/what-landing-zone-should-include.md b/docs/guides/production-framework/ingredients/landing-zone/what-landing-zone-should-include.md index f2f4383a07..656be40430 100644 --- a/docs/guides/production-framework/ingredients/landing-zone/what-landing-zone-should-include.md +++ b/docs/guides/production-framework/ingredients/landing-zone/what-landing-zone-should-include.md @@ -26,5 +26,5 @@ Zone](https://docs.gruntwork.io/docs/guides/build-it-yourself/landing-zone/). diff --git a/docs/guides/production-framework/ingredients/other-ingredients/index.md b/docs/guides/production-framework/ingredients/other-ingredients/index.md index f4a9270198..4c871e8905 100644 --- a/docs/guides/production-framework/ingredients/other-ingredients/index.md +++ b/docs/guides/production-framework/ingredients/other-ingredients/index.md @@ -22,5 +22,5 @@ Performance optimization, cost optimization, and capacity optimization ("rightsi diff --git a/docs/guides/production-framework/ingredients/self-service/common-self-service-use-cases.md b/docs/guides/production-framework/ingredients/self-service/common-self-service-use-cases.md index 2ee1074799..89b10961b6 100644 --- a/docs/guides/production-framework/ingredients/self-service/common-self-service-use-cases.md +++ b/docs/guides/production-framework/ingredients/self-service/common-self-service-use-cases.md @@ -17,5 +17,5 @@ Deploy a new app: that is, a web service written in a general purpose programmin diff --git a/docs/guides/production-framework/ingredients/self-service/how-self-service-should-work.md b/docs/guides/production-framework/ingredients/self-service/how-self-service-should-work.md index 6916271ca8..69133f5e57 100644 --- a/docs/guides/production-framework/ingredients/self-service/how-self-service-should-work.md +++ b/docs/guides/production-framework/ingredients/self-service/how-self-service-should-work.md @@ -19,5 +19,5 @@ Many Ops teams get nervous with the idea of self-service: what if the developers diff --git a/docs/guides/production-framework/ingredients/self-service/index.md b/docs/guides/production-framework/ingredients/self-service/index.md index cd5b98814e..4b8e04386b 100644 --- a/docs/guides/production-framework/ingredients/self-service/index.md +++ b/docs/guides/production-framework/ingredients/self-service/index.md @@ -10,5 +10,5 @@ infrastructure those apps depend on. diff --git a/docs/guides/production-framework/ingredients/service-catalog/application-templates.md b/docs/guides/production-framework/ingredients/service-catalog/application-templates.md index 745330201c..c7ce2e1bc4 100644 --- a/docs/guides/production-framework/ingredients/service-catalog/application-templates.md +++ b/docs/guides/production-framework/ingredients/service-catalog/application-templates.md @@ -72,5 +72,5 @@ You'll want to make it as simple as possible for new apps to be integrated into diff --git a/docs/guides/production-framework/ingredients/service-catalog/index.md b/docs/guides/production-framework/ingredients/service-catalog/index.md index d7b82eda74..ae20b8a567 100644 --- a/docs/guides/production-framework/ingredients/service-catalog/index.md +++ b/docs/guides/production-framework/ingredients/service-catalog/index.md @@ -23,5 +23,5 @@ mean by "Service Catalog" in this guide, and what a modern Service Catalog looks diff --git a/docs/guides/production-framework/ingredients/service-catalog/infrastructure-templates.md b/docs/guides/production-framework/ingredients/service-catalog/infrastructure-templates.md index ca8180bc02..e5c2017720 100644 --- a/docs/guides/production-framework/ingredients/service-catalog/infrastructure-templates.md +++ b/docs/guides/production-framework/ingredients/service-catalog/infrastructure-templates.md @@ -82,5 +82,5 @@ We'll discuss CI / CD more in a dedicated section later on. diff --git a/docs/guides/production-framework/ingredients/service-catalog/modern-service-catalog.md b/docs/guides/production-framework/ingredients/service-catalog/modern-service-catalog.md index 4a11c7b236..dc07d63a8d 100644 --- a/docs/guides/production-framework/ingredients/service-catalog/modern-service-catalog.md +++ b/docs/guides/production-framework/ingredients/service-catalog/modern-service-catalog.md @@ -48,5 +48,5 @@ For a concrete example of a Service Catalog for AWS, see the [Gruntwork Service diff --git a/docs/guides/production-framework/recipes/dev-team-experience.md b/docs/guides/production-framework/recipes/dev-team-experience.md index a5dba50f14..dfca6180e2 100644 --- a/docs/guides/production-framework/recipes/dev-team-experience.md +++ b/docs/guides/production-framework/recipes/dev-team-experience.md @@ -94,5 +94,5 @@ Let's imagine that you've started a team with two developers, Ann and Bob. The t diff --git a/docs/guides/production-framework/recipes/index.md b/docs/guides/production-framework/recipes/index.md index 4e4302ddee..29034dc501 100644 --- a/docs/guides/production-framework/recipes/index.md +++ b/docs/guides/production-framework/recipes/index.md @@ -10,5 +10,5 @@ how all these pieces can work together. diff --git a/docs/guides/production-framework/recipes/ops-team-experience.md b/docs/guides/production-framework/recipes/ops-team-experience.md index b452895bce..493c75912f 100644 --- a/docs/guides/production-framework/recipes/ops-team-experience.md +++ b/docs/guides/production-framework/recipes/ops-team-experience.md @@ -29,5 +29,5 @@ On the Ops side, Carol and Daniel are responsible for maintaining your Service C diff --git a/docs/guides/reference-architecture/example-usage-guide/02-authenticate/01-intro.md b/docs/guides/reference-architecture/example-usage-guide/02-authenticate/01-intro.md index 715af8830a..ecb4cc09fd 100644 --- a/docs/guides/reference-architecture/example-usage-guide/02-authenticate/01-intro.md +++ b/docs/guides/reference-architecture/example-usage-guide/02-authenticate/01-intro.md @@ -29,5 +29,5 @@ and connecting to all the resources in your AWS accounts: diff --git a/docs/guides/reference-architecture/example-usage-guide/02-authenticate/02-setting-up-initial-access.md b/docs/guides/reference-architecture/example-usage-guide/02-authenticate/02-setting-up-initial-access.md index 2d82910142..26b9d09cc2 100644 --- a/docs/guides/reference-architecture/example-usage-guide/02-authenticate/02-setting-up-initial-access.md +++ b/docs/guides/reference-architecture/example-usage-guide/02-authenticate/02-setting-up-initial-access.md @@ -144,5 +144,5 @@ To deploy this new code and create the new IAM users, you will need to: diff --git a/docs/guides/reference-architecture/example-usage-guide/02-authenticate/03-authenticate-to-the-aws-web-console.md b/docs/guides/reference-architecture/example-usage-guide/02-authenticate/03-authenticate-to-the-aws-web-console.md index 2a5db0ddf5..fb3852fd36 100644 --- a/docs/guides/reference-architecture/example-usage-guide/02-authenticate/03-authenticate-to-the-aws-web-console.md +++ b/docs/guides/reference-architecture/example-usage-guide/02-authenticate/03-authenticate-to-the-aws-web-console.md @@ -32,5 +32,5 @@ To authenticate to any other account (e.g., dev, stage, prod), you need to: diff --git a/docs/guides/reference-architecture/example-usage-guide/02-authenticate/04-authenticate-to-aws-via-the-cli.md b/docs/guides/reference-architecture/example-usage-guide/02-authenticate/04-authenticate-to-aws-via-the-cli.md index 30671d79a7..5ff147ff8b 100644 --- a/docs/guides/reference-architecture/example-usage-guide/02-authenticate/04-authenticate-to-aws-via-the-cli.md +++ b/docs/guides/reference-architecture/example-usage-guide/02-authenticate/04-authenticate-to-aws-via-the-cli.md @@ -100,5 +100,5 @@ Be sure to read [`USAGE.md`](https://github.com/99designs/aws-vault/blob/master/ diff --git a/docs/guides/reference-architecture/example-usage-guide/02-authenticate/05-authenticate-to-ec2-instances-via-ssh.md b/docs/guides/reference-architecture/example-usage-guide/02-authenticate/05-authenticate-to-ec2-instances-via-ssh.md index e776dc115e..e67c93b664 100644 --- a/docs/guides/reference-architecture/example-usage-guide/02-authenticate/05-authenticate-to-ec2-instances-via-ssh.md +++ b/docs/guides/reference-architecture/example-usage-guide/02-authenticate/05-authenticate-to-ec2-instances-via-ssh.md @@ -74,5 +74,5 @@ Key Pairs. diff --git a/docs/guides/reference-architecture/example-usage-guide/02-authenticate/06-authenticate-to-the-vpn-server.md b/docs/guides/reference-architecture/example-usage-guide/02-authenticate/06-authenticate-to-the-vpn-server.md index cf4536ff8f..34865e1e87 100644 --- a/docs/guides/reference-architecture/example-usage-guide/02-authenticate/06-authenticate-to-the-vpn-server.md +++ b/docs/guides/reference-architecture/example-usage-guide/02-authenticate/06-authenticate-to-the-vpn-server.md @@ -62,5 +62,5 @@ network (e.g., SSH to EC2 instances in private subnets) as if you were "in" the diff --git a/docs/guides/reference-architecture/example-usage-guide/03-deploy-apps/01-intro.md b/docs/guides/reference-architecture/example-usage-guide/03-deploy-apps/01-intro.md index 8231f5a3cd..80a86dc180 100644 --- a/docs/guides/reference-architecture/example-usage-guide/03-deploy-apps/01-intro.md +++ b/docs/guides/reference-architecture/example-usage-guide/03-deploy-apps/01-intro.md @@ -16,5 +16,5 @@ Architecture. diff --git a/docs/guides/reference-architecture/example-usage-guide/03-deploy-apps/02-what-is-already-deployed.md b/docs/guides/reference-architecture/example-usage-guide/03-deploy-apps/02-what-is-already-deployed.md index 571b1a57b3..5c916e8fa7 100644 --- a/docs/guides/reference-architecture/example-usage-guide/03-deploy-apps/02-what-is-already-deployed.md +++ b/docs/guides/reference-architecture/example-usage-guide/03-deploy-apps/02-what-is-already-deployed.md @@ -15,5 +15,5 @@ practices from [aws-sample-app](https://github.com/gruntwork-io/aws-sample-app/) diff --git a/docs/guides/reference-architecture/example-usage-guide/03-deploy-apps/03-the-app.md b/docs/guides/reference-architecture/example-usage-guide/03-deploy-apps/03-the-app.md index a92e2c5151..832ca21035 100644 --- a/docs/guides/reference-architecture/example-usage-guide/03-deploy-apps/03-the-app.md +++ b/docs/guides/reference-architecture/example-usage-guide/03-deploy-apps/03-the-app.md @@ -40,5 +40,5 @@ Since we need to pull in the dependencies to run this app, we will also need a c diff --git a/docs/guides/reference-architecture/example-usage-guide/03-deploy-apps/04-dockerizing.md b/docs/guides/reference-architecture/example-usage-guide/03-deploy-apps/04-dockerizing.md index fb3bb5fd17..f755fff7e5 100644 --- a/docs/guides/reference-architecture/example-usage-guide/03-deploy-apps/04-dockerizing.md +++ b/docs/guides/reference-architecture/example-usage-guide/03-deploy-apps/04-dockerizing.md @@ -65,5 +65,5 @@ Some things to note when writing up your `Dockerfile` and building your app: diff --git a/docs/guides/reference-architecture/example-usage-guide/03-deploy-apps/05-publish-docker-image.md b/docs/guides/reference-architecture/example-usage-guide/03-deploy-apps/05-publish-docker-image.md index db744947a8..053801f14c 100644 --- a/docs/guides/reference-architecture/example-usage-guide/03-deploy-apps/05-publish-docker-image.md +++ b/docs/guides/reference-architecture/example-usage-guide/03-deploy-apps/05-publish-docker-image.md @@ -62,5 +62,5 @@ docker push 234567890123.dkr.ecr.us-west-2.amazonaws.com/simple-web-app:v1 diff --git a/docs/guides/reference-architecture/example-usage-guide/04-configure-gw-pipelines/01-intro.md b/docs/guides/reference-architecture/example-usage-guide/04-configure-gw-pipelines/01-intro.md index d054f90b9b..1e259a00f1 100644 --- a/docs/guides/reference-architecture/example-usage-guide/04-configure-gw-pipelines/01-intro.md +++ b/docs/guides/reference-architecture/example-usage-guide/04-configure-gw-pipelines/01-intro.md @@ -23,5 +23,5 @@ code](https://gruntwork.io/guides/automations/how-to-configure-a-production-grad diff --git a/docs/guides/reference-architecture/example-usage-guide/04-configure-gw-pipelines/02-ci--cd-pipeline-for-infrastructure-code.md b/docs/guides/reference-architecture/example-usage-guide/04-configure-gw-pipelines/02-ci--cd-pipeline-for-infrastructure-code.md index 429f48d33d..b87629bfc1 100644 --- a/docs/guides/reference-architecture/example-usage-guide/04-configure-gw-pipelines/02-ci--cd-pipeline-for-infrastructure-code.md +++ b/docs/guides/reference-architecture/example-usage-guide/04-configure-gw-pipelines/02-ci--cd-pipeline-for-infrastructure-code.md @@ -99,5 +99,5 @@ For instructions on how to destroy infrastructure, see the [Undeploy guide](../0 diff --git a/docs/guides/reference-architecture/example-usage-guide/04-configure-gw-pipelines/03-ci--cd-pipeline-for-app-code.md b/docs/guides/reference-architecture/example-usage-guide/04-configure-gw-pipelines/03-ci--cd-pipeline-for-app-code.md index 73922825ea..edefb148ff 100644 --- a/docs/guides/reference-architecture/example-usage-guide/04-configure-gw-pipelines/03-ci--cd-pipeline-for-app-code.md +++ b/docs/guides/reference-architecture/example-usage-guide/04-configure-gw-pipelines/03-ci--cd-pipeline-for-app-code.md @@ -64,5 +64,5 @@ Once the branch is merged, updates to the `main` branch will trigger a build job diff --git a/docs/guides/reference-architecture/example-usage-guide/04-configure-gw-pipelines/04-update-the-ci--cd-pipeline-itself.md b/docs/guides/reference-architecture/example-usage-guide/04-configure-gw-pipelines/04-update-the-ci--cd-pipeline-itself.md index 4d6854eba3..0b71e68b4e 100644 --- a/docs/guides/reference-architecture/example-usage-guide/04-configure-gw-pipelines/04-update-the-ci--cd-pipeline-itself.md +++ b/docs/guides/reference-architecture/example-usage-guide/04-configure-gw-pipelines/04-update-the-ci--cd-pipeline-itself.md @@ -70,5 +70,5 @@ pull request as your changes to the `ecs-deploy-runner` module configuration. diff --git a/docs/guides/reference-architecture/example-usage-guide/05-monitoring-alerting-logging/01-intro.md b/docs/guides/reference-architecture/example-usage-guide/05-monitoring-alerting-logging/01-intro.md index 15829f2a4e..e99c37605e 100644 --- a/docs/guides/reference-architecture/example-usage-guide/05-monitoring-alerting-logging/01-intro.md +++ b/docs/guides/reference-architecture/example-usage-guide/05-monitoring-alerting-logging/01-intro.md @@ -14,5 +14,5 @@ and deploy your code, you'll want to see what's happening in your AWS account: diff --git a/docs/guides/reference-architecture/example-usage-guide/05-monitoring-alerting-logging/02-metrics.md b/docs/guides/reference-architecture/example-usage-guide/05-monitoring-alerting-logging/02-metrics.md index ed9fcf0d3e..d40fabc932 100644 --- a/docs/guides/reference-architecture/example-usage-guide/05-monitoring-alerting-logging/02-metrics.md +++ b/docs/guides/reference-architecture/example-usage-guide/05-monitoring-alerting-logging/02-metrics.md @@ -15,5 +15,5 @@ with the most useful metrics for your services and have that open on a big scree diff --git a/docs/guides/reference-architecture/example-usage-guide/05-monitoring-alerting-logging/03-alerts.md b/docs/guides/reference-architecture/example-usage-guide/05-monitoring-alerting-logging/03-alerts.md index 905babda73..73f8cee669 100644 --- a/docs/guides/reference-architecture/example-usage-guide/05-monitoring-alerting-logging/03-alerts.md +++ b/docs/guides/reference-architecture/example-usage-guide/05-monitoring-alerting-logging/03-alerts.md @@ -20,5 +20,5 @@ module](https://github.com/gruntwork-io/terraform-aws-monitoring/tree/master/mod diff --git a/docs/guides/reference-architecture/example-usage-guide/05-monitoring-alerting-logging/04-logs.md b/docs/guides/reference-architecture/example-usage-guide/05-monitoring-alerting-logging/04-logs.md index 64e59dbbc1..4d706297f3 100644 --- a/docs/guides/reference-architecture/example-usage-guide/05-monitoring-alerting-logging/04-logs.md +++ b/docs/guides/reference-architecture/example-usage-guide/05-monitoring-alerting-logging/04-logs.md @@ -9,5 +9,5 @@ your servers in near-real-time. diff --git a/docs/guides/reference-architecture/example-usage-guide/06-adding-a-new-account/01-intro.md b/docs/guides/reference-architecture/example-usage-guide/06-adding-a-new-account/01-intro.md index 63bde52e78..3508d40cc5 100644 --- a/docs/guides/reference-architecture/example-usage-guide/06-adding-a-new-account/01-intro.md +++ b/docs/guides/reference-architecture/example-usage-guide/06-adding-a-new-account/01-intro.md @@ -15,5 +15,5 @@ need to expand the Reference Architecture with more accounts, like a test or san diff --git a/docs/guides/reference-architecture/example-usage-guide/06-adding-a-new-account/02-create-new-account-in-your-aws-org.md b/docs/guides/reference-architecture/example-usage-guide/06-adding-a-new-account/02-create-new-account-in-your-aws-org.md index c735b9c863..b70819b127 100644 --- a/docs/guides/reference-architecture/example-usage-guide/06-adding-a-new-account/02-create-new-account-in-your-aws-org.md +++ b/docs/guides/reference-architecture/example-usage-guide/06-adding-a-new-account/02-create-new-account-in-your-aws-org.md @@ -24,5 +24,5 @@ At this point, you won't need to use the root credentials again until you are re diff --git a/docs/guides/reference-architecture/example-usage-guide/06-adding-a-new-account/03-update-logs-security-shared-accounts-to-allow-cross-account-access.md b/docs/guides/reference-architecture/example-usage-guide/06-adding-a-new-account/03-update-logs-security-shared-accounts-to-allow-cross-account-access.md index a3161aa8a6..55f8de3187 100644 --- a/docs/guides/reference-architecture/example-usage-guide/06-adding-a-new-account/03-update-logs-security-shared-accounts-to-allow-cross-account-access.md +++ b/docs/guides/reference-architecture/example-usage-guide/06-adding-a-new-account/03-update-logs-security-shared-accounts-to-allow-cross-account-access.md @@ -38,5 +38,5 @@ approve it to apply the updated cross account permissions. diff --git a/docs/guides/reference-architecture/example-usage-guide/06-adding-a-new-account/04-deploy-the-security-baseline.md b/docs/guides/reference-architecture/example-usage-guide/06-adding-a-new-account/04-deploy-the-security-baseline.md index e6d6dc7450..aab1a0f75c 100644 --- a/docs/guides/reference-architecture/example-usage-guide/06-adding-a-new-account/04-deploy-the-security-baseline.md +++ b/docs/guides/reference-architecture/example-usage-guide/06-adding-a-new-account/04-deploy-the-security-baseline.md @@ -66,5 +66,5 @@ Once you confirm you have access to the new account from the `security` account, diff --git a/docs/guides/reference-architecture/example-usage-guide/06-adding-a-new-account/05-deploy-the-ecs-deploy-runner.md b/docs/guides/reference-architecture/example-usage-guide/06-adding-a-new-account/05-deploy-the-ecs-deploy-runner.md index 62dd68e5a9..1a413b4ada 100644 --- a/docs/guides/reference-architecture/example-usage-guide/06-adding-a-new-account/05-deploy-the-ecs-deploy-runner.md +++ b/docs/guides/reference-architecture/example-usage-guide/06-adding-a-new-account/05-deploy-the-ecs-deploy-runner.md @@ -37,5 +37,5 @@ to provision new infrastructure in the account. diff --git a/docs/guides/reference-architecture/example-usage-guide/07-undeploy/01-intro.md b/docs/guides/reference-architecture/example-usage-guide/07-undeploy/01-intro.md index 4adc1d9d0b..7ff96968bf 100644 --- a/docs/guides/reference-architecture/example-usage-guide/07-undeploy/01-intro.md +++ b/docs/guides/reference-architecture/example-usage-guide/07-undeploy/01-intro.md @@ -20,5 +20,5 @@ this section, we'll walk you through how to undeploy parts or all of the Referen diff --git a/docs/guides/reference-architecture/example-usage-guide/07-undeploy/02-before-you-get-started.md b/docs/guides/reference-architecture/example-usage-guide/07-undeploy/02-before-you-get-started.md index 3f1ae4b51f..079d54e77e 100644 --- a/docs/guides/reference-architecture/example-usage-guide/07-undeploy/02-before-you-get-started.md +++ b/docs/guides/reference-architecture/example-usage-guide/07-undeploy/02-before-you-get-started.md @@ -9,5 +9,5 @@ accidentally shooting yourself in the foot. diff --git a/docs/guides/reference-architecture/example-usage-guide/07-undeploy/03-pre-requisite-force-destroy-on-s3-buckets.md b/docs/guides/reference-architecture/example-usage-guide/07-undeploy/03-pre-requisite-force-destroy-on-s3-buckets.md index f6a3468d79..0ca3b77673 100644 --- a/docs/guides/reference-architecture/example-usage-guide/07-undeploy/03-pre-requisite-force-destroy-on-s3-buckets.md +++ b/docs/guides/reference-architecture/example-usage-guide/07-undeploy/03-pre-requisite-force-destroy-on-s3-buckets.md @@ -21,5 +21,5 @@ services that expose this variable (note, you may not have all of these in your diff --git a/docs/guides/reference-architecture/example-usage-guide/07-undeploy/04-pre-requisite-understand-module-dependencies.md b/docs/guides/reference-architecture/example-usage-guide/07-undeploy/04-pre-requisite-understand-module-dependencies.md index 1d7514da5d..cead4afc9c 100644 --- a/docs/guides/reference-architecture/example-usage-guide/07-undeploy/04-pre-requisite-understand-module-dependencies.md +++ b/docs/guides/reference-architecture/example-usage-guide/07-undeploy/04-pre-requisite-understand-module-dependencies.md @@ -21,5 +21,5 @@ You can check the module dependency tree with `graph-dependencies` and GraphViz: diff --git a/docs/guides/reference-architecture/example-usage-guide/07-undeploy/05-undeploying-modules-using-gruntwork-pipelines.md b/docs/guides/reference-architecture/example-usage-guide/07-undeploy/05-undeploying-modules-using-gruntwork-pipelines.md index d32bb95102..318cbf04a8 100644 --- a/docs/guides/reference-architecture/example-usage-guide/07-undeploy/05-undeploying-modules-using-gruntwork-pipelines.md +++ b/docs/guides/reference-architecture/example-usage-guide/07-undeploy/05-undeploying-modules-using-gruntwork-pipelines.md @@ -35,5 +35,5 @@ modules that have no existing downstream dependencies. diff --git a/docs/guides/reference-architecture/example-usage-guide/07-undeploy/06-manually-undeploying-a-single-module.md b/docs/guides/reference-architecture/example-usage-guide/07-undeploy/06-manually-undeploying-a-single-module.md index 3f2b1088f3..3b7cbde8b5 100644 --- a/docs/guides/reference-architecture/example-usage-guide/07-undeploy/06-manually-undeploying-a-single-module.md +++ b/docs/guides/reference-architecture/example-usage-guide/07-undeploy/06-manually-undeploying-a-single-module.md @@ -9,5 +9,5 @@ terragrunt destroy diff --git a/docs/guides/reference-architecture/example-usage-guide/07-undeploy/07-manually-undeploying-multiple-modules-or-an-entire-environment.md b/docs/guides/reference-architecture/example-usage-guide/07-undeploy/07-manually-undeploying-multiple-modules-or-an-entire-environment.md index 7d661a66a6..e6512e27ab 100644 --- a/docs/guides/reference-architecture/example-usage-guide/07-undeploy/07-manually-undeploying-multiple-modules-or-an-entire-environment.md +++ b/docs/guides/reference-architecture/example-usage-guide/07-undeploy/07-manually-undeploying-multiple-modules-or-an-entire-environment.md @@ -30,5 +30,5 @@ terragrunt destroy-all \ diff --git a/docs/guides/reference-architecture/example-usage-guide/07-undeploy/08-removing-the-terraform-state.md b/docs/guides/reference-architecture/example-usage-guide/07-undeploy/08-removing-the-terraform-state.md index 55236b9d8d..922ee3c48d 100644 --- a/docs/guides/reference-architecture/example-usage-guide/07-undeploy/08-removing-the-terraform-state.md +++ b/docs/guides/reference-architecture/example-usage-guide/07-undeploy/08-removing-the-terraform-state.md @@ -14,5 +14,5 @@ destroyed successfully**. diff --git a/docs/guides/reference-architecture/example-usage-guide/07-undeploy/09-useful-tips.md b/docs/guides/reference-architecture/example-usage-guide/07-undeploy/09-useful-tips.md index fcb4f107fb..51335f73ce 100644 --- a/docs/guides/reference-architecture/example-usage-guide/07-undeploy/09-useful-tips.md +++ b/docs/guides/reference-architecture/example-usage-guide/07-undeploy/09-useful-tips.md @@ -25,5 +25,5 @@ diff --git a/docs/guides/reference-architecture/example-usage-guide/07-undeploy/10-known-errors.md b/docs/guides/reference-architecture/example-usage-guide/07-undeploy/10-known-errors.md index 273a0162a6..68b4a93472 100644 --- a/docs/guides/reference-architecture/example-usage-guide/07-undeploy/10-known-errors.md +++ b/docs/guides/reference-architecture/example-usage-guide/07-undeploy/10-known-errors.md @@ -24,5 +24,5 @@ There are a few reasons your call to `destroy` may fail: diff --git a/docs/guides/reference-architecture/example-usage-guide/index.md b/docs/guides/reference-architecture/example-usage-guide/index.md index bae91af76d..bdd11c38e1 100644 --- a/docs/guides/reference-architecture/example-usage-guide/index.md +++ b/docs/guides/reference-architecture/example-usage-guide/index.md @@ -161,5 +161,5 @@ Next up, let's have a look at [how to authenticate](02-authenticate/01-intro.md) diff --git a/docs/guides/reference-architecture/index.md b/docs/guides/reference-architecture/index.md index fcbc039e9e..ef04d01884 100644 --- a/docs/guides/reference-architecture/index.md +++ b/docs/guides/reference-architecture/index.md @@ -24,5 +24,5 @@ See a preview of how to use your customized Reference Architecture once we've de diff --git a/docs/guides/stay-up-to-date/cis/cis-1.3.0/core-concepts.md b/docs/guides/stay-up-to-date/cis/cis-1.3.0/core-concepts.md index a98c1c6701..6b2f383057 100644 --- a/docs/guides/stay-up-to-date/cis/cis-1.3.0/core-concepts.md +++ b/docs/guides/stay-up-to-date/cis/cis-1.3.0/core-concepts.md @@ -52,5 +52,5 @@ configure the newly created modules. diff --git a/docs/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md b/docs/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md index 25f3c67691..4f62fc8ead 100644 --- a/docs/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md +++ b/docs/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md @@ -187,5 +187,5 @@ compatible with CIS AWS v1.3.0: diff --git a/docs/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/step-2-manual-steps.md b/docs/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/step-2-manual-steps.md index daa0e178b0..f175c85b2e 100644 --- a/docs/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/step-2-manual-steps.md +++ b/docs/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/step-2-manual-steps.md @@ -11,5 +11,5 @@ on the AWS website for detailed instructions. diff --git a/docs/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/step-3-deploy-new-modules.md b/docs/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/step-3-deploy-new-modules.md index 914e395266..46a2f2cee7 100644 --- a/docs/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/step-3-deploy-new-modules.md +++ b/docs/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/step-3-deploy-new-modules.md @@ -88,5 +88,5 @@ docs](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/tree/v0. diff --git a/docs/guides/stay-up-to-date/cis/cis-1.3.0/index.md b/docs/guides/stay-up-to-date/cis/cis-1.3.0/index.md index 7f1730464e..003479e328 100644 --- a/docs/guides/stay-up-to-date/cis/cis-1.3.0/index.md +++ b/docs/guides/stay-up-to-date/cis/cis-1.3.0/index.md @@ -27,5 +27,5 @@ tag is compatible with CIS AWS v1.3.0, as well as the manuals step you need to p diff --git a/docs/guides/stay-up-to-date/cis/cis-1.4.0/core-concepts.md b/docs/guides/stay-up-to-date/cis/cis-1.4.0/core-concepts.md index 2e77a6e9bd..1328ea4673 100644 --- a/docs/guides/stay-up-to-date/cis/cis-1.4.0/core-concepts.md +++ b/docs/guides/stay-up-to-date/cis/cis-1.4.0/core-concepts.md @@ -38,5 +38,5 @@ necessary manual steps. diff --git a/docs/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md b/docs/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md index 54cc2d206f..42e6c0f7f7 100644 --- a/docs/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md +++ b/docs/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md @@ -82,5 +82,5 @@ compatible with CIS AWS v1.4.0: diff --git a/docs/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-2-update-the-account-baseline-modules.md b/docs/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-2-update-the-account-baseline-modules.md index 6905cc05dd..062f803ad7 100644 --- a/docs/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-2-update-the-account-baseline-modules.md +++ b/docs/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-2-update-the-account-baseline-modules.md @@ -116,5 +116,5 @@ All the other child accounts (logs, stage, prod, etc) need the same configuratio diff --git a/docs/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-3-manual-steps.md b/docs/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-3-manual-steps.md index 505f9064ea..ead39a630a 100644 --- a/docs/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-3-manual-steps.md +++ b/docs/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-3-manual-steps.md @@ -117,5 +117,5 @@ You may be using a region that doesn’t properly support AWS Config (e.g: `ap-n diff --git a/docs/guides/stay-up-to-date/cis/cis-1.4.0/finally.md b/docs/guides/stay-up-to-date/cis/cis-1.4.0/finally.md index 31c990a655..cf190cf32c 100644 --- a/docs/guides/stay-up-to-date/cis/cis-1.4.0/finally.md +++ b/docs/guides/stay-up-to-date/cis/cis-1.4.0/finally.md @@ -8,5 +8,5 @@ If you’ve got any feedback or you think something’s missing from the guide, diff --git a/docs/guides/stay-up-to-date/cis/cis-1.4.0/index.md b/docs/guides/stay-up-to-date/cis/cis-1.4.0/index.md index 9715d14d7b..28f36fc83f 100644 --- a/docs/guides/stay-up-to-date/cis/cis-1.4.0/index.md +++ b/docs/guides/stay-up-to-date/cis/cis-1.4.0/index.md @@ -27,5 +27,5 @@ CIS AWS Foundations Benchmark. diff --git a/docs/guides/stay-up-to-date/index.md b/docs/guides/stay-up-to-date/index.md index 048fce3560..595c1d9a64 100644 --- a/docs/guides/stay-up-to-date/index.md +++ b/docs/guides/stay-up-to-date/index.md @@ -72,5 +72,5 @@ import CardGroup from "/src/components/CardGroup" diff --git a/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/core-concepts.md b/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/core-concepts.md index f520f829ce..457e02864e 100644 --- a/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/core-concepts.md +++ b/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/core-concepts.md @@ -44,5 +44,5 @@ documentation](https://terragrunt.gruntwork.io/docs/features/keep-your-terragrun diff --git a/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/intro.md b/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/intro.md index 92b758f0a1..28287534a6 100644 --- a/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/intro.md +++ b/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/intro.md @@ -41,5 +41,5 @@ include "envcommon" { diff --git a/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/optional-even-dryer-configuration.md b/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/optional-even-dryer-configuration.md index 726c0c287a..10e1b68506 100644 --- a/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/optional-even-dryer-configuration.md +++ b/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/optional-even-dryer-configuration.md @@ -182,5 +182,5 @@ the `inputs` attribute even if it references `dependency` blocks. diff --git a/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/refactoring-common-configurations-for-a-component.md b/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/refactoring-common-configurations-for-a-component.md index 1712bad226..758d9b74e1 100644 --- a/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/refactoring-common-configurations-for-a-component.md +++ b/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/refactoring-common-configurations-for-a-component.md @@ -277,5 +277,5 @@ moved to the common component configuration. diff --git a/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/update-to-the-service-catalog-based-reference-architecture.md b/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/update-to-the-service-catalog-based-reference-architecture.md index 8c34089e63..36827cd1e7 100644 --- a/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/update-to-the-service-catalog-based-reference-architecture.md +++ b/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/update-to-the-service-catalog-based-reference-architecture.md @@ -28,5 +28,5 @@ fully supported by Gruntwork. diff --git a/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/index.md b/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/index.md index 7f9a6da0d7..8ab19f9c38 100644 --- a/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/index.md +++ b/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/index.md @@ -24,5 +24,5 @@ The steps you need to take to update your code to use multi-include to avoid dup diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/core-concepts.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/core-concepts.md index da43be7cdc..9eae391aad 100644 --- a/docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/core-concepts.md +++ b/docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/core-concepts.md @@ -22,5 +22,5 @@ Architecture to be compatible with AWS provider version 3. diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/deployment-walkthrough.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/deployment-walkthrough.md index c42e7b6c3e..d70f05c2c6 100644 --- a/docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/deployment-walkthrough.md +++ b/docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/deployment-walkthrough.md @@ -182,5 +182,5 @@ on how to update your components to be compatible with AWS provider v3. diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/index.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/index.md index bac3cb6966..c8d9b464a9 100644 --- a/docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/index.md +++ b/docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/index.md @@ -29,5 +29,5 @@ which Gruntwork Repo version tag is compatible with AWS provider v3. diff --git a/docs/guides/stay-up-to-date/terraform/terraform-1.x/core-concepts.md b/docs/guides/stay-up-to-date/terraform/terraform-1.x/core-concepts.md index 8d0aeda696..5a1a6d2951 100644 --- a/docs/guides/stay-up-to-date/terraform/terraform-1.x/core-concepts.md +++ b/docs/guides/stay-up-to-date/terraform/terraform-1.x/core-concepts.md @@ -21,5 +21,5 @@ notes](https://github.com/hashicorp/terraform/releases/tag/v1.0.0): diff --git a/docs/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-15.md b/docs/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-15.md index 9675f3226f..ba600f902b 100644 --- a/docs/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-15.md +++ b/docs/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-15.md @@ -27,5 +27,5 @@ If you haven’t already, you need to: diff --git a/docs/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md b/docs/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md index d92cc93a1f..2abff574e1 100644 --- a/docs/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md +++ b/docs/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md @@ -174,5 +174,5 @@ and the respective versions that are compatible with Terraform 1.x: diff --git a/docs/guides/stay-up-to-date/terraform/terraform-1.x/index.md b/docs/guides/stay-up-to-date/terraform/terraform-1.x/index.md index dfe3407fa8..396ce6bd0f 100644 --- a/docs/guides/stay-up-to-date/terraform/terraform-1.x/index.md +++ b/docs/guides/stay-up-to-date/terraform/terraform-1.x/index.md @@ -29,5 +29,5 @@ tag is compatible with Terraform 0.15. diff --git a/docs/guides/stay-up-to-date/terraform/terraform-12/deployment-walkthrough.md b/docs/guides/stay-up-to-date/terraform/terraform-12/deployment-walkthrough.md index 19848de4d5..0b54f139c3 100644 --- a/docs/guides/stay-up-to-date/terraform/terraform-12/deployment-walkthrough.md +++ b/docs/guides/stay-up-to-date/terraform/terraform-12/deployment-walkthrough.md @@ -430,5 +430,5 @@ At the end of this, you should be able to run `terragrunt plan` cleanly. diff --git a/docs/guides/stay-up-to-date/terraform/terraform-12/index.md b/docs/guides/stay-up-to-date/terraform/terraform-12/index.md index c3b084c488..5b98718ce9 100644 --- a/docs/guides/stay-up-to-date/terraform/terraform-12/index.md +++ b/docs/guides/stay-up-to-date/terraform/terraform-12/index.md @@ -34,5 +34,5 @@ This means that both the modules and the live config need to be updated in order diff --git a/docs/guides/stay-up-to-date/terraform/terraform-12/version-compatibility-table.md b/docs/guides/stay-up-to-date/terraform/terraform-12/version-compatibility-table.md index b8b6390e1c..f356f417f8 100644 --- a/docs/guides/stay-up-to-date/terraform/terraform-12/version-compatibility-table.md +++ b/docs/guides/stay-up-to-date/terraform/terraform-12/version-compatibility-table.md @@ -41,5 +41,5 @@ The following lists our Terraform packages and their compatibility with Terrafor diff --git a/docs/guides/stay-up-to-date/terraform/terraform-13/core-concepts.md b/docs/guides/stay-up-to-date/terraform/terraform-13/core-concepts.md index b4d950d5eb..65e529f74a 100644 --- a/docs/guides/stay-up-to-date/terraform/terraform-13/core-concepts.md +++ b/docs/guides/stay-up-to-date/terraform/terraform-13/core-concepts.md @@ -18,5 +18,5 @@ update to these new versions and make other changes to your code, as described i diff --git a/docs/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12.md b/docs/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12.md index 9cd776dc57..92f8a76781 100644 --- a/docs/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12.md +++ b/docs/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12.md @@ -16,5 +16,5 @@ If you haven’t already, you need to: diff --git a/docs/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-13.md b/docs/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-13.md index 0b09996e3b..f2a4db753e 100644 --- a/docs/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-13.md +++ b/docs/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-13.md @@ -10,5 +10,5 @@ Upgrade Guide](https://www.terraform.io/upgrade-guides/0-13.html). diff --git a/docs/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md b/docs/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md index c5d07e9354..56cef67429 100644 --- a/docs/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md +++ b/docs/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md @@ -171,5 +171,5 @@ compatible with Terraform 0.13: diff --git a/docs/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/updating-the-gruntwork-reference-architecture-to-terraform-0-13.md b/docs/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/updating-the-gruntwork-reference-architecture-to-terraform-0-13.md index b09dceb146..0f4e0662f7 100644 --- a/docs/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/updating-the-gruntwork-reference-architecture-to-terraform-0-13.md +++ b/docs/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/updating-the-gruntwork-reference-architecture-to-terraform-0-13.md @@ -40,5 +40,5 @@ refer to PRs in the Standard Reference Architecture section above. diff --git a/docs/guides/stay-up-to-date/terraform/terraform-13/index.md b/docs/guides/stay-up-to-date/terraform/terraform-13/index.md index 1e2814f01e..4b64d28776 100644 --- a/docs/guides/stay-up-to-date/terraform/terraform-13/index.md +++ b/docs/guides/stay-up-to-date/terraform/terraform-13/index.md @@ -27,5 +27,5 @@ tag is compatible with Terraform 0.13. diff --git a/docs/guides/stay-up-to-date/terraform/terraform-14/core-concepts.md b/docs/guides/stay-up-to-date/terraform/terraform-14/core-concepts.md index 7045c84864..586cf3b66f 100644 --- a/docs/guides/stay-up-to-date/terraform/terraform-14/core-concepts.md +++ b/docs/guides/stay-up-to-date/terraform/terraform-14/core-concepts.md @@ -19,5 +19,5 @@ update to these new versions and make other changes to your code, as described i diff --git a/docs/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-13.md b/docs/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-13.md index d50a611fe8..eeff12085c 100644 --- a/docs/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-13.md +++ b/docs/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-13.md @@ -21,5 +21,5 @@ If you haven’t already, you need to: diff --git a/docs/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-14.md b/docs/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-14.md index ac5caeaa44..0a66aeccf9 100644 --- a/docs/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-14.md +++ b/docs/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-14.md @@ -10,5 +10,5 @@ Upgrade Guide](https://www.terraform.io/upgrade-guides/0-14.html). diff --git a/docs/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md b/docs/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md index 98165e10be..17e69350d6 100644 --- a/docs/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md +++ b/docs/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md @@ -170,5 +170,5 @@ compatible with Terraform 0.14: diff --git a/docs/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-4-start-using-lock-files.md b/docs/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-4-start-using-lock-files.md index 325bc7d4f0..c45c84b805 100644 --- a/docs/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-4-start-using-lock-files.md +++ b/docs/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-4-start-using-lock-files.md @@ -17,5 +17,5 @@ to version control. diff --git a/docs/guides/stay-up-to-date/terraform/terraform-14/index.md b/docs/guides/stay-up-to-date/terraform/terraform-14/index.md index 948acb7301..35c0de46ea 100644 --- a/docs/guides/stay-up-to-date/terraform/terraform-14/index.md +++ b/docs/guides/stay-up-to-date/terraform/terraform-14/index.md @@ -28,5 +28,5 @@ tag is compatible with Terraform 0.14. diff --git a/docs/guides/stay-up-to-date/terraform/terraform-15/core-concepts.md b/docs/guides/stay-up-to-date/terraform/terraform-15/core-concepts.md index eae857644e..ed3a693438 100644 --- a/docs/guides/stay-up-to-date/terraform/terraform-15/core-concepts.md +++ b/docs/guides/stay-up-to-date/terraform/terraform-15/core-concepts.md @@ -27,5 +27,5 @@ following section. diff --git a/docs/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-14.md b/docs/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-14.md index ea7865c4d6..323b1c1cf1 100644 --- a/docs/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-14.md +++ b/docs/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-14.md @@ -24,5 +24,5 @@ If you haven’t already, you need to: diff --git a/docs/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-15.md b/docs/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-15.md index 65d2b346bd..4b8bba7ec0 100644 --- a/docs/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-15.md +++ b/docs/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-15.md @@ -10,5 +10,5 @@ Upgrade Guide](https://www.terraform.io/upgrade-guides/0-15.html). diff --git a/docs/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md b/docs/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md index 19a1edc7d5..f228cefa8d 100644 --- a/docs/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md +++ b/docs/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md @@ -170,5 +170,5 @@ compatible with Terraform 0.15: diff --git a/docs/guides/stay-up-to-date/terraform/terraform-15/index.md b/docs/guides/stay-up-to-date/terraform/terraform-15/index.md index 7d3395da1a..bcc4dd190d 100644 --- a/docs/guides/stay-up-to-date/terraform/terraform-15/index.md +++ b/docs/guides/stay-up-to-date/terraform/terraform-15/index.md @@ -30,5 +30,5 @@ compatible with Terraform 0.15. diff --git a/docs/guides/style/golang-style-guide.md b/docs/guides/style/golang-style-guide.md index f4d9986560..d23a3feb54 100644 --- a/docs/guides/style/golang-style-guide.md +++ b/docs/guides/style/golang-style-guide.md @@ -262,5 +262,5 @@ suffix `E` return an error as the last return value; methods without `E` mark th diff --git a/docs/guides/style/index.md b/docs/guides/style/index.md index d77e5786fc..195064b94f 100644 --- a/docs/guides/style/index.md +++ b/docs/guides/style/index.md @@ -20,5 +20,5 @@ Learn Gruntwork's Go coding style. diff --git a/docs/guides/style/terraform-style-guide.md b/docs/guides/style/terraform-style-guide.md index 74c93d2b39..3933d092e7 100644 --- a/docs/guides/style/terraform-style-guide.md +++ b/docs/guides/style/terraform-style-guide.md @@ -395,5 +395,5 @@ func TestECS(t *testing.T) { diff --git a/docs/guides/support.mdx b/docs/guides/support.mdx index bf6c9b6dca..67a00f8f56 100644 --- a/docs/guides/support.mdx +++ b/docs/guides/support.mdx @@ -184,5 +184,5 @@ Looking for more personalized assistance using a particular Gruntwork product? O diff --git a/docs/guides/working-with-code/contributing.md b/docs/guides/working-with-code/contributing.md index ec91c2ac0f..5ed140d690 100644 --- a/docs/guides/working-with-code/contributing.md +++ b/docs/guides/working-with-code/contributing.md @@ -52,5 +52,5 @@ code and release a new version. diff --git a/docs/guides/working-with-code/forking.md b/docs/guides/working-with-code/forking.md index 09ea9501cb..738eed7157 100644 --- a/docs/guides/working-with-code/forking.md +++ b/docs/guides/working-with-code/forking.md @@ -56,5 +56,5 @@ bans all outside sources, then follow the instructions above to fork the code, a diff --git a/docs/guides/working-with-code/versioning.md b/docs/guides/working-with-code/versioning.md index 3f9c9aaf22..3f25d72212 100644 --- a/docs/guides/working-with-code/versioning.md +++ b/docs/guides/working-with-code/versioning.md @@ -68,5 +68,5 @@ Follow the steps below to keep your code up to date: diff --git a/docs/intro.md b/docs/intro.md index f1d8af6916..b91ecf7a07 100644 --- a/docs/intro.md +++ b/docs/intro.md @@ -36,5 +36,5 @@ Open `docs/intro.md` and edit some lines: the site **reloads automatically** and diff --git a/docs/intro/core-concepts/immutable-infrastructure.md b/docs/intro/core-concepts/immutable-infrastructure.md index 69c8db9074..3fd4ca65d5 100644 --- a/docs/intro/core-concepts/immutable-infrastructure.md +++ b/docs/intro/core-concepts/immutable-infrastructure.md @@ -35,5 +35,5 @@ longer work, e.g., if certain packages have been removed from APT or YUM). diff --git a/docs/intro/core-concepts/infrastructure-as-code.md b/docs/intro/core-concepts/infrastructure-as-code.md index 4f9029d9a9..6fc545b01e 100644 --- a/docs/intro/core-concepts/infrastructure-as-code.md +++ b/docs/intro/core-concepts/infrastructure-as-code.md @@ -60,5 +60,5 @@ Packer, Docker, and Helm, each of which we’ll discuss in the next several sect diff --git a/docs/intro/core-concepts/production-framework.md b/docs/intro/core-concepts/production-framework.md index f83f2444a4..0db2ce6d58 100644 --- a/docs/intro/core-concepts/production-framework.md +++ b/docs/intro/core-concepts/production-framework.md @@ -16,5 +16,5 @@ Guide](/docs/guides/production-framework) for the full details. diff --git a/docs/intro/dev-portal/create-account.md b/docs/intro/dev-portal/create-account.md index 4c4f64499a..54e27b66da 100644 --- a/docs/intro/dev-portal/create-account.md +++ b/docs/intro/dev-portal/create-account.md @@ -33,5 +33,5 @@ If you are the admin for your organization, you'll be prompted to confirm detail diff --git a/docs/intro/dev-portal/invite-team.md b/docs/intro/dev-portal/invite-team.md index 3f44c217f6..3589a5fc17 100644 --- a/docs/intro/dev-portal/invite-team.md +++ b/docs/intro/dev-portal/invite-team.md @@ -42,5 +42,5 @@ The number of licenses available depends on the level of your subscription. You diff --git a/docs/intro/dev-portal/link-github-id.md b/docs/intro/dev-portal/link-github-id.md index 5947065dc4..b75d3a59fc 100644 --- a/docs/intro/dev-portal/link-github-id.md +++ b/docs/intro/dev-portal/link-github-id.md @@ -24,5 +24,5 @@ To link a new GitHub ID, you’ll first have to unlink the current one. Although diff --git a/docs/intro/environment-setup/recommended_tools.md b/docs/intro/environment-setup/recommended_tools.md index cbd5692134..fb3167c351 100644 --- a/docs/intro/environment-setup/recommended_tools.md +++ b/docs/intro/environment-setup/recommended_tools.md @@ -86,5 +86,5 @@ docker run -it -v $(pwd):/work gruntwork /bin/bash diff --git a/docs/intro/first-deployment/deploy.md b/docs/intro/first-deployment/deploy.md index ca0f916a31..6a59c90bd9 100644 --- a/docs/intro/first-deployment/deploy.md +++ b/docs/intro/first-deployment/deploy.md @@ -261,5 +261,5 @@ terragrunt apply-all diff --git a/docs/intro/first-deployment/testing.md b/docs/intro/first-deployment/testing.md index fec4f08aea..9f3f832bc6 100644 --- a/docs/intro/first-deployment/testing.md +++ b/docs/intro/first-deployment/testing.md @@ -213,5 +213,5 @@ For a lot more information on writing automated tests for Terraform code, see: diff --git a/docs/intro/first-deployment/using-terraform-modules.md b/docs/intro/first-deployment/using-terraform-modules.md index 3b77cb22ce..ec120eaeeb 100644 --- a/docs/intro/first-deployment/using-terraform-modules.md +++ b/docs/intro/first-deployment/using-terraform-modules.md @@ -248,5 +248,5 @@ output "private_persistence_subnet_ids" { diff --git a/docs/intro/next-steps.mdx b/docs/intro/next-steps.mdx index 7dc372b762..2649b92330 100644 --- a/docs/intro/next-steps.mdx +++ b/docs/intro/next-steps.mdx @@ -28,5 +28,5 @@ Now that your foundational knowledge is in place and your workspace is configure diff --git a/docs/intro/overview/getting-started.mdx b/docs/intro/overview/getting-started.mdx index 1e742496e9..042deef0cd 100644 --- a/docs/intro/overview/getting-started.mdx +++ b/docs/intro/overview/getting-started.mdx @@ -30,5 +30,5 @@ In this introductory guide we’ll cover the fundamentals you'll need in order t diff --git a/docs/intro/overview/gruntwork-production-framework.md b/docs/intro/overview/gruntwork-production-framework.md index f102bf02bd..372e2677e8 100644 --- a/docs/intro/overview/gruntwork-production-framework.md +++ b/docs/intro/overview/gruntwork-production-framework.md @@ -33,5 +33,5 @@ This is an overloaded term, so let's dive into the details of what we mean by a diff --git a/docs/intro/overview/gruntwork-vs-other.md b/docs/intro/overview/gruntwork-vs-other.md index e0629845e1..2649671950 100644 --- a/docs/intro/overview/gruntwork-vs-other.md +++ b/docs/intro/overview/gruntwork-vs-other.md @@ -2,5 +2,5 @@ diff --git a/docs/intro/overview/how-it-works.md b/docs/intro/overview/how-it-works.md index cfd7d89e02..5aeddff74d 100644 --- a/docs/intro/overview/how-it-works.md +++ b/docs/intro/overview/how-it-works.md @@ -55,5 +55,5 @@ Gruntwork products strike a balance between opinionatedness and configurability. diff --git a/docs/intro/overview/intro-to-gruntwork.md b/docs/intro/overview/intro-to-gruntwork.md index b5bcb8a05f..eaf8369f6d 100644 --- a/docs/intro/overview/intro-to-gruntwork.md +++ b/docs/intro/overview/intro-to-gruntwork.md @@ -18,5 +18,5 @@ All Gruntwork products are built on and fully compatible with [open source Terra diff --git a/docs/intro/overview/use-cases.md b/docs/intro/overview/use-cases.md index 97a5669076..e6994bdd82 100644 --- a/docs/intro/overview/use-cases.md +++ b/docs/intro/overview/use-cases.md @@ -2,5 +2,5 @@ diff --git a/docs/intro/tool-fundamentals/docker.md b/docs/intro/tool-fundamentals/docker.md index 227a2ad2f0..312084da82 100644 --- a/docs/intro/tool-fundamentals/docker.md +++ b/docs/intro/tool-fundamentals/docker.md @@ -21,5 +21,5 @@ Nomad that you can use to deploy and manage Docker images. diff --git a/docs/intro/tool-fundamentals/packer.md b/docs/intro/tool-fundamentals/packer.md index f043798a8e..856fca5936 100644 --- a/docs/intro/tool-fundamentals/packer.md +++ b/docs/intro/tool-fundamentals/packer.md @@ -52,5 +52,5 @@ its opinionated tools. diff --git a/docs/intro/tool-fundamentals/terraform.md b/docs/intro/tool-fundamentals/terraform.md index 18827e2317..f0a7c41f89 100644 --- a/docs/intro/tool-fundamentals/terraform.md +++ b/docs/intro/tool-fundamentals/terraform.md @@ -39,5 +39,5 @@ The Gruntwork module library and open source tools are compatible with Terraform diff --git a/docs/intro/tool-fundamentals/terragrunt.md b/docs/intro/tool-fundamentals/terragrunt.md index d5b8fc8890..2f78c44892 100644 --- a/docs/intro/tool-fundamentals/terragrunt.md +++ b/docs/intro/tool-fundamentals/terragrunt.md @@ -35,5 +35,5 @@ Infrastructure as Code Library with plain Terraform, Terraform Enterprise, Atlan diff --git a/docs/reference/intro.md b/docs/reference/intro.md index 5c7c1caa41..4e6f0a644a 100644 --- a/docs/reference/intro.md +++ b/docs/reference/intro.md @@ -8,5 +8,5 @@ This section introduces what's found in the reference area. diff --git a/docs/reference/modules/stub.md b/docs/reference/modules/stub.md index dc22c48297..ac45da3b34 100644 --- a/docs/reference/modules/stub.md +++ b/docs/reference/modules/stub.md @@ -6,5 +6,5 @@ diff --git a/docs/reference/services/app-orchestration/amazon-ecs-cluster.md b/docs/reference/services/app-orchestration/amazon-ecs-cluster.md index 656386a221..8e6f3db053 100644 --- a/docs/reference/services/app-orchestration/amazon-ecs-cluster.md +++ b/docs/reference/services/app-orchestration/amazon-ecs-cluster.md @@ -48,10 +48,22 @@ Deploy an Amazon ECS Cluster * [**`cloud_init_parts`**](#cloud_init_parts) — Cloud init scripts to run on the ECS cluster instances during boot. See the part blocks in [`https://www.terraform.io/docs/providers/template/d/cloudinit_config`](#https://www.terraform.io/docs/providers/template/d/cloudinit_config).html for syntax + + +* [**`cloudwatch_log_group_kms_key_id`**](#cloudwatch_log_group_kms_key_id) — The ID (ARN, alias ARN, AWS ID) of a customer managed KMS Key to use for encrypting log data. + * [**`cloudwatch_log_group_name`**](#cloudwatch_log_group_name) — The name of the log group to create in CloudWatch. Defaults to [``var.cluster_name`](#`var.cluster_name)-logs`. + + +* [**`cloudwatch_log_group_retention_in_days`**](#cloudwatch_log_group_retention_in_days) — The number of days to retain log events in the log group. Refer to [`https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudwatch_log_group#retention_in_days`](#https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudwatch_log_group#retention_in_days) for all the valid values. When null, the log events are retained forever. + + + +* [**`cloudwatch_log_group_tags`**](#cloudwatch_log_group_tags) — Tags to apply on the CloudWatch Log Group, encoded as a map where the keys are tag keys and values are tag values. + * [**`cluster_access_from_sgs`**](#cluster_access_from_sgs) — Specify a list of Security Groups that will have access to the ECS cluster. Only used if [`enable_cluster_access_ports`](#enable_cluster_access_ports) is set to true @@ -180,6 +192,10 @@ Deploy an Amazon ECS Cluster * [**`public_alb_sg_ids`**](#public_alb_sg_ids) — The Security Group ID for the public ALB + + +* [**`should_create_cloudwatch_log_group`**](#should_create_cloudwatch_log_group) — When true, precreate the CloudWatch Log Group to use for log aggregation from the EC2 instances. This is useful if you wish to customize the CloudWatch Log Group with various settings such as retention periods and KMS encryption. When false, the CloudWatch agent will automatically create a basic log group to use. + * [**`ssh_grunt_iam_group`**](#ssh_grunt_iam_group) — If you are using ssh-grunt, this is the name of the IAM group from which users will be allowed to SSH to the nodes in this ECS cluster. This value is only used if [`enable_ssh_grunt`](#enable_ssh_grunt)=true. @@ -268,5 +284,5 @@ Deploy an Amazon ECS Cluster diff --git a/docs/reference/services/app-orchestration/amazon-ecs-fargate-cluster.md b/docs/reference/services/app-orchestration/amazon-ecs-fargate-cluster.md index fcc925b953..4ede36b85a 100644 --- a/docs/reference/services/app-orchestration/amazon-ecs-fargate-cluster.md +++ b/docs/reference/services/app-orchestration/amazon-ecs-fargate-cluster.md @@ -40,5 +40,5 @@ Deploy an Amazon ECS Cluster optimized for Fargate only usage. diff --git a/docs/reference/services/app-orchestration/amazon-ecs-service.md b/docs/reference/services/app-orchestration/amazon-ecs-service.md index fce14890d6..86c37472df 100644 --- a/docs/reference/services/app-orchestration/amazon-ecs-service.md +++ b/docs/reference/services/app-orchestration/amazon-ecs-service.md @@ -52,9 +52,17 @@ Deploy an Amazon ECS Service * [**`clb_name`**](#clb_name) — The name of a Classic Load Balancer (CLB) to associate with this service. Containers in the service will automatically register with the CLB when booting up. Set to null if using ELBv2. + + +* [**`cloudwatch_log_group_kms_key_id`**](#cloudwatch_log_group_kms_key_id) — The ARN of a KMS CMK to use for encrypting log events in the CloudWatch Logs. Set to null to disable encryption. Only used if [`create_cloudwatch_log_group`](#create_cloudwatch_log_group) is true. + -* [**`cloudwatch_log_group_name`**](#cloudwatch_log_group_name) — The name for the Cloudwatch logs that will be generated by the ecs service +* [**`cloudwatch_log_group_name`**](#cloudwatch_log_group_name) — The name for the Cloudwatch logs that will be generated by the ecs service. Only used (and required) if [`create_cloudwatch_log_group`](#create_cloudwatch_log_group) is true. + + + +* [**`cloudwatch_log_group_retention`**](#cloudwatch_log_group_retention) — Number of days to retain log events. Possible values are: 1, 3, 5, 7, 14, 30, 60, 90, 120, 150, 180, 365, 400, 545, 731, 1827, 3653, and 0. Select 0 to never expire. Only used if [`create_cloudwatch_log_group`](#create_cloudwatch_log_group) is true. @@ -64,6 +72,10 @@ Deploy an Amazon ECS Service * [**`cpu`**](#cpu) — The number of CPU units to allocate to the ECS Service. + + +* [**`create_cloudwatch_log_group`**](#create_cloudwatch_log_group) — When true, create and manage the CloudWatch Log Group in the Terraform module instead of relying on ECS. This is useful for configuring options that are not available in the ECS native feature of managing the Log Group (e.g., encryption support). + * [**`create_route53_entry`**](#create_route53_entry) — Set to true if you want a DNS record automatically created and pointed at the the load balancer for the ECS service @@ -472,5 +484,5 @@ Deploy an Amazon ECS Service diff --git a/docs/reference/services/app-orchestration/amazon-eks-core-services.md b/docs/reference/services/app-orchestration/amazon-eks-core-services.md index 45e583ef2d..26d94c68d6 100644 --- a/docs/reference/services/app-orchestration/amazon-eks-core-services.md +++ b/docs/reference/services/app-orchestration/amazon-eks-core-services.md @@ -50,7 +50,7 @@ Deploy core administrative applications on top of Amazon EC2 Kubernetes Service -* [**`cluster_autoscaler_pod_resources`**](#cluster_autoscaler_pod_resources) — Pod resource requests and limits to use. Refer to https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ for more information. +* [**`cluster_autoscaler_pod_resources`**](#cluster_autoscaler_pod_resources) — Pod resource requests and limits to use. Refer to https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ for more information. This is most useful for configuring CPU+Memory availability for Fargate, which defaults to 0.25 vCPU and 256MB RAM. @@ -156,6 +156,10 @@ Deploy core administrative applications on top of Amazon EC2 Kubernetes Service * [**`fluent_bit_log_group_already_exists`**](#fluent_bit_log_group_already_exists) — If set to true, that means that the CloudWatch Log Group fluent-bit should use for streaming logs already exists and does not need to be created. + + +* [**`fluent_bit_log_group_kms_key_id`**](#fluent_bit_log_group_kms_key_id) — The ARN of the KMS key to use to encrypt the logs in the CloudWatch Log Group used for storing container logs streamed with FluentBit. Set to null to disable encryption. + * [**`fluent_bit_log_group_name`**](#fluent_bit_log_group_name) — Name of the CloudWatch Log Group fluent-bit should use to stream logs to. When null (default), uses the [`eks_cluster_name`](#eks_cluster_name) as the Log Group name. @@ -228,5 +232,5 @@ Deploy core administrative applications on top of Amazon EC2 Kubernetes Service diff --git a/docs/reference/services/app-orchestration/amazon-eks-workers.md b/docs/reference/services/app-orchestration/amazon-eks-workers.md index 127a2a3a32..db214f1f2d 100644 --- a/docs/reference/services/app-orchestration/amazon-eks-workers.md +++ b/docs/reference/services/app-orchestration/amazon-eks-workers.md @@ -352,5 +352,5 @@ Deploy EC2 instances as Kubernetes workers for Amazon Elastic Kubernetes Service diff --git a/docs/reference/services/app-orchestration/amazon-eks.md b/docs/reference/services/app-orchestration/amazon-eks.md index 30c679dd4f..d020e40f03 100644 --- a/docs/reference/services/app-orchestration/amazon-eks.md +++ b/docs/reference/services/app-orchestration/amazon-eks.md @@ -456,5 +456,5 @@ Deploy Kubernetes on top of Amazon Elastic Kubernetes Service (EKS) diff --git a/docs/reference/services/app-orchestration/auto-scaling-group-asg.md b/docs/reference/services/app-orchestration/auto-scaling-group-asg.md index 3eedddd6c1..0e22d43a2f 100644 --- a/docs/reference/services/app-orchestration/auto-scaling-group-asg.md +++ b/docs/reference/services/app-orchestration/auto-scaling-group-asg.md @@ -48,6 +48,18 @@ Deploy an AMI across an Auto Scaling Group (ASG), with support for zero-downtime * [**`cloud_init_parts`**](#cloud_init_parts) — Cloud init scripts to run on the ASG instances during boot. See the part blocks in [`https://www.terraform.io/docs/providers/template/d/cloudinit_config`](#https://www.terraform.io/docs/providers/template/d/cloudinit_config).html for syntax + + +* [**`cloudwatch_log_group_kms_key_id`**](#cloudwatch_log_group_kms_key_id) — The ID (ARN, alias ARN, AWS ID) of a customer managed KMS Key to use for encrypting log data. + + + +* [**`cloudwatch_log_group_retention_in_days`**](#cloudwatch_log_group_retention_in_days) — The number of days to retain log events in the log group. Refer to [`https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudwatch_log_group#retention_in_days`](#https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudwatch_log_group#retention_in_days) for all the valid values. When null, the log events are retained forever. + + + +* [**`cloudwatch_log_group_tags`**](#cloudwatch_log_group_tags) — Tags to apply on the CloudWatch Log Group, encoded as a map where the keys are tag keys and values are tag values. + * [**`create_route53_entry`**](#create_route53_entry) — Set to true to create a DNS A record in Route 53 for this service. @@ -184,6 +196,10 @@ Deploy an AMI across an Auto Scaling Group (ASG), with support for zero-downtime * [**`server_ports`**](#server_ports) — The ports the EC2 instances listen on for requests. A Target Group will be created for each port and any rules specified in [`forward_rules`](#forward_rules) will forward traffic to these Target Groups. + + +* [**`should_create_cloudwatch_log_group`**](#should_create_cloudwatch_log_group) — When true, precreate the CloudWatch Log Group to use for log aggregation from the EC2 instances. This is useful if you wish to customize the CloudWatch Log Group with various settings such as retention periods and KMS encryption. When false, the CloudWatch agent will automatically create a basic log group to use. + * [**`ssh_grunt_iam_group`**](#ssh_grunt_iam_group) — If you are using ssh-grunt, this is the name of the IAM group from which users will be allowed to SSH to the instances. To omit this variable, set it to an empty string (do NOT use null, or Terraform will complain). @@ -264,5 +280,5 @@ Deploy an AMI across an Auto Scaling Group (ASG), with support for zero-downtime diff --git a/docs/reference/services/app-orchestration/ec-2-instance.md b/docs/reference/services/app-orchestration/ec-2-instance.md index abf042bb49..c2a3f39110 100644 --- a/docs/reference/services/app-orchestration/ec-2-instance.md +++ b/docs/reference/services/app-orchestration/ec-2-instance.md @@ -56,6 +56,18 @@ Deploy an EC2 Instance, including server hardening, IAM role, EIP, EBS Volume, a * [**`cloud_init_parts`**](#cloud_init_parts) — Cloud init scripts to run on the EC2 instance while it boots. See the part blocks in [`https://www.terraform.io/docs/providers/template/d/cloudinit_config`](#https://www.terraform.io/docs/providers/template/d/cloudinit_config).html for syntax. + + +* [**`cloudwatch_log_group_kms_key_id`**](#cloudwatch_log_group_kms_key_id) — The ID (ARN, alias ARN, AWS ID) of a customer managed KMS Key to use for encrypting log data. + + + +* [**`cloudwatch_log_group_retention_in_days`**](#cloudwatch_log_group_retention_in_days) — The number of days to retain log events in the log group. Refer to [`https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudwatch_log_group#retention_in_days`](#https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudwatch_log_group#retention_in_days) for all the valid values. When null, the log events are retained forever. + + + +* [**`cloudwatch_log_group_tags`**](#cloudwatch_log_group_tags) — Tags to apply on the CloudWatch Log Group, encoded as a map where the keys are tag keys and values are tag values. + * [**`create_dns_record`**](#create_dns_record) — Set to true to create a DNS record in Route53 pointing to the EC2 instance. If true, be sure to set [`fully_qualified_domain_name`](#fully_qualified_domain_name). @@ -140,6 +152,10 @@ Deploy an EC2 Instance, including server hardening, IAM role, EIP, EBS Volume, a * [**`route53_zone_id`**](#route53_zone_id) — The ID of the hosted zone to use. Allows specifying the hosted zone directly instead of looking it up via domain name. Only one of [`route53_lookup_domain_name`](#route53_lookup_domain_name) or [`route53_zone_id`](#route53_zone_id) should be used. + + +* [**`should_create_cloudwatch_log_group`**](#should_create_cloudwatch_log_group) — When true, precreate the CloudWatch Log Group to use for log aggregation from the EC2 instances. This is useful if you wish to customize the CloudWatch Log Group with various settings such as retention periods and KMS encryption. When false, the CloudWatch agent will automatically create a basic log group to use. + * [**`ssh_grunt_iam_group`**](#ssh_grunt_iam_group) — If you are using ssh-grunt, this is the name of the IAM group from which users will be allowed to SSH to this EC2 instance. To omit this variable, set it to an empty string (do NOT use null, or Terraform will complain). @@ -175,6 +191,14 @@ Deploy an EC2 Instance, including server hardening, IAM role, EIP, EBS Volume, a * [**`ec2_instance_iam_role_arn`**](#ec2_instance_iam_role_arn) — The ARN of the EC2 server's IAM role. + + +* [**`ec2_instance_iam_role_id`**](#ec2_instance_iam_role_id) — The ID of the EC2 server's IAM role. + + + +* [**`ec2_instance_iam_role_name`**](#ec2_instance_iam_role_name) — The name of the EC2 server's IAM role. + * [**`ec2_instance_instance_id`**](#ec2_instance_instance_id) — The EC2 instance ID of the EC2 server. @@ -204,5 +228,5 @@ Deploy an EC2 Instance, including server hardening, IAM role, EIP, EBS Volume, a diff --git a/docs/reference/services/app-orchestration/kubernetes-namespace.md b/docs/reference/services/app-orchestration/kubernetes-namespace.md index 4a2543fd4f..15476111be 100644 --- a/docs/reference/services/app-orchestration/kubernetes-namespace.md +++ b/docs/reference/services/app-orchestration/kubernetes-namespace.md @@ -68,5 +68,5 @@ Provision a best practices Kubernetes Namespace on any Kubernetes Cluster. diff --git a/docs/reference/services/app-orchestration/kubernetes-service.md b/docs/reference/services/app-orchestration/kubernetes-service.md index d60f116b60..139f1b815b 100644 --- a/docs/reference/services/app-orchestration/kubernetes-service.md +++ b/docs/reference/services/app-orchestration/kubernetes-service.md @@ -30,7 +30,7 @@ Deploy your application containers as a Kubernetes Service and Deployment follow -* [**`alb_health_check_port`**](#alb_health_check_port) — String value specifying the port that the ALB health check should probe. By default, this will be set to the traffic port. +* [**`alb_health_check_port`**](#alb_health_check_port) — String value specifying the port that the ALB health check should probe. By default, this will be set to the traffic port (the NodePort or port where the service receives traffic). This can also be set to a Kubernetes named port, or direct integer value. See https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.3/guide/ingress/annotations/#healthcheck-port for more information. @@ -116,6 +116,10 @@ Deploy your application containers as a Kubernetes Service and Deployment follow * [**`force_destroy_ingress_access_logs`**](#force_destroy_ingress_access_logs) — A boolean that indicates whether the access logs bucket should be destroyed, even if there are files in it, when you run Terraform destroy. Unless you are using this bucket only for test purposes, you'll want to leave this variable set to false. + + +* [**`helm_chart_version`**](#helm_chart_version) — The version of the k8s-service helm chart to deploy. + * [**`horizontal_pod_autoscaler`**](#horizontal_pod_autoscaler) — Configure the Horizontal Pod Autoscaler information for the associated Deployment. HPA is disabled when this variable is set to null. @@ -166,12 +170,20 @@ Deploy your application containers as a Kubernetes Service and Deployment follow -* [**`ingress_path`**](#ingress_path) — Path prefix that should be matched to route to the service. Use /* to match all paths. +* [**`ingress_path`**](#ingress_path) — Path prefix that should be matched to route to the service. For Kubernetes Versions <1.19, Use /* to match all paths. For Kubernetes Versions >=1.19, use / with [`ingress_path_type`](#ingress_path_type) set to Prefix to match all paths. + + + +* [**`ingress_path_type`**](#ingress_path_type) — The path type to use for the ingress rule. Refer to https://kubernetes.io/docs/concepts/services-networking/ingress/#path-types for more information. * [**`ingress_ssl_redirect_rule_already_exists`**](#ingress_ssl_redirect_rule_already_exists) — Set to true if the Ingress SSL redirect rule is managed externally. This is useful when configuring Ingress grouping and you only want one service to be managing the SSL redirect rules. Only used if [`ingress_configure_ssl_redirect`](#ingress_configure_ssl_redirect) is true. + + +* [**`ingress_ssl_redirect_rule_requires_path_type`**](#ingress_ssl_redirect_rule_requires_path_type) — Whether or not the redirect rule requires setting path type. Set to true when deploying to Kubernetes clusters with version >=1.19. Only used if [`ingress_configure_ssl_redirect`](#ingress_configure_ssl_redirect) is true. + * [**`ingress_target_type`**](#ingress_target_type) — Controls how the ALB routes traffic to the Pods. Supports 'instance' mode (route traffic to NodePort and load balance across all worker nodes, relying on Kubernetes Service networking to route to the pods), or 'ip' mode (route traffic directly to the pod IP - only works with AWS VPC CNI). Must be set to 'ip' if using Fargate. Only used if [`expose_type`](#expose_type) is not cluster-internal. @@ -290,5 +302,5 @@ Deploy your application containers as a Kubernetes Service and Deployment follow diff --git a/docs/reference/services/app-orchestration/lambda.md b/docs/reference/services/app-orchestration/lambda.md index 8be0c7fadf..0a83c8244a 100644 --- a/docs/reference/services/app-orchestration/lambda.md +++ b/docs/reference/services/app-orchestration/lambda.md @@ -252,5 +252,5 @@ Deploy a Lambda on AWS. diff --git a/docs/reference/services/app-orchestration/public-static-website.md b/docs/reference/services/app-orchestration/public-static-website.md index 144dceb5a6..096301bb9a 100644 --- a/docs/reference/services/app-orchestration/public-static-website.md +++ b/docs/reference/services/app-orchestration/public-static-website.md @@ -108,5 +108,5 @@ Deploy your static content and static websites on S3, using a CloudFront CDN. Su diff --git a/docs/reference/services/ci-cd-pipeline/ecs-deploy-runner.md b/docs/reference/services/ci-cd-pipeline/ecs-deploy-runner.md index 553d945aec..c8473a0a65 100644 --- a/docs/reference/services/ci-cd-pipeline/ecs-deploy-runner.md +++ b/docs/reference/services/ci-cd-pipeline/ecs-deploy-runner.md @@ -16,6 +16,18 @@ Use a CI/CD pipeline for deploying infrastructure code updates. * [**`ami_builder_config`**](#ami_builder_config) — Configuration options for the ami-builder container of the ECS deploy runner stack. This container will be used for building AMIs in the CI/CD pipeline using packer. Set to `null` to disable this container. + + +* [**`cloudwatch_log_group_for_ec2_kms_key_id`**](#cloudwatch_log_group_for_ec2_kms_key_id) — The ID (ARN, alias ARN, AWS ID) of a customer managed KMS Key to use for encrypting log data. + + + +* [**`cloudwatch_log_group_for_ec2_retention_in_days`**](#cloudwatch_log_group_for_ec2_retention_in_days) — The number of days to retain log events in the log group. Refer to [`https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudwatch_log_group#retention_in_days`](#https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudwatch_log_group#retention_in_days) for all the valid values. When null, the log events are retained forever. + + + +* [**`cloudwatch_log_group_for_ec2_tags`**](#cloudwatch_log_group_for_ec2_tags) — Tags to apply on the CloudWatch Log Group, encoded as a map where the keys are tag keys and values are tag values. + * [**`container_cpu`**](#container_cpu) — The default CPU units for the instances that Fargate will spin up. The invoker allows users to override the CPU at run time, but this value will be used if the user provides no value for the CPU. Options here: [`https://docs.aws.amazon.com/AmazonECS/latest/developerguide/AWS_Fargate`](#https://docs.aws.amazon.com/AmazonECS/latest/developerguide/AWS_Fargate).html#fargate-tasks-size. @@ -84,6 +96,10 @@ Use a CI/CD pipeline for deploying infrastructure code updates. * [**`shared_secrets_kms_cmk_arn`**](#shared_secrets_kms_cmk_arn) — The ARN of the KMS CMK used for sharing AWS Secrets Manager secrets between accounts. + + +* [**`should_create_cloudwatch_log_group_for_ec2`**](#should_create_cloudwatch_log_group_for_ec2) — When true, precreate the CloudWatch Log Group to use for log aggregation from the EC2 instances. This is useful if you wish to customize the CloudWatch Log Group with various settings such as retention periods and KMS encryption. When false, the CloudWatch agent will automatically create a basic log group to use. + * [**`snapshot_encryption_kms_cmk_arns`**](#snapshot_encryption_kms_cmk_arns) — Map of names to ARNs of KMS CMKs that are used to encrypt snapshots (including AMIs). This module will create the necessary KMS key grants to allow the respective deploy containers access to utilize the keys for managing the encrypted snapshots. The keys are arbitrary names that are used to identify the key. @@ -152,5 +168,5 @@ Use a CI/CD pipeline for deploying infrastructure code updates. diff --git a/docs/reference/services/ci-cd-pipeline/jenkins.md b/docs/reference/services/ci-cd-pipeline/jenkins.md index 51f6791d14..057f3c2445 100644 --- a/docs/reference/services/ci-cd-pipeline/jenkins.md +++ b/docs/reference/services/ci-cd-pipeline/jenkins.md @@ -80,6 +80,18 @@ Deploy Jenkins CI Server on AWS. * [**`cloud_init_parts`**](#cloud_init_parts) — Cloud init scripts to run on the Jenkins server when it is booting. See the part blocks in [`https://www.terraform.io/docs/providers/template/d/cloudinit_config`](#https://www.terraform.io/docs/providers/template/d/cloudinit_config).html for syntax. + + +* [**`cloudwatch_log_group_kms_key_id`**](#cloudwatch_log_group_kms_key_id) — The ID (ARN, alias ARN, AWS ID) of a customer managed KMS Key to use for encrypting log data. + + + +* [**`cloudwatch_log_group_retention_in_days`**](#cloudwatch_log_group_retention_in_days) — The number of days to retain log events in the log group. Refer to [`https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudwatch_log_group#retention_in_days`](#https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudwatch_log_group#retention_in_days) for all the valid values. When null, the log events are retained forever. + + + +* [**`cloudwatch_log_group_tags`**](#cloudwatch_log_group_tags) — Tags to apply on the CloudWatch Log Group, encoded as a map where the keys are tag keys and values are tag values. + * [**`custom_tags`**](#custom_tags) — A list of custom tags to apply to Jenkins and all other resources. @@ -204,6 +216,10 @@ Deploy Jenkins CI Server on AWS. * [**`root_volume_size`**](#root_volume_size) — The amount of disk space, in GB, to allocate for the root volume of this server. Note that all of Jenkins' data is stored on a separate EBS Volume (see [`jenkins_volume_size`](#jenkins_volume_size)), so this root volume is primarily used for the OS, temp folders, apps, etc. + + +* [**`should_create_cloudwatch_log_group`**](#should_create_cloudwatch_log_group) — When true, precreate the CloudWatch Log Group to use for log aggregation from the EC2 instances. This is useful if you wish to customize the CloudWatch Log Group with various settings such as retention periods and KMS encryption. When false, the CloudWatch agent will automatically create a basic log group to use. + * [**`skip_health_check`**](#skip_health_check) — If set to true, skip the health check, and start a rolling deployment of Jenkins without waiting for it to initially be in a healthy state. This is primarily useful if the server group is in a broken state and you want to force a deployment anyway. @@ -300,5 +316,5 @@ Deploy Jenkins CI Server on AWS. diff --git a/docs/reference/services/data-storage/amazon-aurora.md b/docs/reference/services/data-storage/amazon-aurora.md index 7bb8bcf40c..9158f44cf8 100644 --- a/docs/reference/services/data-storage/amazon-aurora.md +++ b/docs/reference/services/data-storage/amazon-aurora.md @@ -323,6 +323,10 @@ Deploy and manage Amazon Aurora using Amazon's Relational Database Service (RDS) * [**`primary_host`**](#primary_host) — The host portion of the Aurora endpoint. [`primary_endpoint`](#primary_endpoint) is in the form '<host>:<port>', and this output returns just the host part. + + +* [**`reader_endpoint`**](#reader_endpoint) — A read-only endpoint for the Aurora cluster, automatically load-balanced across replicas. + * [**`share_snapshot_lambda_arn`**](#share_snapshot_lambda_arn) — The ARN of the AWS Lambda Function used for sharing manual snapshots with secondary accounts. @@ -332,5 +336,5 @@ Deploy and manage Amazon Aurora using Amazon's Relational Database Service (RDS) diff --git a/docs/reference/services/data-storage/amazon-ecr-repositories.md b/docs/reference/services/data-storage/amazon-ecr-repositories.md index 65e49b40b7..96a784a21c 100644 --- a/docs/reference/services/data-storage/amazon-ecr-repositories.md +++ b/docs/reference/services/data-storage/amazon-ecr-repositories.md @@ -32,10 +32,18 @@ Create and manage multiple Amazon Elastic Container Repository (ECR) Repositorie * [**`default_image_tag_mutability`**](#default_image_tag_mutability) — The tag mutability setting for all the repos. Must be one of: MUTABLE or IMMUTABLE. Can be overridden on a per repo basis by the [`image_tag_mutability`](#image_tag_mutability) property in the repositories map. + + +* [**`default_lifecycle_policy_rules`**](#default_lifecycle_policy_rules) — Add lifecycle policy to ECR repo. + * [**`global_tags`**](#global_tags) — A map of tags (where the key and value correspond to tag keys and values) that should be assigned to all ECR repositories. + + +* [**`replication_regions`**](#replication_regions) — List of regions (e.g., us-east-1) to replicate the ECR repository to. + * [**`repositories`**](#repositories) — A map of repo names to configurations for that repository. @@ -64,5 +72,5 @@ Create and manage multiple Amazon Elastic Container Repository (ECR) Repositorie diff --git a/docs/reference/services/data-storage/amazon-elasti-cache-for-memcached.md b/docs/reference/services/data-storage/amazon-elasti-cache-for-memcached.md index 8db25da1c7..8b31802534 100644 --- a/docs/reference/services/data-storage/amazon-elasti-cache-for-memcached.md +++ b/docs/reference/services/data-storage/amazon-elasti-cache-for-memcached.md @@ -96,5 +96,5 @@ Deploy and manage Amazon ElastiCache for Memcached diff --git a/docs/reference/services/data-storage/amazon-elasti-cache-for-redis.md b/docs/reference/services/data-storage/amazon-elasti-cache-for-redis.md index 23affe6642..a246368c3a 100644 --- a/docs/reference/services/data-storage/amazon-elasti-cache-for-redis.md +++ b/docs/reference/services/data-storage/amazon-elasti-cache-for-redis.md @@ -136,5 +136,5 @@ Deploy and manage Amazon ElastiCache for Redis diff --git a/docs/reference/services/data-storage/amazon-elasticsearch.md b/docs/reference/services/data-storage/amazon-elasticsearch.md index 02fdc9e724..12162dcbad 100644 --- a/docs/reference/services/data-storage/amazon-elasticsearch.md +++ b/docs/reference/services/data-storage/amazon-elasticsearch.md @@ -196,5 +196,5 @@ Deploy and manage Amazon Elasticsearch Service diff --git a/docs/reference/services/data-storage/amazon-rds.md b/docs/reference/services/data-storage/amazon-rds.md index 15030db259..d7ac437f60 100644 --- a/docs/reference/services/data-storage/amazon-rds.md +++ b/docs/reference/services/data-storage/amazon-rds.md @@ -360,5 +360,5 @@ Deploy and manage Amazon Relational Database Service (RDS) diff --git a/docs/reference/services/data-storage/s-3-bucket.md b/docs/reference/services/data-storage/s-3-bucket.md index 2e526d7b51..cc822c08e2 100644 --- a/docs/reference/services/data-storage/s-3-bucket.md +++ b/docs/reference/services/data-storage/s-3-bucket.md @@ -16,6 +16,10 @@ Deploy an S3 bucket for data storage, with support for access logging, versionin * [**`access_logging_bucket`**](#access_logging_bucket) — The S3 bucket where access logs for this bucket should be stored. Set to null to disable access logging. + + +* [**`access_logging_bucket_lifecycle_rules`**](#access_logging_bucket_lifecycle_rules) — The lifecycle rules for the access logs bucket. See [`lifecycle_rules`](#lifecycle_rules) for details. + * [**`access_logging_bucket_ownership`**](#access_logging_bucket_ownership) — Configure who will be the default owner of objects uploaded to the access logs S3 bucket: must be one of BucketOwnerPreferred (the bucket owner owns objects), ObjectWriter (the writer of each object owns that object), or null (don't configure this feature). Note that this setting only takes effect if the object is uploaded with the bucket-owner-full-control canned ACL. See https://docs.aws.amazon.com/AmazonS3/latest/dev/about-object-ownership.html for more info. @@ -68,6 +72,10 @@ Deploy an S3 bucket for data storage, with support for access logging, versionin * [**`force_destroy_replica`**](#force_destroy_replica) — If set to true, when you run 'terraform destroy', delete all objects from the replica bucket so that the bucket can be destroyed without error. Warning: these objects are not recoverable so only use this if you're absolutely sure you want to permanently delete everything! + + +* [**`lifecycle_rules`**](#lifecycle_rules) — The lifecycle rules for this S3 bucket. These can be used to change storage types or delete objects based on customizable rules. This should be a map, where each key is a unique ID for the lifecycle rule, and each value is an object that contains the parameters defined in the comment above. + * [**`mfa_delete`**](#mfa_delete) — Enable MFA delete for either 'Change the versioning state of your bucket' or 'Permanently delete an object version'. This cannot be used to toggle this setting but is available to allow managed buckets to reflect the state in AWS. Only used if [`enable_versioning`](#enable_versioning) is true. For instructions on how to enable MFA Delete, check out the README from the terraform-aws-security/private-s3-bucket module. @@ -84,6 +92,10 @@ Deploy an S3 bucket for data storage, with support for access logging, versionin * [**`replica_bucket_already_exists`**](#replica_bucket_already_exists) — If set to true, replica bucket will be expected to already exist. + + +* [**`replica_bucket_lifecycle_rules`**](#replica_bucket_lifecycle_rules) — The lifecycle rules for the replica bucket. See [`lifecycle_rules`](#lifecycle_rules) for details. + * [**`replica_bucket_ownership`**](#replica_bucket_ownership) — Configure who will be the default owner of objects uploaded to the replica S3 bucket: must be one of BucketOwnerPreferred (the bucket owner owns objects), ObjectWriter (the writer of each object owns that object), or null (don't configure this feature). Note that this setting only takes effect if the object is uploaded with the bucket-owner-full-control canned ACL. See https://docs.aws.amazon.com/AmazonS3/latest/dev/about-object-ownership.html for more info. @@ -152,5 +164,5 @@ Deploy an S3 bucket for data storage, with support for access logging, versionin diff --git a/docs/reference/services/intro/create-your-own-service-catalog.md b/docs/reference/services/intro/create-your-own-service-catalog.md index ad95524d22..bd63c3f8a6 100644 --- a/docs/reference/services/intro/create-your-own-service-catalog.md +++ b/docs/reference/services/intro/create-your-own-service-catalog.md @@ -187,5 +187,5 @@ inputs = { diff --git a/docs/reference/services/intro/deploy-new-infrastructure.md b/docs/reference/services/intro/deploy-new-infrastructure.md index 3ac3a32fd7..bbcd73a7e7 100644 --- a/docs/reference/services/intro/deploy-new-infrastructure.md +++ b/docs/reference/services/intro/deploy-new-infrastructure.md @@ -356,5 +356,5 @@ Below are instructions on how to build an AMI using these Packer templates. We'l diff --git a/docs/reference/services/intro/make-changes-to-your-infrastructure.md b/docs/reference/services/intro/make-changes-to-your-infrastructure.md index 4b83fd5b8f..cda7817736 100644 --- a/docs/reference/services/intro/make-changes-to-your-infrastructure.md +++ b/docs/reference/services/intro/make-changes-to-your-infrastructure.md @@ -191,5 +191,5 @@ _(Documentation coming soon. If you need help with this ASAP, please contact [su diff --git a/docs/reference/services/intro/overview.md b/docs/reference/services/intro/overview.md index 166676eaec..a4b6303efd 100644 --- a/docs/reference/services/intro/overview.md +++ b/docs/reference/services/intro/overview.md @@ -94,5 +94,5 @@ Makes sure to ALWAYS read the release notes and migration instructions (if any) diff --git a/docs/reference/services/intro/patterns-used-in-the-service-catalog.md b/docs/reference/services/intro/patterns-used-in-the-service-catalog.md index 24eebe2cb8..3f9abbebbd 100644 --- a/docs/reference/services/intro/patterns-used-in-the-service-catalog.md +++ b/docs/reference/services/intro/patterns-used-in-the-service-catalog.md @@ -96,5 +96,5 @@ most commonly used filters will be: diff --git a/docs/reference/services/landing-zone/aws-app-account-baseline-wrapper.md b/docs/reference/services/landing-zone/aws-app-account-baseline-wrapper.md index 464ff5f50b..807397c02b 100644 --- a/docs/reference/services/landing-zone/aws-app-account-baseline-wrapper.md +++ b/docs/reference/services/landing-zone/aws-app-account-baseline-wrapper.md @@ -232,6 +232,10 @@ A security baseline for AWS Landing Zone for configuring app accounts (dev, stag * [**`enable_encrypted_volumes`**](#enable_encrypted_volumes) — Checks whether the EBS volumes that are in an attached state are encrypted. + + +* [**`enable_github_actions_access`**](#enable_github_actions_access) — When true, create an Open ID Connect Provider that GitHub actions can use to assume IAM roles in the account. Refer to https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services for more information. + * [**`enable_iam_access_analyzer`**](#enable_iam_access_analyzer) — A feature flag to enable or disable this module. @@ -272,6 +276,10 @@ A security baseline for AWS Landing Zone for configuring app accounts (dev, stag * [**`encrypted_volumes_kms_id`**](#encrypted_volumes_kms_id) — ID or ARN of the KMS key that is used to encrypt the volume. Used for configuring the encrypted volumes config rule. + + +* [**`github_actions_openid_connect_provider_thumbprint_list`**](#github_actions_openid_connect_provider_thumbprint_list) — When set, use the statically provided hardcoded list of thumbprints rather than looking it up dynamically. This is useful if you want to trade reliability of the OpenID Connect Provider across certificate renewals with a static list that is obtained using a trustworthy mechanism, to mitigate potential damage from a domain hijacking attack on GitHub domains. + * [**`guardduty_cloudwatch_event_rule_name`**](#guardduty_cloudwatch_event_rule_name) — Name of the Cloudwatch event rules. @@ -583,6 +591,14 @@ A security baseline for AWS Landing Zone for configuring app accounts (dev, stag * [**`config_sns_topic_arns`**](#config_sns_topic_arns) — The ARNs of the SNS Topic used by the config notifications. + + +* [**`github_actions_iam_openid_connect_provider_arn`**](#github_actions_iam_openid_connect_provider_arn) — ARN of the OpenID Connect Provider that can be used to attach AWS IAM Roles to GitHub Actions. + + + +* [**`github_actions_iam_openid_connect_provider_url`**](#github_actions_iam_openid_connect_provider_url) — URL of the OpenID Connect Provider that can be used to attach AWS IAM Roles to GitHub Actions. + * [**`guardduty_cloudwatch_event_rule_arns`**](#guardduty_cloudwatch_event_rule_arns) — The ARNs of the cloudwatch event rules used to publish findings to sns if [`publish_findings_to_sns`](#publish_findings_to_sns) is set to true. @@ -628,5 +644,5 @@ A security baseline for AWS Landing Zone for configuring app accounts (dev, stag diff --git a/docs/reference/services/landing-zone/aws-root-account-baseline-wrapper.md b/docs/reference/services/landing-zone/aws-root-account-baseline-wrapper.md index ea2264ba0b..cade15d51c 100644 --- a/docs/reference/services/landing-zone/aws-root-account-baseline-wrapper.md +++ b/docs/reference/services/landing-zone/aws-root-account-baseline-wrapper.md @@ -876,5 +876,5 @@ A security baseline for AWS Landing Zone for configuring the root account (AKA m diff --git a/docs/reference/services/landing-zone/aws-security-account-baseline-wrapper.md b/docs/reference/services/landing-zone/aws-security-account-baseline-wrapper.md index 9b9afc6385..27fe43698c 100644 --- a/docs/reference/services/landing-zone/aws-security-account-baseline-wrapper.md +++ b/docs/reference/services/landing-zone/aws-security-account-baseline-wrapper.md @@ -236,6 +236,10 @@ A security baseline for AWS Landing Zone for configuring the security account (t * [**`enable_encrypted_volumes`**](#enable_encrypted_volumes) — Checks whether the EBS volumes that are in an attached state are encrypted. + + +* [**`enable_github_actions_access`**](#enable_github_actions_access) — When true, create an Open ID Connect Provider that GitHub actions can use to assume IAM roles in the account. Refer to https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services for more information. + * [**`enable_iam_access_analyzer`**](#enable_iam_access_analyzer) — A feature flag to enable or disable this module. @@ -280,6 +284,10 @@ A security baseline for AWS Landing Zone for configuring the security account (t * [**`force_destroy_users`**](#force_destroy_users) — When destroying this user, destroy even if it has non-Terraform-managed IAM access keys, login profile, or MFA devices. Without [`force_destroy`](#force_destroy) a user with non-Terraform-managed access keys and login profile will fail to be destroyed. + + +* [**`github_actions_openid_connect_provider_thumbprint_list`**](#github_actions_openid_connect_provider_thumbprint_list) — When set, use the statically provided hardcoded list of thumbprints rather than looking it up dynamically. This is useful if you want to trade reliability of the OpenID Connect Provider across certificate renewals with a static list that is obtained using a trustworthy mechanism, to mitigate potential damage from a domain hijacking attack on GitHub domains. + * [**`guardduty_cloudwatch_event_rule_name`**](#guardduty_cloudwatch_event_rule_name) — Name of the Cloudwatch event rules. @@ -751,6 +759,14 @@ A security baseline for AWS Landing Zone for configuring the security account (t * [**`full_access_iam_group_name`**](#full_access_iam_group_name) — + + +* [**`github_actions_iam_openid_connect_provider_arn`**](#github_actions_iam_openid_connect_provider_arn) — ARN of the OpenID Connect Provider that can be used to attach AWS IAM Roles to GitHub Actions. + + + +* [**`github_actions_iam_openid_connect_provider_url`**](#github_actions_iam_openid_connect_provider_url) — URL of the OpenID Connect Provider that can be used to attach AWS IAM Roles to GitHub Actions. + * [**`guardduty_cloudwatch_event_rule_arns`**](#guardduty_cloudwatch_event_rule_arns) — The ARNs of the cloudwatch event rules used to publish findings to sns if [`publish_findings_to_sns`](#publish_findings_to_sns) is set to true. @@ -892,5 +908,5 @@ A security baseline for AWS Landing Zone for configuring the security account (t diff --git a/docs/reference/services/landing-zone/gruntwork-access.md b/docs/reference/services/landing-zone/gruntwork-access.md index 9d41ae9c48..fc21549653 100644 --- a/docs/reference/services/landing-zone/gruntwork-access.md +++ b/docs/reference/services/landing-zone/gruntwork-access.md @@ -56,5 +56,5 @@ Grant the Gruntwork team access to one of your AWS accounts so we can deploy a R diff --git a/docs/reference/services/landing-zone/iam-users-and-iam-groups.md b/docs/reference/services/landing-zone/iam-users-and-iam-groups.md index e5155e6b73..a162a78466 100644 --- a/docs/reference/services/landing-zone/iam-users-and-iam-groups.md +++ b/docs/reference/services/landing-zone/iam-users-and-iam-groups.md @@ -320,5 +320,5 @@ Convenient module to manage best practices set of IAM Groups for permissions man diff --git a/docs/reference/services/networking/elastic-load-balancer-elb.md b/docs/reference/services/networking/elastic-load-balancer-elb.md index e649cf9466..b5ce702e48 100644 --- a/docs/reference/services/networking/elastic-load-balancer-elb.md +++ b/docs/reference/services/networking/elastic-load-balancer-elb.md @@ -176,5 +176,5 @@ Deploy the Application Load Balancer (ALB) for load balancing HTTP and HTTPS, wi diff --git a/docs/reference/services/networking/management-vpc.md b/docs/reference/services/networking/management-vpc.md index d7008d1cdf..bd6f298b25 100644 --- a/docs/reference/services/networking/management-vpc.md +++ b/docs/reference/services/networking/management-vpc.md @@ -12,6 +12,14 @@ Deploy a VPC on AWS for administrative and management functions. + + +* [**`apply_default_nacl_rules`**](#apply_default_nacl_rules) — If true, will apply the default NACL rules in [`default_nacl_ingress_rules`](#default_nacl_ingress_rules) and [`default_nacl_egress_rules`](#default_nacl_egress_rules) on the default NACL of the VPC. Note that every VPC must have a default NACL - when this is false, the original default NACL rules managed by AWS will be used. + + + +* [**`associate_default_nacl_to_subnets`**](#associate_default_nacl_to_subnets) — If true, will associate the default NACL to the public, private, and persistence subnets created by this module. Only used if [`apply_default_nacl_rules`](#apply_default_nacl_rules) is true. Note that this does not guarantee that the subnets are associated with the default NACL. Subnets can only be associated with a single NACL. The default NACL association will be dropped if the subnets are associated with a custom NACL later. + * [**`availability_zone_exclude_ids`**](#availability_zone_exclude_ids) — List of excluded Availability Zone IDs. @@ -48,6 +56,26 @@ Deploy a VPC on AWS for administrative and management functions. * [**`custom_tags_vpc_only`**](#custom_tags_vpc_only) — A map of tags to apply just to the VPC itself, but not any of the other resources. The key is the tag name and the value is the tag value. Note that tags defined here will override tags defined as [`custom_tags`](#custom_tags) in case of conflict. + + +* [**`default_nacl_egress_rules`**](#default_nacl_egress_rules) — The egress rules to apply to the default NACL in the VPC. This is the security group that is used by any subnet that doesn't have its own NACL attached. The value for this variable must be a map where the keys are a unique name for each rule and the values are objects with the same fields as the egress block in the [`aws_default_network_acl`](#aws_default_network_acl) resource: [`https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/default_network_acl`](#https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/default_network_acl). + + + +* [**`default_nacl_ingress_rules`**](#default_nacl_ingress_rules) — The ingress rules to apply to the default NACL in the VPC. This is the NACL that is used by any subnet that doesn't have its own NACL attached. The value for this variable must be a map where the keys are a unique name for each rule and the values are objects with the same fields as the ingress block in the [`aws_default_network_acl`](#aws_default_network_acl) resource: [`https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/default_network_acl`](#https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/default_network_acl). + + + +* [**`default_security_group_egress_rules`**](#default_security_group_egress_rules) — The egress rules to apply to the default security group in the VPC. This is the security group that is used by any resource that doesn't have its own security group attached. The value for this variable must be a map where the keys are a unique name for each rule and the values are objects with the same fields as the egress block in the [`aws_default_security_group`](#aws_default_security_group) resource: [`https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/default_security_group`](#https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/default_security_group)#egress-block. + + + +* [**`default_security_group_ingress_rules`**](#default_security_group_ingress_rules) — The ingress rules to apply to the default security group in the VPC. This is the security group that is used by any resource that doesn't have its own security group attached. The value for this variable must be a map where the keys are a unique name for each rule and the values are objects with the same fields as the ingress block in the [`aws_default_security_group`](#aws_default_security_group) resource: [`https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/default_security_group`](#https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/default_security_group)#ingress-block. + + + +* [**`enable_default_security_group`**](#enable_default_security_group) — If set to false, the default security groups will NOT be created. + * [**`kms_key_arn`**](#kms_key_arn) — The ARN of a KMS key to use for encrypting VPC the flow log. A new KMS key will be created if this is not supplied. @@ -164,5 +192,5 @@ Deploy a VPC on AWS for administrative and management functions. diff --git a/docs/reference/services/networking/route-53-hosted-zones.md b/docs/reference/services/networking/route-53-hosted-zones.md index 1b33280695..8ad36b6ec2 100644 --- a/docs/reference/services/networking/route-53-hosted-zones.md +++ b/docs/reference/services/networking/route-53-hosted-zones.md @@ -76,5 +76,5 @@ Manage DNS entries using https://aws.amazon.com/route53/:Amazon Route 53 diff --git a/docs/reference/services/networking/sns-topics.md b/docs/reference/services/networking/sns-topics.md index 44fb2d6106..667107719e 100644 --- a/docs/reference/services/networking/sns-topics.md +++ b/docs/reference/services/networking/sns-topics.md @@ -60,5 +60,5 @@ Create Amazon Simple Notification Service topics diff --git a/docs/reference/services/networking/virtual-private-cloud-vpc.md b/docs/reference/services/networking/virtual-private-cloud-vpc.md index be48228c82..b785fc7767 100644 --- a/docs/reference/services/networking/virtual-private-cloud-vpc.md +++ b/docs/reference/services/networking/virtual-private-cloud-vpc.md @@ -18,7 +18,11 @@ Deploy a VPC on AWS. -* [**`apply_default_nacl_rules`**](#apply_default_nacl_rules) — If true, will apply the default NACL rules in [`default_nacl_ingress_rules`](#default_nacl_ingress_rules) and [`default_nacl_egress_rules`](#default_nacl_egress_rules) to the public, private, and persistence subnets created by this module. Note that every VPC has default NACL rules that apply to subnets. When this is false, the original default NACL rules managed by AWS will be used. If you are managing NACLs for the subnets using another module or for some reason do not want to use the default NACLs, set this to false. +* [**`apply_default_nacl_rules`**](#apply_default_nacl_rules) — If true, will apply the default NACL rules in [`default_nacl_ingress_rules`](#default_nacl_ingress_rules) and [`default_nacl_egress_rules`](#default_nacl_egress_rules) on the default NACL of the VPC. Note that every VPC must have a default NACL - when this is false, the original default NACL rules managed by AWS will be used. + + + +* [**`associate_default_nacl_to_subnets`**](#associate_default_nacl_to_subnets) — If true, will associate the default NACL to the public, private, and persistence subnets created by this module. Only used if [`apply_default_nacl_rules`](#apply_default_nacl_rules) is true. Note that this does not guarantee that the subnets are associated with the default NACL. Subnets can only be associated with a single NACL. The default NACL association will be dropped if the subnets are associated with a custom NACL later. @@ -348,5 +352,5 @@ Deploy a VPC on AWS. diff --git a/docs/reference/services/security/bastion.md b/docs/reference/services/security/bastion.md index 73612bef92..b9ad725928 100644 --- a/docs/reference/services/security/bastion.md +++ b/docs/reference/services/security/bastion.md @@ -40,6 +40,18 @@ Deploy a Bastion host on to your AWS VPC network. * [**`cloud_init_parts`**](#cloud_init_parts) — Cloud init scripts to run on the bastion host while it boots. See the part blocks in [`https://www.terraform.io/docs/providers/template/d/cloudinit_config`](#https://www.terraform.io/docs/providers/template/d/cloudinit_config).html for syntax. + + +* [**`cloudwatch_log_group_kms_key_id`**](#cloudwatch_log_group_kms_key_id) — The ID (ARN, alias ARN, AWS ID) of a customer managed KMS Key to use for encrypting log data. + + + +* [**`cloudwatch_log_group_retention_in_days`**](#cloudwatch_log_group_retention_in_days) — The number of days to retain log events in the log group. Refer to [`https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudwatch_log_group#retention_in_days`](#https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudwatch_log_group#retention_in_days) for all the valid values. When null, the log events are retained forever. + + + +* [**`cloudwatch_log_group_tags`**](#cloudwatch_log_group_tags) — Tags to apply on the CloudWatch Log Group, encoded as a map where the keys are tag keys and values are tag values. + * [**`create_dns_record`**](#create_dns_record) — Set to true to create a DNS record in Route53 pointing to the bastion. If true, be sure to set [`domain_name`](#domain_name). @@ -92,6 +104,10 @@ Deploy a Bastion host on to your AWS VPC network. * [**`name`**](#name) — The name of the bastion host and the other resources created by these templates + + +* [**`should_create_cloudwatch_log_group`**](#should_create_cloudwatch_log_group) — When true, precreate the CloudWatch Log Group to use for log aggregation from the EC2 instances. This is useful if you wish to customize the CloudWatch Log Group with various settings such as retention periods and KMS encryption. When false, the CloudWatch agent will automatically create a basic log group to use. + * [**`ssh_grunt_iam_group`**](#ssh_grunt_iam_group) — If you are using ssh-grunt, this is the name of the IAM group from which users will be allowed to SSH to this Bastion Host. This value is only used if [`enable_ssh_grunt`](#enable_ssh_grunt)=true. @@ -144,5 +160,5 @@ Deploy a Bastion host on to your AWS VPC network. diff --git a/docs/reference/services/security/open-vpn.md b/docs/reference/services/security/open-vpn.md index 0585018b89..3571c434db 100644 --- a/docs/reference/services/security/open-vpn.md +++ b/docs/reference/services/security/open-vpn.md @@ -60,6 +60,18 @@ Deploy an OpenVPN Server on AWS. * [**`cloud_init_parts`**](#cloud_init_parts) — Cloud init scripts to run on the OpenVPN server while it boots. See the part blocks in [`https://www.terraform.io/docs/providers/template/d/cloudinit_config`](#https://www.terraform.io/docs/providers/template/d/cloudinit_config).html for syntax. + + +* [**`cloudwatch_log_group_kms_key_id`**](#cloudwatch_log_group_kms_key_id) — The ID (ARN, alias ARN, AWS ID) of a customer managed KMS Key to use for encrypting log data. + + + +* [**`cloudwatch_log_group_retention_in_days`**](#cloudwatch_log_group_retention_in_days) — The number of days to retain log events in the log group. Refer to [`https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudwatch_log_group#retention_in_days`](#https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudwatch_log_group#retention_in_days) for all the valid values. When null, the log events are retained forever. + + + +* [**`cloudwatch_log_group_tags`**](#cloudwatch_log_group_tags) — Tags to apply on the CloudWatch Log Group, encoded as a map where the keys are tag keys and values are tag values. + * [**`cmk_administrator_iam_arns`**](#cmk_administrator_iam_arns) — A list of IAM ARNs for users who should be given administrator access to this CMK (e.g. arn:aws:iam::<aws-account-id>:user/<iam-user-arn>). If this list is empty, and [`kms_key_arn`](#kms_key_arn) is null, the ARN of the current user will be used. @@ -148,6 +160,10 @@ Deploy an OpenVPN Server on AWS. * [**`revocation_queue_name`**](#revocation_queue_name) — The name of the sqs queue that will be used to receive certification revocation requests. Note that the queue name will be automatically prefixed with 'openvpn-requests-'. + + +* [**`should_create_cloudwatch_log_group`**](#should_create_cloudwatch_log_group) — When true, precreate the CloudWatch Log Group to use for log aggregation from the EC2 instances. This is useful if you wish to customize the CloudWatch Log Group with various settings such as retention periods and KMS encryption. When false, the CloudWatch agent will automatically create a basic log group to use. + * [**`ssh_grunt_iam_group`**](#ssh_grunt_iam_group) — If you are using ssh-grunt, this is the name of the IAM group from which users will be allowed to SSH to this OpenVPN server. This value is only used if [`enable_ssh_grunt`](#enable_ssh_grunt)=true. @@ -164,6 +180,10 @@ Deploy an OpenVPN Server on AWS. * [**`tenancy`**](#tenancy) — The tenancy of this server. Must be one of: default, dedicated, or host. + + +* [**`use_strong_prime`**](#use_strong_prime) — When true, generate Diffie-Hellman parameters using strong primes. Note that while stronger primes make the keys more cryptographically secure, the effective security gains are known to be insignificant in practice. + * [**`vpc_id`**](#vpc_id) — The ID of the VPC in which to deploy the OpenVPN server. @@ -248,5 +268,5 @@ Deploy an OpenVPN Server on AWS. diff --git a/docs/reference/services/security/tls-scripts.md b/docs/reference/services/security/tls-scripts.md index 9b28c18bc5..e3a6d6e667 100644 --- a/docs/reference/services/security/tls-scripts.md +++ b/docs/reference/services/security/tls-scripts.md @@ -24,5 +24,5 @@ Create TLS certificates, download CA certs for RDS, and generate JVM trust store diff --git a/docs/reference/tools/stub.md b/docs/reference/tools/stub.md index 5293900ae7..04b1020044 100644 --- a/docs/reference/tools/stub.md +++ b/docs/reference/tools/stub.md @@ -6,5 +6,5 @@ diff --git a/package.json b/package.json index e9c5f571f6..48396fb846 100644 --- a/package.json +++ b/package.json @@ -13,7 +13,8 @@ "write-translations": "docusaurus write-translations", "write-heading-ids": "docusaurus write-heading-ids", "typecheck": "tsc", - "regenerate:local": "docs-sourcer" + "regenerate": "env-cmd docs-sourcer", + "regenerate:local": "yarn regenerate --plugins local-copier" }, "dependencies": { "@docusaurus/core": "^2.0.0-beta.14", @@ -22,6 +23,7 @@ "@svgr/webpack": "^5.5.0", "clsx": "^1.1.1", "config": "^3.3.6", + "env-cmd": "^10.1.0", "file-loader": "^6.2.0", "plugin-image-zoom": "ataft/plugin-image-zoom", "posthog-docusaurus": "^1.0.3", @@ -39,7 +41,7 @@ "typescript": "^4.3.5" }, "optionalDependencies": { - "docs-sourcer": "git+ssh://git@github.com/gruntwork-io/docs-sourcer.git#v0.0.6" + "docs-sourcer": "git+ssh://git@github.com/gruntwork-io/docs-sourcer.git#v0.0.8" }, "browserslist": { "production": [ diff --git a/yarn.lock b/yarn.lock index 83bd0d13fe..000c6ce0fd 100644 --- a/yarn.lock +++ b/yarn.lock @@ -2936,11 +2936,6 @@ resolved "https://registry.yarnpkg.com/@types/btoa-lite/-/btoa-lite-1.0.0.tgz#e190a5a548e0b348adb0df9ac7fa5f1151c7cca4" integrity sha512-wJsiX1tosQ+J5+bY5LrSahHxr2wT+uME5UDwdN1kg4frt40euqA+wzECkmq4t5QbveHiJepfdThgQrPw6KiSlg== -"@types/config@^0.0.39": - version "0.0.39" - resolved "https://registry.yarnpkg.com/@types/config/-/config-0.0.39.tgz#aad18ceb9439329adc3d4c6b91a908a72c715612" - integrity sha512-EBHj9lSIyw62vwqCwkeJXjiV6C2m2o+RJZlRWLkHduGYiNBoMXcY6AhSLqjQQ+uPdrPYrOMYvVa41zjo00LbFQ== - "@types/connect-history-api-fallback@^1.3.5": version "1.3.5" resolved "https://registry.yarnpkg.com/@types/connect-history-api-fallback/-/connect-history-api-fallback-1.3.5.tgz#d1f7a8a09d0ed5a57aee5ae9c18ab9b803205dae" @@ -3059,11 +3054,6 @@ resolved "https://registry.yarnpkg.com/@types/node/-/node-15.14.9.tgz#bc43c990c3c9be7281868bbc7b8fdd6e2b57adfa" integrity sha512-qjd88DrCxupx/kJD5yQgZdcYKZKSIGBVDIBE1/LTGcNm3d2Np/jxojkdePDdfnBHJc5W7vSMpbJ1aB7p/Py69A== -"@types/node@^16.11.7": - version "16.11.11" - resolved "https://registry.yarnpkg.com/@types/node/-/node-16.11.11.tgz#6ea7342dfb379ea1210835bada87b3c512120234" - integrity sha512-KB0sixD67CeecHC33MYn+eYARkqTheIRNuu97y2XMjR7Wu3XibO1vaY6VBV6O/a89SPI81cEUIYT87UqUWlZNw== - "@types/parse-json@^4.0.0": version "4.0.0" resolved "https://registry.yarnpkg.com/@types/parse-json/-/parse-json-4.0.0.tgz#2f8bb441434d163b35fb8ffdccd7138927ffb8c0" @@ -3175,11 +3165,6 @@ dependencies: "@types/node" "*" -"@types/spark-md5@^3.0.2": - version "3.0.2" - resolved "https://registry.yarnpkg.com/@types/spark-md5/-/spark-md5-3.0.2.tgz#da2e8a778a20335fc4f40b6471c4b0d86b70da55" - integrity sha512-82E/lVRaqelV9qmRzzJ1PKTpyrpnT7mwdneKNJB9hUtypZDMggloDfFUCIqRRx3lYRxteCwXSq9c+W71Vf0QnQ== - "@types/unist@*", "@types/unist@^2.0.0", "@types/unist@^2.0.2", "@types/unist@^2.0.3": version "2.0.6" resolved "https://registry.yarnpkg.com/@types/unist/-/unist-2.0.6.tgz#250a7b16c3b91f672a24552ec64678eeb1d3a08d" @@ -4024,6 +4009,15 @@ cli-boxes@^2.2.1: resolved "https://registry.yarnpkg.com/cli-boxes/-/cli-boxes-2.2.1.tgz#ddd5035d25094fce220e9cab40a45840a440318f" integrity sha512-y4coMcylgSCdVinjiDBuR8PCC2bLjyGTwEmPb9NHR/QaNU6EUOXcTY/s6VjGMD6ENSEaeQYHCY0GNGS5jfMwPw== +cliui@^7.0.2: + version "7.0.4" + resolved "https://registry.yarnpkg.com/cliui/-/cliui-7.0.4.tgz#a0265ee655476fc807aea9df3df8df7783808b4f" + integrity sha512-OcRE68cOsVMXp1Yvonl/fzkQOyjLSu/8bhPDfQt0e0/Eb283TKP20Fs2MqoPsr9SwA595rRCA+QMzYc9nBP+JQ== + dependencies: + string-width "^4.2.0" + strip-ansi "^6.0.0" + wrap-ansi "^7.0.0" + clone-deep@^4.0.1: version "4.0.1" resolved "https://registry.yarnpkg.com/clone-deep/-/clone-deep-4.0.1.tgz#c19fd9bdbbf85942b4fd979c84dcf7d5f07c2387" @@ -4137,6 +4131,11 @@ commander@^2.20.0: resolved "https://registry.yarnpkg.com/commander/-/commander-2.20.3.tgz#fd485e84c03eb4881c20722ba48035e8531aeb33" integrity sha512-GpVkmM8vF2vQUkj2LvZmD35JxeJOLCwJ9cUkugyk2nuhbv3+mJvpLYYt+0+USMxE+oj+ey/lJEnhZw75x/OMcQ== +commander@^4.0.0: + version "4.1.1" + resolved "https://registry.yarnpkg.com/commander/-/commander-4.1.1.tgz#9fd602bd936294e9e9ef46a3f4d6964044b18068" + integrity sha512-NOKm8xhkzAjzFx8B2v5OAHT+u5pRQc2UCa2Vq9jYL/31o2wi9mxBA7LIFs3sV5VSC49z6pEhfbMULvShKj26WA== + commander@^5.1.0: version "5.1.0" resolved "https://registry.yarnpkg.com/commander/-/commander-5.1.0.tgz#46abbd1652f8e059bddaef99bbdcb2ad9cf179ae" @@ -4323,7 +4322,7 @@ cross-fetch@^3.0.4: dependencies: node-fetch "2.6.1" -cross-spawn@^7.0.1, cross-spawn@^7.0.3: +cross-spawn@^7.0.0, cross-spawn@^7.0.1, cross-spawn@^7.0.3: version "7.0.3" resolved "https://registry.yarnpkg.com/cross-spawn/-/cross-spawn-7.0.3.tgz#f73a85b9d5d41d045551c177e2882d4ac85728a6" integrity sha512-iRDPJKUPVEND7dHPO8rkbOnPpyDygcDFtWjpeWNCgy8WP2rXcxXL8TskReQl6OrB2G7+UJrags1q15Fudc7G6w== @@ -4682,21 +4681,19 @@ dns-txt@^2.0.2: dependencies: buffer-indexof "^1.0.0" -"docs-sourcer@git+ssh://git@github.com/gruntwork-io/docs-sourcer.git#v0.0.6": +"docs-sourcer@git+ssh://git@github.com/gruntwork-io/docs-sourcer.git#v0.0.8": version "0.0.1" - resolved "git+ssh://git@github.com/gruntwork-io/docs-sourcer.git#17623df546c3f2db8305a82988966f1c85100838" + resolved "git+ssh://git@github.com/gruntwork-io/docs-sourcer.git#d1f7a72ebbd166429f258248d23a368a64465bb9" dependencies: "@octokit/auth-app" "^3.6.1" "@octokit/plugin-retry" "^3.0.9" "@octokit/rest" "^18.12.0" - "@types/config" "^0.0.39" - "@types/node" "^16.11.7" - "@types/spark-md5" "^3.0.2" add "^2.0.6" config "^3.3.6" dotenv "^10.0.0" file-loader "^6.2.0" fs "^0.0.1-security" + hcl2-parser "^1.0.3" js-yaml "^4.1.0" lodash "^4.17.21" node-html-markdown "^1.1.3" @@ -4705,6 +4702,7 @@ dns-txt@^2.0.2: unescape "^1.0.1" url-loader "^4.1.1" winston "^3.3.3" + yargs "^17.3.1" dom-converter@^0.2.0: version "0.2.0" @@ -4899,6 +4897,14 @@ entities@^3.0.1: resolved "https://registry.yarnpkg.com/entities/-/entities-3.0.1.tgz#2b887ca62585e96db3903482d336c1006c3001d4" integrity sha512-WiyBqoomrwMdFG1e0kqvASYfnlb0lp8M5o5Fw2OFq1hNZxxcNk8Ik0Xm7LxzBhuidnZB/UtBqVCgUz3kBOP51Q== +env-cmd@^10.1.0: + version "10.1.0" + resolved "https://registry.yarnpkg.com/env-cmd/-/env-cmd-10.1.0.tgz#c7f5d3b550c9519f137fdac4dd8fb6866a8c8c4b" + integrity sha512-mMdWTT9XKN7yNth/6N6g2GuKuJTsKMDHlQFUDacb/heQRRWOTIZ42t1rMHnQu4jYxU1ajdTeJM+9eEETlqToMA== + dependencies: + commander "^4.0.0" + cross-spawn "^7.0.0" + error-ex@^1.3.1: version "1.3.2" resolved "https://registry.yarnpkg.com/error-ex/-/error-ex-1.3.2.tgz#b4ac40648107fdcdcfae242f428bea8a14d4f1bf" @@ -5363,6 +5369,11 @@ gensync@^1.0.0-beta.1, gensync@^1.0.0-beta.2: resolved "https://registry.yarnpkg.com/gensync/-/gensync-1.0.0-beta.2.tgz#32a6ee76c3d7f52d46b2b1ae5d93fea8580a25e0" integrity sha512-3hN7NaskYvMDLQY55gnW3NQ+mesEAepTqlg+VEbj7zzqEMBVNhzcGYYeqFo/TlYz6eQiFcp1HcsCZO+nGgS8zg== +get-caller-file@^2.0.5: + version "2.0.5" + resolved "https://registry.yarnpkg.com/get-caller-file/-/get-caller-file-2.0.5.tgz#4f94412a82db32f36e3b0b9741f8a97feb031f7e" + integrity sha512-DyFP3BM/3YHTQOCUL/w0OZHR0lpKeGrxotcHWcqNEdnltqFwXVfhEBQ94eIo34AfQpo0rGki4cyIiftY06h2Fg== + get-intrinsic@^1.0.2, get-intrinsic@^1.1.0, get-intrinsic@^1.1.1: version "1.1.1" resolved "https://registry.yarnpkg.com/get-intrinsic/-/get-intrinsic-1.1.1.tgz#15f59f376f855c446963948f0d24cd3637b4abc6" @@ -5660,6 +5671,11 @@ hastscript@^6.0.0: property-information "^5.0.0" space-separated-tokens "^1.0.0" +hcl2-parser@^1.0.3: + version "1.0.3" + resolved "https://registry.yarnpkg.com/hcl2-parser/-/hcl2-parser-1.0.3.tgz#096d0ff5a3c46707ace54fcb7571317f5828ff0e" + integrity sha512-NQUm/BFF+2nrBfeqDhhsy4DxxiLHgkeE3FywtjFiXnjSUaio3w4Tz1MQ3vGJBUhyArzOXJ24pO7JwE5LAn7Ncg== + he@1.2.0, he@^1.2.0: version "1.2.0" resolved "https://registry.yarnpkg.com/he/-/he-1.2.0.tgz#84ae65fa7eafb165fddb61566ae14baf05664f0f" @@ -8235,6 +8251,11 @@ repeat-string@^1.5.4: resolved "https://registry.yarnpkg.com/repeat-string/-/repeat-string-1.6.1.tgz#8dcae470e1c88abc2d600fff4a776286da75e637" integrity sha1-jcrkcOHIirwtYA//Sndihtp15jc= +require-directory@^2.1.1: + version "2.1.1" + resolved "https://registry.yarnpkg.com/require-directory/-/require-directory-2.1.1.tgz#8c64ad5fd30dab1c976e2344ffe7f792a6a6df42" + integrity sha1-jGStX9MNqxyXbiNE/+f3kqam30I= + require-from-string@^2.0.2: version "2.0.2" resolved "https://registry.yarnpkg.com/require-from-string/-/require-from-string-2.0.2.tgz#89a7fdd938261267318eafe14f9c32e598c36909" @@ -8719,7 +8740,7 @@ std-env@^2.2.1: dependencies: ci-info "^3.1.1" -string-width@^4.0.0, string-width@^4.1.0, string-width@^4.2.2: +string-width@^4.0.0, string-width@^4.1.0, string-width@^4.2.0, string-width@^4.2.2, string-width@^4.2.3: version "4.2.3" resolved "https://registry.yarnpkg.com/string-width/-/string-width-4.2.3.tgz#269c7117d27b05ad2e536830a8ec895ef9c6d010" integrity sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g== @@ -9676,6 +9697,11 @@ xtend@^4.0.0, xtend@^4.0.1: resolved "https://registry.yarnpkg.com/xtend/-/xtend-4.0.2.tgz#bb72779f5fa465186b1f438f674fa347fdb5db54" integrity sha512-LKYU1iAXJXUgAXn9URjiu+MWhyUXHsvfp7mcuYm9dSUKK0/CjtrUwFAxD82/mCWbtLsGjFIad0wIsod4zrTAEQ== +y18n@^5.0.5: + version "5.0.8" + resolved "https://registry.yarnpkg.com/y18n/-/y18n-5.0.8.tgz#7f4934d0f7ca8c56f95314939ddcd2dd91ce1d55" + integrity sha512-0pfFzegeDWJHJIAmTLRP2DwHjdF5s7jo9tuztdQxAhINCdvS+3nGINqPd00AphqJR/0LhANUS6/+7SCb98YOfA== + yallist@^4.0.0: version "4.0.0" resolved "https://registry.yarnpkg.com/yallist/-/yallist-4.0.0.tgz#9bb92790d9c0effec63be73519e11a35019a3a72" @@ -9686,6 +9712,24 @@ yaml@^1.10.0, yaml@^1.10.2, yaml@^1.7.2: resolved "https://registry.yarnpkg.com/yaml/-/yaml-1.10.2.tgz#2301c5ffbf12b467de8da2333a459e29e7920e4b" integrity sha512-r3vXyErRCYJ7wg28yvBY5VSoAF8ZvlcW9/BwUzEtUsjvX/DKs24dIkuwjtuprwJJHsbyUbLApepYTR1BN4uHrg== +yargs-parser@^21.0.0: + version "21.0.0" + resolved "https://registry.yarnpkg.com/yargs-parser/-/yargs-parser-21.0.0.tgz#a485d3966be4317426dd56bdb6a30131b281dc55" + integrity sha512-z9kApYUOCwoeZ78rfRYYWdiU/iNL6mwwYlkkZfJoyMR1xps+NEBX5X7XmRpxkZHhXJ6+Ey00IwKxBBSW9FIjyA== + +yargs@^17.3.1: + version "17.3.1" + resolved "https://registry.yarnpkg.com/yargs/-/yargs-17.3.1.tgz#da56b28f32e2fd45aefb402ed9c26f42be4c07b9" + integrity sha512-WUANQeVgjLbNsEmGk20f+nlHgOqzRFpiGWVaBrYGYIGANIIu3lWjoyi0fNlFmJkvfhCZ6BXINe7/W2O2bV4iaA== + dependencies: + cliui "^7.0.2" + escalade "^3.1.1" + get-caller-file "^2.0.5" + require-directory "^2.1.1" + string-width "^4.2.3" + y18n "^5.0.5" + yargs-parser "^21.0.0" + yocto-queue@^0.1.0: version "0.1.0" resolved "https://registry.yarnpkg.com/yocto-queue/-/yocto-queue-0.1.0.tgz#0294eb3dee05028d31ee1a5fa2c556a6aaf10a1b"