From 8e75d2fcd99a6d1be534cd17c5ab529944d80a52 Mon Sep 17 00:00:00 2001 From: Eben Eliason Date: Tue, 11 Jan 2022 14:09:13 -0800 Subject: [PATCH 01/20] Refactor guides section sidebars so each guide has its own --- .../{01-overview/overview.md => index.md} | 18 +- _docs-sources/guides/welcome.md | 71 +++++- .../{01-overview/overview.md => index.md} | 20 +- docs/guides/welcome.md | 73 ++++++- docusaurus.config.js | 2 + sidebars.js | 206 ++---------------- sidebars/api-reference.js | 63 ++++++ sidebars/intro-guide.js | 54 +++++ sidebars/refarch-guide.js | 71 ++++++ 9 files changed, 361 insertions(+), 217 deletions(-) rename _docs-sources/guides/reference-architecture/{01-overview/overview.md => index.md} (93%) rename docs/guides/reference-architecture/{01-overview/overview.md => index.md} (93%) create mode 100644 sidebars/api-reference.js create mode 100644 sidebars/intro-guide.js create mode 100644 sidebars/refarch-guide.js diff --git a/_docs-sources/guides/reference-architecture/01-overview/overview.md b/_docs-sources/guides/reference-architecture/index.md similarity index 93% rename from _docs-sources/guides/reference-architecture/01-overview/overview.md rename to _docs-sources/guides/reference-architecture/index.md index 3fd6bec116..876ff2c405 100644 --- a/_docs-sources/guides/reference-architecture/01-overview/overview.md +++ b/_docs-sources/guides/reference-architecture/index.md @@ -2,7 +2,7 @@ pagination_label: Reference Architecture --- -# Architecture Overview +# Setting Up Your Reference Architecture This documentation contains an overview of a deployed and managed architecture. @@ -56,7 +56,7 @@ The list of accounts includes: - **shared-services**: DevOps tooling. - **logs**: An account for centralizing logs from all of the accounts. -Check out the [Authentication docs](../02-authenticate/01-intro.md) for more info on how to authenticate to these accounts and +Check out the [Authentication docs](02-authenticate/01-intro.md) for more info on how to authenticate to these accounts and switch between them. ## VPCs and subnets @@ -105,21 +105,21 @@ VPN client, you are "in the network", and will be able to access the private res to your EC2 Instances). For more info, see the [`openvpn` service](https://github.com/gruntwork-io/terraform-aws-service-catalog/tree/master/modules/mgmt/openvpn-server) and the VPN -section of the [Authentication docs](../02-authenticate/06-authenticate-to-the-vpn-server.md). +section of the [Authentication docs](02-authenticate/06-authenticate-to-the-vpn-server.md). ## GitHub We have set up [GitHub](https://github.com) as a Continuous Integration (CI) server. After every commit, a GitHub job runs your build, tests, packaging, and automated deployment steps. -For more info, see the [Gruntwork Pipelines docs](../04-configure-gw-pipelines/01-intro.md). +For more info, see the [Gruntwork Pipelines docs](04-configure-gw-pipelines/01-intro.md). ## Monitoring, log aggregation, alerting You can find metrics, log files from all your servers, and subscribe to alert notifications using [Amazon CloudWatch](https://aws.amazon.com/cloudwatch/). -For more info, see the [Monitoring, Alerting, and Logging docs](../05-monitoring-alerting-logging/01-intro.md). +For more info, see the [Monitoring, Alerting, and Logging docs](05-monitoring-alerting-logging/01-intro.md). ## DNS and TLS @@ -135,11 +135,11 @@ We have configured security best practices in every aspect of this infrastructur - **Network security**: see [VPCs and subnets](#vpcs-and-subnets). -- **Server access**: see SSH and VPN sections of the [Authentication docs](../02-authenticate/01-intro.md). +- **Server access**: see SSH and VPN sections of the [Authentication docs](02-authenticate/01-intro.md). -- **Application secrets**: see secrets management section of the [Deploy your Apps docs](../03-deploy-apps/01-intro.md). +- **Application secrets**: see secrets management section of the [Deploy your Apps docs](03-deploy-apps/01-intro.md). -- **User accounts**: see the [Authentication docs](../authenticate/setting-up-initial-access). +- **User accounts**: see the [Authentication docs](02-authenticate/02-setting-up-initial-access.md). - **Auditing**: see the [CloudTrail](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/cloudtrail) and [AWS Config](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/aws-config) modules. @@ -155,4 +155,4 @@ for more info. ## Next steps -Next up, let's have a look at [how to authenticate](../authenticate/intro). +Next up, let's have a look at [how to authenticate](02-authenticate/01-intro.md). diff --git a/_docs-sources/guides/welcome.md b/_docs-sources/guides/welcome.md index 88801bd109..775cd609e9 100644 --- a/_docs-sources/guides/welcome.md +++ b/_docs-sources/guides/welcome.md @@ -1,10 +1,15 @@ --- -"sidebar_label": "Introduction" -"sidebar_position": 1 +sidebar_label: "Introduction" +sidebar_position": 1 +hide_table_of_contents: true +hide_title: true --- import Card from "/src/components/Card" import Grid from "/src/components/Grid" +import CenterLayout from "/src/components/CenterLayout" + + # Gruntwork Guides @@ -13,16 +18,74 @@ As a Gruntwork subscriber, you have two primary ways to engage with our library. Learn how to use and administer a Reference Architecture which Gruntwork has deployed for you. Learn how to utilize our service modules to construct a world-class architecture on your own. + +## Build Your Own Architecture + +The Gruntwork IaC library empowers you to construct your own bespoke architecture in record time. By mix-and-matching our modules and services you can quickly define a custom architecture to suit your needs, all with the confidence of having world-class, battle-tested code running under the hood. This series of guides aims to teach you how to configure and deploy some of our most popular services. Additional guides will be added over time, but the principles covered extend to the rest of the IaC library. If you have trouble, don’t hesitate to ask questions via our [support channels](/docs/guides/support). + +### Follow Our Step-By-Step Guides + + + + Set up a multi-account structure using Gruntwork Landing Zone. + + + Implement continuous deployment for your infrastructure code with Gruntwork + Pipelines. + + + Set up your network according to industry best practices using our VPC service. + + + Deploy a Kubernetes Cluster to host all of your apps and services. + + + Make your infrastructure compliant with the CIS AWS Foundations Benchmark. + + + +### Dig Into the Code + + + + View the API reference for our entire service catalog to learn what’s + available. + + + If you're the type who likes to jump straight to the source, this is for + you. + + + + diff --git a/docs/guides/reference-architecture/01-overview/overview.md b/docs/guides/reference-architecture/index.md similarity index 93% rename from docs/guides/reference-architecture/01-overview/overview.md rename to docs/guides/reference-architecture/index.md index de67d69302..b227eb07a6 100644 --- a/docs/guides/reference-architecture/01-overview/overview.md +++ b/docs/guides/reference-architecture/index.md @@ -2,7 +2,7 @@ pagination_label: Reference Architecture --- -# Architecture Overview +# Setting Up Your Reference Architecture This documentation contains an overview of a deployed and managed architecture. @@ -56,7 +56,7 @@ The list of accounts includes: - **shared-services**: DevOps tooling. - **logs**: An account for centralizing logs from all of the accounts. -Check out the [Authentication docs](../02-authenticate/01-intro.md) for more info on how to authenticate to these accounts and +Check out the [Authentication docs](02-authenticate/01-intro.md) for more info on how to authenticate to these accounts and switch between them. ## VPCs and subnets @@ -105,21 +105,21 @@ VPN client, you are "in the network", and will be able to access the private res to your EC2 Instances). For more info, see the [`openvpn` service](https://github.com/gruntwork-io/terraform-aws-service-catalog/tree/master/modules/mgmt/openvpn-server) and the VPN -section of the [Authentication docs](../02-authenticate/06-authenticate-to-the-vpn-server.md). +section of the [Authentication docs](02-authenticate/06-authenticate-to-the-vpn-server.md). ## GitHub We have set up [GitHub](https://github.com) as a Continuous Integration (CI) server. After every commit, a GitHub job runs your build, tests, packaging, and automated deployment steps. -For more info, see the [Gruntwork Pipelines docs](../04-configure-gw-pipelines/01-intro.md). +For more info, see the [Gruntwork Pipelines docs](04-configure-gw-pipelines/01-intro.md). ## Monitoring, log aggregation, alerting You can find metrics, log files from all your servers, and subscribe to alert notifications using [Amazon CloudWatch](https://aws.amazon.com/cloudwatch/). -For more info, see the [Monitoring, Alerting, and Logging docs](../05-monitoring-alerting-logging/01-intro.md). +For more info, see the [Monitoring, Alerting, and Logging docs](05-monitoring-alerting-logging/01-intro.md). ## DNS and TLS @@ -135,11 +135,11 @@ We have configured security best practices in every aspect of this infrastructur - **Network security**: see [VPCs and subnets](#vpcs-and-subnets). -- **Server access**: see SSH and VPN sections of the [Authentication docs](../02-authenticate/01-intro.md). +- **Server access**: see SSH and VPN sections of the [Authentication docs](02-authenticate/01-intro.md). -- **Application secrets**: see secrets management section of the [Deploy your Apps docs](../03-deploy-apps/01-intro.md). +- **Application secrets**: see secrets management section of the [Deploy your Apps docs](03-deploy-apps/01-intro.md). -- **User accounts**: see the [Authentication docs](../authenticate/setting-up-initial-access). +- **User accounts**: see the [Authentication docs](02-authenticate/02-setting-up-initial-access.md). - **Auditing**: see the [CloudTrail](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/cloudtrail) and [AWS Config](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/aws-config) modules. @@ -155,9 +155,9 @@ for more info. ## Next steps -Next up, let's have a look at [how to authenticate](../authenticate/intro). +Next up, let's have a look at [how to authenticate](02-authenticate/01-intro.md). diff --git a/docs/guides/welcome.md b/docs/guides/welcome.md index cbea9b57b6..8172fae1ff 100644 --- a/docs/guides/welcome.md +++ b/docs/guides/welcome.md @@ -1,10 +1,15 @@ --- -"sidebar_label": "Introduction" -"sidebar_position": 1 +sidebar_label: "Introduction" +sidebar_position": 1 +hide_table_of_contents: true +hide_title: true --- import Card from "/src/components/Card" import Grid from "/src/components/Grid" +import CenterLayout from "/src/components/CenterLayout" + + # Gruntwork Guides @@ -13,21 +18,79 @@ As a Gruntwork subscriber, you have two primary ways to engage with our library. Learn how to use and administer a Reference Architecture which Gruntwork has deployed for you. Learn how to utilize our service modules to construct a world-class architecture on your own. +## Build Your Own Architecture + +The Gruntwork IaC library empowers you to construct your own bespoke architecture in record time. By mix-and-matching our modules and services you can quickly define a custom architecture to suit your needs, all with the confidence of having world-class, battle-tested code running under the hood. This series of guides aims to teach you how to configure and deploy some of our most popular services. Additional guides will be added over time, but the principles covered extend to the rest of the IaC library. If you have trouble, don’t hesitate to ask questions via our [support channels](/docs/guides/support). + +### Follow Our Step-By-Step Guides + + + + Set up a multi-account structure using Gruntwork Landing Zone. + + + Implement continuous deployment for your infrastructure code with Gruntwork + Pipelines. + + + Set up your network according to industry best practices using our VPC service. + + + Deploy a Kubernetes Cluster to host all of your apps and services. + + + Make your infrastructure compliant with the CIS AWS Foundations Benchmark. + + + +### Dig Into the Code + + + + View the API reference for our entire service catalog to learn what’s + available. + + + If you're the type who likes to jump straight to the source, this is for + you. + + + + + diff --git a/docusaurus.config.js b/docusaurus.config.js index 6fea808ce9..7923ba3f6b 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -28,6 +28,7 @@ const config = { favicon: "/favicon.ico", organizationName: "gruntwork-io", // Usually your GitHub org/user name. projectName: "docs", // Usually your repo name., + trailingSlash: false, stylesheets: [ "https://fonts.googleapis.com/css2?family=Source+Sans+Pro:ital,wght@0,300;0,400;0,600;0,700;1,300;1,400;1,600;1,700&display=swap", @@ -75,6 +76,7 @@ const config = { position: "left", label: "Guides", docId: "guides/welcome", + activeBasePath: "docs/guides", }, { type: "doc", diff --git a/sidebars.js b/sidebars.js index 9ea28d2bb9..31061b073c 100644 --- a/sidebars.js +++ b/sidebars.js @@ -9,199 +9,27 @@ Create as many sidebars as you want. */ +const introSidebar = require("./sidebars/intro-guide.js") +const refarchSidebar = require("./sidebars/refarch-guide.js") +// const landingZoneSidebar = require("./sidebars/landing-zone-guide.js") +// const pipelineSidebar = require("./sidebars/pipelines-guide.js") +// const vpcSidebar = require("./sidebars/vpc-guide.js") +// const kuberneteSidebar = require("./sidebars/kubernetes-guide.js") +// const complianceSidebar = require("./sidebars/compliance-guide.js") +const apiSidebars = require("./sidebars/api-reference.js") + // @ts-check /** @type {import('@docusaurus/plugin-content-docs').SidebarsConfig} */ const sidebars = { - introSidebar: [ - { - Overview: [ - "intro/overview/intro-to-gruntwork", - // Temporarily hiding the unfinished sections from the sidebar We'll put - // them back shortly and don't want to delete the pages as we know we're - // going to have these sections within a few days. - // "intro/overview/gruntwork-production-framework", - "intro/overview/how-it-works", - // "intro/overview/use-cases", - // "intro/overview/gruntwork-vs-other", - "intro/overview/getting-started", - ], - }, - { - "Core Concepts": [ - "intro/core-concepts/infrastructure-as-code", - "intro/core-concepts/immutable-infrastructure", - ], - }, - { - "Accessing the Dev Portal": [ - "intro/dev-portal/create-account", - "intro/dev-portal/invite-team", - "intro/dev-portal/link-github-id", - ], - }, - { - "Setting Up Your Environment": [ - "intro/environment-setup/recommended_tools", - ], - }, - { - "Tool Fundamentals": [ - "intro/tool-fundamentals/docker", - "intro/tool-fundamentals/packer", - "intro/tool-fundamentals/terraform", - "intro/tool-fundamentals/terragrunt", - ], - }, - { - "Deploy Your First Module": [ - "intro/first-deployment/using-terraform-modules", - "intro/first-deployment/testing", - "intro/first-deployment/deploy", - ], - }, - { - type: "doc", - id: "intro/next-steps", - }, - ], - guidesSidebar: [ - { - type: "doc", - id: "guides/welcome", - }, - { - "The Gruntwork Reference Architecture": [ - "guides/reference-architecture/overview/overview", - { - Authentication: [ - { - type: "autogenerated", - dirName: "guides/reference-architecture/02-authenticate", - }, - ], - }, - { - "Deploying Your Apps": [ - { - type: "autogenerated", - dirName: "guides/reference-architecture/03-deploy-apps", - }, - ], - }, - { - "Configure Gruntwork Pipelines": [ - { - type: "autogenerated", - dirName: - "guides/reference-architecture/04-configure-gw-pipelines", - }, - ], - }, - { - "Monitoring, Alerting & Logging": [ - { - type: "autogenerated", - dirName: - "guides/reference-architecture/05-monitoring-alerting-logging", - }, - ], - }, - { - "Adding a New Account": [ - { - type: "autogenerated", - dirName: "guides/reference-architecture/06-adding-a-new-account", - }, - ], - }, - { - "Undeploying Your Architecture": [ - { - type: "autogenerated", - dirName: "guides/reference-architecture/07-undeploy", - }, - ], - }, - ], - }, - { - "Build it Yourself": [ - { - type: "autogenerated", - dirName: "guides/build-it-yourself", - }, - ], - }, - { - "Stay Up to Date": [ - { - type: "autogenerated", - dirName: "guides/stay-up-to-date", - }, - ], - }, - ], - referenceSidebar: [ - { - type: "doc", - id: "reference/intro", - }, - { - type: "ref", - label: "Service APIs", - id: "reference/services/intro", - }, - { - type: "ref", - label: "Module APIs", - id: "reference/modules/stub", - }, - { - type: "ref", - label: "Tools", - id: "reference/tools/stub", - }, - ], - - modulesSidebar: [{ type: "autogenerated", dirName: "reference/modules" }], - servicesSidebar: [ - "reference/services/intro", - { - "App Orchestration": [ - { - type: "autogenerated", - dirName: "reference/services/app-orchestration", - }, - ], - }, - { - "CI/CD Pipeline": [ - { type: "autogenerated", dirName: "reference/services/ci-cd-pipeline" }, - ], - }, - { - "Data Storage": [ - { type: "autogenerated", dirName: "reference/services/data-storage" }, - ], - }, - { - "Landing Zone": [ - { type: "autogenerated", dirName: "reference/services/landing-zone" }, - ], - }, - { - Networking: [ - { type: "autogenerated", dirName: "reference/services/networking" }, - ], - }, - { - Security: [ - { type: "autogenerated", dirName: "reference/services/security" }, - ], - }, - ], - toolsSidebar: [{ type: "autogenerated", dirName: "reference/tools" }], + introSidebar, + refarchSidebar, + // landingZoneSidebar, + // pipelinesSidebar, + // vpcSidebar, + // kubernetesSidebar, + // complianceSidebar, + ...apiSidebars, } module.exports = sidebars diff --git a/sidebars/api-reference.js b/sidebars/api-reference.js new file mode 100644 index 0000000000..51b68fe466 --- /dev/null +++ b/sidebars/api-reference.js @@ -0,0 +1,63 @@ +const apiSidebars = { + referenceSidebar: [ + { + type: "doc", + id: "reference/intro", + }, + { + type: "ref", + label: "Service APIs", + id: "reference/services/intro", + }, + { + type: "ref", + label: "Module APIs", + id: "reference/modules/stub", + }, + { + type: "ref", + label: "Tools", + id: "reference/tools/stub", + }, + ], + modulesSidebar: [{ type: "autogenerated", dirName: "reference/modules" }], + servicesSidebar: [ + "reference/services/intro", + { + "App Orchestration": [ + { + type: "autogenerated", + dirName: "reference/services/app-orchestration", + }, + ], + }, + { + "CI/CD Pipeline": [ + { type: "autogenerated", dirName: "reference/services/ci-cd-pipeline" }, + ], + }, + { + "Data Storage": [ + { type: "autogenerated", dirName: "reference/services/data-storage" }, + ], + }, + { + "Landing Zone": [ + { type: "autogenerated", dirName: "reference/services/landing-zone" }, + ], + }, + { + Networking: [ + { type: "autogenerated", dirName: "reference/services/networking" }, + ], + }, + { + Security: [ + { type: "autogenerated", dirName: "reference/services/security" }, + ], + }, + ], + toolsSidebar: [{ type: "autogenerated", dirName: "reference/tools" }], +} + +module.exports = apiSidebars diff --git a/sidebars/intro-guide.js b/sidebars/intro-guide.js new file mode 100644 index 0000000000..1997f6aa54 --- /dev/null +++ b/sidebars/intro-guide.js @@ -0,0 +1,54 @@ +const introSidebar = [ + { + Overview: [ + "intro/overview/intro-to-gruntwork", + "intro/overview/how-it-works", + // Temporarily hiding the unfinished sections from the sidebar We'll put + // them back shortly and don't want to delete the pages as we know we're + // going to have these sections within a few days. + // "intro/overview/gruntwork-production-framework", + // "intro/overview/use-cases", + // "intro/overview/gruntwork-vs-other", + "intro/overview/getting-started", + ], + }, + { + "Core Concepts": [ + "intro/core-concepts/infrastructure-as-code", + "intro/core-concepts/immutable-infrastructure", + ], + }, + { + "Accessing the Dev Portal": [ + "intro/dev-portal/create-account", + "intro/dev-portal/invite-team", + "intro/dev-portal/link-github-id", + ], + }, + { + "Setting Up Your Environment": [ + "intro/environment-setup/recommended_tools", + ], + }, + { + "Tool Fundamentals": [ + "intro/tool-fundamentals/docker", + "intro/tool-fundamentals/packer", + "intro/tool-fundamentals/terraform", + "intro/tool-fundamentals/terragrunt", + ], + }, + { + "Deploy Your First Module": [ + "intro/first-deployment/using-terraform-modules", + "intro/first-deployment/testing", + "intro/first-deployment/deploy", + ], + }, + { + type: "doc", + id: "intro/next-steps", + }, +] + +module.exports = introSidebar diff --git a/sidebars/refarch-guide.js b/sidebars/refarch-guide.js new file mode 100644 index 0000000000..5b19b3ee82 --- /dev/null +++ b/sidebars/refarch-guide.js @@ -0,0 +1,71 @@ +const refarchSidebar = [ + { + label: "Reference Architecture Guide", + type: "category", + link: { + type: "doc", + id: "guides/reference-architecture/index", + }, + items: [ + { + Authentication: [ + "guides/reference-architecture/authenticate/intro", + "guides/reference-architecture/authenticate/setting-up-initial-access", + "guides/reference-architecture/authenticate/authenticate-to-the-aws-web-console", + "guides/reference-architecture/authenticate/authenticate-to-aws-via-the-cli", + "guides/reference-architecture/authenticate/authenticate-to-ec2-instances-via-ssh", + "guides/reference-architecture/authenticate/authenticate-to-the-vpn-server", + ], + }, + { + "Deploying Your Apps": [ + "guides/reference-architecture/deploy-apps/intro", + "guides/reference-architecture/deploy-apps/what-is-already-deployed", + "guides/reference-architecture/deploy-apps/the-app", + "guides/reference-architecture/deploy-apps/dockerizing", + "guides/reference-architecture/deploy-apps/publish-docker-image", + ], + }, + { + "Configure Gruntwork Pipelines": [ + "guides/reference-architecture/configure-gw-pipelines/intro", + "guides/reference-architecture/configure-gw-pipelines/ci--cd-pipeline-for-infrastructure-code", + "guides/reference-architecture/configure-gw-pipelines/ci--cd-pipeline-for-app-code", + "guides/reference-architecture/configure-gw-pipelines/update-the-ci--cd-pipeline-itself", + ], + }, + { + "Monitoring, Alerting & Logging": [ + "guides/reference-architecture/monitoring-alerting-logging/intro", + "guides/reference-architecture/monitoring-alerting-logging/metrics", + "guides/reference-architecture/monitoring-alerting-logging/alerts", + "guides/reference-architecture/monitoring-alerting-logging/logs", + ], + }, + { + "Adding a New Account": [ + "guides/reference-architecture/adding-a-new-account/intro", + "guides/reference-architecture/adding-a-new-account/create-new-account-in-your-aws-org", + "guides/reference-architecture/adding-a-new-account/update-logs-security-shared-accounts-to-allow-cross-account-access", + "guides/reference-architecture/adding-a-new-account/deploy-the-security-baseline", + "guides/reference-architecture/adding-a-new-account/deploy-the-ecs-deploy-runner", + ], + }, + { + "Undeploying Your Architecture": [ + "guides/reference-architecture/undeploy/intro", + "guides/reference-architecture/undeploy/before-you-get-started", + "guides/reference-architecture/undeploy/pre-requisite-force-destroy-on-s3-buckets", + "guides/reference-architecture/undeploy/pre-requisite-understand-module-dependencies", + "guides/reference-architecture/undeploy/manually-undeploying-a-single-module", + "guides/reference-architecture/undeploy/manually-undeploying-multiple-modules-or-an-entire-environment", + "guides/reference-architecture/undeploy/removing-the-terraform-state", + "guides/reference-architecture/undeploy/useful-tips", + "guides/reference-architecture/undeploy/known-errors", + ], + }, + ], + }, +] + +module.exports = refarchSidebar From 7559d184556724bbf71f90eb0104e07b591ac5e3 Mon Sep 17 00:00:00 2001 From: Eben Eliason Date: Tue, 11 Jan 2022 14:15:58 -0800 Subject: [PATCH 02/20] Fix refarch links, remove unused features component --- .../02-authenticate/01-intro.md | 12 +- _docs-sources/intro/next-steps.mdx | 4 +- .../02-authenticate/01-intro.md | 14 +-- docs/intro/next-steps.mdx | 6 +- src/components/HomepageFeatures.module.css | 15 --- src/components/HomepageFeatures.tsx | 107 ------------------ src/pages/index.tsx | 2 +- 7 files changed, 19 insertions(+), 141 deletions(-) delete mode 100644 src/components/HomepageFeatures.module.css delete mode 100644 src/components/HomepageFeatures.tsx diff --git a/_docs-sources/guides/reference-architecture/02-authenticate/01-intro.md b/_docs-sources/guides/reference-architecture/02-authenticate/01-intro.md index 2a89b75b42..00bdb02d14 100644 --- a/_docs-sources/guides/reference-architecture/02-authenticate/01-intro.md +++ b/_docs-sources/guides/reference-architecture/02-authenticate/01-intro.md @@ -5,24 +5,24 @@ title: Intro # Authentication -In the last section, you got a basic [overview of the architecture](../01-overview/overview.md), including learning that there is +In the last section, you got a basic [overview of the architecture](../index.md), including learning that there is a variety of infrastructure deployed across multiple AWS accounts. In this section, you'll learn about authenticating and connecting to all the resources in your AWS accounts: -* [Set up initial access](./02-setting-up-initial-access.md): If this is your first time using this infrastructure—that is, +- [Set up initial access](./02-setting-up-initial-access.md): If this is your first time using this infrastructure—that is, if Gruntwork just deployed and handed over the Reference Architecture to you—go through this section first! -* [Authenticate to the AWS Web Console](./03-authenticate-to-the-aws-web-console.md): Learn how to access each of your AWS +- [Authenticate to the AWS Web Console](./03-authenticate-to-the-aws-web-console.md): Learn how to access each of your AWS accounts using a web browser. Since all the infrastructure is managed as code, you shouldn't be making many changes from the web console, but it's still useful for debugging, troubleshooting, learning, and looking at metrics, and logs. -* [Authenticate to AWS via the CLI](./04-authenticate-to-aws-via-the-cli.md): Learn how to access each of your AWS accounts +- [Authenticate to AWS via the CLI](./04-authenticate-to-aws-via-the-cli.md): Learn how to access each of your AWS accounts from the command line. You'll need this to work with CLI tools such as the `aws`, `terraform`, `terragrunt`, and `packer`. -* [Authenticate to the VPN server](./06-authenticate-to-the-vpn-server.md): Just about all of the infrastructure is deployed +- [Authenticate to the VPN server](./06-authenticate-to-the-vpn-server.md): Just about all of the infrastructure is deployed in private subnets, so it is not accessible directly from the public Internet. To be able to SSH to an EC2 instance or connect to a database, you'll first need to get "inside" the networking by connecting to the VPN server. -* [Authenticate to EC2 Instances via SSH](./05-authenticate-to-ec2-instances-via-ssh.md): If you need to debug something on +- [Authenticate to EC2 Instances via SSH](./05-authenticate-to-ec2-instances-via-ssh.md): If you need to debug something on an EC2 instance, you'll need to connect over SSH. diff --git a/_docs-sources/intro/next-steps.mdx b/_docs-sources/intro/next-steps.mdx index 7e668d717c..5163d11b29 100644 --- a/_docs-sources/intro/next-steps.mdx +++ b/_docs-sources/intro/next-steps.mdx @@ -7,12 +7,12 @@ import Grid from "/src/components/Grid" # Next Steps -Now that your foundational knowledge is in place and your workspace is configured, you’re ready to dive in and learn how to deploy production-grade infrastructure. If you’ve purchased a Gruntwork Reference Architecture, use [this guide](/docs/guides/reference-architecture/overview/overview) to get started. Otherwise, view our [courses](/docs/courses) and [guides](/docs/guides/welcome), or check out the [Service Catalog API reference](/docs/reference/services/intro) to learn what’s available. +Now that your foundational knowledge is in place and your workspace is configured, you’re ready to dive in and learn how to deploy production-grade infrastructure. If you’ve purchased a Gruntwork Reference Architecture, use [this guide](/docs/guides/reference-architecture) to get started. Otherwise, view our [courses](/docs/courses) and [guides](/docs/guides/welcome), or check out the [Service Catalog API reference](/docs/reference/services/intro) to learn what’s available. Learn how to use and administer a Reference Architecture which Gruntwork has deployed for you. diff --git a/docs/guides/reference-architecture/02-authenticate/01-intro.md b/docs/guides/reference-architecture/02-authenticate/01-intro.md index 3a7f1fb3fc..715af8830a 100644 --- a/docs/guides/reference-architecture/02-authenticate/01-intro.md +++ b/docs/guides/reference-architecture/02-authenticate/01-intro.md @@ -5,29 +5,29 @@ title: Intro # Authentication -In the last section, you got a basic [overview of the architecture](../01-overview/overview.md), including learning that there is +In the last section, you got a basic [overview of the architecture](../index.md), including learning that there is a variety of infrastructure deployed across multiple AWS accounts. In this section, you'll learn about authenticating and connecting to all the resources in your AWS accounts: -* [Set up initial access](./02-setting-up-initial-access.md): If this is your first time using this infrastructure—that is, +- [Set up initial access](./02-setting-up-initial-access.md): If this is your first time using this infrastructure—that is, if Gruntwork just deployed and handed over the Reference Architecture to you—go through this section first! -* [Authenticate to the AWS Web Console](./03-authenticate-to-the-aws-web-console.md): Learn how to access each of your AWS +- [Authenticate to the AWS Web Console](./03-authenticate-to-the-aws-web-console.md): Learn how to access each of your AWS accounts using a web browser. Since all the infrastructure is managed as code, you shouldn't be making many changes from the web console, but it's still useful for debugging, troubleshooting, learning, and looking at metrics, and logs. -* [Authenticate to AWS via the CLI](./04-authenticate-to-aws-via-the-cli.md): Learn how to access each of your AWS accounts +- [Authenticate to AWS via the CLI](./04-authenticate-to-aws-via-the-cli.md): Learn how to access each of your AWS accounts from the command line. You'll need this to work with CLI tools such as the `aws`, `terraform`, `terragrunt`, and `packer`. -* [Authenticate to the VPN server](./06-authenticate-to-the-vpn-server.md): Just about all of the infrastructure is deployed +- [Authenticate to the VPN server](./06-authenticate-to-the-vpn-server.md): Just about all of the infrastructure is deployed in private subnets, so it is not accessible directly from the public Internet. To be able to SSH to an EC2 instance or connect to a database, you'll first need to get "inside" the networking by connecting to the VPN server. -* [Authenticate to EC2 Instances via SSH](./05-authenticate-to-ec2-instances-via-ssh.md): If you need to debug something on +- [Authenticate to EC2 Instances via SSH](./05-authenticate-to-ec2-instances-via-ssh.md): If you need to debug something on an EC2 instance, you'll need to connect over SSH. diff --git a/docs/intro/next-steps.mdx b/docs/intro/next-steps.mdx index 7ddf041501..f9200ab764 100644 --- a/docs/intro/next-steps.mdx +++ b/docs/intro/next-steps.mdx @@ -7,12 +7,12 @@ import Grid from "/src/components/Grid" # Next Steps -Now that your foundational knowledge is in place and your workspace is configured, you’re ready to dive in and learn how to deploy production-grade infrastructure. If you’ve purchased a Gruntwork Reference Architecture, use [this guide](/docs/guides/reference-architecture/overview/overview) to get started. Otherwise, view our [courses](/docs/courses) and [guides](/docs/guides/welcome), or check out the [Service Catalog API reference](/docs/reference/services/intro) to learn what’s available. +Now that your foundational knowledge is in place and your workspace is configured, you’re ready to dive in and learn how to deploy production-grade infrastructure. If you’ve purchased a Gruntwork Reference Architecture, use [this guide](/docs/guides/reference-architecture) to get started. Otherwise, view our [courses](/docs/courses) and [guides](/docs/guides/welcome), or check out the [Service Catalog API reference](/docs/reference/services/intro) to learn what’s available. Learn how to use and administer a Reference Architecture which Gruntwork has deployed for you. @@ -28,5 +28,5 @@ Now that your foundational knowledge is in place and your workspace is configure diff --git a/src/components/HomepageFeatures.module.css b/src/components/HomepageFeatures.module.css deleted file mode 100644 index dfda7c3df2..0000000000 --- a/src/components/HomepageFeatures.module.css +++ /dev/null @@ -1,15 +0,0 @@ -.features { - display: flex; - align-items: center; - padding: 4rem 0; - width: 100%; -} - -.featureSvg { - height: 200px; - width: 200px; -} - -main { - margin: 0; -} diff --git a/src/components/HomepageFeatures.tsx b/src/components/HomepageFeatures.tsx deleted file mode 100644 index 26bf45082b..0000000000 --- a/src/components/HomepageFeatures.tsx +++ /dev/null @@ -1,107 +0,0 @@ -/** - * Copyright (c) Facebook, Inc. and its affiliates. - * - * This source code is licensed under the MIT license found in the - * LICENSE file in the root directory of this source tree. - */ -import React from 'react'; -import clsx from 'clsx'; -import styles from './HomepageFeatures.module.css'; - -type FeatureItem = { - title: string; - description: JSX.Element; - image?: string; - docId?: string; -}; - -const FeatureList: FeatureItem[] = [ - { - title: 'Set Up Your Accounts', - docId: '/docs/guides/build-it-yourself/landing-zone', - description: ( - <> - Streamline how you create, configure, and secure AWS accounts and multi-account structures. - - ), - }, - { - title: 'Configure a CI/CD Pipeline', - docId: '/docs/guides/build-it-yourself/pipelines', - description: ( - <> - Use your preferred CI tool to set up an end‑to‑end pipeline for your infrastructure code. - - ), - }, - { - title: 'Achieve Compliance', - docId: '/docs/guides/build-it-yourself/compliance', - description: ( - <> - Implement the CIS AWS Foundations Benchmark using our curated collection of modules and services. - - ), - }, - { - title: 'The Reference Architecture', - docId: '/docs/guides/reference-architecture/overview/overview', - description: ( - <> - Bootstrap your infrastructure in about a day by letting Gruntwork deploy a Reference Architecture customized just for you. - - ), - }, - { - title: 'Deploy a Service', - docId: '/docs/guides/build-it-yourself/overview', - description: ( - <> - Learn how to deploy Gruntwork services to construct your own bespoke architecture. - - ), - }, - { - title: 'Courses', - docId: '/courses', - description: ( - <> - Learn DevOps fundamentals with our series of introductory video tutorials. - - ), - }, -]; - -function Feature({title, image, description, docId}: FeatureItem) { - return ( -
- { image && ( -
- {title} -
- )} -
- {docId ? ( -

{title}

- ) : ( -

{title}

) - } -

{description}

-
-
- ); -} - -export default function HomepageFeatures(): JSX.Element { - return ( -
-
-
- {FeatureList.map((props, idx) => ( - - ))} -
-
-
- ); -} diff --git a/src/pages/index.tsx b/src/pages/index.tsx index 2627924677..4950f204de 100644 --- a/src/pages/index.tsx +++ b/src/pages/index.tsx @@ -46,7 +46,7 @@ export default function Home(): JSX.Element { Bought a Reference Architecture? Get your new infrastructure up From 02e3ab0943f578c82f80e89ddfecb14d52b5f38b Mon Sep 17 00:00:00 2001 From: Eugene K Date: Wed, 12 Jan 2022 12:01:04 -0500 Subject: [PATCH 03/20] Huge commit - removed the numerically filenames and correct all links --- ...are-your-infrastructure-live-repository.md | 8 ------ .../_category_.json | 0 .../core-concepts}/_category_.json | 0 .../core-concepts/intro.md} | 0 .../core-concepts/recommendation-sections.md} | 0 .../deployment-walkthrough}/_category_.json | 0 ...create-an-iam-user-in-the-root-account.md} | 0 .../create-the-root-account.md} | 0 .../create-vpc-flow-logs.md} | 0 .../_category_.json | 0 ...y-account-baseline-app-to-logs-account.md} | 0 ...t-baseline-app-to-other-child-accounts.md} | 2 +- ...-account-baseline-root-to-root-account.md} | 2 +- ...-baseline-security-to-security-account.md} | 0 .../enable-key-rotation-for-kms-keys.md} | 0 ...liance-by-following-iam-best-practices.md} | 0 ...ce-by-following-logging-best-practices.md} | 0 ...ce-by-following-storage-best-practices.md} | 4 +-- .../use-iam-roles-for-ec2-instances.md} | 0 .../deployment-approach.md} | 2 +- .../lock-down-the-root-account-iam-users.md} | 0 .../lock-down-the-root-user.md} | 0 .../deployment-walkthrough/pre-requisites.md} | 2 +- ...are-your-infrastructure-live-repository.md | 8 ++++++ .../the-gruntwork-solution.md} | 0 .../intro}/_category_.json | 0 ...t-is-the-cis-aws-foundations-benchmark.md} | 0 .../intro/what-youll-learn-in-this-guide.md} | 4 +-- .../next-steps.md} | 0 .../production-grade-design}/_category_.json | 0 .../identity-and-access-management.md} | 26 +++++++++++++---- .../production-grade-design/intro.md} | 2 +- .../production-grade-design/logging.md} | 0 .../production-grade-design/monitoring.md} | 0 .../production-grade-design/networking.md} | 0 .../production-grade-design/storage.md} | 4 +-- .../traceability-matrix.md} | 0 .../_category_.json | 0 .../core-concepts}/_category_.json | 0 .../interacting-with-kubernetes.md} | 0 .../kubernetes-access-control.md} | 0 .../core-concepts/kubernetes-architecture.md} | 0 .../core-concepts/kubernetes-resources.md} | 0 .../options-for-running-kubernetes-in-aws.md} | 0 .../core-concepts/why-kubernetes.md} | 0 .../10-try-out-the-cluster.md | 0 .../11-updating-the-worker-nodes.md | 0 .../deployment-walkthrough}/_category_.json | 0 ...-to-the-control-plane-and-worker-nodes.md} | 0 ...etrics-and-alarms-for-the-worker-nodes.md} | 0 .../configure-role-mapping.md} | 0 .../configure-the-control-plane.md} | 0 ...igure-the-worker-node-user-data-script.md} | 0 .../configure-the-worker-nodes.md} | 0 .../create-the-worker-node-ami.md} | 0 .../deploy-the-eks-cluster.md} | 0 .../deployment-walkthrough/deploy-the-vpc.md} | 2 +- .../deployment-walkthrough/pre-requisites.md} | 2 +- .../intro}/_category_.json | 0 .../intro/what-is-kubernetes.md} | 0 .../intro/what-youll-learn-in-this-guide.md} | 0 .../next-steps.md} | 0 .../production-grade-design}/_category_.json | 0 .../production-grade-design/authenticate.md} | 0 .../production-grade-design/control-plane.md} | 4 +-- .../iam-role-mapping-and-rbac.md} | 0 .../production-grade-design/intro.md} | 0 .../production-grade-design/logging.md} | 0 .../protecting-pods.md} | 0 .../production-grade-design/use-eks.md} | 0 .../vpc-configuration.md} | 2 +- .../production-grade-design/worker-nodes.md} | 2 +- .../_category_.json | 0 .../core-concepts}/_category_.json | 0 .../core-concepts/aws-account.md} | 0 .../core-concepts/aws-config.md} | 0 .../core-concepts/aws-organizations.md} | 0 .../core-concepts/cloud-trail.md} | 0 .../federated-authentication.md} | 0 .../core-concepts/guard-duty.md} | 0 .../core-concepts/iam-groups.md} | 0 .../core-concepts/iam-policies.md} | 0 .../core-concepts/iam-roles.md} | 26 ++++------------- .../core-concepts/iam-users.md} | 0 .../core-concepts/root-user.md} | 0 .../deployment-walkthrough}/_category_.json | 0 ...-security-baseline-to-the-logs-account.md} | 0 ...y-baseline-to-the-other-child-accounts.md} | 0 ...-security-baseline-to-the-root-account.md} | 0 ...urity-baseline-to-the-security-account.md} | 0 ...security-baseline-for-the-root-account.md} | 0 ...create-an-iam-user-in-the-root-account.md} | 0 .../create-the-root-account.md} | 0 ...-the-root-account-into-terraform-state.md} | 0 .../lock-down-the-root-account-iam-users.md} | 0 ...wn-the-root-user-in-the-child-accounts.md} | 0 .../lock-down-the-root-user.md} | 0 .../deployment-walkthrough/pre-requisites.md} | 0 ...re-your-infrastructure-live-repository.md} | 0 ...ot-user-password-in-each-child-account.md} | 0 ...g-as-an-iam-user-to-the-child-accounts.md} | 0 .../intro}/_category_.json | 0 ...k-aws-landing-zone-vs-the-alternatives.md} | 0 .../what-is-an-aws-account-structure.md} | 0 .../intro/what-youll-learn-in-this-guide.md} | 0 .../next-steps.md} | 2 +- .../production-grade-design}/_category_.json | 0 .../production-grade-design/aws-config.md} | 0 .../child-accounts.md} | 0 .../production-grade-design/cloud-trail.md} | 0 .../federated-auth.md} | 0 .../production-grade-design/guard-duty.md} | 0 .../iam-roles-for-services.md} | 4 +-- .../iam-roles-for-users.md} | 0 .../iam-users-and-groups.md} | 0 .../production-grade-design/intro.md} | 0 .../production-grade-design/mfa-policy.md} | 0 .../password-policy.md} | 2 +- .../the-root-account.md} | 0 .../{1-overview.md => overview.md} | 0 .../_category_.json | 0 .../core-concepts}/_category_.json | 0 .../core-concepts/ci-cd-platforms.md} | 0 .../core-concepts/ci-cd-workflows.md} | 0 .../core-concepts/threat-model-of-ci-cd.md} | 0 .../trunk-based-development-model.md} | 0 .../types-of-infrastructure-code.md} | 0 .../why-is-it-important-to-have-ci-cd.md} | 0 .../deployment-walkthrough}/_category_.json | 0 .../configure-ci-server.md} | 0 .../define-pipeline-as-code.md} | 0 .../deployment-walkthrough/deploy-a-vpc.md} | 2 +- .../deploy-the-ecs-deploy-runner.md} | 0 .../deployment-walkthrough/pre-requisites.md} | 23 ++++++++------- .../try-out-the-ecs-deploy-runner.md} | 0 .../intro}/_category_.json | 0 ...us-integration-and-continuous-delivery.md} | 0 .../intro/what-this-guide-will-not-cover.md} | 0 .../intro/what-youll-learn-in-this-guide.md} | 0 .../next-steps.md} | 0 .../production-grade-design}/_category_.json | 0 .../production-grade-design/intro.md} | 0 .../limit-triggers-for-deploy-server.md} | 0 .../lock-down-vcs-systems.md} | 0 .../options-for-deploy-server.md} | 0 .../summary-of-deployment-sequence.md} | 0 .../summary-of-mitigations.md} | 0 .../use-a-vpc-to-lock-down-deploy-server.md} | 2 +- .../use-approval-flows.md} | 2 +- ...e-deployments-from-within-your-account.md} | 2 +- ...nimal-iam-permissions-for-a-deployment.md} | 0 .../{4-vpc => vpc}/_category_.json | 0 .../core-concepts}/_category_.json | 0 .../core-concepts/cidr-notation.md} | 0 .../default-vp-cs-and-custom-vp-cs.md} | 2 +- ...ays-public-subnets-and-private-subnets.md} | 0 .../core-concepts/nat-gateways.md} | 0 .../core-concepts/network-ac-ls.md} | 0 .../regions-and-availability-zones.md} | 0 .../core-concepts/route-tables.md} | 0 .../core-concepts/security-groups.md} | 0 .../core-concepts/subnets.md} | 0 .../core-concepts/vpc-endpoints.md} | 0 .../core-concepts/vpc-ip-addresses.md} | 0 .../core-concepts/vpc-peering.md} | 0 .../deployment-walkthrough}/_category_.json | 0 ...n-up-default-vp-cs-and-security-groups.md} | 0 .../deploy-a-bastion-host.md} | 0 .../deploy-a-management-vpc.md} | 0 .../deploy-application-vp-cs.md} | 0 .../deployment-walkthrough/pre-requisites.md} | 2 +- .../0-intro => vpc/intro}/_category_.json | 0 .../intro/what-is-a-vpc.md} | 0 .../intro/what-youll-learn-in-this-guide.md} | 0 .../4-next-steps.md => vpc/next-steps.md} | 2 +- .../production-grade-design}/_category_.json | 0 .../production-grade-design/bastion-host.md} | 2 +- .../defense-in-depth.md} | 0 .../internet-gateways-and-nat-gateways.md} | 0 .../production-grade-design/intro.md} | 0 .../multiple-aws-accounts.md} | 2 +- .../multiple-subnet-tiers.md} | 0 .../multiple-vp-cs.md} | 0 .../security-groups-and-nac-ls.md} | 0 .../{1-cis => cis}/_category_.json | 0 .../how-to-update-to-cis-13}/_category_.json | 0 .../how-to-update-to-cis-13/core-concepts.md} | 0 .../deployment-walkthrough}/_category_.json | 0 ...untwork-infrastructure-as-code-library.md} | 0 .../step-2-manual-steps.md} | 0 .../step-3-deploy-new-modules.md} | 8 +++--- .../how-to-update-to-cis-13/intro.md} | 8 +++--- .../how-to-update-to-cis-14}/_category_.json | 0 .../how-to-update-to-cis-14/core-concepts.md} | 2 +- .../deployment-walkthrough}/_category_.json | 0 ...untwork-infrastructure-as-code-library.md} | 0 ...-2-update-the-account-baseline-modules.md} | 16 +++++------ .../step-3-manual-steps.md} | 16 +++++------ .../how-to-update-to-cis-14/finally.md} | 0 .../how-to-update-to-cis-14/intro.md} | 8 +++--- .../_category_.json | 0 .../core-concepts.md} | 0 .../deployment-walkthrough}/_category_.json | 0 .../deployment-walkthrough/intro.md} | 0 .../optional-even-dryer-configuration.md} | 0 ...-common-configurations-for-a-component.md} | 10 +++---- ...e-catalog-based-reference-architecture.md} | 0 .../intro.md} | 4 +-- .../_category_.json | 0 .../core-concepts.md} | 0 .../deployment-walkthrough.md} | 6 ++-- .../intro.md} | 6 ++-- .../_category_.json | 0 .../core-concepts.md} | 0 .../deployment-walkthrough}/_category_.json | 0 ...e-to-be-compatible-with-terraform-0-15.md} | 8 +++--- ...untwork-infrastructure-as-code-library.md} | 0 .../intro.md} | 6 ++-- .../_category_.json | 0 .../deployment-walkthrough.md} | 12 ++++---- .../intro.md} | 0 .../version-compatibility-table.md} | 0 .../_category_.json | 0 .../core-concepts.md} | 4 +-- .../deployment-walkthrough}/_category_.json | 0 ...e-to-be-compatible-with-terraform-0-12.md} | 2 +- ...e-to-be-compatible-with-terraform-0-13.md} | 0 ...untwork-infrastructure-as-code-library.md} | 0 ...ference-architecture-to-terraform-0-13.md} | 2 +- .../intro.md} | 8 +++--- .../_category_.json | 0 .../core-concepts.md} | 2 +- .../deployment-walkthrough}/_category_.json | 0 ...e-to-be-compatible-with-terraform-0-13.md} | 4 +-- ...e-to-be-compatible-with-terraform-0-14.md} | 0 ...untwork-infrastructure-as-code-library.md} | 0 .../step-4-start-using-lock-files.md} | 0 .../intro.md} | 6 ++-- .../_category_.json | 0 .../core-concepts.md} | 0 .../deployment-walkthrough}/_category_.json | 0 ...e-to-be-compatible-with-terraform-0-14.md} | 6 ++-- ...e-to-be-compatible-with-terraform-0-15.md} | 0 ...untwork-infrastructure-as-code-library.md} | 0 .../intro.md} | 6 ++-- .../0-intro/_category_.json | 3 -- .../1-core-concepts/_category_.json | 3 -- .../2-production-grade-design/_category_.json | 3 -- ...are-your-infrastructure-live-repository.md | 13 --------- .../_category_.json | 3 -- .../6-achieve-compliance/_category_.json | 3 -- .../_category_.json | 0 .../core-concepts}/_category_.json | 0 .../core-concepts/intro.md} | 0 .../core-concepts/recommendation-sections.md} | 0 .../deployment-walkthrough}/_category_.json | 0 ...create-an-iam-user-in-the-root-account.md} | 0 .../create-the-root-account.md} | 0 .../create-vpc-flow-logs.md} | 0 .../_category_.json | 0 ...y-account-baseline-app-to-logs-account.md} | 0 ...t-baseline-app-to-other-child-accounts.md} | 4 +-- ...-account-baseline-root-to-root-account.md} | 4 +-- ...-baseline-security-to-security-account.md} | 0 .../enable-key-rotation-for-kms-keys.md} | 0 ...liance-by-following-iam-best-practices.md} | 0 ...ce-by-following-logging-best-practices.md} | 0 ...ce-by-following-storage-best-practices.md} | 6 ++-- .../use-iam-roles-for-ec2-instances.md} | 0 .../deployment-approach.md} | 4 +-- .../lock-down-the-root-account-iam-users.md} | 0 .../lock-down-the-root-user.md} | 0 .../deployment-walkthrough/pre-requisites.md} | 4 +-- ...are-your-infrastructure-live-repository.md | 13 +++++++++ .../the-gruntwork-solution.md} | 0 .../intro}/_category_.json | 0 ...t-is-the-cis-aws-foundations-benchmark.md} | 0 .../intro/what-youll-learn-in-this-guide.md} | 6 ++-- .../next-steps.md} | 0 .../production-grade-design}/_category_.json | 0 .../identity-and-access-management.md} | 28 ++++++++++++++----- .../production-grade-design/intro.md} | 4 +-- .../production-grade-design/logging.md} | 0 .../production-grade-design/monitoring.md} | 0 .../production-grade-design/networking.md} | 0 .../production-grade-design/storage.md} | 6 ++-- .../traceability-matrix.md} | 0 .../_category_.json | 0 .../core-concepts}/_category_.json | 0 .../interacting-with-kubernetes.md} | 0 .../kubernetes-access-control.md} | 0 .../core-concepts/kubernetes-architecture.md} | 0 .../core-concepts/kubernetes-resources.md} | 0 .../options-for-running-kubernetes-in-aws.md} | 0 .../core-concepts/why-kubernetes.md} | 0 .../10-try-out-the-cluster.md | 0 .../11-updating-the-worker-nodes.md | 0 .../deployment-walkthrough}/_category_.json | 0 ...-to-the-control-plane-and-worker-nodes.md} | 0 ...etrics-and-alarms-for-the-worker-nodes.md} | 0 .../configure-role-mapping.md} | 0 .../configure-the-control-plane.md} | 0 ...igure-the-worker-node-user-data-script.md} | 0 .../configure-the-worker-nodes.md} | 0 .../create-the-worker-node-ami.md} | 0 .../deploy-the-eks-cluster.md} | 0 .../deployment-walkthrough/deploy-the-vpc.md} | 4 +-- .../deployment-walkthrough/pre-requisites.md} | 4 +-- .../intro}/_category_.json | 0 .../intro/what-is-kubernetes.md} | 0 .../intro/what-youll-learn-in-this-guide.md} | 0 .../next-steps.md} | 0 .../production-grade-design}/_category_.json | 0 .../production-grade-design/authenticate.md} | 0 .../production-grade-design/control-plane.md} | 6 ++-- .../iam-role-mapping-and-rbac.md} | 0 .../production-grade-design/intro.md} | 0 .../production-grade-design/logging.md} | 0 .../protecting-pods.md} | 0 .../production-grade-design/use-eks.md} | 0 .../vpc-configuration.md} | 4 +-- .../production-grade-design/worker-nodes.md} | 4 +-- .../_category_.json | 0 .../core-concepts}/_category_.json | 0 .../core-concepts/aws-account.md} | 0 .../core-concepts/aws-config.md} | 0 .../core-concepts/aws-organizations.md} | 0 .../core-concepts/cloud-trail.md} | 0 .../federated-authentication.md} | 0 .../core-concepts/guard-duty.md} | 0 .../core-concepts/iam-groups.md} | 0 .../core-concepts/iam-policies.md} | 0 .../core-concepts/iam-roles.md} | 28 ++++--------------- .../core-concepts/iam-users.md} | 0 .../core-concepts/root-user.md} | 0 .../deployment-walkthrough}/_category_.json | 0 ...-security-baseline-to-the-logs-account.md} | 0 ...y-baseline-to-the-other-child-accounts.md} | 0 ...-security-baseline-to-the-root-account.md} | 0 ...urity-baseline-to-the-security-account.md} | 0 ...security-baseline-for-the-root-account.md} | 0 ...create-an-iam-user-in-the-root-account.md} | 0 .../create-the-root-account.md} | 0 ...-the-root-account-into-terraform-state.md} | 0 .../lock-down-the-root-account-iam-users.md} | 0 ...wn-the-root-user-in-the-child-accounts.md} | 0 .../lock-down-the-root-user.md} | 0 .../deployment-walkthrough/pre-requisites.md} | 0 ...re-your-infrastructure-live-repository.md} | 0 ...ot-user-password-in-each-child-account.md} | 0 ...g-as-an-iam-user-to-the-child-accounts.md} | 0 .../intro}/_category_.json | 0 ...k-aws-landing-zone-vs-the-alternatives.md} | 0 .../what-is-an-aws-account-structure.md} | 0 .../intro/what-youll-learn-in-this-guide.md} | 0 .../next-steps.md} | 4 +-- .../production-grade-design}/_category_.json | 0 .../production-grade-design/aws-config.md} | 0 .../child-accounts.md} | 0 .../production-grade-design/cloud-trail.md} | 0 .../federated-auth.md} | 0 .../production-grade-design/guard-duty.md} | 0 .../iam-roles-for-services.md} | 6 ++-- .../iam-roles-for-users.md} | 0 .../iam-users-and-groups.md} | 0 .../production-grade-design/intro.md} | 0 .../production-grade-design/mfa-policy.md} | 0 .../password-policy.md} | 4 +-- .../the-root-account.md} | 0 .../{1-overview.md => overview.md} | 0 .../_category_.json | 0 .../core-concepts}/_category_.json | 0 .../core-concepts/ci-cd-platforms.md} | 0 .../core-concepts/ci-cd-workflows.md} | 0 .../core-concepts/threat-model-of-ci-cd.md} | 0 .../trunk-based-development-model.md} | 0 .../types-of-infrastructure-code.md} | 0 .../why-is-it-important-to-have-ci-cd.md} | 0 .../deployment-walkthrough}/_category_.json | 0 .../configure-ci-server.md} | 0 .../define-pipeline-as-code.md} | 0 .../deployment-walkthrough/deploy-a-vpc.md} | 4 +-- .../deploy-the-ecs-deploy-runner.md} | 0 .../deployment-walkthrough/pre-requisites.md} | 25 ++++++++--------- .../try-out-the-ecs-deploy-runner.md} | 0 .../intro}/_category_.json | 0 ...us-integration-and-continuous-delivery.md} | 0 .../intro/what-this-guide-will-not-cover.md} | 0 .../intro/what-youll-learn-in-this-guide.md} | 0 .../next-steps.md} | 0 .../production-grade-design}/_category_.json | 0 .../production-grade-design/intro.md} | 0 .../limit-triggers-for-deploy-server.md} | 0 .../lock-down-vcs-systems.md} | 0 .../options-for-deploy-server.md} | 0 .../summary-of-deployment-sequence.md} | 0 .../summary-of-mitigations.md} | 0 .../use-a-vpc-to-lock-down-deploy-server.md} | 4 +-- .../use-approval-flows.md} | 4 +-- ...e-deployments-from-within-your-account.md} | 4 +-- ...nimal-iam-permissions-for-a-deployment.md} | 0 .../{4-vpc => vpc}/_category_.json | 0 .../core-concepts}/_category_.json | 0 .../core-concepts/cidr-notation.md} | 0 .../default-vp-cs-and-custom-vp-cs.md} | 4 +-- ...ays-public-subnets-and-private-subnets.md} | 0 .../core-concepts/nat-gateways.md} | 0 .../core-concepts/network-ac-ls.md} | 0 .../regions-and-availability-zones.md} | 0 .../core-concepts/route-tables.md} | 0 .../core-concepts/security-groups.md} | 0 .../core-concepts/subnets.md} | 0 .../core-concepts/vpc-endpoints.md} | 0 .../core-concepts/vpc-ip-addresses.md} | 0 .../core-concepts/vpc-peering.md} | 0 .../deployment-walkthrough}/_category_.json | 0 ...n-up-default-vp-cs-and-security-groups.md} | 0 .../deploy-a-bastion-host.md} | 0 .../deploy-a-management-vpc.md} | 0 .../deploy-application-vp-cs.md} | 0 .../deployment-walkthrough/pre-requisites.md} | 4 +-- .../0-intro => vpc/intro}/_category_.json | 0 .../intro/what-is-a-vpc.md} | 0 .../intro/what-youll-learn-in-this-guide.md} | 0 .../4-next-steps.md => vpc/next-steps.md} | 4 +-- .../production-grade-design}/_category_.json | 0 .../production-grade-design/bastion-host.md} | 4 +-- .../defense-in-depth.md} | 0 .../internet-gateways-and-nat-gateways.md} | 0 .../production-grade-design/intro.md} | 0 .../multiple-aws-accounts.md} | 4 +-- .../multiple-subnet-tiers.md} | 0 .../multiple-vp-cs.md} | 0 .../security-groups-and-nac-ls.md} | 0 .../2-deployment-walkthrough/_category_.json | 3 -- .../{1-cis => cis}/_category_.json | 0 .../how-to-update-to-cis-13}/_category_.json | 0 .../how-to-update-to-cis-13/core-concepts.md} | 0 .../deployment-walkthrough}/_category_.json | 0 ...untwork-infrastructure-as-code-library.md} | 0 .../step-2-manual-steps.md} | 0 .../step-3-deploy-new-modules.md} | 10 +++---- .../how-to-update-to-cis-13/intro.md} | 10 +++---- .../how-to-update-to-cis-14}/_category_.json | 0 .../how-to-update-to-cis-14/core-concepts.md} | 4 +-- .../deployment-walkthrough}/_category_.json | 0 ...untwork-infrastructure-as-code-library.md} | 0 ...-2-update-the-account-baseline-modules.md} | 18 ++++++------ .../step-3-manual-steps.md} | 18 ++++++------ .../how-to-update-to-cis-14/finally.md} | 0 .../how-to-update-to-cis-14/intro.md} | 10 +++---- .../_category_.json | 0 .../core-concepts.md} | 0 .../deployment-walkthrough}/_category_.json | 0 .../deployment-walkthrough/intro.md} | 0 .../optional-even-dryer-configuration.md} | 0 ...-common-configurations-for-a-component.md} | 12 ++++---- ...e-catalog-based-reference-architecture.md} | 0 .../intro.md} | 6 ++-- .../_category_.json | 0 .../core-concepts.md} | 0 .../deployment-walkthrough.md} | 8 +++--- .../intro.md} | 8 +++--- .../_category_.json | 0 .../core-concepts.md} | 0 .../deployment-walkthrough}/_category_.json | 0 ...e-to-be-compatible-with-terraform-0-15.md} | 10 +++---- ...untwork-infrastructure-as-code-library.md} | 0 .../intro.md} | 8 +++--- .../_category_.json | 0 .../deployment-walkthrough.md} | 14 +++++----- .../intro.md} | 0 .../version-compatibility-table.md} | 0 .../_category_.json | 0 .../core-concepts.md} | 6 ++-- .../deployment-walkthrough}/_category_.json | 0 ...e-to-be-compatible-with-terraform-0-12.md} | 4 +-- ...e-to-be-compatible-with-terraform-0-13.md} | 0 ...untwork-infrastructure-as-code-library.md} | 0 ...ference-architecture-to-terraform-0-13.md} | 4 +-- .../intro.md} | 10 +++---- .../_category_.json | 0 .../core-concepts.md} | 4 +-- .../deployment-walkthrough}/_category_.json | 0 ...e-to-be-compatible-with-terraform-0-13.md} | 6 ++-- ...e-to-be-compatible-with-terraform-0-14.md} | 0 ...untwork-infrastructure-as-code-library.md} | 0 .../step-4-start-using-lock-files.md} | 0 .../intro.md} | 8 +++--- .../_category_.json | 0 .../core-concepts.md} | 0 .../deployment-walkthrough}/_category_.json | 0 ...e-to-be-compatible-with-terraform-0-14.md} | 8 +++--- ...e-to-be-compatible-with-terraform-0-15.md} | 0 ...untwork-infrastructure-as-code-library.md} | 0 .../intro.md} | 8 +++--- 496 files changed, 353 insertions(+), 377 deletions(-) delete mode 100644 _docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/2-prepare-your-infrastructure-live-repository.md rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance => achieve-compliance}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/1-core-concepts => achieve-compliance/core-concepts}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/1-core-concepts/0-intro.md => achieve-compliance/core-concepts/intro.md} (100%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/1-core-concepts/1-recommendation-sections.md => achieve-compliance/core-concepts/recommendation-sections.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough => achieve-compliance/deployment-walkthrough}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/5-create-an-iam-user-in-the-root-account.md => achieve-compliance/deployment-walkthrough/create-an-iam-user-in-the-root-account.md} (100%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/3-create-the-root-account.md => achieve-compliance/deployment-walkthrough/create-the-root-account.md} (100%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/9-create-vpc-flow-logs.md => achieve-compliance/deployment-walkthrough/create-vpc-flow-logs.md} (100%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution => achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/1-apply-account-baseline-app-to-logs-account.md => achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-app-to-logs-account.md} (100%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/3-apply-account-baseline-app-to-other-child-accounts.md => achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-app-to-other-child-accounts.md} (99%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/0-apply-account-baseline-root-to-root-account.md => achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-root-to-root-account.md} (99%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/2-apply-account-baseline-security-to-security-account.md => achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-security-to-security-account.md} (100%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/8-enable-key-rotation-for-kms-keys.md => achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/enable-key-rotation-for-kms-keys.md} (100%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/5-maintain-compliance-by-following-iam-best-practices.md => achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-iam-best-practices.md} (100%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/7-maintain-compliance-by-following-logging-best-practices.md => achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-logging-best-practices.md} (100%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/6-maintain-compliance-by-following-storage-best-practices.md => achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-storage-best-practices.md} (88%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/4-use-iam-roles-for-ec2-instances.md => achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/use-iam-roles-for-ec2-instances.md} (100%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/7-deployment-approach.md => achieve-compliance/deployment-walkthrough/deployment-approach.md} (87%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/6-lock-down-the-root-account-iam-users.md => achieve-compliance/deployment-walkthrough/lock-down-the-root-account-iam-users.md} (100%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/4-lock-down-the-root-user.md => achieve-compliance/deployment-walkthrough/lock-down-the-root-user.md} (100%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/0-pre-requisites.md => achieve-compliance/deployment-walkthrough/pre-requisites.md} (94%) create mode 100644 _docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/prepare-your-infrastructure-live-repository.md rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/1-the-gruntwork-solution.md => achieve-compliance/deployment-walkthrough/the-gruntwork-solution.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/0-intro => achieve-compliance/intro}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/0-intro/1-what-is-the-cis-aws-foundations-benchmark.md => achieve-compliance/intro/what-is-the-cis-aws-foundations-benchmark.md} (100%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/0-intro/0-what-youll-learn-in-this-guide.md => achieve-compliance/intro/what-youll-learn-in-this-guide.md} (94%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/4-next-steps.md => achieve-compliance/next-steps.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/2-production-grade-design => achieve-compliance/production-grade-design}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/2-production-grade-design/1-identity-and-access-management.md => achieve-compliance/production-grade-design/identity-and-access-management.md} (90%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/2-production-grade-design/0-intro.md => achieve-compliance/production-grade-design/intro.md} (88%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/2-production-grade-design/3-logging.md => achieve-compliance/production-grade-design/logging.md} (100%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/2-production-grade-design/4-monitoring.md => achieve-compliance/production-grade-design/monitoring.md} (100%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/2-production-grade-design/5-networking.md => achieve-compliance/production-grade-design/networking.md} (100%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/2-production-grade-design/2-storage.md => achieve-compliance/production-grade-design/storage.md} (94%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/5-traceability-matrix.md => achieve-compliance/traceability-matrix.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster => kubernetes-cluster}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/1-core-concepts => kubernetes-cluster/core-concepts}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/1-core-concepts/3-interacting-with-kubernetes.md => kubernetes-cluster/core-concepts/interacting-with-kubernetes.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/1-core-concepts/2-kubernetes-access-control.md => kubernetes-cluster/core-concepts/kubernetes-access-control.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/1-core-concepts/1-kubernetes-architecture.md => kubernetes-cluster/core-concepts/kubernetes-architecture.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/1-core-concepts/4-kubernetes-resources.md => kubernetes-cluster/core-concepts/kubernetes-resources.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/1-core-concepts/5-options-for-running-kubernetes-in-aws.md => kubernetes-cluster/core-concepts/options-for-running-kubernetes-in-aws.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/1-core-concepts/0-why-kubernetes.md => kubernetes-cluster/core-concepts/why-kubernetes.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough => kubernetes-cluster/deployment-walkthrough}/10-try-out-the-cluster.md (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough => kubernetes-cluster/deployment-walkthrough}/11-updating-the-worker-nodes.md (100%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/3-deployment-walkthrough => kubernetes-cluster/deployment-walkthrough}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough/8-configure-access-to-the-control-plane-and-worker-nodes.md => kubernetes-cluster/deployment-walkthrough/configure-access-to-the-control-plane-and-worker-nodes.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough/6-configure-logging-metrics-and-alarms-for-the-worker-nodes.md => kubernetes-cluster/deployment-walkthrough/configure-logging-metrics-and-alarms-for-the-worker-nodes.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough/7-configure-role-mapping.md => kubernetes-cluster/deployment-walkthrough/configure-role-mapping.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough/2-configure-the-control-plane.md => kubernetes-cluster/deployment-walkthrough/configure-the-control-plane.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough/5-configure-the-worker-node-user-data-script.md => kubernetes-cluster/deployment-walkthrough/configure-the-worker-node-user-data-script.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough/3-configure-the-worker-nodes.md => kubernetes-cluster/deployment-walkthrough/configure-the-worker-nodes.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough/4-create-the-worker-node-ami.md => kubernetes-cluster/deployment-walkthrough/create-the-worker-node-ami.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough/9-deploy-the-eks-cluster.md => kubernetes-cluster/deployment-walkthrough/deploy-the-eks-cluster.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough/1-deploy-the-vpc.md => kubernetes-cluster/deployment-walkthrough/deploy-the-vpc.md} (98%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough/0-pre-requisites.md => kubernetes-cluster/deployment-walkthrough/pre-requisites.md} (97%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/0-intro => kubernetes-cluster/intro}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/0-intro/1-what-is-kubernetes.md => kubernetes-cluster/intro/what-is-kubernetes.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/0-intro/0-what-youll-learn-in-this-guide.md => kubernetes-cluster/intro/what-youll-learn-in-this-guide.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/4-next-steps.md => kubernetes-cluster/next-steps.md} (100%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/2-production-grade-design => kubernetes-cluster/production-grade-design}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/2-production-grade-design/5-authenticate.md => kubernetes-cluster/production-grade-design/authenticate.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/2-production-grade-design/3-control-plane.md => kubernetes-cluster/production-grade-design/control-plane.md} (91%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/2-production-grade-design/6-iam-role-mapping-and-rbac.md => kubernetes-cluster/production-grade-design/iam-role-mapping-and-rbac.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/2-production-grade-design/0-intro.md => kubernetes-cluster/production-grade-design/intro.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/2-production-grade-design/7-logging.md => kubernetes-cluster/production-grade-design/logging.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/2-production-grade-design/8-protecting-pods.md => kubernetes-cluster/production-grade-design/protecting-pods.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/2-production-grade-design/1-use-eks.md => kubernetes-cluster/production-grade-design/use-eks.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/2-production-grade-design/2-vpc-configuration.md => kubernetes-cluster/production-grade-design/vpc-configuration.md} (93%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/2-production-grade-design/4-worker-nodes.md => kubernetes-cluster/production-grade-design/worker-nodes.md} (96%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone => landing-zone}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/1-core-concepts => landing-zone/core-concepts}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/1-core-concepts/0-aws-account.md => landing-zone/core-concepts/aws-account.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/1-core-concepts/9-aws-config.md => landing-zone/core-concepts/aws-config.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/1-core-concepts/7-aws-organizations.md => landing-zone/core-concepts/aws-organizations.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/1-core-concepts/8-cloud-trail.md => landing-zone/core-concepts/cloud-trail.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/1-core-concepts/6-federated-authentication.md => landing-zone/core-concepts/federated-authentication.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/1-core-concepts/10-guard-duty.md => landing-zone/core-concepts/guard-duty.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/1-core-concepts/4-iam-groups.md => landing-zone/core-concepts/iam-groups.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/1-core-concepts/3-iam-policies.md => landing-zone/core-concepts/iam-policies.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/1-core-concepts/5-iam-roles.md => landing-zone/core-concepts/iam-roles.md} (96%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/1-core-concepts/2-iam-users.md => landing-zone/core-concepts/iam-users.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/1-core-concepts/1-root-user.md => landing-zone/core-concepts/root-user.md} (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/3-deployment-walkthrough => landing-zone/deployment-walkthrough}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/11-apply-the-security-baseline-to-the-logs-account.md => landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-logs-account.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/13-apply-the-security-baseline-to-the-other-child-accounts.md => landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-other-child-accounts.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/8-apply-the-security-baseline-to-the-root-account.md => landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-root-account.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/12-apply-the-security-baseline-to-the-security-account.md => landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-security-account.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/6-configure-the-security-baseline-for-the-root-account.md => landing-zone/deployment-walkthrough/configure-the-security-baseline-for-the-root-account.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/4-create-an-iam-user-in-the-root-account.md => landing-zone/deployment-walkthrough/create-an-iam-user-in-the-root-account.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/2-create-the-root-account.md => landing-zone/deployment-walkthrough/create-the-root-account.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/7-import-existing-resources-from-the-root-account-into-terraform-state.md => landing-zone/deployment-walkthrough/import-existing-resources-from-the-root-account-into-terraform-state.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/5-lock-down-the-root-account-iam-users.md => landing-zone/deployment-walkthrough/lock-down-the-root-account-iam-users.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/10-lock-down-the-root-user-in-the-child-accounts.md => landing-zone/deployment-walkthrough/lock-down-the-root-user-in-the-child-accounts.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/3-lock-down-the-root-user.md => landing-zone/deployment-walkthrough/lock-down-the-root-user.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/0-pre-requisites.md => landing-zone/deployment-walkthrough/pre-requisites.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/1-prepare-your-infrastructure-live-repository.md => landing-zone/deployment-walkthrough/prepare-your-infrastructure-live-repository.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/9-reset-the-root-user-password-in-each-child-account.md => landing-zone/deployment-walkthrough/reset-the-root-user-password-in-each-child-account.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/14-try-authenticating-as-an-iam-user-to-the-child-accounts.md => landing-zone/deployment-walkthrough/try-authenticating-as-an-iam-user-to-the-child-accounts.md} (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/0-intro => landing-zone/intro}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/0-intro/2-gruntwork-aws-landing-zone-vs-the-alternatives.md => landing-zone/intro/gruntwork-aws-landing-zone-vs-the-alternatives.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/0-intro/1-what-is-an-aws-account-structure.md => landing-zone/intro/what-is-an-aws-account-structure.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/0-intro/0-what-youll-learn-in-this-guide.md => landing-zone/intro/what-youll-learn-in-this-guide.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/4-next-steps.md => landing-zone/next-steps.md} (69%) rename _docs-sources/guides/build-it-yourself/{4-vpc/2-production-grade-design => landing-zone/production-grade-design}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/2-production-grade-design/9-aws-config.md => landing-zone/production-grade-design/aws-config.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/2-production-grade-design/2-child-accounts.md => landing-zone/production-grade-design/child-accounts.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/2-production-grade-design/8-cloud-trail.md => landing-zone/production-grade-design/cloud-trail.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/2-production-grade-design/11-federated-auth.md => landing-zone/production-grade-design/federated-auth.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/2-production-grade-design/10-guard-duty.md => landing-zone/production-grade-design/guard-duty.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/2-production-grade-design/7-iam-roles-for-services.md => landing-zone/production-grade-design/iam-roles-for-services.md} (97%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/2-production-grade-design/3-iam-roles-for-users.md => landing-zone/production-grade-design/iam-roles-for-users.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/2-production-grade-design/4-iam-users-and-groups.md => landing-zone/production-grade-design/iam-users-and-groups.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/2-production-grade-design/0-intro.md => landing-zone/production-grade-design/intro.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/2-production-grade-design/5-mfa-policy.md => landing-zone/production-grade-design/mfa-policy.md} (100%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/2-production-grade-design/6-password-policy.md => landing-zone/production-grade-design/password-policy.md} (76%) rename _docs-sources/guides/build-it-yourself/{2-landing-zone/2-production-grade-design/1-the-root-account.md => landing-zone/production-grade-design/the-root-account.md} (100%) rename _docs-sources/guides/build-it-yourself/{1-overview.md => overview.md} (100%) rename _docs-sources/guides/build-it-yourself/{3-pipelines => pipelines}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/1-core-concepts => pipelines/core-concepts}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/1-core-concepts/5-ci-cd-platforms.md => pipelines/core-concepts/ci-cd-platforms.md} (100%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/1-core-concepts/3-ci-cd-workflows.md => pipelines/core-concepts/ci-cd-workflows.md} (100%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/1-core-concepts/4-threat-model-of-ci-cd.md => pipelines/core-concepts/threat-model-of-ci-cd.md} (100%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/1-core-concepts/1-trunk-based-development-model.md => pipelines/core-concepts/trunk-based-development-model.md} (100%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/1-core-concepts/2-types-of-infrastructure-code.md => pipelines/core-concepts/types-of-infrastructure-code.md} (100%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/1-core-concepts/0-why-is-it-important-to-have-ci-cd.md => pipelines/core-concepts/why-is-it-important-to-have-ci-cd.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough => pipelines/deployment-walkthrough}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/3-deployment-walkthrough/5-configure-ci-server.md => pipelines/deployment-walkthrough/configure-ci-server.md} (100%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/3-deployment-walkthrough/4-define-pipeline-as-code.md => pipelines/deployment-walkthrough/define-pipeline-as-code.md} (100%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/3-deployment-walkthrough/1-deploy-a-vpc.md => pipelines/deployment-walkthrough/deploy-a-vpc.md} (91%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/3-deployment-walkthrough/2-deploy-the-ecs-deploy-runner.md => pipelines/deployment-walkthrough/deploy-the-ecs-deploy-runner.md} (100%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/3-deployment-walkthrough/0-pre-requisites.md => pipelines/deployment-walkthrough/pre-requisites.md} (72%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/3-deployment-walkthrough/3-try-out-the-ecs-deploy-runner.md => pipelines/deployment-walkthrough/try-out-the-ecs-deploy-runner.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/0-intro => pipelines/intro}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/0-intro/1-what-is-continuous-integration-and-continuous-delivery.md => pipelines/intro/what-is-continuous-integration-and-continuous-delivery.md} (100%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/0-intro/2-what-this-guide-will-not-cover.md => pipelines/intro/what-this-guide-will-not-cover.md} (100%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/0-intro/0-what-youll-learn-in-this-guide.md => pipelines/intro/what-youll-learn-in-this-guide.md} (100%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/4-next-steps.md => pipelines/next-steps.md} (100%) rename _docs-sources/guides/build-it-yourself/{5-kubernetes-cluster/2-production-grade-design => pipelines/production-grade-design}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/2-production-grade-design/0-intro.md => pipelines/production-grade-design/intro.md} (100%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/2-production-grade-design/3-limit-triggers-for-deploy-server.md => pipelines/production-grade-design/limit-triggers-for-deploy-server.md} (100%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/2-production-grade-design/7-lock-down-vcs-systems.md => pipelines/production-grade-design/lock-down-vcs-systems.md} (100%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/2-production-grade-design/2-options-for-deploy-server.md => pipelines/production-grade-design/options-for-deploy-server.md} (100%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/2-production-grade-design/9-summary-of-deployment-sequence.md => pipelines/production-grade-design/summary-of-deployment-sequence.md} (100%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/2-production-grade-design/8-summary-of-mitigations.md => pipelines/production-grade-design/summary-of-mitigations.md} (100%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/2-production-grade-design/4-use-a-vpc-to-lock-down-deploy-server.md => pipelines/production-grade-design/use-a-vpc-to-lock-down-deploy-server.md} (71%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/2-production-grade-design/6-use-approval-flows.md => pipelines/production-grade-design/use-approval-flows.md} (90%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/2-production-grade-design/1-use-generic-ci-cd-platforms-as-a-workflow-engine-but-run-infrastructure-deployments-from-within-your-account.md => pipelines/production-grade-design/use-generic-ci-cd-platforms-as-a-workflow-engine-but-run-infrastructure-deployments-from-within-your-account.md} (95%) rename _docs-sources/guides/build-it-yourself/{3-pipelines/2-production-grade-design/5-use-minimal-iam-permissions-for-a-deployment.md => pipelines/production-grade-design/use-minimal-iam-permissions-for-a-deployment.md} (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc => vpc}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/1-core-concepts => vpc/core-concepts}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/1-core-concepts/2-cidr-notation.md => vpc/core-concepts/cidr-notation.md} (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/1-core-concepts/0-default-vp-cs-and-custom-vp-cs.md => vpc/core-concepts/default-vp-cs-and-custom-vp-cs.md} (96%) rename _docs-sources/guides/build-it-yourself/{4-vpc/1-core-concepts/5-internet-gateways-public-subnets-and-private-subnets.md => vpc/core-concepts/internet-gateways-public-subnets-and-private-subnets.md} (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/1-core-concepts/6-nat-gateways.md => vpc/core-concepts/nat-gateways.md} (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/1-core-concepts/8-network-ac-ls.md => vpc/core-concepts/network-ac-ls.md} (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/1-core-concepts/11-regions-and-availability-zones.md => vpc/core-concepts/regions-and-availability-zones.md} (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/1-core-concepts/4-route-tables.md => vpc/core-concepts/route-tables.md} (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/1-core-concepts/7-security-groups.md => vpc/core-concepts/security-groups.md} (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/1-core-concepts/3-subnets.md => vpc/core-concepts/subnets.md} (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/1-core-concepts/10-vpc-endpoints.md => vpc/core-concepts/vpc-endpoints.md} (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/1-core-concepts/1-vpc-ip-addresses.md => vpc/core-concepts/vpc-ip-addresses.md} (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/1-core-concepts/9-vpc-peering.md => vpc/core-concepts/vpc-peering.md} (100%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough => vpc/deployment-walkthrough}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/3-deployment-walkthrough/4-clean-up-default-vp-cs-and-security-groups.md => vpc/deployment-walkthrough/clean-up-default-vp-cs-and-security-groups.md} (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/3-deployment-walkthrough/3-deploy-a-bastion-host.md => vpc/deployment-walkthrough/deploy-a-bastion-host.md} (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/3-deployment-walkthrough/1-deploy-a-management-vpc.md => vpc/deployment-walkthrough/deploy-a-management-vpc.md} (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/3-deployment-walkthrough/2-deploy-application-vp-cs.md => vpc/deployment-walkthrough/deploy-application-vp-cs.md} (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/3-deployment-walkthrough/0-pre-requisites.md => vpc/deployment-walkthrough/pre-requisites.md} (92%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/0-intro => vpc/intro}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/0-intro/1-what-is-a-vpc.md => vpc/intro/what-is-a-vpc.md} (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/0-intro/0-what-youll-learn-in-this-guide.md => vpc/intro/what-youll-learn-in-this-guide.md} (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/4-next-steps.md => vpc/next-steps.md} (91%) rename _docs-sources/guides/build-it-yourself/{6-achieve-compliance/2-production-grade-design => vpc/production-grade-design}/_category_.json (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/2-production-grade-design/7-bastion-host.md => vpc/production-grade-design/bastion-host.md} (96%) rename _docs-sources/guides/build-it-yourself/{4-vpc/2-production-grade-design/1-defense-in-depth.md => vpc/production-grade-design/defense-in-depth.md} (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/2-production-grade-design/6-internet-gateways-and-nat-gateways.md => vpc/production-grade-design/internet-gateways-and-nat-gateways.md} (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/2-production-grade-design/0-intro.md => vpc/production-grade-design/intro.md} (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/2-production-grade-design/2-multiple-aws-accounts.md => vpc/production-grade-design/multiple-aws-accounts.md} (92%) rename _docs-sources/guides/build-it-yourself/{4-vpc/2-production-grade-design/4-multiple-subnet-tiers.md => vpc/production-grade-design/multiple-subnet-tiers.md} (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/2-production-grade-design/3-multiple-vp-cs.md => vpc/production-grade-design/multiple-vp-cs.md} (100%) rename _docs-sources/guides/build-it-yourself/{4-vpc/2-production-grade-design/5-security-groups-and-nac-ls.md => vpc/production-grade-design/security-groups-and-nac-ls.md} (100%) rename _docs-sources/guides/stay-up-to-date/{1-cis => cis}/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/{1-cis/1-how-to-update-to-cis-13 => cis/how-to-update-to-cis-13}/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/{1-cis/1-how-to-update-to-cis-13/1-core-concepts.md => cis/how-to-update-to-cis-13/core-concepts.md} (100%) rename _docs-sources/guides/stay-up-to-date/{1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough => cis/how-to-update-to-cis-13/deployment-walkthrough}/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/{1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/0-step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md => cis/how-to-update-to-cis-13/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md} (100%) rename _docs-sources/guides/stay-up-to-date/{1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/1-step-2-manual-steps.md => cis/how-to-update-to-cis-13/deployment-walkthrough/step-2-manual-steps.md} (100%) rename _docs-sources/guides/stay-up-to-date/{1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/2-step-3-deploy-new-modules.md => cis/how-to-update-to-cis-13/deployment-walkthrough/step-3-deploy-new-modules.md} (92%) rename _docs-sources/guides/stay-up-to-date/{1-cis/1-how-to-update-to-cis-13/0-intro.md => cis/how-to-update-to-cis-13/intro.md} (64%) rename _docs-sources/guides/stay-up-to-date/{1-cis/0-how-to-update-to-cis-14 => cis/how-to-update-to-cis-14}/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/{1-cis/0-how-to-update-to-cis-14/1-core-concepts.md => cis/how-to-update-to-cis-14/core-concepts.md} (89%) rename _docs-sources/guides/stay-up-to-date/{1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough => cis/how-to-update-to-cis-14/deployment-walkthrough}/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/{1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/0-step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md => cis/how-to-update-to-cis-14/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md} (100%) rename _docs-sources/guides/stay-up-to-date/{1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/1-step-2-update-the-account-baseline-modules.md => cis/how-to-update-to-cis-14/deployment-walkthrough/step-2-update-the-account-baseline-modules.md} (87%) rename _docs-sources/guides/stay-up-to-date/{1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/2-step-3-manual-steps.md => cis/how-to-update-to-cis-14/deployment-walkthrough/step-3-manual-steps.md} (94%) rename _docs-sources/guides/stay-up-to-date/{1-cis/0-how-to-update-to-cis-14/3-finally.md => cis/how-to-update-to-cis-14/finally.md} (100%) rename _docs-sources/guides/stay-up-to-date/{1-cis/0-how-to-update-to-cis-14/0-intro.md => cis/how-to-update-to-cis-14/intro.md} (53%) rename _docs-sources/guides/stay-up-to-date/terraform/{6-how-to-dry-your-reference-architecture => how-to-dry-your-reference-architecture}/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{6-how-to-dry-your-reference-architecture/1-core-concepts.md => how-to-dry-your-reference-architecture/core-concepts.md} (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{1-how-to-update-to-terraform-13/2-deployment-walkthrough => how-to-dry-your-reference-architecture/deployment-walkthrough}/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/0-intro.md => how-to-dry-your-reference-architecture/deployment-walkthrough/intro.md} (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/3-optional-even-dryer-configuration.md => how-to-dry-your-reference-architecture/deployment-walkthrough/optional-even-dryer-configuration.md} (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/2-refactoring-common-configurations-for-a-component.md => how-to-dry-your-reference-architecture/deployment-walkthrough/refactoring-common-configurations-for-a-component.md} (96%) rename _docs-sources/guides/stay-up-to-date/terraform/{6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/1-update-to-the-service-catalog-based-reference-architecture.md => how-to-dry-your-reference-architecture/deployment-walkthrough/update-to-the-service-catalog-based-reference-architecture.md} (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{6-how-to-dry-your-reference-architecture/0-intro.md => how-to-dry-your-reference-architecture/intro.md} (90%) rename _docs-sources/guides/stay-up-to-date/terraform/{5-how-to-update-to-aws-provider-v3 => how-to-update-to-aws-provider-v3}/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{5-how-to-update-to-aws-provider-v3/1-core-concepts.md => how-to-update-to-aws-provider-v3/core-concepts.md} (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{5-how-to-update-to-aws-provider-v3/2-deployment-walkthrough.md => how-to-update-to-aws-provider-v3/deployment-walkthrough.md} (98%) rename _docs-sources/guides/stay-up-to-date/terraform/{5-how-to-update-to-aws-provider-v3/0-intro.md => how-to-update-to-aws-provider-v3/intro.md} (83%) rename _docs-sources/guides/stay-up-to-date/terraform/{4-how-to-update-to-terraform-1-x => how-to-update-to-terraform-1-x}/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{4-how-to-update-to-terraform-1-x/1-core-concepts.md => how-to-update-to-terraform-1-x/core-concepts.md} (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{2-how-to-update-to-terraform-14/2-deployment-walkthrough => how-to-update-to-terraform-1-x/deployment-walkthrough}/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{4-how-to-update-to-terraform-1-x/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-15.md => how-to-update-to-terraform-1-x/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-15.md} (68%) rename _docs-sources/guides/stay-up-to-date/terraform/{4-how-to-update-to-terraform-1-x/2-deployment-walkthrough/1-step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md => how-to-update-to-terraform-1-x/deployment-walkthrough/step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md} (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{4-how-to-update-to-terraform-1-x/0-intro.md => how-to-update-to-terraform-1-x/intro.md} (69%) rename _docs-sources/guides/stay-up-to-date/terraform/{0-how-to-update-to-terraform-12 => how-to-update-to-terraform-12}/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{0-how-to-update-to-terraform-12/1-deployment-walkthrough.md => how-to-update-to-terraform-12/deployment-walkthrough.md} (99%) rename _docs-sources/guides/stay-up-to-date/terraform/{0-how-to-update-to-terraform-12/0-intro.md => how-to-update-to-terraform-12/intro.md} (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{0-how-to-update-to-terraform-12/1-version-compatibility-table.md => how-to-update-to-terraform-12/version-compatibility-table.md} (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{1-how-to-update-to-terraform-13 => how-to-update-to-terraform-13}/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{1-how-to-update-to-terraform-13/1-core-concepts.md => how-to-update-to-terraform-13/core-concepts.md} (88%) rename _docs-sources/guides/stay-up-to-date/terraform/{3-how-to-update-to-terraform-15/2-deployment-walkthrough => how-to-update-to-terraform-13/deployment-walkthrough}/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{1-how-to-update-to-terraform-13/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-12.md => how-to-update-to-terraform-13/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12.md} (86%) rename _docs-sources/guides/stay-up-to-date/terraform/{1-how-to-update-to-terraform-13/2-deployment-walkthrough/1-step-2-update-your-code-to-be-compatible-with-terraform-0-13.md => how-to-update-to-terraform-13/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-13.md} (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{1-how-to-update-to-terraform-13/2-deployment-walkthrough/2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md => how-to-update-to-terraform-13/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md} (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{1-how-to-update-to-terraform-13/2-deployment-walkthrough/3-updating-the-gruntwork-reference-architecture-to-terraform-0-13.md => how-to-update-to-terraform-13/deployment-walkthrough/updating-the-gruntwork-reference-architecture-to-terraform-0-13.md} (94%) rename _docs-sources/guides/stay-up-to-date/terraform/{1-how-to-update-to-terraform-13/0-intro.md => how-to-update-to-terraform-13/intro.md} (63%) rename _docs-sources/guides/stay-up-to-date/terraform/{2-how-to-update-to-terraform-14 => how-to-update-to-terraform-14}/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{2-how-to-update-to-terraform-14/1-core-concepts.md => how-to-update-to-terraform-14/core-concepts.md} (94%) rename _docs-sources/guides/stay-up-to-date/terraform/{4-how-to-update-to-terraform-1-x/2-deployment-walkthrough => how-to-update-to-terraform-14/deployment-walkthrough}/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{2-how-to-update-to-terraform-14/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-13.md => how-to-update-to-terraform-14/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-13.md} (85%) rename _docs-sources/guides/stay-up-to-date/terraform/{2-how-to-update-to-terraform-14/2-deployment-walkthrough/1-step-2-update-your-code-to-be-compatible-with-terraform-0-14.md => how-to-update-to-terraform-14/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-14.md} (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{2-how-to-update-to-terraform-14/2-deployment-walkthrough/2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md => how-to-update-to-terraform-14/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md} (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{2-how-to-update-to-terraform-14/2-deployment-walkthrough/3-step-4-start-using-lock-files.md => how-to-update-to-terraform-14/deployment-walkthrough/step-4-start-using-lock-files.md} (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{2-how-to-update-to-terraform-14/0-intro.md => how-to-update-to-terraform-14/intro.md} (68%) rename _docs-sources/guides/stay-up-to-date/terraform/{3-how-to-update-to-terraform-15 => how-to-update-to-terraform-15}/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{3-how-to-update-to-terraform-15/1-core-concepts.md => how-to-update-to-terraform-15/core-concepts.md} (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{6-how-to-dry-your-reference-architecture/2-deployment-walkthrough => how-to-update-to-terraform-15/deployment-walkthrough}/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{3-how-to-update-to-terraform-15/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-14.md => how-to-update-to-terraform-15/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-14.md} (72%) rename _docs-sources/guides/stay-up-to-date/terraform/{3-how-to-update-to-terraform-15/2-deployment-walkthrough/1-step-2-update-your-code-to-be-compatible-with-terraform-0-15.md => how-to-update-to-terraform-15/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-15.md} (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{3-how-to-update-to-terraform-15/2-deployment-walkthrough/2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md => how-to-update-to-terraform-15/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md} (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{3-how-to-update-to-terraform-15/0-intro.md => how-to-update-to-terraform-15/intro.md} (75%) delete mode 100644 docs/guides/build-it-yourself/6-achieve-compliance/0-intro/_category_.json delete mode 100644 docs/guides/build-it-yourself/6-achieve-compliance/1-core-concepts/_category_.json delete mode 100644 docs/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/_category_.json delete mode 100644 docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/2-prepare-your-infrastructure-live-repository.md delete mode 100644 docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/_category_.json delete mode 100644 docs/guides/build-it-yourself/6-achieve-compliance/_category_.json rename docs/guides/build-it-yourself/{5-achieve-compliance => achieve-compliance}/_category_.json (100%) rename docs/guides/build-it-yourself/{2-landing-zone/1-core-concepts => achieve-compliance/core-concepts}/_category_.json (100%) rename docs/guides/build-it-yourself/{6-achieve-compliance/1-core-concepts/0-intro.md => achieve-compliance/core-concepts/intro.md} (100%) rename docs/guides/build-it-yourself/{6-achieve-compliance/1-core-concepts/1-recommendation-sections.md => achieve-compliance/core-concepts/recommendation-sections.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough => achieve-compliance/deployment-walkthrough}/_category_.json (100%) rename docs/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/5-create-an-iam-user-in-the-root-account.md => achieve-compliance/deployment-walkthrough/create-an-iam-user-in-the-root-account.md} (100%) rename docs/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/3-create-the-root-account.md => achieve-compliance/deployment-walkthrough/create-the-root-account.md} (100%) rename docs/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/9-create-vpc-flow-logs.md => achieve-compliance/deployment-walkthrough/create-vpc-flow-logs.md} (100%) rename docs/guides/build-it-yourself/{5-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution => achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution}/_category_.json (100%) rename docs/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/1-apply-account-baseline-app-to-logs-account.md => achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-app-to-logs-account.md} (100%) rename docs/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/3-apply-account-baseline-app-to-other-child-accounts.md => achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-app-to-other-child-accounts.md} (98%) rename docs/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/0-apply-account-baseline-root-to-root-account.md => achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-root-to-root-account.md} (99%) rename docs/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/2-apply-account-baseline-security-to-security-account.md => achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-security-to-security-account.md} (100%) rename docs/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/8-enable-key-rotation-for-kms-keys.md => achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/enable-key-rotation-for-kms-keys.md} (100%) rename docs/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/5-maintain-compliance-by-following-iam-best-practices.md => achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-iam-best-practices.md} (100%) rename docs/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/7-maintain-compliance-by-following-logging-best-practices.md => achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-logging-best-practices.md} (100%) rename docs/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/6-maintain-compliance-by-following-storage-best-practices.md => achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-storage-best-practices.md} (83%) rename docs/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/4-use-iam-roles-for-ec2-instances.md => achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/use-iam-roles-for-ec2-instances.md} (100%) rename docs/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/7-deployment-approach.md => achieve-compliance/deployment-walkthrough/deployment-approach.md} (83%) rename docs/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/6-lock-down-the-root-account-iam-users.md => achieve-compliance/deployment-walkthrough/lock-down-the-root-account-iam-users.md} (100%) rename docs/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/4-lock-down-the-root-user.md => achieve-compliance/deployment-walkthrough/lock-down-the-root-user.md} (100%) rename docs/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/0-pre-requisites.md => achieve-compliance/deployment-walkthrough/pre-requisites.md} (92%) create mode 100644 docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/prepare-your-infrastructure-live-repository.md rename docs/guides/build-it-yourself/{6-achieve-compliance/3-deployment-walkthrough/1-the-gruntwork-solution.md => achieve-compliance/deployment-walkthrough/the-gruntwork-solution.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/0-intro => achieve-compliance/intro}/_category_.json (100%) rename docs/guides/build-it-yourself/{6-achieve-compliance/0-intro/1-what-is-the-cis-aws-foundations-benchmark.md => achieve-compliance/intro/what-is-the-cis-aws-foundations-benchmark.md} (100%) rename docs/guides/build-it-yourself/{6-achieve-compliance/0-intro/0-what-youll-learn-in-this-guide.md => achieve-compliance/intro/what-youll-learn-in-this-guide.md} (92%) rename docs/guides/build-it-yourself/{6-achieve-compliance/4-next-steps.md => achieve-compliance/next-steps.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/2-production-grade-design => achieve-compliance/production-grade-design}/_category_.json (100%) rename docs/guides/build-it-yourself/{6-achieve-compliance/2-production-grade-design/1-identity-and-access-management.md => achieve-compliance/production-grade-design/identity-and-access-management.md} (89%) rename docs/guides/build-it-yourself/{6-achieve-compliance/2-production-grade-design/0-intro.md => achieve-compliance/production-grade-design/intro.md} (83%) rename docs/guides/build-it-yourself/{6-achieve-compliance/2-production-grade-design/3-logging.md => achieve-compliance/production-grade-design/logging.md} (100%) rename docs/guides/build-it-yourself/{6-achieve-compliance/2-production-grade-design/4-monitoring.md => achieve-compliance/production-grade-design/monitoring.md} (100%) rename docs/guides/build-it-yourself/{6-achieve-compliance/2-production-grade-design/5-networking.md => achieve-compliance/production-grade-design/networking.md} (100%) rename docs/guides/build-it-yourself/{6-achieve-compliance/2-production-grade-design/2-storage.md => achieve-compliance/production-grade-design/storage.md} (93%) rename docs/guides/build-it-yourself/{6-achieve-compliance/5-traceability-matrix.md => achieve-compliance/traceability-matrix.md} (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster => kubernetes-cluster}/_category_.json (100%) rename docs/guides/build-it-yourself/{4-vpc/1-core-concepts => kubernetes-cluster/core-concepts}/_category_.json (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/1-core-concepts/3-interacting-with-kubernetes.md => kubernetes-cluster/core-concepts/interacting-with-kubernetes.md} (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/1-core-concepts/2-kubernetes-access-control.md => kubernetes-cluster/core-concepts/kubernetes-access-control.md} (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/1-core-concepts/1-kubernetes-architecture.md => kubernetes-cluster/core-concepts/kubernetes-architecture.md} (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/1-core-concepts/4-kubernetes-resources.md => kubernetes-cluster/core-concepts/kubernetes-resources.md} (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/1-core-concepts/5-options-for-running-kubernetes-in-aws.md => kubernetes-cluster/core-concepts/options-for-running-kubernetes-in-aws.md} (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/1-core-concepts/0-why-kubernetes.md => kubernetes-cluster/core-concepts/why-kubernetes.md} (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough => kubernetes-cluster/deployment-walkthrough}/10-try-out-the-cluster.md (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough => kubernetes-cluster/deployment-walkthrough}/11-updating-the-worker-nodes.md (100%) rename docs/guides/build-it-yourself/{3-pipelines/3-deployment-walkthrough => kubernetes-cluster/deployment-walkthrough}/_category_.json (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough/8-configure-access-to-the-control-plane-and-worker-nodes.md => kubernetes-cluster/deployment-walkthrough/configure-access-to-the-control-plane-and-worker-nodes.md} (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough/6-configure-logging-metrics-and-alarms-for-the-worker-nodes.md => kubernetes-cluster/deployment-walkthrough/configure-logging-metrics-and-alarms-for-the-worker-nodes.md} (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough/7-configure-role-mapping.md => kubernetes-cluster/deployment-walkthrough/configure-role-mapping.md} (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough/2-configure-the-control-plane.md => kubernetes-cluster/deployment-walkthrough/configure-the-control-plane.md} (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough/5-configure-the-worker-node-user-data-script.md => kubernetes-cluster/deployment-walkthrough/configure-the-worker-node-user-data-script.md} (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough/3-configure-the-worker-nodes.md => kubernetes-cluster/deployment-walkthrough/configure-the-worker-nodes.md} (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough/4-create-the-worker-node-ami.md => kubernetes-cluster/deployment-walkthrough/create-the-worker-node-ami.md} (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough/9-deploy-the-eks-cluster.md => kubernetes-cluster/deployment-walkthrough/deploy-the-eks-cluster.md} (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough/1-deploy-the-vpc.md => kubernetes-cluster/deployment-walkthrough/deploy-the-vpc.md} (96%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough/0-pre-requisites.md => kubernetes-cluster/deployment-walkthrough/pre-requisites.md} (94%) rename docs/guides/build-it-yourself/{3-pipelines/0-intro => kubernetes-cluster/intro}/_category_.json (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/0-intro/1-what-is-kubernetes.md => kubernetes-cluster/intro/what-is-kubernetes.md} (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/0-intro/0-what-youll-learn-in-this-guide.md => kubernetes-cluster/intro/what-youll-learn-in-this-guide.md} (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/4-next-steps.md => kubernetes-cluster/next-steps.md} (100%) rename docs/guides/build-it-yourself/{3-pipelines/2-production-grade-design => kubernetes-cluster/production-grade-design}/_category_.json (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/2-production-grade-design/5-authenticate.md => kubernetes-cluster/production-grade-design/authenticate.md} (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/2-production-grade-design/3-control-plane.md => kubernetes-cluster/production-grade-design/control-plane.md} (89%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/2-production-grade-design/6-iam-role-mapping-and-rbac.md => kubernetes-cluster/production-grade-design/iam-role-mapping-and-rbac.md} (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/2-production-grade-design/0-intro.md => kubernetes-cluster/production-grade-design/intro.md} (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/2-production-grade-design/7-logging.md => kubernetes-cluster/production-grade-design/logging.md} (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/2-production-grade-design/8-protecting-pods.md => kubernetes-cluster/production-grade-design/protecting-pods.md} (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/2-production-grade-design/1-use-eks.md => kubernetes-cluster/production-grade-design/use-eks.md} (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/2-production-grade-design/2-vpc-configuration.md => kubernetes-cluster/production-grade-design/vpc-configuration.md} (90%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/2-production-grade-design/4-worker-nodes.md => kubernetes-cluster/production-grade-design/worker-nodes.md} (94%) rename docs/guides/build-it-yourself/{2-landing-zone => landing-zone}/_category_.json (100%) rename docs/guides/build-it-yourself/{5-achieve-compliance/1-core-concepts => landing-zone/core-concepts}/_category_.json (100%) rename docs/guides/build-it-yourself/{2-landing-zone/1-core-concepts/0-aws-account.md => landing-zone/core-concepts/aws-account.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/1-core-concepts/9-aws-config.md => landing-zone/core-concepts/aws-config.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/1-core-concepts/7-aws-organizations.md => landing-zone/core-concepts/aws-organizations.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/1-core-concepts/8-cloud-trail.md => landing-zone/core-concepts/cloud-trail.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/1-core-concepts/6-federated-authentication.md => landing-zone/core-concepts/federated-authentication.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/1-core-concepts/10-guard-duty.md => landing-zone/core-concepts/guard-duty.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/1-core-concepts/4-iam-groups.md => landing-zone/core-concepts/iam-groups.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/1-core-concepts/3-iam-policies.md => landing-zone/core-concepts/iam-policies.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/1-core-concepts/5-iam-roles.md => landing-zone/core-concepts/iam-roles.md} (94%) rename docs/guides/build-it-yourself/{2-landing-zone/1-core-concepts/2-iam-users.md => landing-zone/core-concepts/iam-users.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/1-core-concepts/1-root-user.md => landing-zone/core-concepts/root-user.md} (100%) rename docs/guides/build-it-yourself/{4-vpc/3-deployment-walkthrough => landing-zone/deployment-walkthrough}/_category_.json (100%) rename docs/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/11-apply-the-security-baseline-to-the-logs-account.md => landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-logs-account.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/13-apply-the-security-baseline-to-the-other-child-accounts.md => landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-other-child-accounts.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/8-apply-the-security-baseline-to-the-root-account.md => landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-root-account.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/12-apply-the-security-baseline-to-the-security-account.md => landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-security-account.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/6-configure-the-security-baseline-for-the-root-account.md => landing-zone/deployment-walkthrough/configure-the-security-baseline-for-the-root-account.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/4-create-an-iam-user-in-the-root-account.md => landing-zone/deployment-walkthrough/create-an-iam-user-in-the-root-account.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/2-create-the-root-account.md => landing-zone/deployment-walkthrough/create-the-root-account.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/7-import-existing-resources-from-the-root-account-into-terraform-state.md => landing-zone/deployment-walkthrough/import-existing-resources-from-the-root-account-into-terraform-state.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/5-lock-down-the-root-account-iam-users.md => landing-zone/deployment-walkthrough/lock-down-the-root-account-iam-users.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/10-lock-down-the-root-user-in-the-child-accounts.md => landing-zone/deployment-walkthrough/lock-down-the-root-user-in-the-child-accounts.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/3-lock-down-the-root-user.md => landing-zone/deployment-walkthrough/lock-down-the-root-user.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/0-pre-requisites.md => landing-zone/deployment-walkthrough/pre-requisites.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/1-prepare-your-infrastructure-live-repository.md => landing-zone/deployment-walkthrough/prepare-your-infrastructure-live-repository.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/9-reset-the-root-user-password-in-each-child-account.md => landing-zone/deployment-walkthrough/reset-the-root-user-password-in-each-child-account.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/3-deployment-walkthrough/14-try-authenticating-as-an-iam-user-to-the-child-accounts.md => landing-zone/deployment-walkthrough/try-authenticating-as-an-iam-user-to-the-child-accounts.md} (100%) rename docs/guides/build-it-yourself/{4-vpc/0-intro => landing-zone/intro}/_category_.json (100%) rename docs/guides/build-it-yourself/{2-landing-zone/0-intro/2-gruntwork-aws-landing-zone-vs-the-alternatives.md => landing-zone/intro/gruntwork-aws-landing-zone-vs-the-alternatives.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/0-intro/1-what-is-an-aws-account-structure.md => landing-zone/intro/what-is-an-aws-account-structure.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/0-intro/0-what-youll-learn-in-this-guide.md => landing-zone/intro/what-youll-learn-in-this-guide.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/4-next-steps.md => landing-zone/next-steps.md} (61%) rename docs/guides/build-it-yourself/{4-vpc/2-production-grade-design => landing-zone/production-grade-design}/_category_.json (100%) rename docs/guides/build-it-yourself/{2-landing-zone/2-production-grade-design/9-aws-config.md => landing-zone/production-grade-design/aws-config.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/2-production-grade-design/2-child-accounts.md => landing-zone/production-grade-design/child-accounts.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/2-production-grade-design/8-cloud-trail.md => landing-zone/production-grade-design/cloud-trail.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/2-production-grade-design/11-federated-auth.md => landing-zone/production-grade-design/federated-auth.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/2-production-grade-design/10-guard-duty.md => landing-zone/production-grade-design/guard-duty.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/2-production-grade-design/7-iam-roles-for-services.md => landing-zone/production-grade-design/iam-roles-for-services.md} (96%) rename docs/guides/build-it-yourself/{2-landing-zone/2-production-grade-design/3-iam-roles-for-users.md => landing-zone/production-grade-design/iam-roles-for-users.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/2-production-grade-design/4-iam-users-and-groups.md => landing-zone/production-grade-design/iam-users-and-groups.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/2-production-grade-design/0-intro.md => landing-zone/production-grade-design/intro.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/2-production-grade-design/5-mfa-policy.md => landing-zone/production-grade-design/mfa-policy.md} (100%) rename docs/guides/build-it-yourself/{2-landing-zone/2-production-grade-design/6-password-policy.md => landing-zone/production-grade-design/password-policy.md} (68%) rename docs/guides/build-it-yourself/{2-landing-zone/2-production-grade-design/1-the-root-account.md => landing-zone/production-grade-design/the-root-account.md} (100%) rename docs/guides/build-it-yourself/{1-overview.md => overview.md} (100%) rename docs/guides/build-it-yourself/{3-pipelines => pipelines}/_category_.json (100%) rename docs/guides/build-it-yourself/{3-pipelines/1-core-concepts => pipelines/core-concepts}/_category_.json (100%) rename docs/guides/build-it-yourself/{3-pipelines/1-core-concepts/5-ci-cd-platforms.md => pipelines/core-concepts/ci-cd-platforms.md} (100%) rename docs/guides/build-it-yourself/{3-pipelines/1-core-concepts/3-ci-cd-workflows.md => pipelines/core-concepts/ci-cd-workflows.md} (100%) rename docs/guides/build-it-yourself/{3-pipelines/1-core-concepts/4-threat-model-of-ci-cd.md => pipelines/core-concepts/threat-model-of-ci-cd.md} (100%) rename docs/guides/build-it-yourself/{3-pipelines/1-core-concepts/1-trunk-based-development-model.md => pipelines/core-concepts/trunk-based-development-model.md} (100%) rename docs/guides/build-it-yourself/{3-pipelines/1-core-concepts/2-types-of-infrastructure-code.md => pipelines/core-concepts/types-of-infrastructure-code.md} (100%) rename docs/guides/build-it-yourself/{3-pipelines/1-core-concepts/0-why-is-it-important-to-have-ci-cd.md => pipelines/core-concepts/why-is-it-important-to-have-ci-cd.md} (100%) rename docs/guides/build-it-yourself/{5-achieve-compliance/3-deployment-walkthrough => pipelines/deployment-walkthrough}/_category_.json (100%) rename docs/guides/build-it-yourself/{3-pipelines/3-deployment-walkthrough/5-configure-ci-server.md => pipelines/deployment-walkthrough/configure-ci-server.md} (100%) rename docs/guides/build-it-yourself/{3-pipelines/3-deployment-walkthrough/4-define-pipeline-as-code.md => pipelines/deployment-walkthrough/define-pipeline-as-code.md} (100%) rename docs/guides/build-it-yourself/{3-pipelines/3-deployment-walkthrough/1-deploy-a-vpc.md => pipelines/deployment-walkthrough/deploy-a-vpc.md} (86%) rename docs/guides/build-it-yourself/{3-pipelines/3-deployment-walkthrough/2-deploy-the-ecs-deploy-runner.md => pipelines/deployment-walkthrough/deploy-the-ecs-deploy-runner.md} (100%) rename docs/guides/build-it-yourself/{3-pipelines/3-deployment-walkthrough/0-pre-requisites.md => pipelines/deployment-walkthrough/pre-requisites.md} (70%) rename docs/guides/build-it-yourself/{3-pipelines/3-deployment-walkthrough/3-try-out-the-ecs-deploy-runner.md => pipelines/deployment-walkthrough/try-out-the-ecs-deploy-runner.md} (100%) rename docs/guides/build-it-yourself/{5-achieve-compliance/0-intro => pipelines/intro}/_category_.json (100%) rename docs/guides/build-it-yourself/{3-pipelines/0-intro/1-what-is-continuous-integration-and-continuous-delivery.md => pipelines/intro/what-is-continuous-integration-and-continuous-delivery.md} (100%) rename docs/guides/build-it-yourself/{3-pipelines/0-intro/2-what-this-guide-will-not-cover.md => pipelines/intro/what-this-guide-will-not-cover.md} (100%) rename docs/guides/build-it-yourself/{3-pipelines/0-intro/0-what-youll-learn-in-this-guide.md => pipelines/intro/what-youll-learn-in-this-guide.md} (100%) rename docs/guides/build-it-yourself/{3-pipelines/4-next-steps.md => pipelines/next-steps.md} (100%) rename docs/guides/build-it-yourself/{5-achieve-compliance/2-production-grade-design => pipelines/production-grade-design}/_category_.json (100%) rename docs/guides/build-it-yourself/{3-pipelines/2-production-grade-design/0-intro.md => pipelines/production-grade-design/intro.md} (100%) rename docs/guides/build-it-yourself/{3-pipelines/2-production-grade-design/3-limit-triggers-for-deploy-server.md => pipelines/production-grade-design/limit-triggers-for-deploy-server.md} (100%) rename docs/guides/build-it-yourself/{3-pipelines/2-production-grade-design/7-lock-down-vcs-systems.md => pipelines/production-grade-design/lock-down-vcs-systems.md} (100%) rename docs/guides/build-it-yourself/{3-pipelines/2-production-grade-design/2-options-for-deploy-server.md => pipelines/production-grade-design/options-for-deploy-server.md} (100%) rename docs/guides/build-it-yourself/{3-pipelines/2-production-grade-design/9-summary-of-deployment-sequence.md => pipelines/production-grade-design/summary-of-deployment-sequence.md} (100%) rename docs/guides/build-it-yourself/{3-pipelines/2-production-grade-design/8-summary-of-mitigations.md => pipelines/production-grade-design/summary-of-mitigations.md} (100%) rename docs/guides/build-it-yourself/{3-pipelines/2-production-grade-design/4-use-a-vpc-to-lock-down-deploy-server.md => pipelines/production-grade-design/use-a-vpc-to-lock-down-deploy-server.md} (65%) rename docs/guides/build-it-yourself/{3-pipelines/2-production-grade-design/6-use-approval-flows.md => pipelines/production-grade-design/use-approval-flows.md} (84%) rename docs/guides/build-it-yourself/{3-pipelines/2-production-grade-design/1-use-generic-ci-cd-platforms-as-a-workflow-engine-but-run-infrastructure-deployments-from-within-your-account.md => pipelines/production-grade-design/use-generic-ci-cd-platforms-as-a-workflow-engine-but-run-infrastructure-deployments-from-within-your-account.md} (92%) rename docs/guides/build-it-yourself/{3-pipelines/2-production-grade-design/5-use-minimal-iam-permissions-for-a-deployment.md => pipelines/production-grade-design/use-minimal-iam-permissions-for-a-deployment.md} (100%) rename docs/guides/build-it-yourself/{4-vpc => vpc}/_category_.json (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/1-core-concepts => vpc/core-concepts}/_category_.json (100%) rename docs/guides/build-it-yourself/{4-vpc/1-core-concepts/2-cidr-notation.md => vpc/core-concepts/cidr-notation.md} (100%) rename docs/guides/build-it-yourself/{4-vpc/1-core-concepts/0-default-vp-cs-and-custom-vp-cs.md => vpc/core-concepts/default-vp-cs-and-custom-vp-cs.md} (93%) rename docs/guides/build-it-yourself/{4-vpc/1-core-concepts/5-internet-gateways-public-subnets-and-private-subnets.md => vpc/core-concepts/internet-gateways-public-subnets-and-private-subnets.md} (100%) rename docs/guides/build-it-yourself/{4-vpc/1-core-concepts/6-nat-gateways.md => vpc/core-concepts/nat-gateways.md} (100%) rename docs/guides/build-it-yourself/{4-vpc/1-core-concepts/8-network-ac-ls.md => vpc/core-concepts/network-ac-ls.md} (100%) rename docs/guides/build-it-yourself/{4-vpc/1-core-concepts/11-regions-and-availability-zones.md => vpc/core-concepts/regions-and-availability-zones.md} (100%) rename docs/guides/build-it-yourself/{4-vpc/1-core-concepts/4-route-tables.md => vpc/core-concepts/route-tables.md} (100%) rename docs/guides/build-it-yourself/{4-vpc/1-core-concepts/7-security-groups.md => vpc/core-concepts/security-groups.md} (100%) rename docs/guides/build-it-yourself/{4-vpc/1-core-concepts/3-subnets.md => vpc/core-concepts/subnets.md} (100%) rename docs/guides/build-it-yourself/{4-vpc/1-core-concepts/10-vpc-endpoints.md => vpc/core-concepts/vpc-endpoints.md} (100%) rename docs/guides/build-it-yourself/{4-vpc/1-core-concepts/1-vpc-ip-addresses.md => vpc/core-concepts/vpc-ip-addresses.md} (100%) rename docs/guides/build-it-yourself/{4-vpc/1-core-concepts/9-vpc-peering.md => vpc/core-concepts/vpc-peering.md} (100%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/3-deployment-walkthrough => vpc/deployment-walkthrough}/_category_.json (100%) rename docs/guides/build-it-yourself/{4-vpc/3-deployment-walkthrough/4-clean-up-default-vp-cs-and-security-groups.md => vpc/deployment-walkthrough/clean-up-default-vp-cs-and-security-groups.md} (100%) rename docs/guides/build-it-yourself/{4-vpc/3-deployment-walkthrough/3-deploy-a-bastion-host.md => vpc/deployment-walkthrough/deploy-a-bastion-host.md} (100%) rename docs/guides/build-it-yourself/{4-vpc/3-deployment-walkthrough/1-deploy-a-management-vpc.md => vpc/deployment-walkthrough/deploy-a-management-vpc.md} (100%) rename docs/guides/build-it-yourself/{4-vpc/3-deployment-walkthrough/2-deploy-application-vp-cs.md => vpc/deployment-walkthrough/deploy-application-vp-cs.md} (100%) rename docs/guides/build-it-yourself/{4-vpc/3-deployment-walkthrough/0-pre-requisites.md => vpc/deployment-walkthrough/pre-requisites.md} (88%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/0-intro => vpc/intro}/_category_.json (100%) rename docs/guides/build-it-yourself/{4-vpc/0-intro/1-what-is-a-vpc.md => vpc/intro/what-is-a-vpc.md} (100%) rename docs/guides/build-it-yourself/{4-vpc/0-intro/0-what-youll-learn-in-this-guide.md => vpc/intro/what-youll-learn-in-this-guide.md} (100%) rename docs/guides/build-it-yourself/{4-vpc/4-next-steps.md => vpc/next-steps.md} (83%) rename docs/guides/build-it-yourself/{5-kubernetes-cluster/2-production-grade-design => vpc/production-grade-design}/_category_.json (100%) rename docs/guides/build-it-yourself/{4-vpc/2-production-grade-design/7-bastion-host.md => vpc/production-grade-design/bastion-host.md} (92%) rename docs/guides/build-it-yourself/{4-vpc/2-production-grade-design/1-defense-in-depth.md => vpc/production-grade-design/defense-in-depth.md} (100%) rename docs/guides/build-it-yourself/{4-vpc/2-production-grade-design/6-internet-gateways-and-nat-gateways.md => vpc/production-grade-design/internet-gateways-and-nat-gateways.md} (100%) rename docs/guides/build-it-yourself/{4-vpc/2-production-grade-design/0-intro.md => vpc/production-grade-design/intro.md} (100%) rename docs/guides/build-it-yourself/{4-vpc/2-production-grade-design/2-multiple-aws-accounts.md => vpc/production-grade-design/multiple-aws-accounts.md} (88%) rename docs/guides/build-it-yourself/{4-vpc/2-production-grade-design/4-multiple-subnet-tiers.md => vpc/production-grade-design/multiple-subnet-tiers.md} (100%) rename docs/guides/build-it-yourself/{4-vpc/2-production-grade-design/3-multiple-vp-cs.md => vpc/production-grade-design/multiple-vp-cs.md} (100%) rename docs/guides/build-it-yourself/{4-vpc/2-production-grade-design/5-security-groups-and-nac-ls.md => vpc/production-grade-design/security-groups-and-nac-ls.md} (100%) delete mode 100644 docs/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/_category_.json rename docs/guides/stay-up-to-date/{1-cis => cis}/_category_.json (100%) rename docs/guides/stay-up-to-date/{1-cis/1-how-to-update-to-cis-13 => cis/how-to-update-to-cis-13}/_category_.json (100%) rename docs/guides/stay-up-to-date/{1-cis/1-how-to-update-to-cis-13/1-core-concepts.md => cis/how-to-update-to-cis-13/core-concepts.md} (100%) rename docs/guides/{build-it-yourself/6-achieve-compliance/3-deployment-walkthrough => stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough}/_category_.json (100%) rename docs/guides/stay-up-to-date/{1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/0-step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md => cis/how-to-update-to-cis-13/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md} (100%) rename docs/guides/stay-up-to-date/{1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/1-step-2-manual-steps.md => cis/how-to-update-to-cis-13/deployment-walkthrough/step-2-manual-steps.md} (100%) rename docs/guides/stay-up-to-date/{1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/2-step-3-deploy-new-modules.md => cis/how-to-update-to-cis-13/deployment-walkthrough/step-3-deploy-new-modules.md} (91%) rename docs/guides/stay-up-to-date/{1-cis/1-how-to-update-to-cis-13/0-intro.md => cis/how-to-update-to-cis-13/intro.md} (62%) rename docs/guides/stay-up-to-date/{1-cis/0-how-to-update-to-cis-14 => cis/how-to-update-to-cis-14}/_category_.json (100%) rename docs/guides/stay-up-to-date/{1-cis/0-how-to-update-to-cis-14/1-core-concepts.md => cis/how-to-update-to-cis-14/core-concepts.md} (86%) rename docs/guides/stay-up-to-date/{1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough => cis/how-to-update-to-cis-14/deployment-walkthrough}/_category_.json (100%) rename docs/guides/stay-up-to-date/{1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/0-step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md => cis/how-to-update-to-cis-14/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md} (100%) rename docs/guides/stay-up-to-date/{1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/1-step-2-update-the-account-baseline-modules.md => cis/how-to-update-to-cis-14/deployment-walkthrough/step-2-update-the-account-baseline-modules.md} (86%) rename docs/guides/stay-up-to-date/{1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/2-step-3-manual-steps.md => cis/how-to-update-to-cis-14/deployment-walkthrough/step-3-manual-steps.md} (93%) rename docs/guides/stay-up-to-date/{1-cis/0-how-to-update-to-cis-14/3-finally.md => cis/how-to-update-to-cis-14/finally.md} (100%) rename docs/guides/stay-up-to-date/{1-cis/0-how-to-update-to-cis-14/0-intro.md => cis/how-to-update-to-cis-14/intro.md} (52%) rename docs/guides/stay-up-to-date/terraform/{6-how-to-dry-your-reference-architecture => how-to-dry-your-reference-architecture}/_category_.json (100%) rename docs/guides/stay-up-to-date/terraform/{6-how-to-dry-your-reference-architecture/1-core-concepts.md => how-to-dry-your-reference-architecture/core-concepts.md} (100%) rename docs/guides/stay-up-to-date/terraform/{1-how-to-update-to-terraform-13/2-deployment-walkthrough => how-to-dry-your-reference-architecture/deployment-walkthrough}/_category_.json (100%) rename docs/guides/stay-up-to-date/terraform/{6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/0-intro.md => how-to-dry-your-reference-architecture/deployment-walkthrough/intro.md} (100%) rename docs/guides/stay-up-to-date/terraform/{6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/3-optional-even-dryer-configuration.md => how-to-dry-your-reference-architecture/deployment-walkthrough/optional-even-dryer-configuration.md} (100%) rename docs/guides/stay-up-to-date/terraform/{6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/2-refactoring-common-configurations-for-a-component.md => how-to-dry-your-reference-architecture/deployment-walkthrough/refactoring-common-configurations-for-a-component.md} (96%) rename docs/guides/stay-up-to-date/terraform/{6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/1-update-to-the-service-catalog-based-reference-architecture.md => how-to-dry-your-reference-architecture/deployment-walkthrough/update-to-the-service-catalog-based-reference-architecture.md} (100%) rename docs/guides/stay-up-to-date/terraform/{6-how-to-dry-your-reference-architecture/0-intro.md => how-to-dry-your-reference-architecture/intro.md} (84%) rename docs/guides/stay-up-to-date/terraform/{5-how-to-update-to-aws-provider-v3 => how-to-update-to-aws-provider-v3}/_category_.json (100%) rename docs/guides/stay-up-to-date/terraform/{5-how-to-update-to-aws-provider-v3/1-core-concepts.md => how-to-update-to-aws-provider-v3/core-concepts.md} (100%) rename docs/guides/stay-up-to-date/terraform/{5-how-to-update-to-aws-provider-v3/2-deployment-walkthrough.md => how-to-update-to-aws-provider-v3/deployment-walkthrough.md} (97%) rename docs/guides/stay-up-to-date/terraform/{5-how-to-update-to-aws-provider-v3/0-intro.md => how-to-update-to-aws-provider-v3/intro.md} (79%) rename docs/guides/stay-up-to-date/terraform/{4-how-to-update-to-terraform-1-x => how-to-update-to-terraform-1-x}/_category_.json (100%) rename docs/guides/stay-up-to-date/terraform/{4-how-to-update-to-terraform-1-x/1-core-concepts.md => how-to-update-to-terraform-1-x/core-concepts.md} (100%) rename docs/guides/stay-up-to-date/terraform/{2-how-to-update-to-terraform-14/2-deployment-walkthrough => how-to-update-to-terraform-1-x/deployment-walkthrough}/_category_.json (100%) rename docs/guides/stay-up-to-date/terraform/{4-how-to-update-to-terraform-1-x/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-15.md => how-to-update-to-terraform-1-x/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-15.md} (65%) rename docs/guides/stay-up-to-date/terraform/{4-how-to-update-to-terraform-1-x/2-deployment-walkthrough/1-step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md => how-to-update-to-terraform-1-x/deployment-walkthrough/step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md} (100%) rename docs/guides/stay-up-to-date/terraform/{4-how-to-update-to-terraform-1-x/0-intro.md => how-to-update-to-terraform-1-x/intro.md} (66%) rename docs/guides/stay-up-to-date/terraform/{0-how-to-update-to-terraform-12 => how-to-update-to-terraform-12}/_category_.json (100%) rename docs/guides/stay-up-to-date/terraform/{0-how-to-update-to-terraform-12/1-deployment-walkthrough.md => how-to-update-to-terraform-12/deployment-walkthrough.md} (98%) rename docs/guides/stay-up-to-date/terraform/{0-how-to-update-to-terraform-12/0-intro.md => how-to-update-to-terraform-12/intro.md} (100%) rename docs/guides/stay-up-to-date/terraform/{0-how-to-update-to-terraform-12/1-version-compatibility-table.md => how-to-update-to-terraform-12/version-compatibility-table.md} (100%) rename docs/guides/stay-up-to-date/terraform/{1-how-to-update-to-terraform-13 => how-to-update-to-terraform-13}/_category_.json (100%) rename docs/guides/stay-up-to-date/terraform/{1-how-to-update-to-terraform-13/1-core-concepts.md => how-to-update-to-terraform-13/core-concepts.md} (82%) rename docs/guides/stay-up-to-date/terraform/{3-how-to-update-to-terraform-15/2-deployment-walkthrough => how-to-update-to-terraform-13/deployment-walkthrough}/_category_.json (100%) rename docs/guides/stay-up-to-date/terraform/{1-how-to-update-to-terraform-13/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-12.md => how-to-update-to-terraform-13/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12.md} (79%) rename docs/guides/stay-up-to-date/terraform/{1-how-to-update-to-terraform-13/2-deployment-walkthrough/1-step-2-update-your-code-to-be-compatible-with-terraform-0-13.md => how-to-update-to-terraform-13/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-13.md} (100%) rename docs/guides/stay-up-to-date/terraform/{1-how-to-update-to-terraform-13/2-deployment-walkthrough/2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md => how-to-update-to-terraform-13/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md} (100%) rename docs/guides/stay-up-to-date/terraform/{1-how-to-update-to-terraform-13/2-deployment-walkthrough/3-updating-the-gruntwork-reference-architecture-to-terraform-0-13.md => how-to-update-to-terraform-13/deployment-walkthrough/updating-the-gruntwork-reference-architecture-to-terraform-0-13.md} (90%) rename docs/guides/stay-up-to-date/terraform/{1-how-to-update-to-terraform-13/0-intro.md => how-to-update-to-terraform-13/intro.md} (61%) rename docs/guides/stay-up-to-date/terraform/{2-how-to-update-to-terraform-14 => how-to-update-to-terraform-14}/_category_.json (100%) rename docs/guides/stay-up-to-date/terraform/{2-how-to-update-to-terraform-14/1-core-concepts.md => how-to-update-to-terraform-14/core-concepts.md} (87%) rename docs/guides/stay-up-to-date/terraform/{4-how-to-update-to-terraform-1-x/2-deployment-walkthrough => how-to-update-to-terraform-14/deployment-walkthrough}/_category_.json (100%) rename docs/guides/stay-up-to-date/terraform/{2-how-to-update-to-terraform-14/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-13.md => how-to-update-to-terraform-14/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-13.md} (79%) rename docs/guides/stay-up-to-date/terraform/{2-how-to-update-to-terraform-14/2-deployment-walkthrough/1-step-2-update-your-code-to-be-compatible-with-terraform-0-14.md => how-to-update-to-terraform-14/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-14.md} (100%) rename docs/guides/stay-up-to-date/terraform/{2-how-to-update-to-terraform-14/2-deployment-walkthrough/2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md => how-to-update-to-terraform-14/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md} (100%) rename docs/guides/stay-up-to-date/terraform/{2-how-to-update-to-terraform-14/2-deployment-walkthrough/3-step-4-start-using-lock-files.md => how-to-update-to-terraform-14/deployment-walkthrough/step-4-start-using-lock-files.md} (100%) rename docs/guides/stay-up-to-date/terraform/{2-how-to-update-to-terraform-14/0-intro.md => how-to-update-to-terraform-14/intro.md} (66%) rename docs/guides/stay-up-to-date/terraform/{3-how-to-update-to-terraform-15 => how-to-update-to-terraform-15}/_category_.json (100%) rename docs/guides/stay-up-to-date/terraform/{3-how-to-update-to-terraform-15/1-core-concepts.md => how-to-update-to-terraform-15/core-concepts.md} (100%) rename docs/guides/stay-up-to-date/terraform/{6-how-to-dry-your-reference-architecture/2-deployment-walkthrough => how-to-update-to-terraform-15/deployment-walkthrough}/_category_.json (100%) rename docs/guides/stay-up-to-date/terraform/{3-how-to-update-to-terraform-15/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-14.md => how-to-update-to-terraform-15/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-14.md} (68%) rename docs/guides/stay-up-to-date/terraform/{3-how-to-update-to-terraform-15/2-deployment-walkthrough/1-step-2-update-your-code-to-be-compatible-with-terraform-0-15.md => how-to-update-to-terraform-15/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-15.md} (100%) rename docs/guides/stay-up-to-date/terraform/{3-how-to-update-to-terraform-15/2-deployment-walkthrough/2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md => how-to-update-to-terraform-15/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md} (100%) rename docs/guides/stay-up-to-date/terraform/{3-how-to-update-to-terraform-15/0-intro.md => how-to-update-to-terraform-15/intro.md} (72%) diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/2-prepare-your-infrastructure-live-repository.md b/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/2-prepare-your-infrastructure-live-repository.md deleted file mode 100644 index db3f231f9e..0000000000 --- a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/2-prepare-your-infrastructure-live-repository.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -sidebar_label: Prepare your infrastructure-live repository ---- - -# Prepare your `infrastructure-live` repository - -We’ve previously described exactly how to prepare your repository in the -[Gruntwork Landing Zone guide](../../2-landing-zone/3-deployment-walkthrough/1-prepare-your-infrastructure-live-repository.md). Follow the steps in that section to get your `infrastructure-live` repository set up for the next steps. diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/_category_.json b/_docs-sources/guides/build-it-yourself/achieve-compliance/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/_category_.json rename to _docs-sources/guides/build-it-yourself/achieve-compliance/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/1-core-concepts/_category_.json b/_docs-sources/guides/build-it-yourself/achieve-compliance/core-concepts/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/1-core-concepts/_category_.json rename to _docs-sources/guides/build-it-yourself/achieve-compliance/core-concepts/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/1-core-concepts/0-intro.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/core-concepts/intro.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/1-core-concepts/0-intro.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/core-concepts/intro.md diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/1-core-concepts/1-recommendation-sections.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/core-concepts/recommendation-sections.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/1-core-concepts/1-recommendation-sections.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/core-concepts/recommendation-sections.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/_category_.json b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/_category_.json rename to _docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/5-create-an-iam-user-in-the-root-account.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-an-iam-user-in-the-root-account.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/5-create-an-iam-user-in-the-root-account.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-an-iam-user-in-the-root-account.md diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/3-create-the-root-account.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-the-root-account.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/3-create-the-root-account.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-the-root-account.md diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/9-create-vpc-flow-logs.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-vpc-flow-logs.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/9-create-vpc-flow-logs.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-vpc-flow-logs.md diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/_category_.json b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/_category_.json rename to _docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/1-apply-account-baseline-app-to-logs-account.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-app-to-logs-account.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/1-apply-account-baseline-app-to-logs-account.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-app-to-logs-account.md diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/3-apply-account-baseline-app-to-other-child-accounts.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-app-to-other-child-accounts.md similarity index 99% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/3-apply-account-baseline-app-to-other-child-accounts.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-app-to-other-child-accounts.md index 26bbfeac3c..38b6e41c3e 100644 --- a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/3-apply-account-baseline-app-to-other-child-accounts.md +++ b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-app-to-other-child-accounts.md @@ -275,7 +275,7 @@ On some operating systems, such as MacOS, you may also need to increase your ope 1. Use your IAM user’s user name and password (decrypted using keybase) to log into the web console of the security account (remember to use the IAM user sign-in URL for the security account). -2. Follow the steps in [Lock down the root account IAM users](../6-lock-down-the-root-account-iam-users.md) to lock down your IAM user in the security account. This includes +2. Follow the steps in [Lock down the root account IAM users](../lock-down-the-root-account-iam-users.md) to lock down your IAM user in the security account. This includes configuring an MFA device for your IAM user. 3. After configuring an MFA device, log out, and then log back into the security account again, this time providing your diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/0-apply-account-baseline-root-to-root-account.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-root-to-root-account.md similarity index 99% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/0-apply-account-baseline-root-to-root-account.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-root-to-root-account.md index 277ba2d1b4..0ce0f470c5 100644 --- a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/0-apply-account-baseline-root-to-root-account.md +++ b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-root-to-root-account.md @@ -581,6 +581,6 @@ Use this process to reset the password for the root user of each child account y ## Lock down the root user in the child accounts -Once you’re able to access the root user of each child account, you should follow the steps in [Lock down the root user](../4-lock-down-the-root-user.md) +Once you’re able to access the root user of each child account, you should follow the steps in [Lock down the root user](../lock-down-the-root-user.md) for each of those child accounts—including enabling MFA and deleting the root user’s access keys—and (almost) never use those root users again. diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/2-apply-account-baseline-security-to-security-account.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-security-to-security-account.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/2-apply-account-baseline-security-to-security-account.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-security-to-security-account.md diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/8-enable-key-rotation-for-kms-keys.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/enable-key-rotation-for-kms-keys.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/8-enable-key-rotation-for-kms-keys.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/enable-key-rotation-for-kms-keys.md diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/5-maintain-compliance-by-following-iam-best-practices.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-iam-best-practices.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/5-maintain-compliance-by-following-iam-best-practices.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-iam-best-practices.md diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/7-maintain-compliance-by-following-logging-best-practices.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-logging-best-practices.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/7-maintain-compliance-by-following-logging-best-practices.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-logging-best-practices.md diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/6-maintain-compliance-by-following-storage-best-practices.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-storage-best-practices.md similarity index 88% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/6-maintain-compliance-by-following-storage-best-practices.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-storage-best-practices.md index 2830856fb9..3eba448323 100644 --- a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/6-maintain-compliance-by-following-storage-best-practices.md +++ b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-storage-best-practices.md @@ -3,12 +3,12 @@ ## S3 Buckets To make sure your S3 buckets are compliant with the benchmark, use the -[`private-s3-bucket` module](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/private-s3-bucket) +[`private-s3-bucket` module](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/private-sbucket) to create and manage all of your S3 buckets. This module blocks public access and enforces encryption by default. Note that all Gruntwork modules that create S3 buckets use this module under the hood. You can either use the `private-s3-bucket` module in your own modules, or, if you wish to deploy a standalone S3 bucket, -use the [`s3-bucket` service](https://github.com/gruntwork-io/terraform-aws-service-catalog/blob/master/modules/data-stores/s3-bucket/) +use the [`s3-bucket` service](https://github.com/gruntwork-io/terraform-aws-service-catalog/blob/master/modules/data-stores/sbucket/) from the Gruntwork Service Catalog. To ensure that all the data in your S3 buckets has been discovered, classified and secured, use the diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/4-use-iam-roles-for-ec2-instances.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/use-iam-roles-for-ec2-instances.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/4-use-iam-roles-for-ec2-instances.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/use-iam-roles-for-ec2-instances.md diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/7-deployment-approach.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deployment-approach.md similarity index 87% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/7-deployment-approach.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deployment-approach.md index cb40d79b9c..d61089d820 100644 --- a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/7-deployment-approach.md +++ b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deployment-approach.md @@ -1,7 +1,7 @@ # Deployment approach Before we dive into the code and deployment for each resource, let’s take a step back and understand how the code is structured. -Most of the features explained in the [Production-grade design](../2-production-grade-design/0-intro.md) section will be deployed using the Landing Zone solution, and some more standalone modules like the VPC module. +Most of the features explained in the [Production-grade design](../production-grade-design/intro.md) section will be deployed using the Landing Zone solution, and some more standalone modules like the VPC module. The Landing Zone will be deployed in three steps - the `account-baseline-root` to set up your organization-wide configurations, create the necessary child AWS accounts, set up the CloudTrail and AWS Config buckets. Next, we’ll need to apply the `account-baseline-app` against the created logs account, adding more settings that will be used for aggregation of logs and metrics from the whole organization. Then the `account-baseline-security` will be applied, and that’s responsible to set up your IAM roles and groups that would allow you to access the rest of the accounts within your organization. And finally, the `account-baseline-app` will be applied to an AWS account with the purpose of hosting an application. diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/6-lock-down-the-root-account-iam-users.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/lock-down-the-root-account-iam-users.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/6-lock-down-the-root-account-iam-users.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/lock-down-the-root-account-iam-users.md diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/4-lock-down-the-root-user.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/lock-down-the-root-user.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/4-lock-down-the-root-user.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/lock-down-the-root-user.md diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/0-pre-requisites.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/pre-requisites.md similarity index 94% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/0-pre-requisites.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/pre-requisites.md index 9fbb195aed..36762577b1 100644 --- a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/0-pre-requisites.md +++ b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/pre-requisites.md @@ -4,7 +4,7 @@ pagination_label: Deployment Walkthrough # Pre-requisites -The [Production-grade Design](../2-production-grade-design/0-intro.md) section describes in detail the Terraform resources to use and the approach to take for +The [Production-grade Design](../production-grade-design/intro.md) section describes in detail the Terraform resources to use and the approach to take for each recommendation, but we've already done that grunt work! This section documents how to achieve compliance using the Infrastructure as Code modules from Gruntwork. This walkthrough has the following pre-requisites: diff --git a/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/prepare-your-infrastructure-live-repository.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/prepare-your-infrastructure-live-repository.md new file mode 100644 index 0000000000..1ba70dd285 --- /dev/null +++ b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/prepare-your-infrastructure-live-repository.md @@ -0,0 +1,8 @@ +--- +sidebar_label: Prepare your infrastructure-live repository +--- + +# Prepare your `infrastructure-live` repository + +We’ve previously described exactly how to prepare your repository in the +[Gruntwork Landing Zone guide](../../landing-zone/deployment-walkthrough/prepare-your-infrastructure-live-repository.md). Follow the steps in that section to get your `infrastructure-live` repository set up for the next steps. diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/1-the-gruntwork-solution.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/the-gruntwork-solution.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/1-the-gruntwork-solution.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/the-gruntwork-solution.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/0-intro/_category_.json b/_docs-sources/guides/build-it-yourself/achieve-compliance/intro/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/0-intro/_category_.json rename to _docs-sources/guides/build-it-yourself/achieve-compliance/intro/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/0-intro/1-what-is-the-cis-aws-foundations-benchmark.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/intro/what-is-the-cis-aws-foundations-benchmark.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/0-intro/1-what-is-the-cis-aws-foundations-benchmark.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/intro/what-is-the-cis-aws-foundations-benchmark.md diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/0-intro/0-what-youll-learn-in-this-guide.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/intro/what-youll-learn-in-this-guide.md similarity index 94% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/0-intro/0-what-youll-learn-in-this-guide.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/intro/what-youll-learn-in-this-guide.md index 5458781482..a77ff78f64 100644 --- a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/0-intro/0-what-youll-learn-in-this-guide.md +++ b/_docs-sources/guides/build-it-yourself/achieve-compliance/intro/what-youll-learn-in-this-guide.md @@ -24,8 +24,8 @@ compliant state over time because all of the infrastructure is defined as code. Previously, we supported versions 1.3.0 and 1.2.0 of the Benchmark. If you are looking to upgrade from an older version please follow these in order: -- To upgrade from v1.2.0 to v1.3.0, please follow [this upgrade guide](../../../stay-up-to-date/1-cis/1-how-to-update-to-cis-13/0-intro.md); -- To upgrade from v1.3.0 to v1.4.0, please follow [this upgrade guide](../../../stay-up-to-date/1-cis/0-how-to-update-to-cis-14/0-intro.md). +- To upgrade from v1.2.0 to v1.3.0, please follow [this upgrade guide](../../../stay-up-to-date/cis/how-to-update-to-cis-13/intro.md); +- To upgrade from v1.3.0 to v1.4.0, please follow [this upgrade guide](../../../stay-up-to-date/cis/how-to-update-to-cis-14/intro.md). ![CIS Benchmark Architecture](/img/guides/build-it-yourself/achieve-compliance/cis-account-architecture.png) diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/4-next-steps.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/next-steps.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/4-next-steps.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/next-steps.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/_category_.json b/_docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/_category_.json rename to _docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/1-identity-and-access-management.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/identity-and-access-management.md similarity index 90% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/1-identity-and-access-management.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/identity-and-access-management.md index 6b2260fd58..6ed2b606d1 100644 --- a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/1-identity-and-access-management.md +++ b/_docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/identity-and-access-management.md @@ -274,9 +274,15 @@ substitute `` with the `ServerCertificateId` attribute from th aws iam delete-server-certificate --server-certificate-name ``` -To automate this process you might decide to implement a Lambda function that runs on a regular schedule and removes -all expired SSL/TLS certificates. Check out the [Apply the baseline to the root account](../3-deployment-walkthrough/8-deploy-landing-zone-solution/0-apply-account-baseline-root-to-root-account.md#apply-the-account-baseline-root-baseline-to-the-root-account), [Apply the to the logs account](../3-deployment-walkthrough/8-deploy-landing-zone-solution/1-apply-account-baseline-app-to-logs-account.md) and [Apply the to the security account](../3-deployment-walkthrough/8-deploy-landing-zone-solution/2-apply-account-baseline-security-to-security-account.md) section of the deployment walkthrough -to see how this module is used from the Landing Zone account baselines and is deployed in each of your AWS accounts. +To automate this process you might decide to implement a Lambda function that runs on a regular schedule and removes all +expired SSL/TLS certificates. Check out the [Apply the baseline to the root +account](../deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-root-to-root-account.md#apply-the-account-baseline-root-baseline-to-the-root-account), +[Apply the to the logs +account](../deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-app-to-logs-account.md) and +[Apply the to the security +account](../deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-security-to-security-account.md) +section of the deployment walkthrough to see how this module is used from the Landing Zone account baselines and is +deployed in each of your AWS accounts. ## IAM Access Analyzer @@ -284,9 +290,17 @@ In both versions 1.3.0 and 1.4.0, the CIS recommendations stipulate that the AWS AWS Account or Organization. To achieve this compliance requirement, enable the IAM Access Analyzer service for every AWS region you have enabled in -every one of your AWS accounts. Alternatively, you could make use of the [`iam-access-analyzer-multi-region`](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/iam-access-analyzer-multi-region) module -available in the Gruntwork Service Catalog, or if you’re following this guide, refer to [Apply the baseline to the root account](../3-deployment-walkthrough/8-deploy-landing-zone-solution/0-apply-account-baseline-root-to-root-account.md#apply-the-account-baseline-root-baseline-to-the-root-account), [Apply the to the logs account](../3-deployment-walkthrough/8-deploy-landing-zone-solution/1-apply-account-baseline-app-to-logs-account.md) and [Apply the to the security account](../3-deployment-walkthrough/8-deploy-landing-zone-solution/2-apply-account-baseline-security-to-security-account.md) sections of the -deployment walkthrough to see how this module is used from the Landing Zone account baselines and is deployed in each of your AWS accounts. +every one of your AWS accounts. Alternatively, you could make use of the +[`iam-access-analyzer-multi-region`](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/iam-access-analyzer-multi-region) +module available in the Gruntwork Service Catalog, or if you’re following this guide, refer to [Apply the baseline to +the root +account](../deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-root-to-root-account.md#apply-the-account-baseline-root-baseline-to-the-root-account), +[Apply the to the logs +account](../deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-app-to-logs-account.md) and +[Apply the to the security +account](../deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-security-to-security-account.md) +sections of the deployment walkthrough to see how this module is used from the Landing Zone account baselines and is +deployed in each of your AWS accounts. Once enabled, it will scan only within the boundaries of the AWS Account or Organization it has access to. Only specific resources are analyzed and included in the results - e.g. S3 buckets, SQS, etc. (For the full list of resources supported, diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/0-intro.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/intro.md similarity index 88% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/0-intro.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/intro.md index 845599a64a..85b80a5999 100644 --- a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/0-intro.md +++ b/_docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/intro.md @@ -4,7 +4,7 @@ pagination_label: Production-grade Design # Intro to Production-grade Design -In [core concepts](../1-core-concepts/0-intro.md) we discussed the basics of the AWS Foundations Benchmark. Although it's possible to achieve +In [core concepts](../core-concepts/intro.md) we discussed the basics of the AWS Foundations Benchmark. Although it's possible to achieve compliance with the Benchmark by manually configuring each setting in the web console or entering the CLI commands, we strongly discourage this approach. It precludes [the myriad benefits of using code to manage infrastructure](/docs/intro/core-concepts/infrastructure-as-code). diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/3-logging.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/logging.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/3-logging.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/logging.md diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/4-monitoring.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/monitoring.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/4-monitoring.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/monitoring.md diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/5-networking.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/networking.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/5-networking.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/networking.md diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/2-storage.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/storage.md similarity index 94% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/2-storage.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/storage.md index 6a7d39da58..26cf0f5167 100644 --- a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/2-storage.md +++ b/_docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/storage.md @@ -65,7 +65,7 @@ The CIS 1.4.0 Benchmark recommends a few additional steps to ensure your data is :::info -The steps below are not the full list of actions needed to configure MFA Delete or Amazon Macie for your account. To follow the steps necessary to configure it according to the CIS 1.4.0 Benchmark, please follow the MFA Delete and Macie section in the [the migration guide to CIS 1.4.0](../../../stay-up-to-date/1-cis/0-how-to-update-to-cis-14/0-intro.md), or the deployment guide section in this guide. +The steps below are not the full list of actions needed to configure MFA Delete or Amazon Macie for your account. To follow the steps necessary to configure it according to the CIS 1.4.0 Benchmark, please follow the MFA Delete and Macie section in the [the migration guide to CIS 1.4.0](../../../stay-up-to-date/cis/how-to-update-to-cis-14/intro.md), or the deployment guide section in this guide. ::: ### Enable MFA Delete (recommendation 2.1.3) @@ -105,7 +105,7 @@ aws s3api put-bucket-versioning --region \ --mfa "arn:aws:iam:::mfa/root-account-mfa-device " ``` -We also created a [script](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/private-s3-bucket/mfa-delete-script) to help you enable MFA Delete in all buckets from a single account at once. To learn how to run it and when, please follow the production _Deployment Walkthrough_ guide section below. +We also created a [script](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/private-sbucket/mfa-delete-script) to help you enable MFA Delete in all buckets from a single account at once. To learn how to run it and when, please follow the production _Deployment Walkthrough_ guide section below. ### Configure Amazon Macie (recommendation 2.1.4) diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/5-traceability-matrix.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/traceability-matrix.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/5-traceability-matrix.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/traceability-matrix.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/_category_.json b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/_category_.json rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/_category_.json b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/core-concepts/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/_category_.json rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/core-concepts/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/3-interacting-with-kubernetes.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/core-concepts/interacting-with-kubernetes.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/3-interacting-with-kubernetes.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/core-concepts/interacting-with-kubernetes.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/2-kubernetes-access-control.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-access-control.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/2-kubernetes-access-control.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-access-control.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/1-kubernetes-architecture.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-architecture.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/1-kubernetes-architecture.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-architecture.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/4-kubernetes-resources.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-resources.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/4-kubernetes-resources.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-resources.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/5-options-for-running-kubernetes-in-aws.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/core-concepts/options-for-running-kubernetes-in-aws.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/5-options-for-running-kubernetes-in-aws.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/core-concepts/options-for-running-kubernetes-in-aws.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/0-why-kubernetes.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/core-concepts/why-kubernetes.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/0-why-kubernetes.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/core-concepts/why-kubernetes.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/10-try-out-the-cluster.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/10-try-out-the-cluster.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/10-try-out-the-cluster.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/10-try-out-the-cluster.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/11-updating-the-worker-nodes.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/11-updating-the-worker-nodes.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/11-updating-the-worker-nodes.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/11-updating-the-worker-nodes.md diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/_category_.json b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/_category_.json rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/8-configure-access-to-the-control-plane-and-worker-nodes.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-access-to-the-control-plane-and-worker-nodes.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/8-configure-access-to-the-control-plane-and-worker-nodes.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-access-to-the-control-plane-and-worker-nodes.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/6-configure-logging-metrics-and-alarms-for-the-worker-nodes.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-logging-metrics-and-alarms-for-the-worker-nodes.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/6-configure-logging-metrics-and-alarms-for-the-worker-nodes.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-logging-metrics-and-alarms-for-the-worker-nodes.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/7-configure-role-mapping.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-role-mapping.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/7-configure-role-mapping.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-role-mapping.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/2-configure-the-control-plane.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-control-plane.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/2-configure-the-control-plane.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-control-plane.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/5-configure-the-worker-node-user-data-script.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-worker-node-user-data-script.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/5-configure-the-worker-node-user-data-script.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-worker-node-user-data-script.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/3-configure-the-worker-nodes.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-worker-nodes.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/3-configure-the-worker-nodes.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-worker-nodes.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/4-create-the-worker-node-ami.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/create-the-worker-node-ami.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/4-create-the-worker-node-ami.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/create-the-worker-node-ami.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/9-deploy-the-eks-cluster.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/deploy-the-eks-cluster.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/9-deploy-the-eks-cluster.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/deploy-the-eks-cluster.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/1-deploy-the-vpc.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/deploy-the-vpc.md similarity index 98% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/1-deploy-the-vpc.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/deploy-the-vpc.md index 073dbd24a6..c80c7d431a 100644 --- a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/1-deploy-the-vpc.md +++ b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/deploy-the-vpc.md @@ -1,7 +1,7 @@ # Deploy the VPC The first step is to deploy a VPC. Follow the instructions in -[How to deploy a production-grade VPC on AWS](../../4-vpc/0-intro/0-what-youll-learn-in-this-guide.md) to use +[How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) to use `module-vpc` to create a VPC setup that looks like this: ![A production-grade VPC setup deployed using module-vpc from the Gruntwork Infrastructure as Code Library](/img/guides/build-it-yourself/vpc/vpc-diagram.png) diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/0-pre-requisites.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/pre-requisites.md similarity index 97% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/0-pre-requisites.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/pre-requisites.md index a7e51735c3..991d5c06e8 100644 --- a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/0-pre-requisites.md +++ b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/pre-requisites.md @@ -49,7 +49,7 @@ our [Introduction to Gruntwork](/docs/intro/overview/intro-to-gruntwork). #### AWS accounts This guide deploys infrastructure into one or more AWS accounts. Check out the -[How to configure a production-grade AWS account structure](../../2-landing-zone/0-intro/0-what-youll-learn-in-this-guide.md) +[How to configure a production-grade AWS account structure](../../landing-zone/intro/what-youll-learn-in-this-guide.md) guide for instructions. You will also need to be able to authenticate to these accounts on the CLI: check out [A Comprehensive Guide to Authenticating to AWS on the Command Line](https://blog.gruntwork.io/a-comprehensive-guide-to-authenticating-to-aws-on-the-command-line-63656a686799) for instructions. diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/0-intro/_category_.json b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/intro/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/0-intro/_category_.json rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/intro/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/0-intro/1-what-is-kubernetes.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/intro/what-is-kubernetes.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/0-intro/1-what-is-kubernetes.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/intro/what-is-kubernetes.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/0-intro/0-what-youll-learn-in-this-guide.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/intro/what-youll-learn-in-this-guide.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/0-intro/0-what-youll-learn-in-this-guide.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/intro/what-youll-learn-in-this-guide.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/4-next-steps.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/next-steps.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/4-next-steps.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/next-steps.md diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/2-production-grade-design/_category_.json b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/2-production-grade-design/_category_.json rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/5-authenticate.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/authenticate.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/5-authenticate.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/authenticate.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/3-control-plane.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/control-plane.md similarity index 91% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/3-control-plane.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/control-plane.md index 4cb4c636c9..cc4ea19a30 100644 --- a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/3-control-plane.md +++ b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/control-plane.md @@ -19,7 +19,7 @@ minor version. Your EKS cluster will run in the subnets you specify. We strongly recommend running solely in private subnets that are NOT directly accessible from the public Internet. See -[How to deploy a production-grade VPC on AWS](../../4-vpc/0-intro/0-what-youll-learn-in-this-guide.md) for more +[How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) for more info. #### Endpoint access @@ -28,7 +28,7 @@ You can configure whether the [API endpoint for your EKS cluster](https://docs.a is accessible from (a) within the same VPC and/or (b) from the public Internet. We recommend allowing access from within the VPC, but not from the public Internet. If you need to talk to your Kubernetes cluster from your own computer (e.g., to issue commands via `kubectl`), use a bastion host or VPN server. See -[How to deploy a production-grade VPC on AWS](../../4-vpc/0-intro/0-what-youll-learn-in-this-guide.md) for more +[How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) for more info. #### Cluster IAM Role diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/6-iam-role-mapping-and-rbac.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/iam-role-mapping-and-rbac.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/6-iam-role-mapping-and-rbac.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/iam-role-mapping-and-rbac.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/0-intro.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/intro.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/0-intro.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/intro.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/7-logging.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/logging.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/7-logging.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/logging.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/8-protecting-pods.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/protecting-pods.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/8-protecting-pods.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/protecting-pods.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/1-use-eks.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/use-eks.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/1-use-eks.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/use-eks.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/2-vpc-configuration.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/vpc-configuration.md similarity index 93% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/2-vpc-configuration.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/vpc-configuration.md index deed18e28d..f1d6e48b2c 100644 --- a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/2-vpc-configuration.md +++ b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/vpc-configuration.md @@ -2,7 +2,7 @@ EKS relies on a _[Virtual Private Cloud (VPC)](https://aws.amazon.com/vpc/)_ to provide the basic network topology and to manage communication across the nodes (see -[How to deploy a production-grade VPC on AWS](../../4-vpc/0-intro/0-what-youll-learn-in-this-guide.md) for more +[How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) for more information on VPCs). Here are the key VPC considerations for your EKS cluster:
diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/4-worker-nodes.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/worker-nodes.md similarity index 96% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/4-worker-nodes.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/worker-nodes.md index 5df8a2a58d..7b16bc04f7 100644 --- a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/4-worker-nodes.md +++ b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/worker-nodes.md @@ -20,7 +20,7 @@ value `owned`. We strongly recommend running the Auto Scaling Group for your worker nodes in private subnets that are NOT directly accessible from the public Internet. See -[How to deploy a production-grade VPC on AWS](../../4-vpc/0-intro/0-what-youll-learn-in-this-guide.md) for more +[How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) for more info. #### AMI diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/_category_.json b/_docs-sources/guides/build-it-yourself/landing-zone/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/_category_.json rename to _docs-sources/guides/build-it-yourself/landing-zone/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/_category_.json b/_docs-sources/guides/build-it-yourself/landing-zone/core-concepts/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/_category_.json rename to _docs-sources/guides/build-it-yourself/landing-zone/core-concepts/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/1-core-concepts/0-aws-account.md b/_docs-sources/guides/build-it-yourself/landing-zone/core-concepts/aws-account.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/1-core-concepts/0-aws-account.md rename to _docs-sources/guides/build-it-yourself/landing-zone/core-concepts/aws-account.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/1-core-concepts/9-aws-config.md b/_docs-sources/guides/build-it-yourself/landing-zone/core-concepts/aws-config.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/1-core-concepts/9-aws-config.md rename to _docs-sources/guides/build-it-yourself/landing-zone/core-concepts/aws-config.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/1-core-concepts/7-aws-organizations.md b/_docs-sources/guides/build-it-yourself/landing-zone/core-concepts/aws-organizations.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/1-core-concepts/7-aws-organizations.md rename to _docs-sources/guides/build-it-yourself/landing-zone/core-concepts/aws-organizations.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/1-core-concepts/8-cloud-trail.md b/_docs-sources/guides/build-it-yourself/landing-zone/core-concepts/cloud-trail.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/1-core-concepts/8-cloud-trail.md rename to _docs-sources/guides/build-it-yourself/landing-zone/core-concepts/cloud-trail.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/1-core-concepts/6-federated-authentication.md b/_docs-sources/guides/build-it-yourself/landing-zone/core-concepts/federated-authentication.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/1-core-concepts/6-federated-authentication.md rename to _docs-sources/guides/build-it-yourself/landing-zone/core-concepts/federated-authentication.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/1-core-concepts/10-guard-duty.md b/_docs-sources/guides/build-it-yourself/landing-zone/core-concepts/guard-duty.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/1-core-concepts/10-guard-duty.md rename to _docs-sources/guides/build-it-yourself/landing-zone/core-concepts/guard-duty.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/1-core-concepts/4-iam-groups.md b/_docs-sources/guides/build-it-yourself/landing-zone/core-concepts/iam-groups.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/1-core-concepts/4-iam-groups.md rename to _docs-sources/guides/build-it-yourself/landing-zone/core-concepts/iam-groups.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/1-core-concepts/3-iam-policies.md b/_docs-sources/guides/build-it-yourself/landing-zone/core-concepts/iam-policies.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/1-core-concepts/3-iam-policies.md rename to _docs-sources/guides/build-it-yourself/landing-zone/core-concepts/iam-policies.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/1-core-concepts/5-iam-roles.md b/_docs-sources/guides/build-it-yourself/landing-zone/core-concepts/iam-roles.md similarity index 96% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/1-core-concepts/5-iam-roles.md rename to _docs-sources/guides/build-it-yourself/landing-zone/core-concepts/iam-roles.md index 8ae2d414c2..a352e5e873 100644 --- a/_docs-sources/guides/build-it-yourself/2-landing-zone/1-core-concepts/5-iam-roles.md +++ b/_docs-sources/guides/build-it-yourself/landing-zone/core-concepts/iam-roles.md @@ -5,8 +5,6 @@ you to attach IAM policies to it, (b) specify which other IAM entities to trust, can _assume_ the IAM role to be temporarily get access to the permissions in those IAM policies. The two most common use cases for IAM roles are: - -
#### Service roles @@ -26,13 +24,10 @@ S3 bucket in account `B` and allow that role to be assumed by an IAM user in acc able to access the contents of the S3 bucket by assuming the IAM role in account `B`. This ability to assume IAM roles across different AWS accounts is the critical glue that truly makes a multi AWS account structure possible. -
Here are some more details on how IAM roles work: - -
#### IAM policies @@ -45,30 +40,29 @@ You must define a _trust policy_ for each IAM role, which is a JSON document (ve specifies who can assume this IAM role. For example, here is a trust policy that allows this IAM role to be assumed by an IAM user named `Bob` in AWS account `111122223333`: -
-``` json +```json { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "sts:AssumeRole", - "Principal": {"AWS": "arn:aws:iam::111122223333:user/Bob"} + "Principal": { "AWS": "arn:aws:iam::111122223333:user/Bob" } } ] } ``` Note that a trust policy alone does NOT automatically give Bob the ability to assume this IAM role. Cross-account -access always requires permissions in *both* accounts. So, if Bob is in AWS account `111122223333` and you want him to +access always requires permissions in _both_ accounts. So, if Bob is in AWS account `111122223333` and you want him to have access to an IAM role called `foo` in account `444455556666`, then you need to configure permissions in both accounts: first, in account `444455556666`, the `foo` IAM role must have a trust policy that gives `sts:AssumeRole` permissions to account `111122223333`, as shown above; second, in account `111122223333`, you also need to attach an IAM policy to Bob’s IAM user that allows him to assume the `foo` IAM role, which might look like this: -``` json +```json { "Version": "2012-10-17", "Statement": [ @@ -81,8 +75,6 @@ IAM policy to Bob’s IAM user that allows him to assume the `foo` IAM role, whi } ``` - -
#### Assuming an IAM role @@ -96,7 +88,6 @@ will be valid for 1-12 hours, depending on IAM role settings, after which you mu new keys. Note that to make the `AssumeRole` API call, you must first authenticate to AWS using some other mechanism. For example, for an IAM user to assume an IAM role, the workflow looks like this: -
![The process for assuming an IAM role](/img/guides/build-it-yourself/landing-zone/assume-iam-role.png) @@ -114,8 +105,6 @@ The basic steps are: 5. Now all of your subsequent API calls will be on behalf of the assumed IAM role, with access to whatever permissions are attached to that role - -
#### IAM roles and AWS services @@ -123,7 +112,7 @@ The basic steps are: Most AWS services have native support built-in for assuming IAM roles. For example, you can associate an IAM role directly with an EC2 instance, and that instance will automatically assume the IAM role every few hours, making the temporary credentials available in -_[EC2 instance metadata](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html#instancedata-data-retrieval)_. +_[EC2 instance metadata](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ecinstance-metadata.html#instancedata-data-retrieval)_. Just about every AWS CLI and SDK tool knows how to read and periodically update temporary credentials from EC2 instance metadata, so in practice, as soon as you attach an IAM role to an EC2 instance, any code running on that EC2 instance can automatically make API calls on behalf of that IAM role, with whatever permissions are attached to that @@ -132,9 +121,4 @@ copy credentials (access keys) onto that instance. The same strategy works with use IAM roles as a secure way to give your Lambda functions, ECS services, Step Functions, and many other AWS services permissions to access specific resources in your AWS account. -
- - - - diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/1-core-concepts/2-iam-users.md b/_docs-sources/guides/build-it-yourself/landing-zone/core-concepts/iam-users.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/1-core-concepts/2-iam-users.md rename to _docs-sources/guides/build-it-yourself/landing-zone/core-concepts/iam-users.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/1-core-concepts/1-root-user.md b/_docs-sources/guides/build-it-yourself/landing-zone/core-concepts/root-user.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/1-core-concepts/1-root-user.md rename to _docs-sources/guides/build-it-yourself/landing-zone/core-concepts/root-user.md diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/_category_.json b/_docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/_category_.json rename to _docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/11-apply-the-security-baseline-to-the-logs-account.md b/_docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-logs-account.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/11-apply-the-security-baseline-to-the-logs-account.md rename to _docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-logs-account.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/13-apply-the-security-baseline-to-the-other-child-accounts.md b/_docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-other-child-accounts.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/13-apply-the-security-baseline-to-the-other-child-accounts.md rename to _docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-other-child-accounts.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/8-apply-the-security-baseline-to-the-root-account.md b/_docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-root-account.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/8-apply-the-security-baseline-to-the-root-account.md rename to _docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-root-account.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/12-apply-the-security-baseline-to-the-security-account.md b/_docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-security-account.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/12-apply-the-security-baseline-to-the-security-account.md rename to _docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-security-account.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/6-configure-the-security-baseline-for-the-root-account.md b/_docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/configure-the-security-baseline-for-the-root-account.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/6-configure-the-security-baseline-for-the-root-account.md rename to _docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/configure-the-security-baseline-for-the-root-account.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/4-create-an-iam-user-in-the-root-account.md b/_docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/create-an-iam-user-in-the-root-account.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/4-create-an-iam-user-in-the-root-account.md rename to _docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/create-an-iam-user-in-the-root-account.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/2-create-the-root-account.md b/_docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/create-the-root-account.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/2-create-the-root-account.md rename to _docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/create-the-root-account.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/7-import-existing-resources-from-the-root-account-into-terraform-state.md b/_docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/import-existing-resources-from-the-root-account-into-terraform-state.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/7-import-existing-resources-from-the-root-account-into-terraform-state.md rename to _docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/import-existing-resources-from-the-root-account-into-terraform-state.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/5-lock-down-the-root-account-iam-users.md b/_docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/lock-down-the-root-account-iam-users.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/5-lock-down-the-root-account-iam-users.md rename to _docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/lock-down-the-root-account-iam-users.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/10-lock-down-the-root-user-in-the-child-accounts.md b/_docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/lock-down-the-root-user-in-the-child-accounts.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/10-lock-down-the-root-user-in-the-child-accounts.md rename to _docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/lock-down-the-root-user-in-the-child-accounts.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/3-lock-down-the-root-user.md b/_docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/lock-down-the-root-user.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/3-lock-down-the-root-user.md rename to _docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/lock-down-the-root-user.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/0-pre-requisites.md b/_docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/pre-requisites.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/0-pre-requisites.md rename to _docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/pre-requisites.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/1-prepare-your-infrastructure-live-repository.md b/_docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/prepare-your-infrastructure-live-repository.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/1-prepare-your-infrastructure-live-repository.md rename to _docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/prepare-your-infrastructure-live-repository.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/9-reset-the-root-user-password-in-each-child-account.md b/_docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/reset-the-root-user-password-in-each-child-account.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/9-reset-the-root-user-password-in-each-child-account.md rename to _docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/reset-the-root-user-password-in-each-child-account.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/14-try-authenticating-as-an-iam-user-to-the-child-accounts.md b/_docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/try-authenticating-as-an-iam-user-to-the-child-accounts.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/14-try-authenticating-as-an-iam-user-to-the-child-accounts.md rename to _docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/try-authenticating-as-an-iam-user-to-the-child-accounts.md diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/0-intro/_category_.json b/_docs-sources/guides/build-it-yourself/landing-zone/intro/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/0-intro/_category_.json rename to _docs-sources/guides/build-it-yourself/landing-zone/intro/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/0-intro/2-gruntwork-aws-landing-zone-vs-the-alternatives.md b/_docs-sources/guides/build-it-yourself/landing-zone/intro/gruntwork-aws-landing-zone-vs-the-alternatives.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/0-intro/2-gruntwork-aws-landing-zone-vs-the-alternatives.md rename to _docs-sources/guides/build-it-yourself/landing-zone/intro/gruntwork-aws-landing-zone-vs-the-alternatives.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/0-intro/1-what-is-an-aws-account-structure.md b/_docs-sources/guides/build-it-yourself/landing-zone/intro/what-is-an-aws-account-structure.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/0-intro/1-what-is-an-aws-account-structure.md rename to _docs-sources/guides/build-it-yourself/landing-zone/intro/what-is-an-aws-account-structure.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/0-intro/0-what-youll-learn-in-this-guide.md b/_docs-sources/guides/build-it-yourself/landing-zone/intro/what-youll-learn-in-this-guide.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/0-intro/0-what-youll-learn-in-this-guide.md rename to _docs-sources/guides/build-it-yourself/landing-zone/intro/what-youll-learn-in-this-guide.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/4-next-steps.md b/_docs-sources/guides/build-it-yourself/landing-zone/next-steps.md similarity index 69% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/4-next-steps.md rename to _docs-sources/guides/build-it-yourself/landing-zone/next-steps.md index 2e7f31ac3c..3b37dc077d 100644 --- a/_docs-sources/guides/build-it-yourself/2-landing-zone/4-next-steps.md +++ b/_docs-sources/guides/build-it-yourself/landing-zone/next-steps.md @@ -2,4 +2,4 @@ Now that you have your basic AWS account structure set up, the next step is to start deploying infrastructure in those accounts! Usually, the best starting point is to configure your network topology, as described in -[How to deploy a production-grade VPC on AWS](../4-vpc/0-intro/0-what-youll-learn-in-this-guide.md). +[How to deploy a production-grade VPC on AWS](../vpc/intro/what-youll-learn-in-this-guide.md). diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/2-production-grade-design/_category_.json b/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/2-production-grade-design/_category_.json rename to _docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/9-aws-config.md b/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/aws-config.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/9-aws-config.md rename to _docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/aws-config.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/2-child-accounts.md b/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/child-accounts.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/2-child-accounts.md rename to _docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/child-accounts.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/8-cloud-trail.md b/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/cloud-trail.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/8-cloud-trail.md rename to _docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/cloud-trail.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/11-federated-auth.md b/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/federated-auth.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/11-federated-auth.md rename to _docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/federated-auth.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/10-guard-duty.md b/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/guard-duty.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/10-guard-duty.md rename to _docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/guard-duty.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/7-iam-roles-for-services.md b/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-services.md similarity index 97% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/7-iam-roles-for-services.md rename to _docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-services.md index 9a4b6f3217..3d1f3971c9 100644 --- a/_docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/7-iam-roles-for-services.md +++ b/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-services.md @@ -54,7 +54,7 @@ need to take extra care in terms of who can assume this IAM role, what permissio services. For example, if you have Jenkins running on an EC2 instance, and you give that EC2 instance access to an IAM role so it can deploy your apps, you should do your best to minimize the permissions that IAM role has (e.g., to just `ecs` permissions if deploying to ECS) and you should ensure that your Jenkins instance runs in private -subnets so that it is NOT accessible from the public Internet (see [How to deploy a production-grade VPC on AWS](../../4-vpc/0-intro/0-what-youll-learn-in-this-guide.md)). +subnets so that it is NOT accessible from the public Internet (see [How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md)). #### Use the right Principal @@ -89,7 +89,7 @@ want an IAM role that can be assumed by a Lambda function, the `Principal` will While IAM roles offer a convenient way to give an EC2 instance permissions to make API calls without having to manually copy credentials to the EC2 instance, the default security configuration for them is not particularly secure. That’s because the IAM role is exposed to the code on the EC2 instance through -[EC2 instance metadata](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html#instancedata-data-retrieval), +[EC2 instance metadata](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ecinstance-metadata.html#instancedata-data-retrieval), which is an http endpoint (`\http://169.254.169.254`) that _anyone_ on the EC2 instance can access. That means that any compromise of that EC2 instance instantly gives an attacker access to all the permissions in that IAM role. We **strongly** recommend mitigating this by limiting access to the endpoint solely to specific OS users (e.g., solely to diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/3-iam-roles-for-users.md b/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-users.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/3-iam-roles-for-users.md rename to _docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-users.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/4-iam-users-and-groups.md b/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/iam-users-and-groups.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/4-iam-users-and-groups.md rename to _docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/iam-users-and-groups.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/0-intro.md b/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/intro.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/0-intro.md rename to _docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/intro.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/5-mfa-policy.md b/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/mfa-policy.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/5-mfa-policy.md rename to _docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/mfa-policy.md diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/6-password-policy.md b/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/password-policy.md similarity index 76% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/6-password-policy.md rename to _docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/password-policy.md index 8f5ceaa5c4..1e586991ea 100644 --- a/_docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/6-password-policy.md +++ b/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/password-policy.md @@ -3,4 +3,4 @@ In any account that has IAM users (which should just be the root and security accounts), configure a password policy that ensures all IAM users have strong passwords. The exact policy you use depends on your company’s requirements (e.g., certain compliance requirements may force you to use a specific password policy), but you may want to consider -[NIST 800-63 guidelines](https://pages.nist.gov/800-63-3/sp800-63b.html#memsecret) as a reasonable starting point. +[NIST 800-63 guidelines](https://pages.nist.gov/8063/sp8063b.html#memsecret) as a reasonable starting point. diff --git a/_docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/1-the-root-account.md b/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/the-root-account.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/2-landing-zone/2-production-grade-design/1-the-root-account.md rename to _docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/the-root-account.md diff --git a/_docs-sources/guides/build-it-yourself/1-overview.md b/_docs-sources/guides/build-it-yourself/overview.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/1-overview.md rename to _docs-sources/guides/build-it-yourself/overview.md diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/_category_.json b/_docs-sources/guides/build-it-yourself/pipelines/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/_category_.json rename to _docs-sources/guides/build-it-yourself/pipelines/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/1-core-concepts/_category_.json b/_docs-sources/guides/build-it-yourself/pipelines/core-concepts/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/1-core-concepts/_category_.json rename to _docs-sources/guides/build-it-yourself/pipelines/core-concepts/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/1-core-concepts/5-ci-cd-platforms.md b/_docs-sources/guides/build-it-yourself/pipelines/core-concepts/ci-cd-platforms.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/1-core-concepts/5-ci-cd-platforms.md rename to _docs-sources/guides/build-it-yourself/pipelines/core-concepts/ci-cd-platforms.md diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/1-core-concepts/3-ci-cd-workflows.md b/_docs-sources/guides/build-it-yourself/pipelines/core-concepts/ci-cd-workflows.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/1-core-concepts/3-ci-cd-workflows.md rename to _docs-sources/guides/build-it-yourself/pipelines/core-concepts/ci-cd-workflows.md diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/1-core-concepts/4-threat-model-of-ci-cd.md b/_docs-sources/guides/build-it-yourself/pipelines/core-concepts/threat-model-of-ci-cd.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/1-core-concepts/4-threat-model-of-ci-cd.md rename to _docs-sources/guides/build-it-yourself/pipelines/core-concepts/threat-model-of-ci-cd.md diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/1-core-concepts/1-trunk-based-development-model.md b/_docs-sources/guides/build-it-yourself/pipelines/core-concepts/trunk-based-development-model.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/1-core-concepts/1-trunk-based-development-model.md rename to _docs-sources/guides/build-it-yourself/pipelines/core-concepts/trunk-based-development-model.md diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/1-core-concepts/2-types-of-infrastructure-code.md b/_docs-sources/guides/build-it-yourself/pipelines/core-concepts/types-of-infrastructure-code.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/1-core-concepts/2-types-of-infrastructure-code.md rename to _docs-sources/guides/build-it-yourself/pipelines/core-concepts/types-of-infrastructure-code.md diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/1-core-concepts/0-why-is-it-important-to-have-ci-cd.md b/_docs-sources/guides/build-it-yourself/pipelines/core-concepts/why-is-it-important-to-have-ci-cd.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/1-core-concepts/0-why-is-it-important-to-have-ci-cd.md rename to _docs-sources/guides/build-it-yourself/pipelines/core-concepts/why-is-it-important-to-have-ci-cd.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/_category_.json b/_docs-sources/guides/build-it-yourself/pipelines/deployment-walkthrough/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/_category_.json rename to _docs-sources/guides/build-it-yourself/pipelines/deployment-walkthrough/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/5-configure-ci-server.md b/_docs-sources/guides/build-it-yourself/pipelines/deployment-walkthrough/configure-ci-server.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/5-configure-ci-server.md rename to _docs-sources/guides/build-it-yourself/pipelines/deployment-walkthrough/configure-ci-server.md diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/4-define-pipeline-as-code.md b/_docs-sources/guides/build-it-yourself/pipelines/deployment-walkthrough/define-pipeline-as-code.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/4-define-pipeline-as-code.md rename to _docs-sources/guides/build-it-yourself/pipelines/deployment-walkthrough/define-pipeline-as-code.md diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/1-deploy-a-vpc.md b/_docs-sources/guides/build-it-yourself/pipelines/deployment-walkthrough/deploy-a-vpc.md similarity index 91% rename from _docs-sources/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/1-deploy-a-vpc.md rename to _docs-sources/guides/build-it-yourself/pipelines/deployment-walkthrough/deploy-a-vpc.md index f430e74095..1f54d9aea1 100644 --- a/_docs-sources/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/1-deploy-a-vpc.md +++ b/_docs-sources/guides/build-it-yourself/pipelines/deployment-walkthrough/deploy-a-vpc.md @@ -1,7 +1,7 @@ # Deploy a VPC The first step is to deploy a VPC. Follow the instructions in -[How to deploy a production-grade VPC on AWS](../../4-vpc/0-intro/0-what-youll-learn-in-this-guide.md) to use +[How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) to use `module-vpc` to create a VPC setup that looks like this: ![A production-grade VPC setup deployed using module-vpc from the Gruntwork Infrastructure as Code Library](/img/guides/build-it-yourself/pipelines/vpc-diagram.png) diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/2-deploy-the-ecs-deploy-runner.md b/_docs-sources/guides/build-it-yourself/pipelines/deployment-walkthrough/deploy-the-ecs-deploy-runner.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/2-deploy-the-ecs-deploy-runner.md rename to _docs-sources/guides/build-it-yourself/pipelines/deployment-walkthrough/deploy-the-ecs-deploy-runner.md diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/0-pre-requisites.md b/_docs-sources/guides/build-it-yourself/pipelines/deployment-walkthrough/pre-requisites.md similarity index 72% rename from _docs-sources/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/0-pre-requisites.md rename to _docs-sources/guides/build-it-yourself/pipelines/deployment-walkthrough/pre-requisites.md index 986a7925fd..3d543d8cea 100644 --- a/_docs-sources/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/0-pre-requisites.md +++ b/_docs-sources/guides/build-it-yourself/pipelines/deployment-walkthrough/pre-requisites.md @@ -36,22 +36,21 @@ official getting started guide](https://circleci.com/docs/2.0/getting-started/#s #### AWS accounts -This guide deploys infrastructure into one or more AWS accounts. Check out the -[Production Grade AWS Account Structure](https://gruntwork.io/guides/foundations/how-to-configure-production-grade-aws-account-structure) guide for instructions. -You will also need to be able to authenticate to these accounts on the CLI: check out -[A Comprehensive Guide to Authenticating to AWS on the Command Line](https://blog.gruntwork.io/a-comprehensive-guide-to-authenticating-to-aws-on-the-command-line-63656a686799) -for instructions. +This guide deploys infrastructure into one or more AWS accounts. Check out the [Production Grade AWS Account +Structure](https://gruntwork.io/guides/foundations/how-to-configure-production-grade-aws-account-structure) guide for +instructions. You will also need to be able to authenticate to these accounts on the CLI: check out [A Comprehensive +Guide to Authenticating to AWS on the Command +Line](https://blog.gruntwork.io/a-comprehensive-guide-to-authenticating-to-aws-on-the-command-line-63656a686799) for +instructions. #### Repository structure -This guide assumes your infrastructure code is organized in a manner similar to -that covered in the [Prepare Your Module](/docs/intro/first-deployment/using-terraform-modules) introduction section. This means -that you should have two repositories for your infrastructure code, -`infrastructure-modules` and `infrastructure-live`. Make sure that the +This guide assumes your infrastructure code is organized in a manner similar to that covered in the [Prepare Your +Module](/docs/intro/first-deployment/using-terraform-modules) introduction section. This means that you should have two +repositories for your≤ infrastructure code, `infrastructure-modules` and `infrastructure-live`. Make sure that the `infrastructure-live` repository is locked down as recommended in [Lock down VCS -systems](../2-production-grade-design/7-lock-down-vcs-systems.md). This guide -will assume that `master` is the protected branch where infrastructure is -deployed from. +systems](../production-grade-design/lock-down-vcs-systems.md). This guide will assume that `master` is the protected +branch where infrastructure is deployed from.
diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/3-try-out-the-ecs-deploy-runner.md b/_docs-sources/guides/build-it-yourself/pipelines/deployment-walkthrough/try-out-the-ecs-deploy-runner.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/3-try-out-the-ecs-deploy-runner.md rename to _docs-sources/guides/build-it-yourself/pipelines/deployment-walkthrough/try-out-the-ecs-deploy-runner.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/0-intro/_category_.json b/_docs-sources/guides/build-it-yourself/pipelines/intro/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/0-intro/_category_.json rename to _docs-sources/guides/build-it-yourself/pipelines/intro/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/0-intro/1-what-is-continuous-integration-and-continuous-delivery.md b/_docs-sources/guides/build-it-yourself/pipelines/intro/what-is-continuous-integration-and-continuous-delivery.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/0-intro/1-what-is-continuous-integration-and-continuous-delivery.md rename to _docs-sources/guides/build-it-yourself/pipelines/intro/what-is-continuous-integration-and-continuous-delivery.md diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/0-intro/2-what-this-guide-will-not-cover.md b/_docs-sources/guides/build-it-yourself/pipelines/intro/what-this-guide-will-not-cover.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/0-intro/2-what-this-guide-will-not-cover.md rename to _docs-sources/guides/build-it-yourself/pipelines/intro/what-this-guide-will-not-cover.md diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/0-intro/0-what-youll-learn-in-this-guide.md b/_docs-sources/guides/build-it-yourself/pipelines/intro/what-youll-learn-in-this-guide.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/0-intro/0-what-youll-learn-in-this-guide.md rename to _docs-sources/guides/build-it-yourself/pipelines/intro/what-youll-learn-in-this-guide.md diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/4-next-steps.md b/_docs-sources/guides/build-it-yourself/pipelines/next-steps.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/4-next-steps.md rename to _docs-sources/guides/build-it-yourself/pipelines/next-steps.md diff --git a/_docs-sources/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/_category_.json b/_docs-sources/guides/build-it-yourself/pipelines/production-grade-design/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/_category_.json rename to _docs-sources/guides/build-it-yourself/pipelines/production-grade-design/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/2-production-grade-design/0-intro.md b/_docs-sources/guides/build-it-yourself/pipelines/production-grade-design/intro.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/2-production-grade-design/0-intro.md rename to _docs-sources/guides/build-it-yourself/pipelines/production-grade-design/intro.md diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/2-production-grade-design/3-limit-triggers-for-deploy-server.md b/_docs-sources/guides/build-it-yourself/pipelines/production-grade-design/limit-triggers-for-deploy-server.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/2-production-grade-design/3-limit-triggers-for-deploy-server.md rename to _docs-sources/guides/build-it-yourself/pipelines/production-grade-design/limit-triggers-for-deploy-server.md diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/2-production-grade-design/7-lock-down-vcs-systems.md b/_docs-sources/guides/build-it-yourself/pipelines/production-grade-design/lock-down-vcs-systems.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/2-production-grade-design/7-lock-down-vcs-systems.md rename to _docs-sources/guides/build-it-yourself/pipelines/production-grade-design/lock-down-vcs-systems.md diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/2-production-grade-design/2-options-for-deploy-server.md b/_docs-sources/guides/build-it-yourself/pipelines/production-grade-design/options-for-deploy-server.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/2-production-grade-design/2-options-for-deploy-server.md rename to _docs-sources/guides/build-it-yourself/pipelines/production-grade-design/options-for-deploy-server.md diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/2-production-grade-design/9-summary-of-deployment-sequence.md b/_docs-sources/guides/build-it-yourself/pipelines/production-grade-design/summary-of-deployment-sequence.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/2-production-grade-design/9-summary-of-deployment-sequence.md rename to _docs-sources/guides/build-it-yourself/pipelines/production-grade-design/summary-of-deployment-sequence.md diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/2-production-grade-design/8-summary-of-mitigations.md b/_docs-sources/guides/build-it-yourself/pipelines/production-grade-design/summary-of-mitigations.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/2-production-grade-design/8-summary-of-mitigations.md rename to _docs-sources/guides/build-it-yourself/pipelines/production-grade-design/summary-of-mitigations.md diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/2-production-grade-design/4-use-a-vpc-to-lock-down-deploy-server.md b/_docs-sources/guides/build-it-yourself/pipelines/production-grade-design/use-a-vpc-to-lock-down-deploy-server.md similarity index 71% rename from _docs-sources/guides/build-it-yourself/3-pipelines/2-production-grade-design/4-use-a-vpc-to-lock-down-deploy-server.md rename to _docs-sources/guides/build-it-yourself/pipelines/production-grade-design/use-a-vpc-to-lock-down-deploy-server.md index 54c1e9dfb7..74d114a2ce 100644 --- a/_docs-sources/guides/build-it-yourself/3-pipelines/2-production-grade-design/4-use-a-vpc-to-lock-down-deploy-server.md +++ b/_docs-sources/guides/build-it-yourself/pipelines/production-grade-design/use-a-vpc-to-lock-down-deploy-server.md @@ -1,6 +1,6 @@ # Use a VPC to lock down deploy server Run your infrastructure deployment workloads in a [Virtual Private Cloud (VPC)](https://aws.amazon.com/vpc/) to isolate -the workloads in a restricted network topology (see [How to deploy a production-grade VPC on AWS](../../4-vpc/0-intro/0-what-youll-learn-in-this-guide.md) for more information on VPCs). Configure it to run all workloads in private +the workloads in a restricted network topology (see [How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) for more information on VPCs). Configure it to run all workloads in private subnets that are not publicly accessible. Make sure to block all inbound internet access and consider blocking all outbound access except for the minimum required (e.g, allow access to AWS APIs). diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/2-production-grade-design/6-use-approval-flows.md b/_docs-sources/guides/build-it-yourself/pipelines/production-grade-design/use-approval-flows.md similarity index 90% rename from _docs-sources/guides/build-it-yourself/3-pipelines/2-production-grade-design/6-use-approval-flows.md rename to _docs-sources/guides/build-it-yourself/pipelines/production-grade-design/use-approval-flows.md index c5e62f6f1d..0198713139 100644 --- a/_docs-sources/guides/build-it-yourself/3-pipelines/2-production-grade-design/6-use-approval-flows.md +++ b/_docs-sources/guides/build-it-yourself/pipelines/production-grade-design/use-approval-flows.md @@ -1,6 +1,6 @@ # Use approval flows -It is important that human review is baked into each deployment. As covered in [CI/CD workflows](../1-core-concepts/3-ci-cd-workflows.md), it is difficult to +It is important that human review is baked into each deployment. As covered in [CI/CD workflows](../core-concepts/ci-cd-workflows.md), it is difficult to build an automated test suite that builds enough confidence in your infrastructure code to do the right thing. This is important, as failed infrastructure deployments could be catastrophic to your business, and there is no concept of rollback with infrastructure deployment tools. This means that you will almost always want to have some form of approval diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/2-production-grade-design/1-use-generic-ci-cd-platforms-as-a-workflow-engine-but-run-infrastructure-deployments-from-within-your-account.md b/_docs-sources/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 similarity index 95% rename from _docs-sources/guides/build-it-yourself/3-pipelines/2-production-grade-design/1-use-generic-ci-cd-platforms-as-a-workflow-engine-but-run-infrastructure-deployments-from-within-your-account.md rename to _docs-sources/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 05aa133668..05f689f859 100644 --- a/_docs-sources/guides/build-it-yourself/3-pipelines/2-production-grade-design/1-use-generic-ci-cd-platforms-as-a-workflow-engine-but-run-infrastructure-deployments-from-within-your-account.md +++ b/_docs-sources/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 @@ -1,6 +1,6 @@ # Use generic CI/CD platforms as a workflow engine but run infrastructure deployments from within your account -Given the limitations and tradeoffs of the various platforms we covered in [CI/CD platforms](../1-core-concepts/5-ci-cd-platforms.md), we don’t recommend +Given the limitations and tradeoffs of the various platforms we covered in [CI/CD platforms](../core-concepts/ci-cd-platforms.md), we don’t recommend relying on a single platform for implementing the entire workflow. Instead, we recommend a hybrid solution that takes advantage of the strengths of each platform, and cover the weaknesses. The design looks as follows: diff --git a/_docs-sources/guides/build-it-yourself/3-pipelines/2-production-grade-design/5-use-minimal-iam-permissions-for-a-deployment.md b/_docs-sources/guides/build-it-yourself/pipelines/production-grade-design/use-minimal-iam-permissions-for-a-deployment.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/3-pipelines/2-production-grade-design/5-use-minimal-iam-permissions-for-a-deployment.md rename to _docs-sources/guides/build-it-yourself/pipelines/production-grade-design/use-minimal-iam-permissions-for-a-deployment.md diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/_category_.json b/_docs-sources/guides/build-it-yourself/vpc/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/_category_.json rename to _docs-sources/guides/build-it-yourself/vpc/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/1-core-concepts/_category_.json b/_docs-sources/guides/build-it-yourself/vpc/core-concepts/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/1-core-concepts/_category_.json rename to _docs-sources/guides/build-it-yourself/vpc/core-concepts/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/2-cidr-notation.md b/_docs-sources/guides/build-it-yourself/vpc/core-concepts/cidr-notation.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/2-cidr-notation.md rename to _docs-sources/guides/build-it-yourself/vpc/core-concepts/cidr-notation.md diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/0-default-vp-cs-and-custom-vp-cs.md b/_docs-sources/guides/build-it-yourself/vpc/core-concepts/default-vp-cs-and-custom-vp-cs.md similarity index 96% rename from _docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/0-default-vp-cs-and-custom-vp-cs.md rename to _docs-sources/guides/build-it-yourself/vpc/core-concepts/default-vp-cs-and-custom-vp-cs.md index 1051e1a58f..09aac8d709 100644 --- a/_docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/0-default-vp-cs-and-custom-vp-cs.md +++ b/_docs-sources/guides/build-it-yourself/vpc/core-concepts/default-vp-cs-and-custom-vp-cs.md @@ -47,7 +47,7 @@ you’re typically better off creating a new, custom VPC. #### Custom VPCs -For any production use cases, you should create a _custom VPC_. In the [Production-grade design](../2-production-grade-design/0-intro.md) section, we’ll go +For any production use cases, you should create a _custom VPC_. In the [Production-grade design](../production-grade-design/intro.md) section, we’ll go over how to configure a VPC with the kind of security, scalability, and high availability you need in production. diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/5-internet-gateways-public-subnets-and-private-subnets.md b/_docs-sources/guides/build-it-yourself/vpc/core-concepts/internet-gateways-public-subnets-and-private-subnets.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/5-internet-gateways-public-subnets-and-private-subnets.md rename to _docs-sources/guides/build-it-yourself/vpc/core-concepts/internet-gateways-public-subnets-and-private-subnets.md diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/6-nat-gateways.md b/_docs-sources/guides/build-it-yourself/vpc/core-concepts/nat-gateways.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/6-nat-gateways.md rename to _docs-sources/guides/build-it-yourself/vpc/core-concepts/nat-gateways.md diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/8-network-ac-ls.md b/_docs-sources/guides/build-it-yourself/vpc/core-concepts/network-ac-ls.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/8-network-ac-ls.md rename to _docs-sources/guides/build-it-yourself/vpc/core-concepts/network-ac-ls.md diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/11-regions-and-availability-zones.md b/_docs-sources/guides/build-it-yourself/vpc/core-concepts/regions-and-availability-zones.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/11-regions-and-availability-zones.md rename to _docs-sources/guides/build-it-yourself/vpc/core-concepts/regions-and-availability-zones.md diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/4-route-tables.md b/_docs-sources/guides/build-it-yourself/vpc/core-concepts/route-tables.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/4-route-tables.md rename to _docs-sources/guides/build-it-yourself/vpc/core-concepts/route-tables.md diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/7-security-groups.md b/_docs-sources/guides/build-it-yourself/vpc/core-concepts/security-groups.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/7-security-groups.md rename to _docs-sources/guides/build-it-yourself/vpc/core-concepts/security-groups.md diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/3-subnets.md b/_docs-sources/guides/build-it-yourself/vpc/core-concepts/subnets.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/3-subnets.md rename to _docs-sources/guides/build-it-yourself/vpc/core-concepts/subnets.md diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/10-vpc-endpoints.md b/_docs-sources/guides/build-it-yourself/vpc/core-concepts/vpc-endpoints.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/10-vpc-endpoints.md rename to _docs-sources/guides/build-it-yourself/vpc/core-concepts/vpc-endpoints.md diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/1-vpc-ip-addresses.md b/_docs-sources/guides/build-it-yourself/vpc/core-concepts/vpc-ip-addresses.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/1-vpc-ip-addresses.md rename to _docs-sources/guides/build-it-yourself/vpc/core-concepts/vpc-ip-addresses.md diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/9-vpc-peering.md b/_docs-sources/guides/build-it-yourself/vpc/core-concepts/vpc-peering.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/1-core-concepts/9-vpc-peering.md rename to _docs-sources/guides/build-it-yourself/vpc/core-concepts/vpc-peering.md diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/_category_.json b/_docs-sources/guides/build-it-yourself/vpc/deployment-walkthrough/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/_category_.json rename to _docs-sources/guides/build-it-yourself/vpc/deployment-walkthrough/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/4-clean-up-default-vp-cs-and-security-groups.md b/_docs-sources/guides/build-it-yourself/vpc/deployment-walkthrough/clean-up-default-vp-cs-and-security-groups.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/4-clean-up-default-vp-cs-and-security-groups.md rename to _docs-sources/guides/build-it-yourself/vpc/deployment-walkthrough/clean-up-default-vp-cs-and-security-groups.md diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/3-deploy-a-bastion-host.md b/_docs-sources/guides/build-it-yourself/vpc/deployment-walkthrough/deploy-a-bastion-host.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/3-deploy-a-bastion-host.md rename to _docs-sources/guides/build-it-yourself/vpc/deployment-walkthrough/deploy-a-bastion-host.md diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/1-deploy-a-management-vpc.md b/_docs-sources/guides/build-it-yourself/vpc/deployment-walkthrough/deploy-a-management-vpc.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/1-deploy-a-management-vpc.md rename to _docs-sources/guides/build-it-yourself/vpc/deployment-walkthrough/deploy-a-management-vpc.md diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/2-deploy-application-vp-cs.md b/_docs-sources/guides/build-it-yourself/vpc/deployment-walkthrough/deploy-application-vp-cs.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/2-deploy-application-vp-cs.md rename to _docs-sources/guides/build-it-yourself/vpc/deployment-walkthrough/deploy-application-vp-cs.md diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/0-pre-requisites.md b/_docs-sources/guides/build-it-yourself/vpc/deployment-walkthrough/pre-requisites.md similarity index 92% rename from _docs-sources/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/0-pre-requisites.md rename to _docs-sources/guides/build-it-yourself/vpc/deployment-walkthrough/pre-requisites.md index 6d352cb3e9..891c0e276e 100644 --- a/_docs-sources/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/0-pre-requisites.md +++ b/_docs-sources/guides/build-it-yourself/vpc/deployment-walkthrough/pre-requisites.md @@ -34,7 +34,7 @@ our [Introduction to Gruntwork](/docs/intro/overview/intro-to-gruntwork) #### AWS accounts This guide deploys infrastructure into one or more AWS accounts. Check out the -[Production Grade AWS Account Structure](../../2-landing-zone/0-intro/0-what-youll-learn-in-this-guide.md) guide for instructions. +[Production Grade AWS Account Structure](../../landing-zone/intro/what-youll-learn-in-this-guide.md) guide for instructions. You will also need to be able to authenticate to these accounts on the CLI: check out [A Comprehensive Guide to Authenticating to AWS on the Command Line](https://blog.gruntwork.io/a-comprehensive-guide-to-authenticating-to-aws-on-the-command-line-63656a686799) for instructions. diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/0-intro/_category_.json b/_docs-sources/guides/build-it-yourself/vpc/intro/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/0-intro/_category_.json rename to _docs-sources/guides/build-it-yourself/vpc/intro/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/0-intro/1-what-is-a-vpc.md b/_docs-sources/guides/build-it-yourself/vpc/intro/what-is-a-vpc.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/0-intro/1-what-is-a-vpc.md rename to _docs-sources/guides/build-it-yourself/vpc/intro/what-is-a-vpc.md diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/0-intro/0-what-youll-learn-in-this-guide.md b/_docs-sources/guides/build-it-yourself/vpc/intro/what-youll-learn-in-this-guide.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/0-intro/0-what-youll-learn-in-this-guide.md rename to _docs-sources/guides/build-it-yourself/vpc/intro/what-youll-learn-in-this-guide.md diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/4-next-steps.md b/_docs-sources/guides/build-it-yourself/vpc/next-steps.md similarity index 91% rename from _docs-sources/guides/build-it-yourself/4-vpc/4-next-steps.md rename to _docs-sources/guides/build-it-yourself/vpc/next-steps.md index 80f50bc88f..7b2469fc8f 100644 --- a/_docs-sources/guides/build-it-yourself/4-vpc/4-next-steps.md +++ b/_docs-sources/guides/build-it-yourself/vpc/next-steps.md @@ -4,7 +4,7 @@ Now that you have your management and application VPCs deployed, you can start b on top of them! Typically, the best next step is to deploy a cluster of servers for running your applications by using one of the following guides: -- [How to deploy a production-grade Kubernetes cluster on AWS](../5-kubernetes-cluster/0-intro/0-what-youll-learn-in-this-guide.md) +- [How to deploy a production-grade Kubernetes cluster on AWS](../kubernetes-cluster/intro/what-youll-learn-in-this-guide.md) - `How to deploy a production grade ECS cluster on AWS` _(coming soon!)_ - `How to deploy a production grade Nomad cluster on AWS` _(coming soon!)_ - `How to deploy a production grade Auto Scaling Group on AWS` _(coming soon!)_ diff --git a/_docs-sources/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/_category_.json b/_docs-sources/guides/build-it-yourself/vpc/production-grade-design/_category_.json similarity index 100% rename from _docs-sources/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/_category_.json rename to _docs-sources/guides/build-it-yourself/vpc/production-grade-design/_category_.json diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/2-production-grade-design/7-bastion-host.md b/_docs-sources/guides/build-it-yourself/vpc/production-grade-design/bastion-host.md similarity index 96% rename from _docs-sources/guides/build-it-yourself/4-vpc/2-production-grade-design/7-bastion-host.md rename to _docs-sources/guides/build-it-yourself/vpc/production-grade-design/bastion-host.md index e8d421ab0b..370db5178f 100644 --- a/_docs-sources/guides/build-it-yourself/4-vpc/2-production-grade-design/7-bastion-host.md +++ b/_docs-sources/guides/build-it-yourself/vpc/production-grade-design/bastion-host.md @@ -13,7 +13,7 @@ the server, lock down all ports (except SSH and/or VPN), rebuild and redeploy th the `How to deploy a production-grade bastion host on AWS` guide _(coming soon!)_ for full details on bastion hosts. Other solutions that can work with resources in private subnets include -[EC2 Instance Connect](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Connect-using-EC2-Instance-Connect.html), +[EC2 Instance Connect](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Connect-using-ECInstance-Connect.html), which can allow you to SSH to EC2 Instances via a browser-based SSH client in the Amazon EC2 Console, and [AWS Systems Manager Sessions](https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager.html), which allow you to manage and connect to EC2 Instances via a custom protocol managed by AWS. diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/2-production-grade-design/1-defense-in-depth.md b/_docs-sources/guides/build-it-yourself/vpc/production-grade-design/defense-in-depth.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/2-production-grade-design/1-defense-in-depth.md rename to _docs-sources/guides/build-it-yourself/vpc/production-grade-design/defense-in-depth.md diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/2-production-grade-design/6-internet-gateways-and-nat-gateways.md b/_docs-sources/guides/build-it-yourself/vpc/production-grade-design/internet-gateways-and-nat-gateways.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/2-production-grade-design/6-internet-gateways-and-nat-gateways.md rename to _docs-sources/guides/build-it-yourself/vpc/production-grade-design/internet-gateways-and-nat-gateways.md diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/2-production-grade-design/0-intro.md b/_docs-sources/guides/build-it-yourself/vpc/production-grade-design/intro.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/2-production-grade-design/0-intro.md rename to _docs-sources/guides/build-it-yourself/vpc/production-grade-design/intro.md diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/2-production-grade-design/2-multiple-aws-accounts.md b/_docs-sources/guides/build-it-yourself/vpc/production-grade-design/multiple-aws-accounts.md similarity index 92% rename from _docs-sources/guides/build-it-yourself/4-vpc/2-production-grade-design/2-multiple-aws-accounts.md rename to _docs-sources/guides/build-it-yourself/vpc/production-grade-design/multiple-aws-accounts.md index 6c3af87050..0857c6ba3a 100644 --- a/_docs-sources/guides/build-it-yourself/4-vpc/2-production-grade-design/2-multiple-aws-accounts.md +++ b/_docs-sources/guides/build-it-yourself/vpc/production-grade-design/multiple-aws-accounts.md @@ -11,5 +11,5 @@ change something in prod rather than pre-prod). Therefore, your best bet is to put pre-production environments and production environments in completely separate AWS accounts. This makes it easy to, for example, grant relatively lax permissions in pre-prod environments, but very -strict permissions in production. Check out the [Production Grade AWS Account Structure](../../2-landing-zone/0-intro/0-what-youll-learn-in-this-guide.md) +strict permissions in production. Check out the [Production Grade AWS Account Structure](../../landing-zone/intro/what-youll-learn-in-this-guide.md) guide for instructions. diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/2-production-grade-design/4-multiple-subnet-tiers.md b/_docs-sources/guides/build-it-yourself/vpc/production-grade-design/multiple-subnet-tiers.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/2-production-grade-design/4-multiple-subnet-tiers.md rename to _docs-sources/guides/build-it-yourself/vpc/production-grade-design/multiple-subnet-tiers.md diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/2-production-grade-design/3-multiple-vp-cs.md b/_docs-sources/guides/build-it-yourself/vpc/production-grade-design/multiple-vp-cs.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/2-production-grade-design/3-multiple-vp-cs.md rename to _docs-sources/guides/build-it-yourself/vpc/production-grade-design/multiple-vp-cs.md diff --git a/_docs-sources/guides/build-it-yourself/4-vpc/2-production-grade-design/5-security-groups-and-nac-ls.md b/_docs-sources/guides/build-it-yourself/vpc/production-grade-design/security-groups-and-nac-ls.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/4-vpc/2-production-grade-design/5-security-groups-and-nac-ls.md rename to _docs-sources/guides/build-it-yourself/vpc/production-grade-design/security-groups-and-nac-ls.md diff --git a/_docs-sources/guides/stay-up-to-date/1-cis/_category_.json b/_docs-sources/guides/stay-up-to-date/cis/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/1-cis/_category_.json rename to _docs-sources/guides/stay-up-to-date/cis/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/_category_.json b/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/_category_.json rename to _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/1-core-concepts.md b/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/core-concepts.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/1-core-concepts.md rename to _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/core-concepts.md diff --git a/_docs-sources/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/_category_.json b/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/_category_.json rename to _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/0-step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md b/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/0-step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md rename to _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md diff --git a/_docs-sources/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/1-step-2-manual-steps.md b/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/step-2-manual-steps.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/1-step-2-manual-steps.md rename to _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/step-2-manual-steps.md diff --git a/_docs-sources/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/2-step-3-deploy-new-modules.md b/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/step-3-deploy-new-modules.md similarity index 92% rename from _docs-sources/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/2-step-3-deploy-new-modules.md rename to _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/step-3-deploy-new-modules.md index 7f9ad48c04..7d104fd70e 100644 --- a/_docs-sources/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/2-step-3-deploy-new-modules.md +++ b/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/step-3-deploy-new-modules.md @@ -11,7 +11,7 @@ accidentally to a resource such as AWS Elastic Load Balancer (ELB), which can da achieve this recommendation, check out the [example](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/tree/v0.10.0/examples/cleanup-expired-certs/terraform) of the ready-made `cleanup-expired-certs` module. For the code examples of deploying this module, see the -[relevant section](../../../../build-it-yourself/6-achieve-compliance/2-production-grade-design/1-identity-and-access-management.md#cleanup-expired-ssl-tls-certificates) +[relevant section](../../../../build-it-yourself/achieve-compliance/production-grade-design/identity-and-access-management.md#cleanup-expired-ssl-tls-certificates) of our "How to achieve compliance with the CIS AWS Foundations Benchmark" guide. ## 2. Deploy IAM Access Analyzer module (recommendation 1.21) @@ -31,7 +31,7 @@ The IAM Access Analyzer will scan only within the AWS Account or Organization bo To help you achieve CIS AWS v1.3 compliance, you can find examples of how to use the ready-made module as part of the `landingzone` module in the `terraform-aws-service-catalog` repository [v0.15.4](https://github.com/gruntwork-io/terraform-aws-service-catalog/releases/tag/v0.15.4), and specifically the `account-baseline-root` and `account-baseline-security` [examples](https://github.com/gruntwork-io/terraform-aws-service-catalog/tree/v0.15.4/examples/for-learning-and-testing/landingzone). For the code examples of deploying this module, see the -[relevant section](../../../../build-it-yourself/6-achieve-compliance/2-production-grade-design/1-identity-and-access-management.md#iam-access-analyzer) +[relevant section](../../../../build-it-yourself/achieve-compliance/production-grade-design/identity-and-access-management.md#iam-access-analyzer) of our "How to achieve compliance with the CIS AWS Foundations Benchmark" guide. ## 3. Deploy the ebs-encryption-multi-region module (recommendation 2.2.1) @@ -42,7 +42,7 @@ a module that configures volume encryption by default in all enabled regions. Ch configure AWS EBS encryption in all allowed regions of an AWS Account. For the code examples of deploying this module, see the -[relevant section](../../../../build-it-yourself/6-achieve-compliance/2-production-grade-design/2-storage.md#configure-ebs-encryption) +[relevant section](../../../../build-it-yourself/achieve-compliance/production-grade-design/storage.md#configure-ebs-encryption) of our "Achieve Compliance With the CIS AWS Foundations Benchmark" guide. ## 4. Deploy the vpc-app-network-acl and vpc-mgmt-network-acl modules (recommendation 5.1) @@ -72,7 +72,7 @@ module "vpc_app_network_acls" { ``` For the code examples of deploying this module, see the -[relevant section](../../../../build-it-yourself/6-achieve-compliance/2-production-grade-design/5-networking.md) +[relevant section](../../../../build-it-yourself/achieve-compliance/production-grade-design/networking.md) of our "How to achieve compliance with the CIS AWS Foundations Benchmark" guide. ### 4.1 Network ACL Rules Quota limit diff --git a/_docs-sources/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/0-intro.md b/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/intro.md similarity index 64% rename from _docs-sources/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/0-intro.md rename to _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/intro.md index 45ce6f924f..3a886ace3d 100644 --- a/_docs-sources/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/0-intro.md +++ b/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/intro.md @@ -7,20 +7,20 @@ pagination_label: Update to CIS AWS Foundations Benchmark 1.3.0 This guide will walk you through how to update from version 1.2.0 to version 1.3.0 of the CIS AWS Foundations Benchmark. If your infrastructure is already compliant with the Benchmark's version 1.2.0, and you are looking to upgrade to v1.3.0, this guide is for you. If you are starting to work on compliance with this benchmark from scratch, check out our -[How to achieve compliance with the CIS AWS Foundations Benchmark](../../../build-it-yourself/6-achieve-compliance/0-intro/0-what-youll-learn-in-this-guide.md) guide instead. +[How to achieve compliance with the CIS AWS Foundations Benchmark](../../../build-it-yourself/achieve-compliance/intro/what-youll-learn-in-this-guide.md) guide instead. This guide consists of two main sections:
-#### [Core Concepts](./1-core-concepts.md) +#### [Core Concepts](./core-concepts.md) An overview of the CIS AWS Foundations Benchmark v1.3.0 and why it is important to update your code for compatibility. -#### [Deployment walkthrough](./2-deployment-walkthrough/0-step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md) +#### [Deployment walkthrough](./deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md) The steps you need to take to update your code to be compliant with CIS AWS v1.3.0. It includes a -[version compatibility table](./2-deployment-walkthrough/0-step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md#compatibility-table) you can use as a reference to know which Gruntwork Repo version +[version compatibility table](./deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md#compatibility-table) you can use as a reference to know which Gruntwork Repo version tag is compatible with CIS AWS v1.3.0, as well as the manuals step you need to perform to achieve said compliance.
diff --git a/_docs-sources/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/_category_.json b/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/_category_.json rename to _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/1-core-concepts.md b/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/core-concepts.md similarity index 89% rename from _docs-sources/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/1-core-concepts.md rename to _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/core-concepts.md index 02e52e8a33..0a87509db0 100644 --- a/_docs-sources/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/1-core-concepts.md +++ b/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/core-concepts.md @@ -32,6 +32,6 @@ created a new module for Amazon Macie, and updated the Landing Zone modules so t include relevant configurations for the Amazon Macie service. The latter will satisfy the recommendation 2.1.4. To ensure compliance with version 1.4.0 of the CIS AWS Foundations Benchmark, you’ll need to follow all the -instructions in the [Deployment walkthrough](./2-deployment-walkthrough/0-step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md) section; precisely, follow Steps 1 and 2 to ensure that +instructions in the [Deployment walkthrough](./deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md) section; precisely, follow Steps 1 and 2 to ensure that the existing modules get updated to their CIS AWS v1.4.0 compliant versions and follow Step 3 to perform the necessary manual steps. diff --git a/_docs-sources/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/_category_.json b/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/_category_.json rename to _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/0-step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md b/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/0-step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md rename to _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md diff --git a/_docs-sources/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/1-step-2-update-the-account-baseline-modules.md b/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/step-2-update-the-account-baseline-modules.md similarity index 87% rename from _docs-sources/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/1-step-2-update-the-account-baseline-modules.md rename to _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/step-2-update-the-account-baseline-modules.md index 8148564681..3a177e1d8b 100644 --- a/_docs-sources/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/1-step-2-update-the-account-baseline-modules.md +++ b/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/step-2-update-the-account-baseline-modules.md @@ -16,16 +16,16 @@ The account baseline modules had three breaking changes between versions v0.22.0 these migration steps before updating the module versions. - [v0.23.0](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/releases/tag/v0.23.0): Refactored the - SecurityHub module to remove a Python script that managed invitations between the AWS accounts. It’s necessary to run a - state migration to manage the invitations with Terraform. + SecurityHub module to remove a Python script that managed invitations between the AWS accounts. It’s necessary to run a + state migration to manage the invitations with Terraform. - [v0.24.0](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/releases/tag/v0.24.0): This release introduces MFA Delete. You will need to follow the migration guide to ensure all S3 buckets are properly secured. Note: It is unlikely you will need to perform this step on the AWS root account as they typically don’t contain S3 buckets. Please ensure you migrate all other AWS accounts. - [v0.25.0](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/releases/tag/v0.25.0): Update the codebase - to a new multi-region approach. In [v0.51.0](https://github.com/gruntwork-io/terraform-aws-security/releases/tag/v0.51.0) of - `terraform-aws-security`, we refactored how we build multi-region modules—that - is, those modules that deploy resources across every single AWS region, such as `aws-config-multi-region`—to no longer - create nested provider blocks, and instead, have users pass in providers via the providers map. + to a new multi-region approach. In [v0.51.0](https://github.com/gruntwork-io/terraform-aws-security/releases/tag/v0.51.0) of + `terraform-aws-security`, we refactored how we build multi-region modules—that + is, those modules that deploy resources across every single AWS region, such as `aws-config-multi-region`—to no longer + create nested provider blocks, and instead, have users pass in providers via the providers map. Additionally, earlier versions of the account baseline modules did not set the following variables, so please ensure that they exist. Here is [an example](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/blob/v0.27.0/examples/for-production/infrastructure-live/logs/_global/account-baseline/terragrunt.hcl#L281) of what you might set the values to for the prod account. @@ -47,7 +47,7 @@ git::git@github.com:gruntwork-io/terraform-aws-cis-service-catalog.git//modules/ ``` Now execute Terraform/Terragrunt `apply`. It should take approximately ~30 minutes to apply the account baseline -modules. If you encounter any issues then please check out the [Known Issues](./2-step-3-manual-steps.md#known-issues) section. +modules. If you encounter any issues then please check out the [Known Issues](./step-3-manual-steps.md#known-issues) section. :::info @@ -64,7 +64,7 @@ in our CIS service catalog. :::info Manual steps required! After updating the account baseline modules as described below, make sure you perform the manual steps -outlined in the [Configure Amazon Macie (recommendation 2.1.4)](./2-step-3-manual-steps.md#configure-amazon-macie-recommendation-214) section. +outlined in the [Configure Amazon Macie (recommendation 2.1.4)](./step-3-manual-steps.md#configure-amazon-macie-recommendation-214) section. ::: diff --git a/_docs-sources/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/2-step-3-manual-steps.md b/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/step-3-manual-steps.md similarity index 94% rename from _docs-sources/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/2-step-3-manual-steps.md rename to _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/step-3-manual-steps.md index 8290300f7a..0dea56df98 100644 --- a/_docs-sources/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/2-step-3-manual-steps.md +++ b/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/step-3-manual-steps.md @@ -24,12 +24,12 @@ In order to enable MFA Delete, you need to: - [Configure MFA for the root user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html#id_root-user_manage_mfa) - Create a bucket with `mfa_delete=false`. - Using the root user, call the AWS CLI to enable MFA Delete. If you are using `aws-vault`, it is necessary to use the `--no-session` flag. - ```bash - aws s3api put-bucket-versioning --region \ - --bucket \ - --versioning-configuration Status=Enabled,MFADelete=Enabled \ - --mfa "arn:aws:iam:::mfa/root-account-mfa-device " - ``` + ```bash + aws s3api put-bucket-versioning --region \ + --bucket \ + --versioning-configuration Status=Enabled,MFADelete=Enabled \ + --mfa "arn:aws:iam:::mfa/root-account-mfa-device " + ``` - Set `mfa_delete=true` in your Terraform code - Remove any Lifecycle Rule that the bucket might contain (for the `aws-config-bucket` and `cloudtrail-bucket` modules, enabling `mfa_delete` will already disable the lifecycle rules). - Run `terraform apply`. @@ -39,7 +39,7 @@ We also created a script to help you enable MFA Delete in all buckets from a sin ### Using mfa-delete.sh -If you want to enable MFA Delete to _all_ your buckets at once, you can use the script at [terraform-aws-security/private-s3-bucket/mfa-delete-script](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/private-s3-bucket). You need to use the access keys for the root user and the root MFA code. +If you want to enable MFA Delete to _all_ your buckets at once, you can use the script at [terraform-aws-security/private-s3-bucket/mfa-delete-script](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/private-sbucket). You need to use the access keys for the root user and the root MFA code. Usage: @@ -88,7 +88,7 @@ so that it completely automates all the steps of configuring Amazon Macie, and n To set up Macie to analyze the desired S3 buckets, you’ll need to create a **Macie classification job**. Typically, you’ll want it to analyze all the buckets in the region. However, the terraform AWS provider does not support specifying all the buckets in a region - it requires that an explicit list of buckets be provided (see related bug [here](https://github.com/hashicorp/terraform-provider-aws/issues/20044)). Therefore, you’ll need to maintain an explicit list of buckets per region, namely in the variable `buckets_to_analyze`. Please read the -[documentation](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/blob/master/modules/security/macie/variables.tf#L21-L30) +[documentation](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/blob/master/modules/security/macie/variables.tf#L2L30) for this variable in order to understand how to structure the list of buckets per region. Once the above issue in the terraform AWS provider has been resolved, we will [update the Gruntwork macie module](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/issues/204) diff --git a/_docs-sources/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/3-finally.md b/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/finally.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/3-finally.md rename to _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/finally.md diff --git a/_docs-sources/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/0-intro.md b/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/intro.md similarity index 53% rename from _docs-sources/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/0-intro.md rename to _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/intro.md index 2484ca6a09..3eff6d3db5 100644 --- a/_docs-sources/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/0-intro.md +++ b/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/intro.md @@ -8,14 +8,14 @@ This guide consists of two main sections:
-#### [Core Concepts](./1-core-concepts.md) +#### [Core Concepts](./core-concepts.md) An overview of the CIS AWS Foundations Benchmark v1.4.0 and why it is important to update your code for compatibility. -#### [Deployment walkthrough](./2-deployment-walkthrough/0-step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md) +#### [Deployment walkthrough](./deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md) The steps you need to take to update your code to be compliant with v1.4.0. It includes a -[version compatibility table](./2-deployment-walkthrough/0-step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md#compatibility-table) you can use as a reference to know which Gruntwork Repo version +[version compatibility table](./deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md#compatibility-table) you can use as a reference to know which Gruntwork Repo version tag is compatible along with the deployment steps you need to perform to achieve compliance with version 1.4.0 of the CIS AWS Foundations Benchmark. @@ -23,4 +23,4 @@ CIS AWS Foundations Benchmark. ## Previous versions of this guide -- [How to update to CIS AWS Foundations Benchmark v1.3.0](../1-how-to-update-to-cis-13/0-intro.md) +- [How to update to CIS AWS Foundations Benchmark v1.3.0](../how-to-update-to-cis-13/intro.md) diff --git a/_docs-sources/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/_category_.json rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/1-core-concepts.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/core-concepts.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/1-core-concepts.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/core-concepts.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/2-deployment-walkthrough/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/2-deployment-walkthrough/_category_.json rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/0-intro.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/intro.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/0-intro.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/intro.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/3-optional-even-dryer-configuration.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/optional-even-dryer-configuration.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/3-optional-even-dryer-configuration.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/optional-even-dryer-configuration.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/2-refactoring-common-configurations-for-a-component.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/refactoring-common-configurations-for-a-component.md similarity index 96% rename from _docs-sources/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/2-refactoring-common-configurations-for-a-component.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/refactoring-common-configurations-for-a-component.md index 6ec445cf46..69f8e69935 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/2-refactoring-common-configurations-for-a-component.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/refactoring-common-configurations-for-a-component.md @@ -4,13 +4,13 @@ The rest of this guide will cover how to identify and extract the common configu in your Reference Architecture. These steps can be used to refactor any component that is deployed in multiple accounts or environments in your Reference Architecture. -- [Step 1: Identify the component](#step-1-identify-the-component) +- [Step 1: Identify the component](#step-identify-the-component) -- [Step 2: Identify common configurations](#step-2-identify-common-configurations) +- [Step 2: Identify common configurations](#step-identify-common-configurations) -- [Step 3: Extract common configurations](#step-3-extract-common-configurations) +- [Step 3: Extract common configurations](#step-extract-common-configurations) -- [Step 4: Update child configurations](#step-4-update-child-configurations) +- [Step 4: Update child configurations](#step-1-update-child-configurations) ## Step 1: Identify the component @@ -53,7 +53,7 @@ Example inventory: - `security/us-west-2/mgmt/ecs-deploy-runner` -As mentioned in the [Background](../1-core-concepts.md#background), the changes will be isolated to Terragrunt configuration files (syntactic changes vs +As mentioned in the [Background](../core-concepts.md#background), the changes will be isolated to Terragrunt configuration files (syntactic changes vs semantic changes) and there will be no need to roll out the changes using `terraform`. Given that, the order in which the components are updated does not matter. You can update the components in whatever order you would like. diff --git a/_docs-sources/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/1-update-to-the-service-catalog-based-reference-architecture.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/update-to-the-service-catalog-based-reference-architecture.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/1-update-to-the-service-catalog-based-reference-architecture.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/update-to-the-service-catalog-based-reference-architecture.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/0-intro.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/intro.md similarity index 90% rename from _docs-sources/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/0-intro.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/intro.md index 417c87df15..09d1ab12b6 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/0-intro.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/intro.md @@ -18,10 +18,10 @@ configuration across your project. This guide consists of two main sections: -#### [Core Concepts](1-core-concepts.md) +#### [Core Concepts](core-concepts.md) An overview of the multi-include feature and how it helps to DRY up the Gruntwork Reference Architecture. -#### [Deployment Walkthrough](2-deployment-walkthrough/0-intro.md) +#### [Deployment Walkthrough](deployment-walkthrough/intro.md) The steps you need to take to update your code to use multi-include to avoid duplicating common configuration. diff --git a/_docs-sources/guides/stay-up-to-date/terraform/5-how-to-update-to-aws-provider-v3/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/5-how-to-update-to-aws-provider-v3/_category_.json rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/terraform/5-how-to-update-to-aws-provider-v3/1-core-concepts.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/core-concepts.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/5-how-to-update-to-aws-provider-v3/1-core-concepts.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/core-concepts.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/5-how-to-update-to-aws-provider-v3/2-deployment-walkthrough.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/deployment-walkthrough.md similarity index 98% rename from _docs-sources/guides/stay-up-to-date/terraform/5-how-to-update-to-aws-provider-v3/2-deployment-walkthrough.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/deployment-walkthrough.md index 5df6306702..8ca342e672 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/5-how-to-update-to-aws-provider-v3/2-deployment-walkthrough.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/deployment-walkthrough.md @@ -164,17 +164,17 @@ to update your snapshot of the Gruntwork Reference Architecture: #### CIS Reference Architecture Refer to the release notes for -[v0.0.1-20201021](https://github.com/gruntwork-io/cis-infrastructure-live-acme/releases/tag/v0.0.1-20201021) +[v0.0.1-20201021](https://github.com/gruntwork-io/cis-infrastructure-live-acme/releases/tag/v0.0.20201021) of the `cis-infrastructure-live-acme` repository for instructions on how to update the CIS components of the Reference Architecture to be compatible with AWS provider v3. For all other components, refer to the release notes for -[v0.0.1-20201021](https://github.com/gruntwork-io/infrastructure-modules-multi-account-acme/releases/tag/v0.0.1-20201021) +[v0.0.1-20201021](https://github.com/gruntwork-io/infrastructure-modules-multi-account-acme/releases/tag/v0.0.20201021) of the `infrastructure-modules-multi-account-acme` repository. #### Standard Reference Architecture Refer to the release notes for -[v0.0.1-20201021](https://github.com/gruntwork-io/infrastructure-modules-multi-account-acme/releases/tag/v0.0.1-20201021) +[v0.0.1-20201021](https://github.com/gruntwork-io/infrastructure-modules-multi-account-acme/releases/tag/v0.0.20201021) of the `infrastructure-modules-multi-account-acme` repository for instructions on how to update your components to be compatible with AWS provider v3. diff --git a/_docs-sources/guides/stay-up-to-date/terraform/5-how-to-update-to-aws-provider-v3/0-intro.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/intro.md similarity index 83% rename from _docs-sources/guides/stay-up-to-date/terraform/5-how-to-update-to-aws-provider-v3/0-intro.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/intro.md index ac38ee12fe..4ecb9fea16 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/5-how-to-update-to-aws-provider-v3/0-intro.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/intro.md @@ -16,17 +16,17 @@ This guide consists of three main sections:
-#### [Core Concepts](1-core-concepts.md) +#### [Core Concepts](core-concepts.md) An overview of version 3 of the AWS provider and why it is important to update your code for compatibility. -#### [Deployment walkthrough](2-deployment-walkthrough.md) +#### [Deployment walkthrough](deployment-walkthrough.md) The steps you need to take to update your code relying on the Gruntwork Infrastructure as Code library and your version of the Gruntwork Reference Architecture with compatibility with AWS provider v3. Includes a [version -compatibility table](2-deployment-walkthrough.md#version-compatibility-table) you can use as a reference to know +compatibility table](deployment-walkthrough.md#version-compatibility-table) you can use as a reference to know which Gruntwork Repo version tag is compatible with AWS provider v3.
diff --git a/_docs-sources/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/_category_.json rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/1-core-concepts.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/core-concepts.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/1-core-concepts.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/core-concepts.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/2-deployment-walkthrough/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/deployment-walkthrough/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/2-deployment-walkthrough/_category_.json rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/deployment-walkthrough/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-15.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-15.md similarity index 68% rename from _docs-sources/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-15.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-15.md index 8a87ce1c3d..5b8fd4ccfe 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-15.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-15.md @@ -10,16 +10,16 @@ If you haven’t already, you need to: 0.15.0 or above first! 1. If you’re still on Terraform 0.11 or older, see our - [Terraform 0.12 upgrade guide](../../0-how-to-update-to-terraform-12/0-intro.md). + [Terraform 0.12 upgrade guide](../../how-to-update-to-terraform-12/intro.md). 2. If you’re still on Terraform 0.12, see our - [Terraform 0.13 upgrade guide](../../1-how-to-update-to-terraform-13/0-intro.md). + [Terraform 0.13 upgrade guide](../../how-to-update-to-terraform-13/intro.md). 3. If you’re still on Terraform 0.13, see our - [Terraform 0.14 upgrade guide](../../2-how-to-update-to-terraform-14/0-intro.md). + [Terraform 0.14 upgrade guide](../../how-to-update-to-terraform-14/intro.md). 4. If you’re still on Terraform 0.14, see our - [Terraform 0.15 upgrade guide](../../3-how-to-update-to-terraform-15/0-intro.md). + [Terraform 0.15 upgrade guide](../../how-to-update-to-terraform-15/intro.md). 2. Update all your Gruntwork modules to the latest versions just _before_ the TF 1.x versions in the compatibility table below. The upgrade will be much easier and less error prone if you keep the number of version jumps as small diff --git a/_docs-sources/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/2-deployment-walkthrough/1-step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/deployment-walkthrough/step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/2-deployment-walkthrough/1-step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/deployment-walkthrough/step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/0-intro.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/intro.md similarity index 69% rename from _docs-sources/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/0-intro.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/intro.md index a4dfe653ce..53cbc942a5 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/0-intro.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/intro.md @@ -18,15 +18,15 @@ This guide consists of two main sections:
-#### [Core Concepts](1-core-concepts.md) +#### [Core Concepts](core-concepts.md) An overview of Terraform 1.x. -#### [Deployment walkthrough](2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-15.md) +#### [Deployment walkthrough](deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-15.md) The steps you need to take to update your code relying on the Gruntwork Infrastructure as Code library to work with Terraform 1.x. Includes a -[version compatibility table](2-deployment-walkthrough/1-step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md#version-compatibility-table) you can use as a reference to know which Gruntwork Repo version +[version compatibility table](deployment-walkthrough/step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md#version-compatibility-table) you can use as a reference to know which Gruntwork Repo version tag is compatible with Terraform 0.15.
diff --git a/_docs-sources/guides/stay-up-to-date/terraform/0-how-to-update-to-terraform-12/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/0-how-to-update-to-terraform-12/_category_.json rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/terraform/0-how-to-update-to-terraform-12/1-deployment-walkthrough.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/deployment-walkthrough.md similarity index 99% rename from _docs-sources/guides/stay-up-to-date/terraform/0-how-to-update-to-terraform-12/1-deployment-walkthrough.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/deployment-walkthrough.md index 6253d90aa0..bf12ffe986 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/0-how-to-update-to-terraform-12/1-deployment-walkthrough.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/deployment-walkthrough.md @@ -16,14 +16,14 @@ that prevent using your TF11 and older modules directly with TF12. For the safes going through the process of updating all your modules to use the new HCL2 syntax using the `terraform 0.12upgrade` tool that ships with TF12. -Before starting, read through the [Terraform 0.12 upgrade guide](https://www.terraform.io/upgrade-guides/0-12.html) so +Before starting, read through the [Terraform 0.12 upgrade guide](https://www.terraform.io/upgrade-guides/12.html) so you can learn about the types of changes you’ll have to make. Familiarity of the changes help with detecting errors and gotchas that the upgrade tool occasionally misses. Here is the rough process: -1. [Install and setup Terraform 0.12](#install-and-setup-terraform-0-12) -1. [Upgrade each module for 0.12 compatibility](#upgrade-each-module-for-0-12-compatibility) +1. [Install and setup Terraform 0.12](#install-and-setup-terraform-12) +1. [Upgrade each module for 0.12 compatibility](#upgrade-each-module-for-1compatibility) ### Install and setup Terraform 0.12 @@ -124,7 +124,7 @@ it is very easy to "start over", such as a sandbox or dev environment!** 1. Go into the folder with the Terraform module: `cd infrastructure-modules/networking/vpc-app` 1. Search your code for any references to Gruntwork modules. Update each module to the version number specified in the right-most column of the [Gruntwork module compatibility - table](1-version-compatibility-table.md) (or newer). For example, + table](version-compatibility-table.md) (or newer). For example, our example `infrastructure-modules/networking/vpc-app` [makes use of module-vpc](https://github.com/gruntwork-io/infrastructure-modules-multi-account-acme/blob/3158e4ebe83156f3917f8d168a6985678e30acfa/networking/vpc-app/main.tf#L38), which you’ll want to upgrade to `v0.6.0` (or newer). @@ -176,7 +176,7 @@ terragrunt `terraform.tfvars` files to the new syntax. Here is the rough process: -1. [Install and setup Terragrunt 0.19](#install-and-setup-terragrunt-0-19) +1. [Install and setup Terragrunt 0.19](#install-and-setup-terragrunt-19) 1. [Migrate terraform.tfvars to terragrunt.hcl](#migrate-terraform-tfvars-to-terragrunt-hcl) 1. [Switch common tfvars files to use yaml](#switch-common-tfvars-files-to-use-yaml) @@ -224,7 +224,7 @@ environment to test the changes you are making to that module (e.g [`infrastructure-live/dev/us-east-1/dev/vpc`](https://github.com/gruntwork-io/infrastructure-live-multi-account-acme/tree/dd6dce7f737f8c1bd32466b69e905b2bdd25db80/dev/us-east-1/dev/vpc)). The rough process should be: -1. Upgrade the module to TF12 syntax following the steps [listed above](#upgrade-each-module-for-0-12-compatibility). +1. Upgrade the module to TF12 syntax following the steps [listed above](#upgrade-each-module-for-1compatibility). 1. Update the live config for a pre-prod environment that deploys the module. 1. Run `terragrunt plan` to verify the changes. Use `--terragrunt-source` so you can point to the updated module (see the docs on [working locally](https://github.com/gruntwork-io/terragrunt#working-locally)). Carefully review to make diff --git a/_docs-sources/guides/stay-up-to-date/terraform/0-how-to-update-to-terraform-12/0-intro.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/intro.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/0-how-to-update-to-terraform-12/0-intro.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/intro.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/0-how-to-update-to-terraform-12/1-version-compatibility-table.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/version-compatibility-table.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/0-how-to-update-to-terraform-12/1-version-compatibility-table.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/version-compatibility-table.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/_category_.json rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/1-core-concepts.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/core-concepts.md similarity index 88% rename from _docs-sources/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/1-core-concepts.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/core-concepts.md index 972dd8badd..3538035a17 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/1-core-concepts.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/core-concepts.md @@ -3,7 +3,7 @@ # Core Concepts -[Terraform 0.13 was released on August 10th, 2020](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-0-13). +[Terraform 0.13 was released on August 10th, 2020](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-13). Some of the major new features in 0.13 include: 1. The ability to use `count`, `for_each`, and `depends_on` with modules. @@ -12,7 +12,7 @@ Some of the major new features in 0.13 include: 3. Custom variable validation. -For more info, check out the [announcement blog post](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-0-13). +For more info, check out the [announcement blog post](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-13). 0.13 is a major new release for Terraform, which means it includes a number of backwards incompatible changes. We have gone through all the Terraform modules in the [Gruntwork diff --git a/_docs-sources/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/2-deployment-walkthrough/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/2-deployment-walkthrough/_category_.json rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-12.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12.md similarity index 86% rename from _docs-sources/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-12.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12.md index 70db1e0c0b..5e06d311fa 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-12.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12.md @@ -9,7 +9,7 @@ If you haven’t already, you need to: 1. Update your code to work with Terraform 0.12. Do NOT skip from, say, 0.11, straight to 0.13. You MUST update to 0.12.26 or above first! If you’re still on Terraform 0.11 or older, see our - [Terraform 0.12 upgrade guide](../../0-how-to-update-to-terraform-12/0-intro.md) for instructions. + [Terraform 0.12 upgrade guide](../../how-to-update-to-terraform-12/intro.md) for instructions. 2. Update all your Gruntwork modules to the latest versions just _before_ the TF 0.13 versions in the compatibility table below. The upgrade will be much easier and less error prone if you keep the number of version jumps as small diff --git a/_docs-sources/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/2-deployment-walkthrough/1-step-2-update-your-code-to-be-compatible-with-terraform-0-13.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-13.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/2-deployment-walkthrough/1-step-2-update-your-code-to-be-compatible-with-terraform-0-13.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-13.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/2-deployment-walkthrough/2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/2-deployment-walkthrough/2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/2-deployment-walkthrough/3-updating-the-gruntwork-reference-architecture-to-terraform-0-13.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/updating-the-gruntwork-reference-architecture-to-terraform-0-13.md similarity index 94% rename from _docs-sources/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/2-deployment-walkthrough/3-updating-the-gruntwork-reference-architecture-to-terraform-0-13.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/updating-the-gruntwork-reference-architecture-to-terraform-0-13.md index 974f5232ee..14cf19e42e 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/2-deployment-walkthrough/3-updating-the-gruntwork-reference-architecture-to-terraform-0-13.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/updating-the-gruntwork-reference-architecture-to-terraform-0-13.md @@ -10,7 +10,7 @@ the infrastructure code for deploying the Reference Architecture. You will need to update the relevant code in `infrastructure-modules` to use a compatible version of the Gruntwork Infrastructure as Code Library, as per [the compatibility -table](2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md#version-compatibility-table) +table](step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md#version-compatibility-table) above. To help guide you through the upgrade process, we have updated the Acme diff --git a/_docs-sources/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/0-intro.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/intro.md similarity index 63% rename from _docs-sources/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/0-intro.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/intro.md index 8992b54878..795d2b95b3 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/0-intro.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/intro.md @@ -7,7 +7,7 @@ pagination_label: Update to Terraform 13 This guide will walk you through how to update the [Gruntwork Reference Architecture](https://gruntwork.io/reference-architecture/) and any code that depends on the [Gruntwork Infrastructure as Code Library](https://gruntwork.io/infrastructure-as-code-library/) to -[Terraform 0.13](https://www.terraform.io/upgrade-guides/0-13.html). Terraform 0.13 introduces a number of new features +[Terraform 0.13](https://www.terraform.io/upgrade-guides/13.html). Terraform 0.13 introduces a number of new features and fixes, but it also has a number of backwards incompatibilities that have to be incorporated into your codebase. ## What you’ll learn in this guide @@ -16,15 +16,15 @@ This guide consists of two main sections:
-#### [Core Concepts](1-core-concepts.md) +#### [Core Concepts](core-concepts.md) An overview of Terraform 0.13 and why it is important to update your code for compatibility. -#### [Deployment walkthrough](2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-12.md) +#### [Deployment walkthrough](deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12.md) The steps you need to take to update your code relying on the Gruntwork Infrastructure as Code library and your version of the Gruntwork Reference Architecture to work with Terraform 0.13. Includes a -[version compatibility table](2-deployment-walkthrough/2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md#version-compatibility-table) you can use as a reference to know which Gruntwork Repo version +[version compatibility table](deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md#version-compatibility-table) you can use as a reference to know which Gruntwork Repo version tag is compatible with Terraform 0.13.
diff --git a/_docs-sources/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/_category_.json rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/1-core-concepts.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/core-concepts.md similarity index 94% rename from _docs-sources/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/1-core-concepts.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/core-concepts.md index c0b97637ba..766fbd9aee 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/1-core-concepts.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/core-concepts.md @@ -13,7 +13,7 @@ December 02, 2020](https://www.hashicorp.com/blog/announcing-hashicorp-terraform 3. A lock file for provider dependency versions. For more info, check out the -[announcement blog post](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-0-14-general-availability). +[announcement blog post](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-1general-availability). 0.14 is a major new release for Terraform, which means it includes some backwards incompatible changes. We have gone through all the Terraform modules in the [Gruntwork diff --git a/_docs-sources/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/2-deployment-walkthrough/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/2-deployment-walkthrough/_category_.json rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-13.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-13.md similarity index 85% rename from _docs-sources/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-13.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-13.md index e376be6f7e..7c20745988 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-13.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-13.md @@ -9,10 +9,10 @@ If you haven’t already, you need to: 1. Update your code to work with Terraform 0.13. Do NOT skip from, say, 0.11, straight to 0.14. You MUST update to 0.13.0 or above first! If you’re still on Terraform 0.11 or older, see our [Terraform 0.12 upgrade - guide](../../0-how-to-update-to-terraform-12/0-intro.md) for + guide](../../how-to-update-to-terraform-12/intro.md) for instructions. If you’re still on Terraform 0.12, see our [Terraform 0.13 upgrade - guide](../../1-how-to-update-to-terraform-13/0-intro.md). + guide](../../how-to-update-to-terraform-13/intro.md). 2. Update all your Gruntwork modules to the latest versions just _before_ the TF 0.14 versions in the compatibility table below. The upgrade will be much diff --git a/_docs-sources/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/2-deployment-walkthrough/1-step-2-update-your-code-to-be-compatible-with-terraform-0-14.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-14.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/2-deployment-walkthrough/1-step-2-update-your-code-to-be-compatible-with-terraform-0-14.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-14.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/2-deployment-walkthrough/2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/2-deployment-walkthrough/2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/2-deployment-walkthrough/3-step-4-start-using-lock-files.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-4-start-using-lock-files.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/2-deployment-walkthrough/3-step-4-start-using-lock-files.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-4-start-using-lock-files.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/0-intro.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/intro.md similarity index 68% rename from _docs-sources/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/0-intro.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/intro.md index 2435b5dc16..6d27917e4d 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/0-intro.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/intro.md @@ -17,15 +17,15 @@ This guide consists of two main sections:
-#### [Core Concepts](1-core-concepts.md) +#### [Core Concepts](core-concepts.md) An overview of Terraform 0.14 and why it is important to update your code for compatibility. -#### [Deployment walkthrough](2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-13.md) +#### [Deployment walkthrough](deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-13.md) The steps you need to take to update your code relying on the Gruntwork Infrastructure as Code library to work with Terraform 0.14. Includes a -[version compatibility table](2-deployment-walkthrough/2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md#version-compatibility-table) you can use as a reference to know which Gruntwork Repo version +[version compatibility table](deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md#version-compatibility-table) you can use as a reference to know which Gruntwork Repo version tag is compatible with Terraform 0.14.
diff --git a/_docs-sources/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/_category_.json rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/1-core-concepts.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/core-concepts.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/1-core-concepts.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/core-concepts.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/_category_.json rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-14.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-14.md similarity index 72% rename from _docs-sources/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-14.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-14.md index 59616934dc..7d7a2caa4c 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-14.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-14.md @@ -10,13 +10,13 @@ If you haven’t already, you need to: 0.14.0 or above first! 1. If you’re still on Terraform 0.11 or older, see our - [Terraform 0.12 upgrade guide](../../0-how-to-update-to-terraform-12/0-intro.md). + [Terraform 0.12 upgrade guide](../../how-to-update-to-terraform-12/intro.md). 2. If you’re still on Terraform 0.12, see our - [Terraform 0.13 upgrade guide](../../1-how-to-update-to-terraform-13/0-intro.md). + [Terraform 0.13 upgrade guide](../../how-to-update-to-terraform-13/intro.md). 3. If you’re still on Terraform 0.13, see our - [Terraform 0.14 upgrade guide](../../2-how-to-update-to-terraform-14/0-intro.md). + [Terraform 0.14 upgrade guide](../../how-to-update-to-terraform-14/intro.md). 2. Update all your Gruntwork modules to the latest versions just _before_ the TF 0.15 versions in the compatibility table below. The upgrade will be much easier and less error prone if you keep the number of version jumps as small diff --git a/_docs-sources/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/2-deployment-walkthrough/1-step-2-update-your-code-to-be-compatible-with-terraform-0-15.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-15.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/2-deployment-walkthrough/1-step-2-update-your-code-to-be-compatible-with-terraform-0-15.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-15.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/2-deployment-walkthrough/2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/2-deployment-walkthrough/2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/0-intro.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/intro.md similarity index 75% rename from _docs-sources/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/0-intro.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/intro.md index c92d92d13a..4cdab8d428 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/0-intro.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/intro.md @@ -17,16 +17,16 @@ This guide consists of two main sections:
-#### [Core Concepts](1-core-concepts.md) +#### [Core Concepts](core-concepts.md) An overview of Terraform 0.15 and why it is important to update your code for compatibility. -#### [Deployment walkthrough](2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-14.md) +#### [Deployment walkthrough](deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-14.md) The steps you need to take to update your code relying on the Gruntwork Infrastructure as Code library to work with Terraform 0.15. Includes a [version compatibility -table](2-deployment-walkthrough/2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md#version-compatibility-table) +table](deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md#version-compatibility-table) you can use as a reference to know which Gruntwork Repo version tag is compatible with Terraform 0.15. diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/0-intro/_category_.json b/docs/guides/build-it-yourself/6-achieve-compliance/0-intro/_category_.json deleted file mode 100644 index 824e59ad25..0000000000 --- a/docs/guides/build-it-yourself/6-achieve-compliance/0-intro/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ -"label": "Intro" -} \ No newline at end of file diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/1-core-concepts/_category_.json b/docs/guides/build-it-yourself/6-achieve-compliance/1-core-concepts/_category_.json deleted file mode 100644 index cd85871b6b..0000000000 --- a/docs/guides/build-it-yourself/6-achieve-compliance/1-core-concepts/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ -"label": "Core concepts" -} \ No newline at end of file diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/_category_.json b/docs/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/_category_.json deleted file mode 100644 index 8c8bc9a850..0000000000 --- a/docs/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ -"label": "Production-grade design" -} \ No newline at end of file diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/2-prepare-your-infrastructure-live-repository.md b/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/2-prepare-your-infrastructure-live-repository.md deleted file mode 100644 index dbc36fad3e..0000000000 --- a/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/2-prepare-your-infrastructure-live-repository.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -sidebar_label: Prepare your infrastructure-live repository ---- - -# Prepare your `infrastructure-live` repository - -We’ve previously described exactly how to prepare your repository in the -[Gruntwork Landing Zone guide](../../2-landing-zone/3-deployment-walkthrough/1-prepare-your-infrastructure-live-repository.md). Follow the steps in that section to get your `infrastructure-live` repository set up for the next steps. - - - diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/_category_.json b/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/_category_.json deleted file mode 100644 index 153ca2acf1..0000000000 --- a/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "label": "Deploy Landing Zone Solution" -} diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/_category_.json b/docs/guides/build-it-yourself/6-achieve-compliance/_category_.json deleted file mode 100644 index 67fc37efed..0000000000 --- a/docs/guides/build-it-yourself/6-achieve-compliance/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "label": "Achieve Compliance With the CIS AWS Foundations Benchmark" -} diff --git a/docs/guides/build-it-yourself/5-achieve-compliance/_category_.json b/docs/guides/build-it-yourself/achieve-compliance/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/5-achieve-compliance/_category_.json rename to docs/guides/build-it-yourself/achieve-compliance/_category_.json diff --git a/docs/guides/build-it-yourself/2-landing-zone/1-core-concepts/_category_.json b/docs/guides/build-it-yourself/achieve-compliance/core-concepts/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/1-core-concepts/_category_.json rename to docs/guides/build-it-yourself/achieve-compliance/core-concepts/_category_.json diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/1-core-concepts/0-intro.md b/docs/guides/build-it-yourself/achieve-compliance/core-concepts/intro.md similarity index 100% rename from docs/guides/build-it-yourself/6-achieve-compliance/1-core-concepts/0-intro.md rename to docs/guides/build-it-yourself/achieve-compliance/core-concepts/intro.md diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/1-core-concepts/1-recommendation-sections.md b/docs/guides/build-it-yourself/achieve-compliance/core-concepts/recommendation-sections.md similarity index 100% rename from docs/guides/build-it-yourself/6-achieve-compliance/1-core-concepts/1-recommendation-sections.md rename to docs/guides/build-it-yourself/achieve-compliance/core-concepts/recommendation-sections.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/_category_.json b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/_category_.json rename to docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/_category_.json diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/5-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 similarity index 100% rename from docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/5-create-an-iam-user-in-the-root-account.md rename to docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-an-iam-user-in-the-root-account.md diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/3-create-the-root-account.md b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-the-root-account.md similarity index 100% rename from docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/3-create-the-root-account.md rename to docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-the-root-account.md diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/9-create-vpc-flow-logs.md b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-vpc-flow-logs.md similarity index 100% rename from docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/9-create-vpc-flow-logs.md rename to docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-vpc-flow-logs.md diff --git a/docs/guides/build-it-yourself/5-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/_category_.json b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/5-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/_category_.json rename to docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/_category_.json diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/1-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 similarity index 100% rename from docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/1-apply-account-baseline-app-to-logs-account.md rename to docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-app-to-logs-account.md diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/3-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 similarity index 98% rename from docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/3-apply-account-baseline-app-to-other-child-accounts.md rename to docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-app-to-other-child-accounts.md index e8b2e3e830..856e0c737b 100644 --- a/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/3-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 @@ -275,7 +275,7 @@ On some operating systems, such as MacOS, you may also need to increase your ope 1. Use your IAM user’s user name and password (decrypted using keybase) to log into the web console of the security account (remember to use the IAM user sign-in URL for the security account). -2. Follow the steps in [Lock down the root account IAM users](../6-lock-down-the-root-account-iam-users.md) to lock down your IAM user in the security account. This includes +2. Follow the steps in [Lock down the root account IAM users](../lock-down-the-root-account-iam-users.md) to lock down your IAM user in the security account. This includes configuring an MFA device for your IAM user. 3. After configuring an MFA device, log out, and then log back into the security account again, this time providing your @@ -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/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/0-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 similarity index 99% rename from docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/0-apply-account-baseline-root-to-root-account.md rename to docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-root-to-root-account.md index 018092fef5..3560d159fb 100644 --- a/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/0-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 @@ -581,11 +581,11 @@ Use this process to reset the password for the root user of each child account y ## Lock down the root user in the child accounts -Once you’re able to access the root user of each child account, you should follow the steps in [Lock down the root user](../4-lock-down-the-root-user.md) +Once you’re able to access the root user of each child account, you should follow the steps in [Lock down the root user](../lock-down-the-root-user.md) for each of those child accounts—including enabling MFA and deleting the root user’s access keys—and (almost) never use those root users again. diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/2-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 similarity index 100% rename from docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/2-apply-account-baseline-security-to-security-account.md rename to docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-security-to-security-account.md diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/8-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 similarity index 100% rename from docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/8-enable-key-rotation-for-kms-keys.md rename to docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/enable-key-rotation-for-kms-keys.md diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/5-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 similarity index 100% rename from docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/5-maintain-compliance-by-following-iam-best-practices.md rename to docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-iam-best-practices.md diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/7-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 similarity index 100% rename from docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/7-maintain-compliance-by-following-logging-best-practices.md rename to docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-logging-best-practices.md diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/6-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 similarity index 83% rename from docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/6-maintain-compliance-by-following-storage-best-practices.md rename to docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-storage-best-practices.md index cf8cb3c16e..114709e65a 100644 --- a/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/6-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 @@ -3,12 +3,12 @@ ## S3 Buckets To make sure your S3 buckets are compliant with the benchmark, use the -[`private-s3-bucket` module](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/private-s3-bucket) +[`private-s3-bucket` module](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/private-sbucket) to create and manage all of your S3 buckets. This module blocks public access and enforces encryption by default. Note that all Gruntwork modules that create S3 buckets use this module under the hood. You can either use the `private-s3-bucket` module in your own modules, or, if you wish to deploy a standalone S3 bucket, -use the [`s3-bucket` service](https://github.com/gruntwork-io/terraform-aws-service-catalog/blob/master/modules/data-stores/s3-bucket/) +use the [`s3-bucket` service](https://github.com/gruntwork-io/terraform-aws-service-catalog/blob/master/modules/data-stores/sbucket/) from the Gruntwork Service Catalog. To ensure that all the data in your S3 buckets has been discovered, classified and secured, use the @@ -18,5 +18,5 @@ the hood. diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/4-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 similarity index 100% rename from docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/8-deploy-landing-zone-solution/4-use-iam-roles-for-ec2-instances.md rename to docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/use-iam-roles-for-ec2-instances.md diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/7-deployment-approach.md b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deployment-approach.md similarity index 83% rename from docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/7-deployment-approach.md rename to docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deployment-approach.md index 50a5cbf1dc..53dd560b53 100644 --- a/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/7-deployment-approach.md +++ b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deployment-approach.md @@ -1,7 +1,7 @@ # Deployment approach Before we dive into the code and deployment for each resource, let’s take a step back and understand how the code is structured. -Most of the features explained in the [Production-grade design](../2-production-grade-design/0-intro.md) section will be deployed using the Landing Zone solution, and some more standalone modules like the VPC module. +Most of the features explained in the [Production-grade design](../production-grade-design/intro.md) section will be deployed using the Landing Zone solution, and some more standalone modules like the VPC module. The Landing Zone will be deployed in three steps - the `account-baseline-root` to set up your organization-wide configurations, create the necessary child AWS accounts, set up the CloudTrail and AWS Config buckets. Next, we’ll need to apply the `account-baseline-app` against the created logs account, adding more settings that will be used for aggregation of logs and metrics from the whole organization. Then the `account-baseline-security` will be applied, and that’s responsible to set up your IAM roles and groups that would allow you to access the rest of the accounts within your organization. And finally, the `account-baseline-app` will be applied to an AWS account with the purpose of hosting an application. @@ -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/6-achieve-compliance/3-deployment-walkthrough/6-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 similarity index 100% rename from docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/6-lock-down-the-root-account-iam-users.md rename to docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/lock-down-the-root-account-iam-users.md diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/4-lock-down-the-root-user.md b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/lock-down-the-root-user.md similarity index 100% rename from docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/4-lock-down-the-root-user.md rename to docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/lock-down-the-root-user.md diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/0-pre-requisites.md b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/pre-requisites.md similarity index 92% rename from docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/0-pre-requisites.md rename to docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/pre-requisites.md index 8849469e39..86446c2ba9 100644 --- a/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/0-pre-requisites.md +++ b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/pre-requisites.md @@ -4,7 +4,7 @@ pagination_label: Deployment Walkthrough # Pre-requisites -The [Production-grade Design](../2-production-grade-design/0-intro.md) section describes in detail the Terraform resources to use and the approach to take for +The [Production-grade Design](../production-grade-design/intro.md) section describes in detail the Terraform resources to use and the approach to take for each recommendation, but we've already done that grunt work! This section documents how to achieve compliance using the Infrastructure as Code modules from Gruntwork. This walkthrough has the following pre-requisites: @@ -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 new file mode 100644 index 0000000000..e450263adc --- /dev/null +++ b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/prepare-your-infrastructure-live-repository.md @@ -0,0 +1,13 @@ +--- +sidebar_label: Prepare your infrastructure-live repository +--- + +# Prepare your `infrastructure-live` repository + +We’ve previously described exactly how to prepare your repository in the +[Gruntwork Landing Zone guide](../../landing-zone/deployment-walkthrough/prepare-your-infrastructure-live-repository.md). Follow the steps in that section to get your `infrastructure-live` repository set up for the next steps. + + + diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/1-the-gruntwork-solution.md b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/the-gruntwork-solution.md similarity index 100% rename from docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/1-the-gruntwork-solution.md rename to docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/the-gruntwork-solution.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/0-intro/_category_.json b/docs/guides/build-it-yourself/achieve-compliance/intro/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/0-intro/_category_.json rename to docs/guides/build-it-yourself/achieve-compliance/intro/_category_.json diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/0-intro/1-what-is-the-cis-aws-foundations-benchmark.md b/docs/guides/build-it-yourself/achieve-compliance/intro/what-is-the-cis-aws-foundations-benchmark.md similarity index 100% rename from docs/guides/build-it-yourself/6-achieve-compliance/0-intro/1-what-is-the-cis-aws-foundations-benchmark.md rename to docs/guides/build-it-yourself/achieve-compliance/intro/what-is-the-cis-aws-foundations-benchmark.md diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/0-intro/0-what-youll-learn-in-this-guide.md b/docs/guides/build-it-yourself/achieve-compliance/intro/what-youll-learn-in-this-guide.md similarity index 92% rename from docs/guides/build-it-yourself/6-achieve-compliance/0-intro/0-what-youll-learn-in-this-guide.md rename to docs/guides/build-it-yourself/achieve-compliance/intro/what-youll-learn-in-this-guide.md index b40c6b48bb..8a3cb15301 100644 --- a/docs/guides/build-it-yourself/6-achieve-compliance/0-intro/0-what-youll-learn-in-this-guide.md +++ b/docs/guides/build-it-yourself/achieve-compliance/intro/what-youll-learn-in-this-guide.md @@ -24,8 +24,8 @@ compliant state over time because all of the infrastructure is defined as code. Previously, we supported versions 1.3.0 and 1.2.0 of the Benchmark. If you are looking to upgrade from an older version please follow these in order: -- To upgrade from v1.2.0 to v1.3.0, please follow [this upgrade guide](../../../stay-up-to-date/1-cis/1-how-to-update-to-cis-13/0-intro.md); -- To upgrade from v1.3.0 to v1.4.0, please follow [this upgrade guide](../../../stay-up-to-date/1-cis/0-how-to-update-to-cis-14/0-intro.md). +- To upgrade from v1.2.0 to v1.3.0, please follow [this upgrade guide](../../../stay-up-to-date/cis/how-to-update-to-cis-13/intro.md); +- To upgrade from v1.3.0 to v1.4.0, please follow [this upgrade guide](../../../stay-up-to-date/cis/how-to-update-to-cis-14/intro.md). ![CIS Benchmark Architecture](/img/guides/build-it-yourself/achieve-compliance/cis-account-architecture.png) @@ -69,5 +69,5 @@ walkthrough. diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/4-next-steps.md b/docs/guides/build-it-yourself/achieve-compliance/next-steps.md similarity index 100% rename from docs/guides/build-it-yourself/6-achieve-compliance/4-next-steps.md rename to docs/guides/build-it-yourself/achieve-compliance/next-steps.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/_category_.json b/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/_category_.json rename to docs/guides/build-it-yourself/achieve-compliance/production-grade-design/_category_.json diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/1-identity-and-access-management.md b/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/identity-and-access-management.md similarity index 89% rename from docs/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/1-identity-and-access-management.md rename to docs/guides/build-it-yourself/achieve-compliance/production-grade-design/identity-and-access-management.md index c84cde13ac..cd5c79a48c 100644 --- a/docs/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/1-identity-and-access-management.md +++ b/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/identity-and-access-management.md @@ -274,9 +274,15 @@ substitute `` with the `ServerCertificateId` attribute from th aws iam delete-server-certificate --server-certificate-name ``` -To automate this process you might decide to implement a Lambda function that runs on a regular schedule and removes -all expired SSL/TLS certificates. Check out the [Apply the baseline to the root account](../3-deployment-walkthrough/8-deploy-landing-zone-solution/0-apply-account-baseline-root-to-root-account.md#apply-the-account-baseline-root-baseline-to-the-root-account), [Apply the to the logs account](../3-deployment-walkthrough/8-deploy-landing-zone-solution/1-apply-account-baseline-app-to-logs-account.md) and [Apply the to the security account](../3-deployment-walkthrough/8-deploy-landing-zone-solution/2-apply-account-baseline-security-to-security-account.md) section of the deployment walkthrough -to see how this module is used from the Landing Zone account baselines and is deployed in each of your AWS accounts. +To automate this process you might decide to implement a Lambda function that runs on a regular schedule and removes all +expired SSL/TLS certificates. Check out the [Apply the baseline to the root +account](../deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-root-to-root-account.md#apply-the-account-baseline-root-baseline-to-the-root-account), +[Apply the to the logs +account](../deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-app-to-logs-account.md) and +[Apply the to the security +account](../deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-security-to-security-account.md) +section of the deployment walkthrough to see how this module is used from the Landing Zone account baselines and is +deployed in each of your AWS accounts. ## IAM Access Analyzer @@ -284,9 +290,17 @@ In both versions 1.3.0 and 1.4.0, the CIS recommendations stipulate that the AWS AWS Account or Organization. To achieve this compliance requirement, enable the IAM Access Analyzer service for every AWS region you have enabled in -every one of your AWS accounts. Alternatively, you could make use of the [`iam-access-analyzer-multi-region`](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/iam-access-analyzer-multi-region) module -available in the Gruntwork Service Catalog, or if you’re following this guide, refer to [Apply the baseline to the root account](../3-deployment-walkthrough/8-deploy-landing-zone-solution/0-apply-account-baseline-root-to-root-account.md#apply-the-account-baseline-root-baseline-to-the-root-account), [Apply the to the logs account](../3-deployment-walkthrough/8-deploy-landing-zone-solution/1-apply-account-baseline-app-to-logs-account.md) and [Apply the to the security account](../3-deployment-walkthrough/8-deploy-landing-zone-solution/2-apply-account-baseline-security-to-security-account.md) sections of the -deployment walkthrough to see how this module is used from the Landing Zone account baselines and is deployed in each of your AWS accounts. +every one of your AWS accounts. Alternatively, you could make use of the +[`iam-access-analyzer-multi-region`](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/iam-access-analyzer-multi-region) +module available in the Gruntwork Service Catalog, or if you’re following this guide, refer to [Apply the baseline to +the root +account](../deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-root-to-root-account.md#apply-the-account-baseline-root-baseline-to-the-root-account), +[Apply the to the logs +account](../deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-app-to-logs-account.md) and +[Apply the to the security +account](../deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-security-to-security-account.md) +sections of the deployment walkthrough to see how this module is used from the Landing Zone account baselines and is +deployed in each of your AWS accounts. Once enabled, it will scan only within the boundaries of the AWS Account or Organization it has access to. Only specific resources are analyzed and included in the results - e.g. S3 buckets, SQS, etc. (For the full list of resources supported, @@ -333,5 +347,5 @@ For further detail, follow the manual steps outlined in the CIS Benchmark docume diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/0-intro.md b/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/intro.md similarity index 83% rename from docs/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/0-intro.md rename to docs/guides/build-it-yourself/achieve-compliance/production-grade-design/intro.md index f623f666a0..8226f954a0 100644 --- a/docs/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/0-intro.md +++ b/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/intro.md @@ -4,7 +4,7 @@ pagination_label: Production-grade Design # Intro to Production-grade Design -In [core concepts](../1-core-concepts/0-intro.md) we discussed the basics of the AWS Foundations Benchmark. Although it's possible to achieve +In [core concepts](../core-concepts/intro.md) we discussed the basics of the AWS Foundations Benchmark. Although it's possible to achieve compliance with the Benchmark by manually configuring each setting in the web console or entering the CLI commands, we strongly discourage this approach. It precludes [the myriad benefits of using code to manage infrastructure](/docs/intro/core-concepts/infrastructure-as-code). @@ -18,5 +18,5 @@ edition of Terraform Up & Running](https://blog.gruntwork.io/terraform-up-runnin diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/3-logging.md b/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/logging.md similarity index 100% rename from docs/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/3-logging.md rename to docs/guides/build-it-yourself/achieve-compliance/production-grade-design/logging.md diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/4-monitoring.md b/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/monitoring.md similarity index 100% rename from docs/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/4-monitoring.md rename to docs/guides/build-it-yourself/achieve-compliance/production-grade-design/monitoring.md diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/5-networking.md b/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/networking.md similarity index 100% rename from docs/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/5-networking.md rename to docs/guides/build-it-yourself/achieve-compliance/production-grade-design/networking.md diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/2-storage.md b/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/storage.md similarity index 93% rename from docs/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/2-storage.md rename to docs/guides/build-it-yourself/achieve-compliance/production-grade-design/storage.md index d842679183..d6e12dd4f7 100644 --- a/docs/guides/build-it-yourself/6-achieve-compliance/2-production-grade-design/2-storage.md +++ b/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/storage.md @@ -65,7 +65,7 @@ The CIS 1.4.0 Benchmark recommends a few additional steps to ensure your data is :::info -The steps below are not the full list of actions needed to configure MFA Delete or Amazon Macie for your account. To follow the steps necessary to configure it according to the CIS 1.4.0 Benchmark, please follow the MFA Delete and Macie section in the [the migration guide to CIS 1.4.0](../../../stay-up-to-date/1-cis/0-how-to-update-to-cis-14/0-intro.md), or the deployment guide section in this guide. +The steps below are not the full list of actions needed to configure MFA Delete or Amazon Macie for your account. To follow the steps necessary to configure it according to the CIS 1.4.0 Benchmark, please follow the MFA Delete and Macie section in the [the migration guide to CIS 1.4.0](../../../stay-up-to-date/cis/how-to-update-to-cis-14/intro.md), or the deployment guide section in this guide. ::: ### Enable MFA Delete (recommendation 2.1.3) @@ -105,7 +105,7 @@ aws s3api put-bucket-versioning --region \ --mfa "arn:aws:iam:::mfa/root-account-mfa-device " ``` -We also created a [script](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/private-s3-bucket/mfa-delete-script) to help you enable MFA Delete in all buckets from a single account at once. To learn how to run it and when, please follow the production _Deployment Walkthrough_ guide section below. +We also created a [script](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/private-sbucket/mfa-delete-script) to help you enable MFA Delete in all buckets from a single account at once. To learn how to run it and when, please follow the production _Deployment Walkthrough_ guide section below. ### Configure Amazon Macie (recommendation 2.1.4) @@ -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/6-achieve-compliance/5-traceability-matrix.md b/docs/guides/build-it-yourself/achieve-compliance/traceability-matrix.md similarity index 100% rename from docs/guides/build-it-yourself/6-achieve-compliance/5-traceability-matrix.md rename to docs/guides/build-it-yourself/achieve-compliance/traceability-matrix.md diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/_category_.json b/docs/guides/build-it-yourself/kubernetes-cluster/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/_category_.json rename to docs/guides/build-it-yourself/kubernetes-cluster/_category_.json diff --git a/docs/guides/build-it-yourself/4-vpc/1-core-concepts/_category_.json b/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/1-core-concepts/_category_.json rename to docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/_category_.json diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/3-interacting-with-kubernetes.md b/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/interacting-with-kubernetes.md similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/3-interacting-with-kubernetes.md rename to docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/interacting-with-kubernetes.md diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/2-kubernetes-access-control.md b/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-access-control.md similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/2-kubernetes-access-control.md rename to docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-access-control.md diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/1-kubernetes-architecture.md b/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-architecture.md similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/1-kubernetes-architecture.md rename to docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-architecture.md diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/4-kubernetes-resources.md b/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-resources.md similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/4-kubernetes-resources.md rename to docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-resources.md diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/5-options-for-running-kubernetes-in-aws.md b/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/options-for-running-kubernetes-in-aws.md similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/5-options-for-running-kubernetes-in-aws.md rename to docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/options-for-running-kubernetes-in-aws.md diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/0-why-kubernetes.md b/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/why-kubernetes.md similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/0-why-kubernetes.md rename to docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/why-kubernetes.md diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/10-try-out-the-cluster.md b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/10-try-out-the-cluster.md similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/10-try-out-the-cluster.md rename to docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/10-try-out-the-cluster.md diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/11-updating-the-worker-nodes.md b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/11-updating-the-worker-nodes.md similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/11-updating-the-worker-nodes.md rename to docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/11-updating-the-worker-nodes.md diff --git a/docs/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/_category_.json b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/_category_.json rename to docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/_category_.json diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/8-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 similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/8-configure-access-to-the-control-plane-and-worker-nodes.md rename to docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-access-to-the-control-plane-and-worker-nodes.md diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/6-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 similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/6-configure-logging-metrics-and-alarms-for-the-worker-nodes.md rename to docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-logging-metrics-and-alarms-for-the-worker-nodes.md diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/7-configure-role-mapping.md b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-role-mapping.md similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/7-configure-role-mapping.md rename to docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-role-mapping.md diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/2-configure-the-control-plane.md b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-control-plane.md similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/2-configure-the-control-plane.md rename to docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-control-plane.md diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/5-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 similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/5-configure-the-worker-node-user-data-script.md rename to docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-worker-node-user-data-script.md diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/3-configure-the-worker-nodes.md b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-worker-nodes.md similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/3-configure-the-worker-nodes.md rename to docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-worker-nodes.md diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/4-create-the-worker-node-ami.md b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/create-the-worker-node-ami.md similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/4-create-the-worker-node-ami.md rename to docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/create-the-worker-node-ami.md diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/9-deploy-the-eks-cluster.md b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/deploy-the-eks-cluster.md similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/9-deploy-the-eks-cluster.md rename to docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/deploy-the-eks-cluster.md diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/1-deploy-the-vpc.md b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/deploy-the-vpc.md similarity index 96% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/1-deploy-the-vpc.md rename to docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/deploy-the-vpc.md index b0dd2ce762..49ec3a9a0a 100644 --- a/docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/1-deploy-the-vpc.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/deploy-the-vpc.md @@ -1,7 +1,7 @@ # Deploy the VPC The first step is to deploy a VPC. Follow the instructions in -[How to deploy a production-grade VPC on AWS](../../4-vpc/0-intro/0-what-youll-learn-in-this-guide.md) to use +[How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) to use `module-vpc` to create a VPC setup that looks like this: ![A production-grade VPC setup deployed using module-vpc from the Gruntwork Infrastructure as Code Library](/img/guides/build-it-yourself/vpc/vpc-diagram.png) @@ -149,5 +149,5 @@ terragrunt apply diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/0-pre-requisites.md b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/pre-requisites.md similarity index 94% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/0-pre-requisites.md rename to docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/pre-requisites.md index f48357c90d..69402691cb 100644 --- a/docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/0-pre-requisites.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/pre-requisites.md @@ -49,7 +49,7 @@ our [Introduction to Gruntwork](/docs/intro/overview/intro-to-gruntwork). #### AWS accounts This guide deploys infrastructure into one or more AWS accounts. Check out the -[How to configure a production-grade AWS account structure](../../2-landing-zone/0-intro/0-what-youll-learn-in-this-guide.md) +[How to configure a production-grade AWS account structure](../../landing-zone/intro/what-youll-learn-in-this-guide.md) guide for instructions. You will also need to be able to authenticate to these accounts on the CLI: check out [A Comprehensive Guide to Authenticating to AWS on the Command Line](https://blog.gruntwork.io/a-comprehensive-guide-to-authenticating-to-aws-on-the-command-line-63656a686799) for instructions. @@ -58,5 +58,5 @@ for instructions. diff --git a/docs/guides/build-it-yourself/3-pipelines/0-intro/_category_.json b/docs/guides/build-it-yourself/kubernetes-cluster/intro/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/0-intro/_category_.json rename to docs/guides/build-it-yourself/kubernetes-cluster/intro/_category_.json diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/0-intro/1-what-is-kubernetes.md b/docs/guides/build-it-yourself/kubernetes-cluster/intro/what-is-kubernetes.md similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/0-intro/1-what-is-kubernetes.md rename to docs/guides/build-it-yourself/kubernetes-cluster/intro/what-is-kubernetes.md diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/0-intro/0-what-youll-learn-in-this-guide.md b/docs/guides/build-it-yourself/kubernetes-cluster/intro/what-youll-learn-in-this-guide.md similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/0-intro/0-what-youll-learn-in-this-guide.md rename to docs/guides/build-it-yourself/kubernetes-cluster/intro/what-youll-learn-in-this-guide.md diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/4-next-steps.md b/docs/guides/build-it-yourself/kubernetes-cluster/next-steps.md similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/4-next-steps.md rename to docs/guides/build-it-yourself/kubernetes-cluster/next-steps.md diff --git a/docs/guides/build-it-yourself/3-pipelines/2-production-grade-design/_category_.json b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/2-production-grade-design/_category_.json rename to docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/_category_.json diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/5-authenticate.md b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/authenticate.md similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/5-authenticate.md rename to docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/authenticate.md diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/3-control-plane.md b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/control-plane.md similarity index 89% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/3-control-plane.md rename to docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/control-plane.md index 337b29351c..b084b2084a 100644 --- a/docs/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/3-control-plane.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/control-plane.md @@ -19,7 +19,7 @@ minor version. Your EKS cluster will run in the subnets you specify. We strongly recommend running solely in private subnets that are NOT directly accessible from the public Internet. See -[How to deploy a production-grade VPC on AWS](../../4-vpc/0-intro/0-what-youll-learn-in-this-guide.md) for more +[How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) for more info. #### Endpoint access @@ -28,7 +28,7 @@ You can configure whether the [API endpoint for your EKS cluster](https://docs.a is accessible from (a) within the same VPC and/or (b) from the public Internet. We recommend allowing access from within the VPC, but not from the public Internet. If you need to talk to your Kubernetes cluster from your own computer (e.g., to issue commands via `kubectl`), use a bastion host or VPN server. See -[How to deploy a production-grade VPC on AWS](../../4-vpc/0-intro/0-what-youll-learn-in-this-guide.md) for more +[How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) for more info. #### Cluster IAM Role @@ -54,5 +54,5 @@ CloudWatch. diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/6-iam-role-mapping-and-rbac.md b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/iam-role-mapping-and-rbac.md similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/6-iam-role-mapping-and-rbac.md rename to docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/iam-role-mapping-and-rbac.md diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/0-intro.md b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/intro.md similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/0-intro.md rename to docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/intro.md diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/7-logging.md b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/logging.md similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/7-logging.md rename to docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/logging.md diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/8-protecting-pods.md b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/protecting-pods.md similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/8-protecting-pods.md rename to docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/protecting-pods.md diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/1-use-eks.md b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/use-eks.md similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/1-use-eks.md rename to docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/use-eks.md diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/2-vpc-configuration.md b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/vpc-configuration.md similarity index 90% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/2-vpc-configuration.md rename to docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/vpc-configuration.md index ef5b5b9f55..8dd782a876 100644 --- a/docs/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/2-vpc-configuration.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/vpc-configuration.md @@ -2,7 +2,7 @@ EKS relies on a _[Virtual Private Cloud (VPC)](https://aws.amazon.com/vpc/)_ to provide the basic network topology and to manage communication across the nodes (see -[How to deploy a production-grade VPC on AWS](../../4-vpc/0-intro/0-what-youll-learn-in-this-guide.md) for more +[How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) for more information on VPCs). Here are the key VPC considerations for your EKS cluster:
@@ -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/5-kubernetes-cluster/2-production-grade-design/4-worker-nodes.md b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/worker-nodes.md similarity index 94% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/4-worker-nodes.md rename to docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/worker-nodes.md index ba070a9f54..32bd9219a5 100644 --- a/docs/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/4-worker-nodes.md +++ b/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/worker-nodes.md @@ -20,7 +20,7 @@ value `owned`. We strongly recommend running the Auto Scaling Group for your worker nodes in private subnets that are NOT directly accessible from the public Internet. See -[How to deploy a production-grade VPC on AWS](../../4-vpc/0-intro/0-what-youll-learn-in-this-guide.md) for more +[How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) for more info. #### AMI @@ -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/2-landing-zone/_category_.json b/docs/guides/build-it-yourself/landing-zone/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/_category_.json rename to docs/guides/build-it-yourself/landing-zone/_category_.json diff --git a/docs/guides/build-it-yourself/5-achieve-compliance/1-core-concepts/_category_.json b/docs/guides/build-it-yourself/landing-zone/core-concepts/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/5-achieve-compliance/1-core-concepts/_category_.json rename to docs/guides/build-it-yourself/landing-zone/core-concepts/_category_.json diff --git a/docs/guides/build-it-yourself/2-landing-zone/1-core-concepts/0-aws-account.md b/docs/guides/build-it-yourself/landing-zone/core-concepts/aws-account.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/1-core-concepts/0-aws-account.md rename to docs/guides/build-it-yourself/landing-zone/core-concepts/aws-account.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/1-core-concepts/9-aws-config.md b/docs/guides/build-it-yourself/landing-zone/core-concepts/aws-config.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/1-core-concepts/9-aws-config.md rename to docs/guides/build-it-yourself/landing-zone/core-concepts/aws-config.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/1-core-concepts/7-aws-organizations.md b/docs/guides/build-it-yourself/landing-zone/core-concepts/aws-organizations.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/1-core-concepts/7-aws-organizations.md rename to docs/guides/build-it-yourself/landing-zone/core-concepts/aws-organizations.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/1-core-concepts/8-cloud-trail.md b/docs/guides/build-it-yourself/landing-zone/core-concepts/cloud-trail.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/1-core-concepts/8-cloud-trail.md rename to docs/guides/build-it-yourself/landing-zone/core-concepts/cloud-trail.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/1-core-concepts/6-federated-authentication.md b/docs/guides/build-it-yourself/landing-zone/core-concepts/federated-authentication.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/1-core-concepts/6-federated-authentication.md rename to docs/guides/build-it-yourself/landing-zone/core-concepts/federated-authentication.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/1-core-concepts/10-guard-duty.md b/docs/guides/build-it-yourself/landing-zone/core-concepts/guard-duty.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/1-core-concepts/10-guard-duty.md rename to docs/guides/build-it-yourself/landing-zone/core-concepts/guard-duty.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/1-core-concepts/4-iam-groups.md b/docs/guides/build-it-yourself/landing-zone/core-concepts/iam-groups.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/1-core-concepts/4-iam-groups.md rename to docs/guides/build-it-yourself/landing-zone/core-concepts/iam-groups.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/1-core-concepts/3-iam-policies.md b/docs/guides/build-it-yourself/landing-zone/core-concepts/iam-policies.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/1-core-concepts/3-iam-policies.md rename to docs/guides/build-it-yourself/landing-zone/core-concepts/iam-policies.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/1-core-concepts/5-iam-roles.md b/docs/guides/build-it-yourself/landing-zone/core-concepts/iam-roles.md similarity index 94% rename from docs/guides/build-it-yourself/2-landing-zone/1-core-concepts/5-iam-roles.md rename to docs/guides/build-it-yourself/landing-zone/core-concepts/iam-roles.md index 77696444b2..a48e5683f0 100644 --- a/docs/guides/build-it-yourself/2-landing-zone/1-core-concepts/5-iam-roles.md +++ b/docs/guides/build-it-yourself/landing-zone/core-concepts/iam-roles.md @@ -5,8 +5,6 @@ you to attach IAM policies to it, (b) specify which other IAM entities to trust, can _assume_ the IAM role to be temporarily get access to the permissions in those IAM policies. The two most common use cases for IAM roles are: - -
#### Service roles @@ -26,13 +24,10 @@ S3 bucket in account `B` and allow that role to be assumed by an IAM user in acc able to access the contents of the S3 bucket by assuming the IAM role in account `B`. This ability to assume IAM roles across different AWS accounts is the critical glue that truly makes a multi AWS account structure possible. -
Here are some more details on how IAM roles work: - -
#### IAM policies @@ -45,30 +40,29 @@ You must define a _trust policy_ for each IAM role, which is a JSON document (ve specifies who can assume this IAM role. For example, here is a trust policy that allows this IAM role to be assumed by an IAM user named `Bob` in AWS account `111122223333`: -
-``` json +```json { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "sts:AssumeRole", - "Principal": {"AWS": "arn:aws:iam::111122223333:user/Bob"} + "Principal": { "AWS": "arn:aws:iam::111122223333:user/Bob" } } ] } ``` Note that a trust policy alone does NOT automatically give Bob the ability to assume this IAM role. Cross-account -access always requires permissions in *both* accounts. So, if Bob is in AWS account `111122223333` and you want him to +access always requires permissions in _both_ accounts. So, if Bob is in AWS account `111122223333` and you want him to have access to an IAM role called `foo` in account `444455556666`, then you need to configure permissions in both accounts: first, in account `444455556666`, the `foo` IAM role must have a trust policy that gives `sts:AssumeRole` permissions to account `111122223333`, as shown above; second, in account `111122223333`, you also need to attach an IAM policy to Bob’s IAM user that allows him to assume the `foo` IAM role, which might look like this: -``` json +```json { "Version": "2012-10-17", "Statement": [ @@ -81,8 +75,6 @@ IAM policy to Bob’s IAM user that allows him to assume the `foo` IAM role, whi } ``` - -
#### Assuming an IAM role @@ -96,7 +88,6 @@ will be valid for 1-12 hours, depending on IAM role settings, after which you mu new keys. Note that to make the `AssumeRole` API call, you must first authenticate to AWS using some other mechanism. For example, for an IAM user to assume an IAM role, the workflow looks like this: -
![The process for assuming an IAM role](/img/guides/build-it-yourself/landing-zone/assume-iam-role.png) @@ -114,8 +105,6 @@ The basic steps are: 5. Now all of your subsequent API calls will be on behalf of the assumed IAM role, with access to whatever permissions are attached to that role - -
#### IAM roles and AWS services @@ -123,7 +112,7 @@ The basic steps are: Most AWS services have native support built-in for assuming IAM roles. For example, you can associate an IAM role directly with an EC2 instance, and that instance will automatically assume the IAM role every few hours, making the temporary credentials available in -_[EC2 instance metadata](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html#instancedata-data-retrieval)_. +_[EC2 instance metadata](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ecinstance-metadata.html#instancedata-data-retrieval)_. Just about every AWS CLI and SDK tool knows how to read and periodically update temporary credentials from EC2 instance metadata, so in practice, as soon as you attach an IAM role to an EC2 instance, any code running on that EC2 instance can automatically make API calls on behalf of that IAM role, with whatever permissions are attached to that @@ -132,14 +121,9 @@ copy credentials (access keys) onto that instance. The same strategy works with use IAM roles as a secure way to give your Lambda functions, ECS services, Step Functions, and many other AWS services permissions to access specific resources in your AWS account. -
- - - - diff --git a/docs/guides/build-it-yourself/2-landing-zone/1-core-concepts/2-iam-users.md b/docs/guides/build-it-yourself/landing-zone/core-concepts/iam-users.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/1-core-concepts/2-iam-users.md rename to docs/guides/build-it-yourself/landing-zone/core-concepts/iam-users.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/1-core-concepts/1-root-user.md b/docs/guides/build-it-yourself/landing-zone/core-concepts/root-user.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/1-core-concepts/1-root-user.md rename to docs/guides/build-it-yourself/landing-zone/core-concepts/root-user.md diff --git a/docs/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/_category_.json b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/_category_.json rename to docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/_category_.json diff --git a/docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/11-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 similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/11-apply-the-security-baseline-to-the-logs-account.md rename to docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-logs-account.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/13-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 similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/13-apply-the-security-baseline-to-the-other-child-accounts.md rename to docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-other-child-accounts.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/8-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 similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/8-apply-the-security-baseline-to-the-root-account.md rename to docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-root-account.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/12-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 similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/12-apply-the-security-baseline-to-the-security-account.md rename to docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-security-account.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/6-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 similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/6-configure-the-security-baseline-for-the-root-account.md rename to docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/configure-the-security-baseline-for-the-root-account.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/4-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 similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/4-create-an-iam-user-in-the-root-account.md rename to docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/create-an-iam-user-in-the-root-account.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/2-create-the-root-account.md b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/create-the-root-account.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/2-create-the-root-account.md rename to docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/create-the-root-account.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/7-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 similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/7-import-existing-resources-from-the-root-account-into-terraform-state.md rename to docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/import-existing-resources-from-the-root-account-into-terraform-state.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/5-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 similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/5-lock-down-the-root-account-iam-users.md rename to docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/lock-down-the-root-account-iam-users.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/10-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 similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/10-lock-down-the-root-user-in-the-child-accounts.md rename to docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/lock-down-the-root-user-in-the-child-accounts.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/3-lock-down-the-root-user.md b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/lock-down-the-root-user.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/3-lock-down-the-root-user.md rename to docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/lock-down-the-root-user.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/0-pre-requisites.md b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/pre-requisites.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/0-pre-requisites.md rename to docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/pre-requisites.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/1-prepare-your-infrastructure-live-repository.md b/docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/prepare-your-infrastructure-live-repository.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/1-prepare-your-infrastructure-live-repository.md rename to docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/prepare-your-infrastructure-live-repository.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/9-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 similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/9-reset-the-root-user-password-in-each-child-account.md rename to docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/reset-the-root-user-password-in-each-child-account.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/14-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 similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/3-deployment-walkthrough/14-try-authenticating-as-an-iam-user-to-the-child-accounts.md rename to docs/guides/build-it-yourself/landing-zone/deployment-walkthrough/try-authenticating-as-an-iam-user-to-the-child-accounts.md diff --git a/docs/guides/build-it-yourself/4-vpc/0-intro/_category_.json b/docs/guides/build-it-yourself/landing-zone/intro/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/0-intro/_category_.json rename to docs/guides/build-it-yourself/landing-zone/intro/_category_.json diff --git a/docs/guides/build-it-yourself/2-landing-zone/0-intro/2-gruntwork-aws-landing-zone-vs-the-alternatives.md b/docs/guides/build-it-yourself/landing-zone/intro/gruntwork-aws-landing-zone-vs-the-alternatives.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/0-intro/2-gruntwork-aws-landing-zone-vs-the-alternatives.md rename to docs/guides/build-it-yourself/landing-zone/intro/gruntwork-aws-landing-zone-vs-the-alternatives.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/0-intro/1-what-is-an-aws-account-structure.md b/docs/guides/build-it-yourself/landing-zone/intro/what-is-an-aws-account-structure.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/0-intro/1-what-is-an-aws-account-structure.md rename to docs/guides/build-it-yourself/landing-zone/intro/what-is-an-aws-account-structure.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/0-intro/0-what-youll-learn-in-this-guide.md b/docs/guides/build-it-yourself/landing-zone/intro/what-youll-learn-in-this-guide.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/0-intro/0-what-youll-learn-in-this-guide.md rename to docs/guides/build-it-yourself/landing-zone/intro/what-youll-learn-in-this-guide.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/4-next-steps.md b/docs/guides/build-it-yourself/landing-zone/next-steps.md similarity index 61% rename from docs/guides/build-it-yourself/2-landing-zone/4-next-steps.md rename to docs/guides/build-it-yourself/landing-zone/next-steps.md index ac05369e82..f80b8e712e 100644 --- a/docs/guides/build-it-yourself/2-landing-zone/4-next-steps.md +++ b/docs/guides/build-it-yourself/landing-zone/next-steps.md @@ -2,9 +2,9 @@ Now that you have your basic AWS account structure set up, the next step is to start deploying infrastructure in those accounts! Usually, the best starting point is to configure your network topology, as described in -[How to deploy a production-grade VPC on AWS](../4-vpc/0-intro/0-what-youll-learn-in-this-guide.md). +[How to deploy a production-grade VPC on AWS](../vpc/intro/what-youll-learn-in-this-guide.md). diff --git a/docs/guides/build-it-yourself/4-vpc/2-production-grade-design/_category_.json b/docs/guides/build-it-yourself/landing-zone/production-grade-design/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/2-production-grade-design/_category_.json rename to docs/guides/build-it-yourself/landing-zone/production-grade-design/_category_.json diff --git a/docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/9-aws-config.md b/docs/guides/build-it-yourself/landing-zone/production-grade-design/aws-config.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/9-aws-config.md rename to docs/guides/build-it-yourself/landing-zone/production-grade-design/aws-config.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/2-child-accounts.md b/docs/guides/build-it-yourself/landing-zone/production-grade-design/child-accounts.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/2-child-accounts.md rename to docs/guides/build-it-yourself/landing-zone/production-grade-design/child-accounts.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/8-cloud-trail.md b/docs/guides/build-it-yourself/landing-zone/production-grade-design/cloud-trail.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/8-cloud-trail.md rename to docs/guides/build-it-yourself/landing-zone/production-grade-design/cloud-trail.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/11-federated-auth.md b/docs/guides/build-it-yourself/landing-zone/production-grade-design/federated-auth.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/11-federated-auth.md rename to docs/guides/build-it-yourself/landing-zone/production-grade-design/federated-auth.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/10-guard-duty.md b/docs/guides/build-it-yourself/landing-zone/production-grade-design/guard-duty.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/10-guard-duty.md rename to docs/guides/build-it-yourself/landing-zone/production-grade-design/guard-duty.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/7-iam-roles-for-services.md b/docs/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-services.md similarity index 96% rename from docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/7-iam-roles-for-services.md rename to docs/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-services.md index 820f6463c8..b8faf413b8 100644 --- a/docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/7-iam-roles-for-services.md +++ b/docs/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-services.md @@ -54,7 +54,7 @@ need to take extra care in terms of who can assume this IAM role, what permissio services. For example, if you have Jenkins running on an EC2 instance, and you give that EC2 instance access to an IAM role so it can deploy your apps, you should do your best to minimize the permissions that IAM role has (e.g., to just `ecs` permissions if deploying to ECS) and you should ensure that your Jenkins instance runs in private -subnets so that it is NOT accessible from the public Internet (see [How to deploy a production-grade VPC on AWS](../../4-vpc/0-intro/0-what-youll-learn-in-this-guide.md)). +subnets so that it is NOT accessible from the public Internet (see [How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md)). #### Use the right Principal @@ -89,7 +89,7 @@ want an IAM role that can be assumed by a Lambda function, the `Principal` will While IAM roles offer a convenient way to give an EC2 instance permissions to make API calls without having to manually copy credentials to the EC2 instance, the default security configuration for them is not particularly secure. That’s because the IAM role is exposed to the code on the EC2 instance through -[EC2 instance metadata](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html#instancedata-data-retrieval), +[EC2 instance metadata](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ecinstance-metadata.html#instancedata-data-retrieval), which is an http endpoint (`\http://169.254.169.254`) that _anyone_ on the EC2 instance can access. That means that any compromise of that EC2 instance instantly gives an attacker access to all the permissions in that IAM role. We **strongly** recommend mitigating this by limiting access to the endpoint solely to specific OS users (e.g., solely to @@ -136,5 +136,5 @@ sensitive machine user access keys. diff --git a/docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/3-iam-roles-for-users.md b/docs/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-users.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/3-iam-roles-for-users.md rename to docs/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-users.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/4-iam-users-and-groups.md b/docs/guides/build-it-yourself/landing-zone/production-grade-design/iam-users-and-groups.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/4-iam-users-and-groups.md rename to docs/guides/build-it-yourself/landing-zone/production-grade-design/iam-users-and-groups.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/0-intro.md b/docs/guides/build-it-yourself/landing-zone/production-grade-design/intro.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/0-intro.md rename to docs/guides/build-it-yourself/landing-zone/production-grade-design/intro.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/5-mfa-policy.md b/docs/guides/build-it-yourself/landing-zone/production-grade-design/mfa-policy.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/5-mfa-policy.md rename to docs/guides/build-it-yourself/landing-zone/production-grade-design/mfa-policy.md diff --git a/docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/6-password-policy.md b/docs/guides/build-it-yourself/landing-zone/production-grade-design/password-policy.md similarity index 68% rename from docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/6-password-policy.md rename to docs/guides/build-it-yourself/landing-zone/production-grade-design/password-policy.md index 0d1c9a950f..18395fb742 100644 --- a/docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/6-password-policy.md +++ b/docs/guides/build-it-yourself/landing-zone/production-grade-design/password-policy.md @@ -3,9 +3,9 @@ In any account that has IAM users (which should just be the root and security accounts), configure a password policy that ensures all IAM users have strong passwords. The exact policy you use depends on your company’s requirements (e.g., certain compliance requirements may force you to use a specific password policy), but you may want to consider -[NIST 800-63 guidelines](https://pages.nist.gov/800-63-3/sp800-63b.html#memsecret) as a reasonable starting point. +[NIST 800-63 guidelines](https://pages.nist.gov/8063/sp8063b.html#memsecret) as a reasonable starting point. diff --git a/docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/1-the-root-account.md b/docs/guides/build-it-yourself/landing-zone/production-grade-design/the-root-account.md similarity index 100% rename from docs/guides/build-it-yourself/2-landing-zone/2-production-grade-design/1-the-root-account.md rename to docs/guides/build-it-yourself/landing-zone/production-grade-design/the-root-account.md diff --git a/docs/guides/build-it-yourself/1-overview.md b/docs/guides/build-it-yourself/overview.md similarity index 100% rename from docs/guides/build-it-yourself/1-overview.md rename to docs/guides/build-it-yourself/overview.md diff --git a/docs/guides/build-it-yourself/3-pipelines/_category_.json b/docs/guides/build-it-yourself/pipelines/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/_category_.json rename to docs/guides/build-it-yourself/pipelines/_category_.json diff --git a/docs/guides/build-it-yourself/3-pipelines/1-core-concepts/_category_.json b/docs/guides/build-it-yourself/pipelines/core-concepts/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/1-core-concepts/_category_.json rename to docs/guides/build-it-yourself/pipelines/core-concepts/_category_.json diff --git a/docs/guides/build-it-yourself/3-pipelines/1-core-concepts/5-ci-cd-platforms.md b/docs/guides/build-it-yourself/pipelines/core-concepts/ci-cd-platforms.md similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/1-core-concepts/5-ci-cd-platforms.md rename to docs/guides/build-it-yourself/pipelines/core-concepts/ci-cd-platforms.md diff --git a/docs/guides/build-it-yourself/3-pipelines/1-core-concepts/3-ci-cd-workflows.md b/docs/guides/build-it-yourself/pipelines/core-concepts/ci-cd-workflows.md similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/1-core-concepts/3-ci-cd-workflows.md rename to docs/guides/build-it-yourself/pipelines/core-concepts/ci-cd-workflows.md diff --git a/docs/guides/build-it-yourself/3-pipelines/1-core-concepts/4-threat-model-of-ci-cd.md b/docs/guides/build-it-yourself/pipelines/core-concepts/threat-model-of-ci-cd.md similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/1-core-concepts/4-threat-model-of-ci-cd.md rename to docs/guides/build-it-yourself/pipelines/core-concepts/threat-model-of-ci-cd.md diff --git a/docs/guides/build-it-yourself/3-pipelines/1-core-concepts/1-trunk-based-development-model.md b/docs/guides/build-it-yourself/pipelines/core-concepts/trunk-based-development-model.md similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/1-core-concepts/1-trunk-based-development-model.md rename to docs/guides/build-it-yourself/pipelines/core-concepts/trunk-based-development-model.md diff --git a/docs/guides/build-it-yourself/3-pipelines/1-core-concepts/2-types-of-infrastructure-code.md b/docs/guides/build-it-yourself/pipelines/core-concepts/types-of-infrastructure-code.md similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/1-core-concepts/2-types-of-infrastructure-code.md rename to docs/guides/build-it-yourself/pipelines/core-concepts/types-of-infrastructure-code.md diff --git a/docs/guides/build-it-yourself/3-pipelines/1-core-concepts/0-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 similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/1-core-concepts/0-why-is-it-important-to-have-ci-cd.md rename to docs/guides/build-it-yourself/pipelines/core-concepts/why-is-it-important-to-have-ci-cd.md diff --git a/docs/guides/build-it-yourself/5-achieve-compliance/3-deployment-walkthrough/_category_.json b/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/5-achieve-compliance/3-deployment-walkthrough/_category_.json rename to docs/guides/build-it-yourself/pipelines/deployment-walkthrough/_category_.json diff --git a/docs/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/5-configure-ci-server.md b/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/configure-ci-server.md similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/5-configure-ci-server.md rename to docs/guides/build-it-yourself/pipelines/deployment-walkthrough/configure-ci-server.md diff --git a/docs/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/4-define-pipeline-as-code.md b/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/define-pipeline-as-code.md similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/4-define-pipeline-as-code.md rename to docs/guides/build-it-yourself/pipelines/deployment-walkthrough/define-pipeline-as-code.md diff --git a/docs/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/1-deploy-a-vpc.md b/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/deploy-a-vpc.md similarity index 86% rename from docs/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/1-deploy-a-vpc.md rename to docs/guides/build-it-yourself/pipelines/deployment-walkthrough/deploy-a-vpc.md index 4c73224fec..415766d97f 100644 --- a/docs/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/1-deploy-a-vpc.md +++ b/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/deploy-a-vpc.md @@ -1,7 +1,7 @@ # Deploy a VPC The first step is to deploy a VPC. Follow the instructions in -[How to deploy a production-grade VPC on AWS](../../4-vpc/0-intro/0-what-youll-learn-in-this-guide.md) to use +[How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) to use `module-vpc` to create a VPC setup that looks like this: ![A production-grade VPC setup deployed using module-vpc from the Gruntwork Infrastructure as Code Library](/img/guides/build-it-yourself/pipelines/vpc-diagram.png) @@ -37,5 +37,5 @@ infrastructure-live diff --git a/docs/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/2-deploy-the-ecs-deploy-runner.md b/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/deploy-the-ecs-deploy-runner.md similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/2-deploy-the-ecs-deploy-runner.md rename to docs/guides/build-it-yourself/pipelines/deployment-walkthrough/deploy-the-ecs-deploy-runner.md diff --git a/docs/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/0-pre-requisites.md b/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/pre-requisites.md similarity index 70% rename from docs/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/0-pre-requisites.md rename to docs/guides/build-it-yourself/pipelines/deployment-walkthrough/pre-requisites.md index cfb284dd08..67941b7d4e 100644 --- a/docs/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/0-pre-requisites.md +++ b/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/pre-requisites.md @@ -36,22 +36,21 @@ official getting started guide](https://circleci.com/docs/2.0/getting-started/#s #### AWS accounts -This guide deploys infrastructure into one or more AWS accounts. Check out the -[Production Grade AWS Account Structure](https://gruntwork.io/guides/foundations/how-to-configure-production-grade-aws-account-structure) guide for instructions. -You will also need to be able to authenticate to these accounts on the CLI: check out -[A Comprehensive Guide to Authenticating to AWS on the Command Line](https://blog.gruntwork.io/a-comprehensive-guide-to-authenticating-to-aws-on-the-command-line-63656a686799) -for instructions. +This guide deploys infrastructure into one or more AWS accounts. Check out the [Production Grade AWS Account +Structure](https://gruntwork.io/guides/foundations/how-to-configure-production-grade-aws-account-structure) guide for +instructions. You will also need to be able to authenticate to these accounts on the CLI: check out [A Comprehensive +Guide to Authenticating to AWS on the Command +Line](https://blog.gruntwork.io/a-comprehensive-guide-to-authenticating-to-aws-on-the-command-line-63656a686799) for +instructions. #### Repository structure -This guide assumes your infrastructure code is organized in a manner similar to -that covered in the [Prepare Your Module](/docs/intro/first-deployment/using-terraform-modules) introduction section. This means -that you should have two repositories for your infrastructure code, -`infrastructure-modules` and `infrastructure-live`. Make sure that the +This guide assumes your infrastructure code is organized in a manner similar to that covered in the [Prepare Your +Module](/docs/intro/first-deployment/using-terraform-modules) introduction section. This means that you should have two +repositories for your≤ infrastructure code, `infrastructure-modules` and `infrastructure-live`. Make sure that the `infrastructure-live` repository is locked down as recommended in [Lock down VCS -systems](../2-production-grade-design/7-lock-down-vcs-systems.md). This guide -will assume that `master` is the protected branch where infrastructure is -deployed from. +systems](../production-grade-design/lock-down-vcs-systems.md). This guide will assume that `master` is the protected +branch where infrastructure is deployed from.
@@ -68,5 +67,5 @@ on alternative options, such as how to diff --git a/docs/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/3-try-out-the-ecs-deploy-runner.md b/docs/guides/build-it-yourself/pipelines/deployment-walkthrough/try-out-the-ecs-deploy-runner.md similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/3-deployment-walkthrough/3-try-out-the-ecs-deploy-runner.md rename to docs/guides/build-it-yourself/pipelines/deployment-walkthrough/try-out-the-ecs-deploy-runner.md diff --git a/docs/guides/build-it-yourself/5-achieve-compliance/0-intro/_category_.json b/docs/guides/build-it-yourself/pipelines/intro/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/5-achieve-compliance/0-intro/_category_.json rename to docs/guides/build-it-yourself/pipelines/intro/_category_.json diff --git a/docs/guides/build-it-yourself/3-pipelines/0-intro/1-what-is-continuous-integration-and-continuous-delivery.md b/docs/guides/build-it-yourself/pipelines/intro/what-is-continuous-integration-and-continuous-delivery.md similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/0-intro/1-what-is-continuous-integration-and-continuous-delivery.md rename to docs/guides/build-it-yourself/pipelines/intro/what-is-continuous-integration-and-continuous-delivery.md diff --git a/docs/guides/build-it-yourself/3-pipelines/0-intro/2-what-this-guide-will-not-cover.md b/docs/guides/build-it-yourself/pipelines/intro/what-this-guide-will-not-cover.md similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/0-intro/2-what-this-guide-will-not-cover.md rename to docs/guides/build-it-yourself/pipelines/intro/what-this-guide-will-not-cover.md diff --git a/docs/guides/build-it-yourself/3-pipelines/0-intro/0-what-youll-learn-in-this-guide.md b/docs/guides/build-it-yourself/pipelines/intro/what-youll-learn-in-this-guide.md similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/0-intro/0-what-youll-learn-in-this-guide.md rename to docs/guides/build-it-yourself/pipelines/intro/what-youll-learn-in-this-guide.md diff --git a/docs/guides/build-it-yourself/3-pipelines/4-next-steps.md b/docs/guides/build-it-yourself/pipelines/next-steps.md similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/4-next-steps.md rename to docs/guides/build-it-yourself/pipelines/next-steps.md diff --git a/docs/guides/build-it-yourself/5-achieve-compliance/2-production-grade-design/_category_.json b/docs/guides/build-it-yourself/pipelines/production-grade-design/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/5-achieve-compliance/2-production-grade-design/_category_.json rename to docs/guides/build-it-yourself/pipelines/production-grade-design/_category_.json diff --git a/docs/guides/build-it-yourself/3-pipelines/2-production-grade-design/0-intro.md b/docs/guides/build-it-yourself/pipelines/production-grade-design/intro.md similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/2-production-grade-design/0-intro.md rename to docs/guides/build-it-yourself/pipelines/production-grade-design/intro.md diff --git a/docs/guides/build-it-yourself/3-pipelines/2-production-grade-design/3-limit-triggers-for-deploy-server.md b/docs/guides/build-it-yourself/pipelines/production-grade-design/limit-triggers-for-deploy-server.md similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/2-production-grade-design/3-limit-triggers-for-deploy-server.md rename to docs/guides/build-it-yourself/pipelines/production-grade-design/limit-triggers-for-deploy-server.md diff --git a/docs/guides/build-it-yourself/3-pipelines/2-production-grade-design/7-lock-down-vcs-systems.md b/docs/guides/build-it-yourself/pipelines/production-grade-design/lock-down-vcs-systems.md similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/2-production-grade-design/7-lock-down-vcs-systems.md rename to docs/guides/build-it-yourself/pipelines/production-grade-design/lock-down-vcs-systems.md diff --git a/docs/guides/build-it-yourself/3-pipelines/2-production-grade-design/2-options-for-deploy-server.md b/docs/guides/build-it-yourself/pipelines/production-grade-design/options-for-deploy-server.md similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/2-production-grade-design/2-options-for-deploy-server.md rename to docs/guides/build-it-yourself/pipelines/production-grade-design/options-for-deploy-server.md diff --git a/docs/guides/build-it-yourself/3-pipelines/2-production-grade-design/9-summary-of-deployment-sequence.md b/docs/guides/build-it-yourself/pipelines/production-grade-design/summary-of-deployment-sequence.md similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/2-production-grade-design/9-summary-of-deployment-sequence.md rename to docs/guides/build-it-yourself/pipelines/production-grade-design/summary-of-deployment-sequence.md diff --git a/docs/guides/build-it-yourself/3-pipelines/2-production-grade-design/8-summary-of-mitigations.md b/docs/guides/build-it-yourself/pipelines/production-grade-design/summary-of-mitigations.md similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/2-production-grade-design/8-summary-of-mitigations.md rename to docs/guides/build-it-yourself/pipelines/production-grade-design/summary-of-mitigations.md diff --git a/docs/guides/build-it-yourself/3-pipelines/2-production-grade-design/4-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 similarity index 65% rename from docs/guides/build-it-yourself/3-pipelines/2-production-grade-design/4-use-a-vpc-to-lock-down-deploy-server.md rename to docs/guides/build-it-yourself/pipelines/production-grade-design/use-a-vpc-to-lock-down-deploy-server.md index 34aac8c046..cbc876d220 100644 --- a/docs/guides/build-it-yourself/3-pipelines/2-production-grade-design/4-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 @@ -1,11 +1,11 @@ # Use a VPC to lock down deploy server Run your infrastructure deployment workloads in a [Virtual Private Cloud (VPC)](https://aws.amazon.com/vpc/) to isolate -the workloads in a restricted network topology (see [How to deploy a production-grade VPC on AWS](../../4-vpc/0-intro/0-what-youll-learn-in-this-guide.md) for more information on VPCs). Configure it to run all workloads in private +the workloads in a restricted network topology (see [How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) for more information on VPCs). Configure it to run all workloads in private subnets that are not publicly accessible. Make sure to block all inbound internet access and consider blocking all outbound access except for the minimum required (e.g, allow access to AWS APIs). diff --git a/docs/guides/build-it-yourself/3-pipelines/2-production-grade-design/6-use-approval-flows.md b/docs/guides/build-it-yourself/pipelines/production-grade-design/use-approval-flows.md similarity index 84% rename from docs/guides/build-it-yourself/3-pipelines/2-production-grade-design/6-use-approval-flows.md rename to docs/guides/build-it-yourself/pipelines/production-grade-design/use-approval-flows.md index 198bf41e4c..40f6e5d505 100644 --- a/docs/guides/build-it-yourself/3-pipelines/2-production-grade-design/6-use-approval-flows.md +++ b/docs/guides/build-it-yourself/pipelines/production-grade-design/use-approval-flows.md @@ -1,6 +1,6 @@ # Use approval flows -It is important that human review is baked into each deployment. As covered in [CI/CD workflows](../1-core-concepts/3-ci-cd-workflows.md), it is difficult to +It is important that human review is baked into each deployment. As covered in [CI/CD workflows](../core-concepts/ci-cd-workflows.md), it is difficult to build an automated test suite that builds enough confidence in your infrastructure code to do the right thing. This is important, as failed infrastructure deployments could be catastrophic to your business, and there is no concept of rollback with infrastructure deployment tools. This means that you will almost always want to have some form of approval @@ -12,5 +12,5 @@ can approve the workflow. diff --git a/docs/guides/build-it-yourself/3-pipelines/2-production-grade-design/1-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 similarity index 92% rename from docs/guides/build-it-yourself/3-pipelines/2-production-grade-design/1-use-generic-ci-cd-platforms-as-a-workflow-engine-but-run-infrastructure-deployments-from-within-your-account.md rename to 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 6d4fd8f89a..11bf37ac47 100644 --- a/docs/guides/build-it-yourself/3-pipelines/2-production-grade-design/1-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 @@ -1,6 +1,6 @@ # Use generic CI/CD platforms as a workflow engine but run infrastructure deployments from within your account -Given the limitations and tradeoffs of the various platforms we covered in [CI/CD platforms](../1-core-concepts/5-ci-cd-platforms.md), we don’t recommend +Given the limitations and tradeoffs of the various platforms we covered in [CI/CD platforms](../core-concepts/ci-cd-platforms.md), we don’t recommend relying on a single platform for implementing the entire workflow. Instead, we recommend a hybrid solution that takes advantage of the strengths of each platform, and cover the weaknesses. The design looks as follows: @@ -28,5 +28,5 @@ builds on existing code, but they don’t get arbitrary admin access. diff --git a/docs/guides/build-it-yourself/3-pipelines/2-production-grade-design/5-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 similarity index 100% rename from docs/guides/build-it-yourself/3-pipelines/2-production-grade-design/5-use-minimal-iam-permissions-for-a-deployment.md rename to docs/guides/build-it-yourself/pipelines/production-grade-design/use-minimal-iam-permissions-for-a-deployment.md diff --git a/docs/guides/build-it-yourself/4-vpc/_category_.json b/docs/guides/build-it-yourself/vpc/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/_category_.json rename to docs/guides/build-it-yourself/vpc/_category_.json diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/_category_.json b/docs/guides/build-it-yourself/vpc/core-concepts/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/1-core-concepts/_category_.json rename to docs/guides/build-it-yourself/vpc/core-concepts/_category_.json diff --git a/docs/guides/build-it-yourself/4-vpc/1-core-concepts/2-cidr-notation.md b/docs/guides/build-it-yourself/vpc/core-concepts/cidr-notation.md similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/1-core-concepts/2-cidr-notation.md rename to docs/guides/build-it-yourself/vpc/core-concepts/cidr-notation.md diff --git a/docs/guides/build-it-yourself/4-vpc/1-core-concepts/0-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 similarity index 93% rename from docs/guides/build-it-yourself/4-vpc/1-core-concepts/0-default-vp-cs-and-custom-vp-cs.md rename to docs/guides/build-it-yourself/vpc/core-concepts/default-vp-cs-and-custom-vp-cs.md index a2265d1dfc..a5ccffd23b 100644 --- a/docs/guides/build-it-yourself/4-vpc/1-core-concepts/0-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 @@ -47,12 +47,12 @@ you’re typically better off creating a new, custom VPC. #### Custom VPCs -For any production use cases, you should create a _custom VPC_. In the [Production-grade design](../2-production-grade-design/0-intro.md) section, we’ll go +For any production use cases, you should create a _custom VPC_. In the [Production-grade design](../production-grade-design/intro.md) section, we’ll go over how to configure a VPC with the kind of security, scalability, and high availability you need in production.
diff --git a/docs/guides/build-it-yourself/4-vpc/1-core-concepts/5-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 similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/1-core-concepts/5-internet-gateways-public-subnets-and-private-subnets.md rename to docs/guides/build-it-yourself/vpc/core-concepts/internet-gateways-public-subnets-and-private-subnets.md diff --git a/docs/guides/build-it-yourself/4-vpc/1-core-concepts/6-nat-gateways.md b/docs/guides/build-it-yourself/vpc/core-concepts/nat-gateways.md similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/1-core-concepts/6-nat-gateways.md rename to docs/guides/build-it-yourself/vpc/core-concepts/nat-gateways.md diff --git a/docs/guides/build-it-yourself/4-vpc/1-core-concepts/8-network-ac-ls.md b/docs/guides/build-it-yourself/vpc/core-concepts/network-ac-ls.md similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/1-core-concepts/8-network-ac-ls.md rename to docs/guides/build-it-yourself/vpc/core-concepts/network-ac-ls.md diff --git a/docs/guides/build-it-yourself/4-vpc/1-core-concepts/11-regions-and-availability-zones.md b/docs/guides/build-it-yourself/vpc/core-concepts/regions-and-availability-zones.md similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/1-core-concepts/11-regions-and-availability-zones.md rename to docs/guides/build-it-yourself/vpc/core-concepts/regions-and-availability-zones.md diff --git a/docs/guides/build-it-yourself/4-vpc/1-core-concepts/4-route-tables.md b/docs/guides/build-it-yourself/vpc/core-concepts/route-tables.md similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/1-core-concepts/4-route-tables.md rename to docs/guides/build-it-yourself/vpc/core-concepts/route-tables.md diff --git a/docs/guides/build-it-yourself/4-vpc/1-core-concepts/7-security-groups.md b/docs/guides/build-it-yourself/vpc/core-concepts/security-groups.md similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/1-core-concepts/7-security-groups.md rename to docs/guides/build-it-yourself/vpc/core-concepts/security-groups.md diff --git a/docs/guides/build-it-yourself/4-vpc/1-core-concepts/3-subnets.md b/docs/guides/build-it-yourself/vpc/core-concepts/subnets.md similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/1-core-concepts/3-subnets.md rename to docs/guides/build-it-yourself/vpc/core-concepts/subnets.md diff --git a/docs/guides/build-it-yourself/4-vpc/1-core-concepts/10-vpc-endpoints.md b/docs/guides/build-it-yourself/vpc/core-concepts/vpc-endpoints.md similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/1-core-concepts/10-vpc-endpoints.md rename to docs/guides/build-it-yourself/vpc/core-concepts/vpc-endpoints.md diff --git a/docs/guides/build-it-yourself/4-vpc/1-core-concepts/1-vpc-ip-addresses.md b/docs/guides/build-it-yourself/vpc/core-concepts/vpc-ip-addresses.md similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/1-core-concepts/1-vpc-ip-addresses.md rename to docs/guides/build-it-yourself/vpc/core-concepts/vpc-ip-addresses.md diff --git a/docs/guides/build-it-yourself/4-vpc/1-core-concepts/9-vpc-peering.md b/docs/guides/build-it-yourself/vpc/core-concepts/vpc-peering.md similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/1-core-concepts/9-vpc-peering.md rename to docs/guides/build-it-yourself/vpc/core-concepts/vpc-peering.md diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/_category_.json b/docs/guides/build-it-yourself/vpc/deployment-walkthrough/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/3-deployment-walkthrough/_category_.json rename to docs/guides/build-it-yourself/vpc/deployment-walkthrough/_category_.json diff --git a/docs/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/4-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 similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/4-clean-up-default-vp-cs-and-security-groups.md rename to docs/guides/build-it-yourself/vpc/deployment-walkthrough/clean-up-default-vp-cs-and-security-groups.md diff --git a/docs/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/3-deploy-a-bastion-host.md b/docs/guides/build-it-yourself/vpc/deployment-walkthrough/deploy-a-bastion-host.md similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/3-deploy-a-bastion-host.md rename to docs/guides/build-it-yourself/vpc/deployment-walkthrough/deploy-a-bastion-host.md diff --git a/docs/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/1-deploy-a-management-vpc.md b/docs/guides/build-it-yourself/vpc/deployment-walkthrough/deploy-a-management-vpc.md similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/1-deploy-a-management-vpc.md rename to docs/guides/build-it-yourself/vpc/deployment-walkthrough/deploy-a-management-vpc.md diff --git a/docs/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/2-deploy-application-vp-cs.md b/docs/guides/build-it-yourself/vpc/deployment-walkthrough/deploy-application-vp-cs.md similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/2-deploy-application-vp-cs.md rename to docs/guides/build-it-yourself/vpc/deployment-walkthrough/deploy-application-vp-cs.md diff --git a/docs/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/0-pre-requisites.md b/docs/guides/build-it-yourself/vpc/deployment-walkthrough/pre-requisites.md similarity index 88% rename from docs/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/0-pre-requisites.md rename to docs/guides/build-it-yourself/vpc/deployment-walkthrough/pre-requisites.md index a68c253d5c..ac572fad16 100644 --- a/docs/guides/build-it-yourself/4-vpc/3-deployment-walkthrough/0-pre-requisites.md +++ b/docs/guides/build-it-yourself/vpc/deployment-walkthrough/pre-requisites.md @@ -34,7 +34,7 @@ our [Introduction to Gruntwork](/docs/intro/overview/intro-to-gruntwork) #### AWS accounts This guide deploys infrastructure into one or more AWS accounts. Check out the -[Production Grade AWS Account Structure](../../2-landing-zone/0-intro/0-what-youll-learn-in-this-guide.md) guide for instructions. +[Production Grade AWS Account Structure](../../landing-zone/intro/what-youll-learn-in-this-guide.md) guide for instructions. You will also need to be able to authenticate to these accounts on the CLI: check out [A Comprehensive Guide to Authenticating to AWS on the Command Line](https://blog.gruntwork.io/a-comprehensive-guide-to-authenticating-to-aws-on-the-command-line-63656a686799) for instructions. @@ -43,5 +43,5 @@ for instructions. diff --git a/docs/guides/build-it-yourself/5-kubernetes-cluster/0-intro/_category_.json b/docs/guides/build-it-yourself/vpc/intro/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/0-intro/_category_.json rename to docs/guides/build-it-yourself/vpc/intro/_category_.json diff --git a/docs/guides/build-it-yourself/4-vpc/0-intro/1-what-is-a-vpc.md b/docs/guides/build-it-yourself/vpc/intro/what-is-a-vpc.md similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/0-intro/1-what-is-a-vpc.md rename to docs/guides/build-it-yourself/vpc/intro/what-is-a-vpc.md diff --git a/docs/guides/build-it-yourself/4-vpc/0-intro/0-what-youll-learn-in-this-guide.md b/docs/guides/build-it-yourself/vpc/intro/what-youll-learn-in-this-guide.md similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/0-intro/0-what-youll-learn-in-this-guide.md rename to docs/guides/build-it-yourself/vpc/intro/what-youll-learn-in-this-guide.md diff --git a/docs/guides/build-it-yourself/4-vpc/4-next-steps.md b/docs/guides/build-it-yourself/vpc/next-steps.md similarity index 83% rename from docs/guides/build-it-yourself/4-vpc/4-next-steps.md rename to docs/guides/build-it-yourself/vpc/next-steps.md index 67aca63a9f..0203fdc41e 100644 --- a/docs/guides/build-it-yourself/4-vpc/4-next-steps.md +++ b/docs/guides/build-it-yourself/vpc/next-steps.md @@ -4,7 +4,7 @@ Now that you have your management and application VPCs deployed, you can start b on top of them! Typically, the best next step is to deploy a cluster of servers for running your applications by using one of the following guides: -- [How to deploy a production-grade Kubernetes cluster on AWS](../5-kubernetes-cluster/0-intro/0-what-youll-learn-in-this-guide.md) +- [How to deploy a production-grade Kubernetes cluster on AWS](../kubernetes-cluster/intro/what-youll-learn-in-this-guide.md) - `How to deploy a production grade ECS cluster on AWS` _(coming soon!)_ - `How to deploy a production grade Nomad cluster on AWS` _(coming soon!)_ - `How to deploy a production grade Auto Scaling Group on AWS` _(coming soon!)_ @@ -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/5-kubernetes-cluster/2-production-grade-design/_category_.json b/docs/guides/build-it-yourself/vpc/production-grade-design/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/5-kubernetes-cluster/2-production-grade-design/_category_.json rename to docs/guides/build-it-yourself/vpc/production-grade-design/_category_.json diff --git a/docs/guides/build-it-yourself/4-vpc/2-production-grade-design/7-bastion-host.md b/docs/guides/build-it-yourself/vpc/production-grade-design/bastion-host.md similarity index 92% rename from docs/guides/build-it-yourself/4-vpc/2-production-grade-design/7-bastion-host.md rename to docs/guides/build-it-yourself/vpc/production-grade-design/bastion-host.md index 445c6a8726..e72c76d0a8 100644 --- a/docs/guides/build-it-yourself/4-vpc/2-production-grade-design/7-bastion-host.md +++ b/docs/guides/build-it-yourself/vpc/production-grade-design/bastion-host.md @@ -13,12 +13,12 @@ the server, lock down all ports (except SSH and/or VPN), rebuild and redeploy th the `How to deploy a production-grade bastion host on AWS` guide _(coming soon!)_ for full details on bastion hosts. Other solutions that can work with resources in private subnets include -[EC2 Instance Connect](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Connect-using-EC2-Instance-Connect.html), +[EC2 Instance Connect](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Connect-using-ECInstance-Connect.html), which can allow you to SSH to EC2 Instances via a browser-based SSH client in the Amazon EC2 Console, and [AWS Systems Manager Sessions](https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager.html), which allow you to manage and connect to EC2 Instances via a custom protocol managed by AWS. diff --git a/docs/guides/build-it-yourself/4-vpc/2-production-grade-design/1-defense-in-depth.md b/docs/guides/build-it-yourself/vpc/production-grade-design/defense-in-depth.md similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/2-production-grade-design/1-defense-in-depth.md rename to docs/guides/build-it-yourself/vpc/production-grade-design/defense-in-depth.md diff --git a/docs/guides/build-it-yourself/4-vpc/2-production-grade-design/6-internet-gateways-and-nat-gateways.md b/docs/guides/build-it-yourself/vpc/production-grade-design/internet-gateways-and-nat-gateways.md similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/2-production-grade-design/6-internet-gateways-and-nat-gateways.md rename to docs/guides/build-it-yourself/vpc/production-grade-design/internet-gateways-and-nat-gateways.md diff --git a/docs/guides/build-it-yourself/4-vpc/2-production-grade-design/0-intro.md b/docs/guides/build-it-yourself/vpc/production-grade-design/intro.md similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/2-production-grade-design/0-intro.md rename to docs/guides/build-it-yourself/vpc/production-grade-design/intro.md diff --git a/docs/guides/build-it-yourself/4-vpc/2-production-grade-design/2-multiple-aws-accounts.md b/docs/guides/build-it-yourself/vpc/production-grade-design/multiple-aws-accounts.md similarity index 88% rename from docs/guides/build-it-yourself/4-vpc/2-production-grade-design/2-multiple-aws-accounts.md rename to docs/guides/build-it-yourself/vpc/production-grade-design/multiple-aws-accounts.md index 384d87a359..b878b7335d 100644 --- a/docs/guides/build-it-yourself/4-vpc/2-production-grade-design/2-multiple-aws-accounts.md +++ b/docs/guides/build-it-yourself/vpc/production-grade-design/multiple-aws-accounts.md @@ -11,10 +11,10 @@ change something in prod rather than pre-prod). Therefore, your best bet is to put pre-production environments and production environments in completely separate AWS accounts. This makes it easy to, for example, grant relatively lax permissions in pre-prod environments, but very -strict permissions in production. Check out the [Production Grade AWS Account Structure](../../2-landing-zone/0-intro/0-what-youll-learn-in-this-guide.md) +strict permissions in production. Check out the [Production Grade AWS Account Structure](../../landing-zone/intro/what-youll-learn-in-this-guide.md) guide for instructions. diff --git a/docs/guides/build-it-yourself/4-vpc/2-production-grade-design/4-multiple-subnet-tiers.md b/docs/guides/build-it-yourself/vpc/production-grade-design/multiple-subnet-tiers.md similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/2-production-grade-design/4-multiple-subnet-tiers.md rename to docs/guides/build-it-yourself/vpc/production-grade-design/multiple-subnet-tiers.md diff --git a/docs/guides/build-it-yourself/4-vpc/2-production-grade-design/3-multiple-vp-cs.md b/docs/guides/build-it-yourself/vpc/production-grade-design/multiple-vp-cs.md similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/2-production-grade-design/3-multiple-vp-cs.md rename to docs/guides/build-it-yourself/vpc/production-grade-design/multiple-vp-cs.md diff --git a/docs/guides/build-it-yourself/4-vpc/2-production-grade-design/5-security-groups-and-nac-ls.md b/docs/guides/build-it-yourself/vpc/production-grade-design/security-groups-and-nac-ls.md similarity index 100% rename from docs/guides/build-it-yourself/4-vpc/2-production-grade-design/5-security-groups-and-nac-ls.md rename to docs/guides/build-it-yourself/vpc/production-grade-design/security-groups-and-nac-ls.md diff --git a/docs/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/_category_.json b/docs/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/_category_.json deleted file mode 100644 index cd05330845..0000000000 --- a/docs/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ -"label": "Deployment walkthrough" -} \ No newline at end of file diff --git a/docs/guides/stay-up-to-date/1-cis/_category_.json b/docs/guides/stay-up-to-date/cis/_category_.json similarity index 100% rename from docs/guides/stay-up-to-date/1-cis/_category_.json rename to docs/guides/stay-up-to-date/cis/_category_.json diff --git a/docs/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/_category_.json b/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/_category_.json similarity index 100% rename from docs/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/_category_.json rename to docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/_category_.json diff --git a/docs/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/1-core-concepts.md b/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/core-concepts.md similarity index 100% rename from docs/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/1-core-concepts.md rename to docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/core-concepts.md diff --git a/docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/_category_.json b/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/_category_.json similarity index 100% rename from docs/guides/build-it-yourself/6-achieve-compliance/3-deployment-walkthrough/_category_.json rename to docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/_category_.json diff --git a/docs/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/0-step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md b/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md similarity index 100% rename from docs/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/0-step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md rename to docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md diff --git a/docs/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/1-step-2-manual-steps.md b/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/step-2-manual-steps.md similarity index 100% rename from docs/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/1-step-2-manual-steps.md rename to docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/step-2-manual-steps.md diff --git a/docs/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/2-step-3-deploy-new-modules.md b/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/step-3-deploy-new-modules.md similarity index 91% rename from docs/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/2-step-3-deploy-new-modules.md rename to docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/step-3-deploy-new-modules.md index 28f1e1efce..914e395266 100644 --- a/docs/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/2-deployment-walkthrough/2-step-3-deploy-new-modules.md +++ b/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/step-3-deploy-new-modules.md @@ -11,7 +11,7 @@ accidentally to a resource such as AWS Elastic Load Balancer (ELB), which can da achieve this recommendation, check out the [example](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/tree/v0.10.0/examples/cleanup-expired-certs/terraform) of the ready-made `cleanup-expired-certs` module. For the code examples of deploying this module, see the -[relevant section](../../../../build-it-yourself/6-achieve-compliance/2-production-grade-design/1-identity-and-access-management.md#cleanup-expired-ssl-tls-certificates) +[relevant section](../../../../build-it-yourself/achieve-compliance/production-grade-design/identity-and-access-management.md#cleanup-expired-ssl-tls-certificates) of our "How to achieve compliance with the CIS AWS Foundations Benchmark" guide. ## 2. Deploy IAM Access Analyzer module (recommendation 1.21) @@ -31,7 +31,7 @@ The IAM Access Analyzer will scan only within the AWS Account or Organization bo To help you achieve CIS AWS v1.3 compliance, you can find examples of how to use the ready-made module as part of the `landingzone` module in the `terraform-aws-service-catalog` repository [v0.15.4](https://github.com/gruntwork-io/terraform-aws-service-catalog/releases/tag/v0.15.4), and specifically the `account-baseline-root` and `account-baseline-security` [examples](https://github.com/gruntwork-io/terraform-aws-service-catalog/tree/v0.15.4/examples/for-learning-and-testing/landingzone). For the code examples of deploying this module, see the -[relevant section](../../../../build-it-yourself/6-achieve-compliance/2-production-grade-design/1-identity-and-access-management.md#iam-access-analyzer) +[relevant section](../../../../build-it-yourself/achieve-compliance/production-grade-design/identity-and-access-management.md#iam-access-analyzer) of our "How to achieve compliance with the CIS AWS Foundations Benchmark" guide. ## 3. Deploy the ebs-encryption-multi-region module (recommendation 2.2.1) @@ -42,7 +42,7 @@ a module that configures volume encryption by default in all enabled regions. Ch configure AWS EBS encryption in all allowed regions of an AWS Account. For the code examples of deploying this module, see the -[relevant section](../../../../build-it-yourself/6-achieve-compliance/2-production-grade-design/2-storage.md#configure-ebs-encryption) +[relevant section](../../../../build-it-yourself/achieve-compliance/production-grade-design/storage.md#configure-ebs-encryption) of our "Achieve Compliance With the CIS AWS Foundations Benchmark" guide. ## 4. Deploy the vpc-app-network-acl and vpc-mgmt-network-acl modules (recommendation 5.1) @@ -72,7 +72,7 @@ module "vpc_app_network_acls" { ``` For the code examples of deploying this module, see the -[relevant section](../../../../build-it-yourself/6-achieve-compliance/2-production-grade-design/5-networking.md) +[relevant section](../../../../build-it-yourself/achieve-compliance/production-grade-design/networking.md) of our "How to achieve compliance with the CIS AWS Foundations Benchmark" guide. ### 4.1 Network ACL Rules Quota limit @@ -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/1-cis/1-how-to-update-to-cis-13/0-intro.md b/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/intro.md similarity index 62% rename from docs/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/0-intro.md rename to docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/intro.md index e14885c0e9..a5916657bb 100644 --- a/docs/guides/stay-up-to-date/1-cis/1-how-to-update-to-cis-13/0-intro.md +++ b/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/intro.md @@ -7,25 +7,25 @@ pagination_label: Update to CIS AWS Foundations Benchmark 1.3.0 This guide will walk you through how to update from version 1.2.0 to version 1.3.0 of the CIS AWS Foundations Benchmark. If your infrastructure is already compliant with the Benchmark's version 1.2.0, and you are looking to upgrade to v1.3.0, this guide is for you. If you are starting to work on compliance with this benchmark from scratch, check out our -[How to achieve compliance with the CIS AWS Foundations Benchmark](../../../build-it-yourself/6-achieve-compliance/0-intro/0-what-youll-learn-in-this-guide.md) guide instead. +[How to achieve compliance with the CIS AWS Foundations Benchmark](../../../build-it-yourself/achieve-compliance/intro/what-youll-learn-in-this-guide.md) guide instead. This guide consists of two main sections:
-#### [Core Concepts](./1-core-concepts.md) +#### [Core Concepts](./core-concepts.md) An overview of the CIS AWS Foundations Benchmark v1.3.0 and why it is important to update your code for compatibility. -#### [Deployment walkthrough](./2-deployment-walkthrough/0-step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md) +#### [Deployment walkthrough](./deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md) The steps you need to take to update your code to be compliant with CIS AWS v1.3.0. It includes a -[version compatibility table](./2-deployment-walkthrough/0-step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md#compatibility-table) you can use as a reference to know which Gruntwork Repo version +[version compatibility table](./deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md#compatibility-table) you can use as a reference to know which Gruntwork Repo version tag is compatible with CIS AWS v1.3.0, as well as the manuals step you need to perform to achieve said compliance.
diff --git a/docs/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/_category_.json b/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/_category_.json similarity index 100% rename from docs/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/_category_.json rename to docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/_category_.json diff --git a/docs/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/1-core-concepts.md b/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/core-concepts.md similarity index 86% rename from docs/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/1-core-concepts.md rename to docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/core-concepts.md index 2849400c37..2e77a6e9bd 100644 --- a/docs/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/1-core-concepts.md +++ b/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/core-concepts.md @@ -32,11 +32,11 @@ created a new module for Amazon Macie, and updated the Landing Zone modules so t include relevant configurations for the Amazon Macie service. The latter will satisfy the recommendation 2.1.4. To ensure compliance with version 1.4.0 of the CIS AWS Foundations Benchmark, you’ll need to follow all the -instructions in the [Deployment walkthrough](./2-deployment-walkthrough/0-step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md) section; precisely, follow Steps 1 and 2 to ensure that +instructions in the [Deployment walkthrough](./deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md) section; precisely, follow Steps 1 and 2 to ensure that the existing modules get updated to their CIS AWS v1.4.0 compliant versions and follow Step 3 to perform the necessary manual steps. diff --git a/docs/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/_category_.json b/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/_category_.json similarity index 100% rename from docs/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/_category_.json rename to docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/_category_.json diff --git a/docs/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/0-step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md b/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md similarity index 100% rename from docs/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/0-step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md rename to docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md diff --git a/docs/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/1-step-2-update-the-account-baseline-modules.md b/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/step-2-update-the-account-baseline-modules.md similarity index 86% rename from docs/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/1-step-2-update-the-account-baseline-modules.md rename to docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/step-2-update-the-account-baseline-modules.md index 3a0cdf1d87..6905cc05dd 100644 --- a/docs/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/1-step-2-update-the-account-baseline-modules.md +++ b/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/step-2-update-the-account-baseline-modules.md @@ -16,16 +16,16 @@ The account baseline modules had three breaking changes between versions v0.22.0 these migration steps before updating the module versions. - [v0.23.0](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/releases/tag/v0.23.0): Refactored the - SecurityHub module to remove a Python script that managed invitations between the AWS accounts. It’s necessary to run a - state migration to manage the invitations with Terraform. + SecurityHub module to remove a Python script that managed invitations between the AWS accounts. It’s necessary to run a + state migration to manage the invitations with Terraform. - [v0.24.0](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/releases/tag/v0.24.0): This release introduces MFA Delete. You will need to follow the migration guide to ensure all S3 buckets are properly secured. Note: It is unlikely you will need to perform this step on the AWS root account as they typically don’t contain S3 buckets. Please ensure you migrate all other AWS accounts. - [v0.25.0](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/releases/tag/v0.25.0): Update the codebase - to a new multi-region approach. In [v0.51.0](https://github.com/gruntwork-io/terraform-aws-security/releases/tag/v0.51.0) of - `terraform-aws-security`, we refactored how we build multi-region modules—that - is, those modules that deploy resources across every single AWS region, such as `aws-config-multi-region`—to no longer - create nested provider blocks, and instead, have users pass in providers via the providers map. + to a new multi-region approach. In [v0.51.0](https://github.com/gruntwork-io/terraform-aws-security/releases/tag/v0.51.0) of + `terraform-aws-security`, we refactored how we build multi-region modules—that + is, those modules that deploy resources across every single AWS region, such as `aws-config-multi-region`—to no longer + create nested provider blocks, and instead, have users pass in providers via the providers map. Additionally, earlier versions of the account baseline modules did not set the following variables, so please ensure that they exist. Here is [an example](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/blob/v0.27.0/examples/for-production/infrastructure-live/logs/_global/account-baseline/terragrunt.hcl#L281) of what you might set the values to for the prod account. @@ -47,7 +47,7 @@ git::git@github.com:gruntwork-io/terraform-aws-cis-service-catalog.git//modules/ ``` Now execute Terraform/Terragrunt `apply`. It should take approximately ~30 minutes to apply the account baseline -modules. If you encounter any issues then please check out the [Known Issues](./2-step-3-manual-steps.md#known-issues) section. +modules. If you encounter any issues then please check out the [Known Issues](./step-3-manual-steps.md#known-issues) section. :::info @@ -64,7 +64,7 @@ in our CIS service catalog. :::info Manual steps required! After updating the account baseline modules as described below, make sure you perform the manual steps -outlined in the [Configure Amazon Macie (recommendation 2.1.4)](./2-step-3-manual-steps.md#configure-amazon-macie-recommendation-214) section. +outlined in the [Configure Amazon Macie (recommendation 2.1.4)](./step-3-manual-steps.md#configure-amazon-macie-recommendation-214) section. ::: @@ -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/1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/2-step-3-manual-steps.md b/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/step-3-manual-steps.md similarity index 93% rename from docs/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/2-step-3-manual-steps.md rename to docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/step-3-manual-steps.md index 3ed14e9655..178fc84900 100644 --- a/docs/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/2-deployment-walkthrough/2-step-3-manual-steps.md +++ b/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/step-3-manual-steps.md @@ -24,12 +24,12 @@ In order to enable MFA Delete, you need to: - [Configure MFA for the root user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html#id_root-user_manage_mfa) - Create a bucket with `mfa_delete=false`. - Using the root user, call the AWS CLI to enable MFA Delete. If you are using `aws-vault`, it is necessary to use the `--no-session` flag. - ```bash - aws s3api put-bucket-versioning --region \ - --bucket \ - --versioning-configuration Status=Enabled,MFADelete=Enabled \ - --mfa "arn:aws:iam:::mfa/root-account-mfa-device " - ``` + ```bash + aws s3api put-bucket-versioning --region \ + --bucket \ + --versioning-configuration Status=Enabled,MFADelete=Enabled \ + --mfa "arn:aws:iam:::mfa/root-account-mfa-device " + ``` - Set `mfa_delete=true` in your Terraform code - Remove any Lifecycle Rule that the bucket might contain (for the `aws-config-bucket` and `cloudtrail-bucket` modules, enabling `mfa_delete` will already disable the lifecycle rules). - Run `terraform apply`. @@ -39,7 +39,7 @@ We also created a script to help you enable MFA Delete in all buckets from a sin ### Using mfa-delete.sh -If you want to enable MFA Delete to _all_ your buckets at once, you can use the script at [terraform-aws-security/private-s3-bucket/mfa-delete-script](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/private-s3-bucket). You need to use the access keys for the root user and the root MFA code. +If you want to enable MFA Delete to _all_ your buckets at once, you can use the script at [terraform-aws-security/private-s3-bucket/mfa-delete-script](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/private-sbucket). You need to use the access keys for the root user and the root MFA code. Usage: @@ -88,7 +88,7 @@ so that it completely automates all the steps of configuring Amazon Macie, and n To set up Macie to analyze the desired S3 buckets, you’ll need to create a **Macie classification job**. Typically, you’ll want it to analyze all the buckets in the region. However, the terraform AWS provider does not support specifying all the buckets in a region - it requires that an explicit list of buckets be provided (see related bug [here](https://github.com/hashicorp/terraform-provider-aws/issues/20044)). Therefore, you’ll need to maintain an explicit list of buckets per region, namely in the variable `buckets_to_analyze`. Please read the -[documentation](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/blob/master/modules/security/macie/variables.tf#L21-L30) +[documentation](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/blob/master/modules/security/macie/variables.tf#L2L30) for this variable in order to understand how to structure the list of buckets per region. Once the above issue in the terraform AWS provider has been resolved, we will [update the Gruntwork macie module](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/issues/204) @@ -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/1-cis/0-how-to-update-to-cis-14/3-finally.md b/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/finally.md similarity index 100% rename from docs/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/3-finally.md rename to docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/finally.md diff --git a/docs/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/0-intro.md b/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/intro.md similarity index 52% rename from docs/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/0-intro.md rename to docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/intro.md index c0bcdf935a..5f889d9cd5 100644 --- a/docs/guides/stay-up-to-date/1-cis/0-how-to-update-to-cis-14/0-intro.md +++ b/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/intro.md @@ -8,14 +8,14 @@ This guide consists of two main sections:
-#### [Core Concepts](./1-core-concepts.md) +#### [Core Concepts](./core-concepts.md) An overview of the CIS AWS Foundations Benchmark v1.4.0 and why it is important to update your code for compatibility. -#### [Deployment walkthrough](./2-deployment-walkthrough/0-step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md) +#### [Deployment walkthrough](./deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md) The steps you need to take to update your code to be compliant with v1.4.0. It includes a -[version compatibility table](./2-deployment-walkthrough/0-step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md#compatibility-table) you can use as a reference to know which Gruntwork Repo version +[version compatibility table](./deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md#compatibility-table) you can use as a reference to know which Gruntwork Repo version tag is compatible along with the deployment steps you need to perform to achieve compliance with version 1.4.0 of the CIS AWS Foundations Benchmark. @@ -23,9 +23,9 @@ CIS AWS Foundations Benchmark. ## Previous versions of this guide -- [How to update to CIS AWS Foundations Benchmark v1.3.0](../1-how-to-update-to-cis-13/0-intro.md) +- [How to update to CIS AWS Foundations Benchmark v1.3.0](../how-to-update-to-cis-13/intro.md) diff --git a/docs/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/_category_.json b/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/_category_.json similarity index 100% rename from docs/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/_category_.json rename to docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/_category_.json diff --git a/docs/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/1-core-concepts.md b/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/core-concepts.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/1-core-concepts.md rename to docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/core-concepts.md diff --git a/docs/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/2-deployment-walkthrough/_category_.json b/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/_category_.json similarity index 100% rename from docs/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/2-deployment-walkthrough/_category_.json rename to docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/_category_.json diff --git a/docs/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/0-intro.md b/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/intro.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/0-intro.md rename to docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/intro.md diff --git a/docs/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/3-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 similarity index 100% rename from docs/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/3-optional-even-dryer-configuration.md rename to docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/optional-even-dryer-configuration.md diff --git a/docs/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/2-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 similarity index 96% rename from docs/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/2-refactoring-common-configurations-for-a-component.md rename to docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/refactoring-common-configurations-for-a-component.md index 8d002e99d0..b718886e61 100644 --- a/docs/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/2-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 @@ -4,13 +4,13 @@ The rest of this guide will cover how to identify and extract the common configu in your Reference Architecture. These steps can be used to refactor any component that is deployed in multiple accounts or environments in your Reference Architecture. -- [Step 1: Identify the component](#step-1-identify-the-component) +- [Step 1: Identify the component](#step-identify-the-component) -- [Step 2: Identify common configurations](#step-2-identify-common-configurations) +- [Step 2: Identify common configurations](#step-identify-common-configurations) -- [Step 3: Extract common configurations](#step-3-extract-common-configurations) +- [Step 3: Extract common configurations](#step-extract-common-configurations) -- [Step 4: Update child configurations](#step-4-update-child-configurations) +- [Step 4: Update child configurations](#step-1-update-child-configurations) ## Step 1: Identify the component @@ -53,7 +53,7 @@ Example inventory: - `security/us-west-2/mgmt/ecs-deploy-runner` -As mentioned in the [Background](../1-core-concepts.md#background), the changes will be isolated to Terragrunt configuration files (syntactic changes vs +As mentioned in the [Background](../core-concepts.md#background), the changes will be isolated to Terragrunt configuration files (syntactic changes vs semantic changes) and there will be no need to roll out the changes using `terraform`. Given that, the order in which the components are updated does not matter. You can update the components in whatever order you would like. @@ -297,5 +297,5 @@ moved to the common component configuration. diff --git a/docs/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/1-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 similarity index 100% rename from docs/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/1-update-to-the-service-catalog-based-reference-architecture.md rename to docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/update-to-the-service-catalog-based-reference-architecture.md diff --git a/docs/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/0-intro.md b/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/intro.md similarity index 84% rename from docs/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/0-intro.md rename to docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/intro.md index e6c6bdbba6..e4b02191a4 100644 --- a/docs/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/0-intro.md +++ b/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/intro.md @@ -18,15 +18,15 @@ configuration across your project. This guide consists of two main sections: -#### [Core Concepts](1-core-concepts.md) +#### [Core Concepts](core-concepts.md) An overview of the multi-include feature and how it helps to DRY up the Gruntwork Reference Architecture. -#### [Deployment Walkthrough](2-deployment-walkthrough/0-intro.md) +#### [Deployment Walkthrough](deployment-walkthrough/intro.md) The steps you need to take to update your code to use multi-include to avoid duplicating common configuration. diff --git a/docs/guides/stay-up-to-date/terraform/5-how-to-update-to-aws-provider-v3/_category_.json b/docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/_category_.json similarity index 100% rename from docs/guides/stay-up-to-date/terraform/5-how-to-update-to-aws-provider-v3/_category_.json rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/_category_.json diff --git a/docs/guides/stay-up-to-date/terraform/5-how-to-update-to-aws-provider-v3/1-core-concepts.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/core-concepts.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/5-how-to-update-to-aws-provider-v3/1-core-concepts.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/core-concepts.md diff --git a/docs/guides/stay-up-to-date/terraform/5-how-to-update-to-aws-provider-v3/2-deployment-walkthrough.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/deployment-walkthrough.md similarity index 97% rename from docs/guides/stay-up-to-date/terraform/5-how-to-update-to-aws-provider-v3/2-deployment-walkthrough.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/deployment-walkthrough.md index 93fa27f996..94de271712 100644 --- a/docs/guides/stay-up-to-date/terraform/5-how-to-update-to-aws-provider-v3/2-deployment-walkthrough.md +++ b/docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/deployment-walkthrough.md @@ -164,17 +164,17 @@ to update your snapshot of the Gruntwork Reference Architecture: #### CIS Reference Architecture Refer to the release notes for -[v0.0.1-20201021](https://github.com/gruntwork-io/cis-infrastructure-live-acme/releases/tag/v0.0.1-20201021) +[v0.0.1-20201021](https://github.com/gruntwork-io/cis-infrastructure-live-acme/releases/tag/v0.0.20201021) of the `cis-infrastructure-live-acme` repository for instructions on how to update the CIS components of the Reference Architecture to be compatible with AWS provider v3. For all other components, refer to the release notes for -[v0.0.1-20201021](https://github.com/gruntwork-io/infrastructure-modules-multi-account-acme/releases/tag/v0.0.1-20201021) +[v0.0.1-20201021](https://github.com/gruntwork-io/infrastructure-modules-multi-account-acme/releases/tag/v0.0.20201021) of the `infrastructure-modules-multi-account-acme` repository. #### Standard Reference Architecture Refer to the release notes for -[v0.0.1-20201021](https://github.com/gruntwork-io/infrastructure-modules-multi-account-acme/releases/tag/v0.0.1-20201021) +[v0.0.1-20201021](https://github.com/gruntwork-io/infrastructure-modules-multi-account-acme/releases/tag/v0.0.20201021) of the `infrastructure-modules-multi-account-acme` repository for instructions on how to update your components to be compatible with AWS provider v3. @@ -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/5-how-to-update-to-aws-provider-v3/0-intro.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/intro.md similarity index 79% rename from docs/guides/stay-up-to-date/terraform/5-how-to-update-to-aws-provider-v3/0-intro.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/intro.md index 08f777fc7f..754ecc7e84 100644 --- a/docs/guides/stay-up-to-date/terraform/5-how-to-update-to-aws-provider-v3/0-intro.md +++ b/docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/intro.md @@ -16,22 +16,22 @@ This guide consists of three main sections:
-#### [Core Concepts](1-core-concepts.md) +#### [Core Concepts](core-concepts.md) An overview of version 3 of the AWS provider and why it is important to update your code for compatibility. -#### [Deployment walkthrough](2-deployment-walkthrough.md) +#### [Deployment walkthrough](deployment-walkthrough.md) The steps you need to take to update your code relying on the Gruntwork Infrastructure as Code library and your version of the Gruntwork Reference Architecture with compatibility with AWS provider v3. Includes a [version -compatibility table](2-deployment-walkthrough.md#version-compatibility-table) you can use as a reference to know +compatibility table](deployment-walkthrough.md#version-compatibility-table) you can use as a reference to know which Gruntwork Repo version tag is compatible with AWS provider v3.
diff --git a/docs/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/_category_.json b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/_category_.json similarity index 100% rename from docs/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/_category_.json rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/_category_.json diff --git a/docs/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/1-core-concepts.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/core-concepts.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/1-core-concepts.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/core-concepts.md diff --git a/docs/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/2-deployment-walkthrough/_category_.json b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/deployment-walkthrough/_category_.json similarity index 100% rename from docs/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/2-deployment-walkthrough/_category_.json rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/deployment-walkthrough/_category_.json diff --git a/docs/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-15.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-15.md similarity index 65% rename from docs/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-15.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-15.md index 30b33886e2..b1aa7dade9 100644 --- a/docs/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-15.md +++ b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-15.md @@ -10,16 +10,16 @@ If you haven’t already, you need to: 0.15.0 or above first! 1. If you’re still on Terraform 0.11 or older, see our - [Terraform 0.12 upgrade guide](../../0-how-to-update-to-terraform-12/0-intro.md). + [Terraform 0.12 upgrade guide](../../how-to-update-to-terraform-12/intro.md). 2. If you’re still on Terraform 0.12, see our - [Terraform 0.13 upgrade guide](../../1-how-to-update-to-terraform-13/0-intro.md). + [Terraform 0.13 upgrade guide](../../how-to-update-to-terraform-13/intro.md). 3. If you’re still on Terraform 0.13, see our - [Terraform 0.14 upgrade guide](../../2-how-to-update-to-terraform-14/0-intro.md). + [Terraform 0.14 upgrade guide](../../how-to-update-to-terraform-14/intro.md). 4. If you’re still on Terraform 0.14, see our - [Terraform 0.15 upgrade guide](../../3-how-to-update-to-terraform-15/0-intro.md). + [Terraform 0.15 upgrade guide](../../how-to-update-to-terraform-15/intro.md). 2. Update all your Gruntwork modules to the latest versions just _before_ the TF 1.x versions in the compatibility table below. The upgrade will be much easier and less error prone if you keep the number of version jumps as small @@ -27,5 +27,5 @@ If you haven’t already, you need to: diff --git a/docs/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/2-deployment-walkthrough/1-step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/deployment-walkthrough/step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/2-deployment-walkthrough/1-step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/deployment-walkthrough/step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md diff --git a/docs/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/0-intro.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/intro.md similarity index 66% rename from docs/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/0-intro.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/intro.md index 258e672b55..05c585282c 100644 --- a/docs/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/0-intro.md +++ b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/intro.md @@ -18,20 +18,20 @@ This guide consists of two main sections:
-#### [Core Concepts](1-core-concepts.md) +#### [Core Concepts](core-concepts.md) An overview of Terraform 1.x. -#### [Deployment walkthrough](2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-15.md) +#### [Deployment walkthrough](deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-15.md) The steps you need to take to update your code relying on the Gruntwork Infrastructure as Code library to work with Terraform 1.x. Includes a -[version compatibility table](2-deployment-walkthrough/1-step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md#version-compatibility-table) you can use as a reference to know which Gruntwork Repo version +[version compatibility table](deployment-walkthrough/step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md#version-compatibility-table) you can use as a reference to know which Gruntwork Repo version tag is compatible with Terraform 0.15.
diff --git a/docs/guides/stay-up-to-date/terraform/0-how-to-update-to-terraform-12/_category_.json b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/_category_.json similarity index 100% rename from docs/guides/stay-up-to-date/terraform/0-how-to-update-to-terraform-12/_category_.json rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/_category_.json diff --git a/docs/guides/stay-up-to-date/terraform/0-how-to-update-to-terraform-12/1-deployment-walkthrough.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/deployment-walkthrough.md similarity index 98% rename from docs/guides/stay-up-to-date/terraform/0-how-to-update-to-terraform-12/1-deployment-walkthrough.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/deployment-walkthrough.md index 8bc2fa8afa..746ad52884 100644 --- a/docs/guides/stay-up-to-date/terraform/0-how-to-update-to-terraform-12/1-deployment-walkthrough.md +++ b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/deployment-walkthrough.md @@ -16,14 +16,14 @@ that prevent using your TF11 and older modules directly with TF12. For the safes going through the process of updating all your modules to use the new HCL2 syntax using the `terraform 0.12upgrade` tool that ships with TF12. -Before starting, read through the [Terraform 0.12 upgrade guide](https://www.terraform.io/upgrade-guides/0-12.html) so +Before starting, read through the [Terraform 0.12 upgrade guide](https://www.terraform.io/upgrade-guides/12.html) so you can learn about the types of changes you’ll have to make. Familiarity of the changes help with detecting errors and gotchas that the upgrade tool occasionally misses. Here is the rough process: -1. [Install and setup Terraform 0.12](#install-and-setup-terraform-0-12) -1. [Upgrade each module for 0.12 compatibility](#upgrade-each-module-for-0-12-compatibility) +1. [Install and setup Terraform 0.12](#install-and-setup-terraform-12) +1. [Upgrade each module for 0.12 compatibility](#upgrade-each-module-for-1compatibility) ### Install and setup Terraform 0.12 @@ -124,7 +124,7 @@ it is very easy to "start over", such as a sandbox or dev environment!** 1. Go into the folder with the Terraform module: `cd infrastructure-modules/networking/vpc-app` 1. Search your code for any references to Gruntwork modules. Update each module to the version number specified in the right-most column of the [Gruntwork module compatibility - table](1-version-compatibility-table.md) (or newer). For example, + table](version-compatibility-table.md) (or newer). For example, our example `infrastructure-modules/networking/vpc-app` [makes use of module-vpc](https://github.com/gruntwork-io/infrastructure-modules-multi-account-acme/blob/3158e4ebe83156f3917f8d168a6985678e30acfa/networking/vpc-app/main.tf#L38), which you’ll want to upgrade to `v0.6.0` (or newer). @@ -176,7 +176,7 @@ terragrunt `terraform.tfvars` files to the new syntax. Here is the rough process: -1. [Install and setup Terragrunt 0.19](#install-and-setup-terragrunt-0-19) +1. [Install and setup Terragrunt 0.19](#install-and-setup-terragrunt-19) 1. [Migrate terraform.tfvars to terragrunt.hcl](#migrate-terraform-tfvars-to-terragrunt-hcl) 1. [Switch common tfvars files to use yaml](#switch-common-tfvars-files-to-use-yaml) @@ -224,7 +224,7 @@ environment to test the changes you are making to that module (e.g [`infrastructure-live/dev/us-east-1/dev/vpc`](https://github.com/gruntwork-io/infrastructure-live-multi-account-acme/tree/dd6dce7f737f8c1bd32466b69e905b2bdd25db80/dev/us-east-1/dev/vpc)). The rough process should be: -1. Upgrade the module to TF12 syntax following the steps [listed above](#upgrade-each-module-for-0-12-compatibility). +1. Upgrade the module to TF12 syntax following the steps [listed above](#upgrade-each-module-for-1compatibility). 1. Update the live config for a pre-prod environment that deploys the module. 1. Run `terragrunt plan` to verify the changes. Use `--terragrunt-source` so you can point to the updated module (see the docs on [working locally](https://github.com/gruntwork-io/terragrunt#working-locally)). Carefully review to make @@ -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/0-how-to-update-to-terraform-12/0-intro.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/intro.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/0-how-to-update-to-terraform-12/0-intro.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/intro.md diff --git a/docs/guides/stay-up-to-date/terraform/0-how-to-update-to-terraform-12/1-version-compatibility-table.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/version-compatibility-table.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/0-how-to-update-to-terraform-12/1-version-compatibility-table.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/version-compatibility-table.md diff --git a/docs/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/_category_.json b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/_category_.json similarity index 100% rename from docs/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/_category_.json rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/_category_.json diff --git a/docs/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/1-core-concepts.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/core-concepts.md similarity index 82% rename from docs/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/1-core-concepts.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/core-concepts.md index a79274a928..b5b3ac6980 100644 --- a/docs/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/1-core-concepts.md +++ b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/core-concepts.md @@ -3,7 +3,7 @@ # Core Concepts -[Terraform 0.13 was released on August 10th, 2020](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-0-13). +[Terraform 0.13 was released on August 10th, 2020](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-13). Some of the major new features in 0.13 include: 1. The ability to use `count`, `for_each`, and `depends_on` with modules. @@ -12,7 +12,7 @@ Some of the major new features in 0.13 include: 3. Custom variable validation. -For more info, check out the [announcement blog post](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-0-13). +For more info, check out the [announcement blog post](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-13). 0.13 is a major new release for Terraform, which means it includes a number of backwards incompatible changes. We have gone through all the Terraform modules in the [Gruntwork @@ -21,5 +21,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/3-how-to-update-to-terraform-15/2-deployment-walkthrough/_category_.json b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/_category_.json similarity index 100% rename from docs/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/2-deployment-walkthrough/_category_.json rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/_category_.json diff --git a/docs/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-12.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12.md similarity index 79% rename from docs/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-12.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12.md index ffdf724e6f..27a3d4374f 100644 --- a/docs/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-12.md +++ b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12.md @@ -9,7 +9,7 @@ If you haven’t already, you need to: 1. Update your code to work with Terraform 0.12. Do NOT skip from, say, 0.11, straight to 0.13. You MUST update to 0.12.26 or above first! If you’re still on Terraform 0.11 or older, see our - [Terraform 0.12 upgrade guide](../../0-how-to-update-to-terraform-12/0-intro.md) for instructions. + [Terraform 0.12 upgrade guide](../../how-to-update-to-terraform-12/intro.md) for instructions. 2. Update all your Gruntwork modules to the latest versions just _before_ the TF 0.13 versions in the compatibility table below. The upgrade will be much easier and less error prone if you keep the number of version jumps as small @@ -17,5 +17,5 @@ If you haven’t already, you need to: diff --git a/docs/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/2-deployment-walkthrough/1-step-2-update-your-code-to-be-compatible-with-terraform-0-13.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-13.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/2-deployment-walkthrough/1-step-2-update-your-code-to-be-compatible-with-terraform-0-13.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-13.md diff --git a/docs/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/2-deployment-walkthrough/2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/2-deployment-walkthrough/2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md diff --git a/docs/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/2-deployment-walkthrough/3-updating-the-gruntwork-reference-architecture-to-terraform-0-13.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/updating-the-gruntwork-reference-architecture-to-terraform-0-13.md similarity index 90% rename from docs/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/2-deployment-walkthrough/3-updating-the-gruntwork-reference-architecture-to-terraform-0-13.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/updating-the-gruntwork-reference-architecture-to-terraform-0-13.md index 297a0b6afc..b09dceb146 100644 --- a/docs/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/2-deployment-walkthrough/3-updating-the-gruntwork-reference-architecture-to-terraform-0-13.md +++ b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/updating-the-gruntwork-reference-architecture-to-terraform-0-13.md @@ -10,7 +10,7 @@ the infrastructure code for deploying the Reference Architecture. You will need to update the relevant code in `infrastructure-modules` to use a compatible version of the Gruntwork Infrastructure as Code Library, as per [the compatibility -table](2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md#version-compatibility-table) +table](step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md#version-compatibility-table) above. To help guide you through the upgrade process, we have updated the Acme @@ -40,5 +40,5 @@ refer to PRs in the Standard Reference Architecture section above. diff --git a/docs/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/0-intro.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/intro.md similarity index 61% rename from docs/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/0-intro.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/intro.md index 11b1fbe110..1fc8f9b1c6 100644 --- a/docs/guides/stay-up-to-date/terraform/1-how-to-update-to-terraform-13/0-intro.md +++ b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/intro.md @@ -7,7 +7,7 @@ pagination_label: Update to Terraform 13 This guide will walk you through how to update the [Gruntwork Reference Architecture](https://gruntwork.io/reference-architecture/) and any code that depends on the [Gruntwork Infrastructure as Code Library](https://gruntwork.io/infrastructure-as-code-library/) to -[Terraform 0.13](https://www.terraform.io/upgrade-guides/0-13.html). Terraform 0.13 introduces a number of new features +[Terraform 0.13](https://www.terraform.io/upgrade-guides/13.html). Terraform 0.13 introduces a number of new features and fixes, but it also has a number of backwards incompatibilities that have to be incorporated into your codebase. ## What you’ll learn in this guide @@ -16,20 +16,20 @@ This guide consists of two main sections:
-#### [Core Concepts](1-core-concepts.md) +#### [Core Concepts](core-concepts.md) An overview of Terraform 0.13 and why it is important to update your code for compatibility. -#### [Deployment walkthrough](2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-12.md) +#### [Deployment walkthrough](deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12.md) The steps you need to take to update your code relying on the Gruntwork Infrastructure as Code library and your version of the Gruntwork Reference Architecture to work with Terraform 0.13. Includes a -[version compatibility table](2-deployment-walkthrough/2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md#version-compatibility-table) you can use as a reference to know which Gruntwork Repo version +[version compatibility table](deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md#version-compatibility-table) you can use as a reference to know which Gruntwork Repo version tag is compatible with Terraform 0.13.
diff --git a/docs/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/_category_.json b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/_category_.json similarity index 100% rename from docs/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/_category_.json rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/_category_.json diff --git a/docs/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/1-core-concepts.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/core-concepts.md similarity index 87% rename from docs/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/1-core-concepts.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/core-concepts.md index 1282affe7d..70cb58428a 100644 --- a/docs/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/1-core-concepts.md +++ b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/core-concepts.md @@ -13,7 +13,7 @@ December 02, 2020](https://www.hashicorp.com/blog/announcing-hashicorp-terraform 3. A lock file for provider dependency versions. For more info, check out the -[announcement blog post](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-0-14-general-availability). +[announcement blog post](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-1general-availability). 0.14 is a major new release for Terraform, which means it includes some backwards incompatible changes. We have gone through all the Terraform modules in the [Gruntwork @@ -22,5 +22,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/4-how-to-update-to-terraform-1-x/2-deployment-walkthrough/_category_.json b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/_category_.json similarity index 100% rename from docs/guides/stay-up-to-date/terraform/4-how-to-update-to-terraform-1-x/2-deployment-walkthrough/_category_.json rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/_category_.json diff --git a/docs/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-13.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-13.md similarity index 79% rename from docs/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-13.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-13.md index c0007fafb6..779755568d 100644 --- a/docs/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-13.md +++ b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-13.md @@ -9,10 +9,10 @@ If you haven’t already, you need to: 1. Update your code to work with Terraform 0.13. Do NOT skip from, say, 0.11, straight to 0.14. You MUST update to 0.13.0 or above first! If you’re still on Terraform 0.11 or older, see our [Terraform 0.12 upgrade - guide](../../0-how-to-update-to-terraform-12/0-intro.md) for + guide](../../how-to-update-to-terraform-12/intro.md) for instructions. If you’re still on Terraform 0.12, see our [Terraform 0.13 upgrade - guide](../../1-how-to-update-to-terraform-13/0-intro.md). + guide](../../how-to-update-to-terraform-13/intro.md). 2. Update all your Gruntwork modules to the latest versions just _before_ the TF 0.14 versions in the compatibility table below. The upgrade will be much @@ -21,5 +21,5 @@ If you haven’t already, you need to: diff --git a/docs/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/2-deployment-walkthrough/1-step-2-update-your-code-to-be-compatible-with-terraform-0-14.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-14.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/2-deployment-walkthrough/1-step-2-update-your-code-to-be-compatible-with-terraform-0-14.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-14.md diff --git a/docs/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/2-deployment-walkthrough/2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/2-deployment-walkthrough/2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md diff --git a/docs/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/2-deployment-walkthrough/3-step-4-start-using-lock-files.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-4-start-using-lock-files.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/2-deployment-walkthrough/3-step-4-start-using-lock-files.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-4-start-using-lock-files.md diff --git a/docs/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/0-intro.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/intro.md similarity index 66% rename from docs/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/0-intro.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/intro.md index 8a8e823717..9d1c240d32 100644 --- a/docs/guides/stay-up-to-date/terraform/2-how-to-update-to-terraform-14/0-intro.md +++ b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/intro.md @@ -17,20 +17,20 @@ This guide consists of two main sections:
-#### [Core Concepts](1-core-concepts.md) +#### [Core Concepts](core-concepts.md) An overview of Terraform 0.14 and why it is important to update your code for compatibility. -#### [Deployment walkthrough](2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-13.md) +#### [Deployment walkthrough](deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-13.md) The steps you need to take to update your code relying on the Gruntwork Infrastructure as Code library to work with Terraform 0.14. Includes a -[version compatibility table](2-deployment-walkthrough/2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md#version-compatibility-table) you can use as a reference to know which Gruntwork Repo version +[version compatibility table](deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md#version-compatibility-table) you can use as a reference to know which Gruntwork Repo version tag is compatible with Terraform 0.14.
diff --git a/docs/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/_category_.json b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/_category_.json similarity index 100% rename from docs/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/_category_.json rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/_category_.json diff --git a/docs/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/1-core-concepts.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/core-concepts.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/1-core-concepts.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/core-concepts.md diff --git a/docs/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/_category_.json b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/_category_.json similarity index 100% rename from docs/guides/stay-up-to-date/terraform/6-how-to-dry-your-reference-architecture/2-deployment-walkthrough/_category_.json rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/_category_.json diff --git a/docs/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-14.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-14.md similarity index 68% rename from docs/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-14.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-14.md index de96453ed9..afd97aedae 100644 --- a/docs/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-14.md +++ b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-14.md @@ -10,13 +10,13 @@ If you haven’t already, you need to: 0.14.0 or above first! 1. If you’re still on Terraform 0.11 or older, see our - [Terraform 0.12 upgrade guide](../../0-how-to-update-to-terraform-12/0-intro.md). + [Terraform 0.12 upgrade guide](../../how-to-update-to-terraform-12/intro.md). 2. If you’re still on Terraform 0.12, see our - [Terraform 0.13 upgrade guide](../../1-how-to-update-to-terraform-13/0-intro.md). + [Terraform 0.13 upgrade guide](../../how-to-update-to-terraform-13/intro.md). 3. If you’re still on Terraform 0.13, see our - [Terraform 0.14 upgrade guide](../../2-how-to-update-to-terraform-14/0-intro.md). + [Terraform 0.14 upgrade guide](../../how-to-update-to-terraform-14/intro.md). 2. Update all your Gruntwork modules to the latest versions just _before_ the TF 0.15 versions in the compatibility table below. The upgrade will be much easier and less error prone if you keep the number of version jumps as small @@ -24,5 +24,5 @@ If you haven’t already, you need to: diff --git a/docs/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/2-deployment-walkthrough/1-step-2-update-your-code-to-be-compatible-with-terraform-0-15.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-15.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/2-deployment-walkthrough/1-step-2-update-your-code-to-be-compatible-with-terraform-0-15.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-15.md diff --git a/docs/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/2-deployment-walkthrough/2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/2-deployment-walkthrough/2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md diff --git a/docs/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/0-intro.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/intro.md similarity index 72% rename from docs/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/0-intro.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/intro.md index 5553668d03..4ca3d1eddb 100644 --- a/docs/guides/stay-up-to-date/terraform/3-how-to-update-to-terraform-15/0-intro.md +++ b/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/intro.md @@ -17,16 +17,16 @@ This guide consists of two main sections:
-#### [Core Concepts](1-core-concepts.md) +#### [Core Concepts](core-concepts.md) An overview of Terraform 0.15 and why it is important to update your code for compatibility. -#### [Deployment walkthrough](2-deployment-walkthrough/0-step-1-update-your-code-to-be-compatible-with-terraform-0-14.md) +#### [Deployment walkthrough](deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-14.md) The steps you need to take to update your code relying on the Gruntwork Infrastructure as Code library to work with Terraform 0.15. Includes a [version compatibility -table](2-deployment-walkthrough/2-step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md#version-compatibility-table) +table](deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md#version-compatibility-table) you can use as a reference to know which Gruntwork Repo version tag is compatible with Terraform 0.15. @@ -34,5 +34,5 @@ compatible with Terraform 0.15. From 30d6d6a20a40ad12ae26653d88b31fbb7e1bb16d Mon Sep 17 00:00:00 2001 From: Eben Eliason Date: Wed, 12 Jan 2022 10:44:07 -0800 Subject: [PATCH 04/20] Trying out welcome layout --- _docs-sources/guides/welcome.md | 26 ++++++++++++++++++++++++++ docs/guides/welcome.md | 28 +++++++++++++++++++++++++++- 2 files changed, 53 insertions(+), 1 deletion(-) diff --git a/_docs-sources/guides/welcome.md b/_docs-sources/guides/welcome.md index 775cd609e9..3ca459fad5 100644 --- a/_docs-sources/guides/welcome.md +++ b/_docs-sources/guides/welcome.md @@ -88,4 +88,30 @@ The Gruntwork IaC library empowers you to construct your own bespoke architectur +## Stay Up to Date + + +
+ +### CIS AWS Foundations Benchmark + +- [Update to version 1.4.0](#) +- [Update to version 1.3.0](#) + +
+
+ +### Terraform + +- [Update to version 1.X](#) +- [Update to Terraform 15](#) +- [Update to Terraform 14](#) +- [Update to Terraform 13](#) +- [Update to Terraform 12](#) +- [Update to Version 3 of the Terraform provider](#) +- [DRY your Reference Architecture](#) + +
+ + diff --git a/docs/guides/welcome.md b/docs/guides/welcome.md index 8172fae1ff..2635a13e2d 100644 --- a/docs/guides/welcome.md +++ b/docs/guides/welcome.md @@ -88,9 +88,35 @@ The Gruntwork IaC library empowers you to construct your own bespoke architectur +## Stay Up to Date + + +
+ +### CIS AWS Foundations Benchmark + +- [Update to version 1.4.0](#) +- [Update to version 1.3.0](#) + +
+
+ +### Terraform + +- [Update to version 1.X](#) +- [Update to Terraform 15](#) +- [Update to Terraform 14](#) +- [Update to Terraform 13](#) +- [Update to Terraform 12](#) +- [Update to Version 3 of the Terraform provider](#) +- [DRY your Reference Architecture](#) + +
+ + From 1a27e2743ced5c21f4ce83702756ecb8b0125a37 Mon Sep 17 00:00:00 2001 From: Eugene K Date: Wed, 12 Jan 2022 16:20:16 -0500 Subject: [PATCH 05/20] Added landingzone guide sidebar --- .../what-is-an-aws-account-structure.md | 0 .../build-it-yourself/landing-zone/index.md | 59 ++++++++++++++--- .../landing-zone/intro/_category_.json | 3 - .../intro/what-youll-learn-in-this-guide.md | 49 -------------- .../what-is-an-aws-account-structure.md | 0 .../build-it-yourself/landing-zone/index.md | 59 +++++++++++++++-- .../intro/what-youll-learn-in-this-guide.md | 54 --------------- sidebars.js | 4 +- sidebars/landing-zone-guide.js | 65 +++++++++++++++++++ 9 files changed, 172 insertions(+), 121 deletions(-) rename _docs-sources/guides/build-it-yourself/landing-zone/{intro => core-concepts}/what-is-an-aws-account-structure.md (100%) rename docs/guides/build-it-yourself/landing-zone/intro/gruntwork-aws-landing-zone-vs-the-alternatives.md => _docs-sources/guides/build-it-yourself/landing-zone/index.md (54%) delete mode 100644 _docs-sources/guides/build-it-yourself/landing-zone/intro/_category_.json delete mode 100644 _docs-sources/guides/build-it-yourself/landing-zone/intro/what-youll-learn-in-this-guide.md rename docs/guides/build-it-yourself/landing-zone/{intro => core-concepts}/what-is-an-aws-account-structure.md (100%) rename _docs-sources/guides/build-it-yourself/landing-zone/intro/gruntwork-aws-landing-zone-vs-the-alternatives.md => docs/guides/build-it-yourself/landing-zone/index.md (52%) delete mode 100644 docs/guides/build-it-yourself/landing-zone/intro/what-youll-learn-in-this-guide.md create mode 100644 sidebars/landing-zone-guide.js diff --git a/_docs-sources/guides/build-it-yourself/landing-zone/intro/what-is-an-aws-account-structure.md b/_docs-sources/guides/build-it-yourself/landing-zone/core-concepts/what-is-an-aws-account-structure.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/landing-zone/intro/what-is-an-aws-account-structure.md rename to _docs-sources/guides/build-it-yourself/landing-zone/core-concepts/what-is-an-aws-account-structure.md diff --git a/docs/guides/build-it-yourself/landing-zone/intro/gruntwork-aws-landing-zone-vs-the-alternatives.md b/_docs-sources/guides/build-it-yourself/landing-zone/index.md similarity index 54% rename from docs/guides/build-it-yourself/landing-zone/intro/gruntwork-aws-landing-zone-vs-the-alternatives.md rename to _docs-sources/guides/build-it-yourself/landing-zone/index.md index 6636df8222..e3b7f2652b 100644 --- a/docs/guides/build-it-yourself/landing-zone/intro/gruntwork-aws-landing-zone-vs-the-alternatives.md +++ b/_docs-sources/guides/build-it-yourself/landing-zone/index.md @@ -1,4 +1,23 @@ -# Gruntwork AWS Landing Zone vs the alternatives +--- +sidebar_label: What you’ll learn in this guide +pagination_label: Configure Your Accounts With Landing Zone +--- + +import { CardList } from "/src/components/CardGroup" + +# Configure Your Accounts with Landing Zone + +:::caution + +This guide hasn’t been updated in the past 6 months. If you find any inaccuracies, please share with us at feedback@gruntwork.io. + +::: + +## Overview + +This guide will walk you through the process of configuring a production-grade AWS account structure, including how to manage multiple environments, users, permissions, and audit logging. We’ll also discuss how to implement a Landing Zone solution that lets you quickly spin up new AWS accounts that all implement a security baseline that enforces your company’s policies. + +## Gruntwork AWS Landing Zone vs the alternatives In June 2018, Amazon [announced](https://aws.amazon.com/about-aws/whats-new/2018/06/introducing-aws-landing-zone/) AWS Landing Zone, which solved three core problems: @@ -45,11 +64,33 @@ Because we use Terraform, we do not currently see the need for adding a first-cl solution, however some users may wish to add UI or UI-like functionality through their CI system or other Terraform automation tools. - - - - - - +## Sections + +Feel free to read this guide from start to finish or skip around to whatever sections interest you. + + + + An overview of the core concepts you need to understand to set up an AWS account structure, including AWS Organizations, IAM Users, IAM Roles, IAM Groups, CloudTrail, and more. + + + An overview of how to configure a secure, scalable, highly available AWS account structure that you can rely on in production. + + + A step-by-step guide to configuring a production-grade AWS account structure using the Gruntwork AWS Landing Zone solution, including how to manage it all with customizable security baselines defined in Terraform. + + + What to do once you’ve got your AWS account structure configured. + + diff --git a/_docs-sources/guides/build-it-yourself/landing-zone/intro/_category_.json b/_docs-sources/guides/build-it-yourself/landing-zone/intro/_category_.json deleted file mode 100644 index 824e59ad25..0000000000 --- a/_docs-sources/guides/build-it-yourself/landing-zone/intro/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ -"label": "Intro" -} \ No newline at end of file diff --git a/_docs-sources/guides/build-it-yourself/landing-zone/intro/what-youll-learn-in-this-guide.md b/_docs-sources/guides/build-it-yourself/landing-zone/intro/what-youll-learn-in-this-guide.md deleted file mode 100644 index 787786fcd2..0000000000 --- a/_docs-sources/guides/build-it-yourself/landing-zone/intro/what-youll-learn-in-this-guide.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -sidebar_label: What you’ll learn in this guide -pagination_label: Configure Your Accounts With Landing Zone ---- - -import { CardList } from "/src/components/CardGroup" - -# Configure Your Accounts with Landing Zone - -:::caution - -This guide hasn’t been updated in the past 6 months. If you find any inaccuracies, please share with us at feedback@gruntwork.io. - -::: - -## Overview - -This guide will walk you through the process of configuring a production-grade AWS account structure, including how to manage multiple environments, users, permissions, and audit logging. We’ll also discuss how to implement a Landing Zone solution that lets you quickly spin up new AWS accounts that all implement a security baseline that enforces your company’s policies. - -## Sections - -Feel free to read this guide from start to finish or skip around to whatever sections interest you. - - - - An overview of the core concepts you need to understand to set up an AWS account structure, including AWS Organizations, IAM Users, IAM Roles, IAM Groups, CloudTrail, and more. - - - An overview of how to configure a secure, scalable, highly available AWS account structure that you can rely on in production. - - - A step-by-step guide to configuring a production-grade AWS account structure using the Gruntwork AWS Landing Zone solution, including how to manage it all with customizable security baselines defined in Terraform. - - - What to do once you’ve got your AWS account structure configured. - - diff --git a/docs/guides/build-it-yourself/landing-zone/intro/what-is-an-aws-account-structure.md b/docs/guides/build-it-yourself/landing-zone/core-concepts/what-is-an-aws-account-structure.md similarity index 100% rename from docs/guides/build-it-yourself/landing-zone/intro/what-is-an-aws-account-structure.md rename to docs/guides/build-it-yourself/landing-zone/core-concepts/what-is-an-aws-account-structure.md diff --git a/_docs-sources/guides/build-it-yourself/landing-zone/intro/gruntwork-aws-landing-zone-vs-the-alternatives.md b/docs/guides/build-it-yourself/landing-zone/index.md similarity index 52% rename from _docs-sources/guides/build-it-yourself/landing-zone/intro/gruntwork-aws-landing-zone-vs-the-alternatives.md rename to docs/guides/build-it-yourself/landing-zone/index.md index 62b8026a87..c04549509f 100644 --- a/_docs-sources/guides/build-it-yourself/landing-zone/intro/gruntwork-aws-landing-zone-vs-the-alternatives.md +++ b/docs/guides/build-it-yourself/landing-zone/index.md @@ -1,4 +1,23 @@ -# Gruntwork AWS Landing Zone vs the alternatives +--- +sidebar_label: What you’ll learn in this guide +pagination_label: Configure Your Accounts With Landing Zone +--- + +import { CardList } from "/src/components/CardGroup" + +# Configure Your Accounts with Landing Zone + +:::caution + +This guide hasn’t been updated in the past 6 months. If you find any inaccuracies, please share with us at feedback@gruntwork.io. + +::: + +## Overview + +This guide will walk you through the process of configuring a production-grade AWS account structure, including how to manage multiple environments, users, permissions, and audit logging. We’ll also discuss how to implement a Landing Zone solution that lets you quickly spin up new AWS accounts that all implement a security baseline that enforces your company’s policies. + +## Gruntwork AWS Landing Zone vs the alternatives In June 2018, Amazon [announced](https://aws.amazon.com/about-aws/whats-new/2018/06/introducing-aws-landing-zone/) AWS Landing Zone, which solved three core problems: @@ -45,6 +64,38 @@ Because we use Terraform, we do not currently see the need for adding a first-cl solution, however some users may wish to add UI or UI-like functionality through their CI system or other Terraform automation tools. - - - +## Sections + +Feel free to read this guide from start to finish or skip around to whatever sections interest you. + + + + An overview of the core concepts you need to understand to set up an AWS account structure, including AWS Organizations, IAM Users, IAM Roles, IAM Groups, CloudTrail, and more. + + + An overview of how to configure a secure, scalable, highly available AWS account structure that you can rely on in production. + + + A step-by-step guide to configuring a production-grade AWS account structure using the Gruntwork AWS Landing Zone solution, including how to manage it all with customizable security baselines defined in Terraform. + + + What to do once you’ve got your AWS account structure configured. + + + + + diff --git a/docs/guides/build-it-yourself/landing-zone/intro/what-youll-learn-in-this-guide.md b/docs/guides/build-it-yourself/landing-zone/intro/what-youll-learn-in-this-guide.md deleted file mode 100644 index cb440df08c..0000000000 --- a/docs/guides/build-it-yourself/landing-zone/intro/what-youll-learn-in-this-guide.md +++ /dev/null @@ -1,54 +0,0 @@ ---- -sidebar_label: What you’ll learn in this guide -pagination_label: Configure Your Accounts With Landing Zone ---- - -import { CardList } from "/src/components/CardGroup" - -# Configure Your Accounts with Landing Zone - -:::caution - -This guide hasn’t been updated in the past 6 months. If you find any inaccuracies, please share with us at feedback@gruntwork.io. - -::: - -## Overview - -This guide will walk you through the process of configuring a production-grade AWS account structure, including how to manage multiple environments, users, permissions, and audit logging. We’ll also discuss how to implement a Landing Zone solution that lets you quickly spin up new AWS accounts that all implement a security baseline that enforces your company’s policies. - -## Sections - -Feel free to read this guide from start to finish or skip around to whatever sections interest you. - - - - An overview of the core concepts you need to understand to set up an AWS account structure, including AWS Organizations, IAM Users, IAM Roles, IAM Groups, CloudTrail, and more. - - - An overview of how to configure a secure, scalable, highly available AWS account structure that you can rely on in production. - - - A step-by-step guide to configuring a production-grade AWS account structure using the Gruntwork AWS Landing Zone solution, including how to manage it all with customizable security baselines defined in Terraform. - - - What to do once you’ve got your AWS account structure configured. - - - - - diff --git a/sidebars.js b/sidebars.js index 31061b073c..445d78e4ad 100644 --- a/sidebars.js +++ b/sidebars.js @@ -11,7 +11,7 @@ const introSidebar = require("./sidebars/intro-guide.js") const refarchSidebar = require("./sidebars/refarch-guide.js") -// const landingZoneSidebar = require("./sidebars/landing-zone-guide.js") +const landingZoneSidebar = require("./sidebars/landing-zone-guide.js") // const pipelineSidebar = require("./sidebars/pipelines-guide.js") // const vpcSidebar = require("./sidebars/vpc-guide.js") // const kuberneteSidebar = require("./sidebars/kubernetes-guide.js") @@ -24,7 +24,7 @@ const apiSidebars = require("./sidebars/api-reference.js") const sidebars = { introSidebar, refarchSidebar, - // landingZoneSidebar, + landingZoneSidebar, // pipelinesSidebar, // vpcSidebar, // kubernetesSidebar, diff --git a/sidebars/landing-zone-guide.js b/sidebars/landing-zone-guide.js new file mode 100644 index 0000000000..06a9827276 --- /dev/null +++ b/sidebars/landing-zone-guide.js @@ -0,0 +1,65 @@ +const landingZoneGuide = [ + { + label: "Landing Zone Guides", + type: "category", + link: { + type: "doc", + id: "guides/build-it-yourself/landing-zone/index", + }, + items: [ + { + "Core Concepts": [ + "guides/build-it-yourself/landing-zone/core-concepts/what-is-an-aws-account-structure", + "guides/build-it-yourself/landing-zone/core-concepts/aws-account", + "guides/build-it-yourself/landing-zone/core-concepts/root-user", + "guides/build-it-yourself/landing-zone/core-concepts/iam-users", + "guides/build-it-yourself/landing-zone/core-concepts/iam-policies", + "guides/build-it-yourself/landing-zone/core-concepts/iam-groups", + "guides/build-it-yourself/landing-zone/core-concepts/iam-roles", + "guides/build-it-yourself/landing-zone/core-concepts/federated-authentication", + "guides/build-it-yourself/landing-zone/core-concepts/aws-organizations", + "guides/build-it-yourself/landing-zone/core-concepts/cloud-trail", + "guides/build-it-yourself/landing-zone/core-concepts/aws-config", + "guides/build-it-yourself/landing-zone/core-concepts/guard-duty", + ], + }, + { + "Production Grade Design": [ + "guides/build-it-yourself/landing-zone/production-grade-design/intro", + "guides/build-it-yourself/landing-zone/production-grade-design/the-root-account", + "guides/build-it-yourself/landing-zone/production-grade-design/child-accounts", + "guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-users", + "guides/build-it-yourself/landing-zone/production-grade-design/iam-users-and-groups", + "guides/build-it-yourself/landing-zone/production-grade-design/mfa-policy", + "guides/build-it-yourself/landing-zone/production-grade-design/password-policy", + "guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-services", + "guides/build-it-yourself/landing-zone/production-grade-design/cloud-trail", + "guides/build-it-yourself/landing-zone/production-grade-design/aws-config", + "guides/build-it-yourself/landing-zone/production-grade-design/guard-duty", + "guides/build-it-yourself/landing-zone/production-grade-design/federated-auth", + ], + }, + { + "Deployment walkthrough": [ + "guides/build-it-yourself/landing-zone/deployment-walkthrough/pre-requisites", + "guides/build-it-yourself/landing-zone/deployment-walkthrough/prepare-your-infrastructure-live-repository", + "guides/build-it-yourself/landing-zone/deployment-walkthrough/create-the-root-account", + "guides/build-it-yourself/landing-zone/deployment-walkthrough/lock-down-the-root-user", + "guides/build-it-yourself/landing-zone/deployment-walkthrough/create-an-iam-user-in-the-root-account", + "guides/build-it-yourself/landing-zone/deployment-walkthrough/lock-down-the-root-account-iam-users", + "guides/build-it-yourself/landing-zone/deployment-walkthrough/configure-the-security-baseline-for-the-root-account", + "guides/build-it-yourself/landing-zone/deployment-walkthrough/import-existing-resources-from-the-root-account-into-terraform-state", + "guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-root-account", + "guides/build-it-yourself/landing-zone/deployment-walkthrough/reset-the-root-user-password-in-each-child-account", + "guides/build-it-yourself/landing-zone/deployment-walkthrough/lock-down-the-root-user-in-the-child-accounts", + "guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-logs-account", + "guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-security-account", + "guides/build-it-yourself/landing-zone/deployment-walkthrough/apply-the-security-baseline-to-the-other-child-accounts", + "guides/build-it-yourself/landing-zone/deployment-walkthrough/try-authenticating-as-an-iam-user-to-the-child-accounts", + ], + }, + ], + }, +] + +module.exports = landingZoneGuide From 49de579b464ed7c6f341da1a64827ce2f432fb1d Mon Sep 17 00:00:00 2001 From: Eugene K Date: Wed, 12 Jan 2022 16:51:20 -0500 Subject: [PATCH 06/20] Added sidebar for pipelines --- ...ous-integration-and-continuous-delivery.md | 0 .../build-it-yourself/pipelines/index.md | 34 +++++++++++-- .../pipelines/intro/_category_.json | 3 -- .../intro/what-this-guide-will-not-cover.md | 28 ----------- ...ous-integration-and-continuous-delivery.md | 0 .../build-it-yourself/pipelines/index.md | 34 +++++++++++++ .../intro/what-this-guide-will-not-cover.md | 33 ------------ sidebars.js | 4 +- sidebars/pipelines-guide.js | 50 +++++++++++++++++++ 9 files changed, 115 insertions(+), 71 deletions(-) rename _docs-sources/guides/build-it-yourself/pipelines/{intro => core-concepts}/what-is-continuous-integration-and-continuous-delivery.md (100%) rename docs/guides/build-it-yourself/pipelines/intro/what-youll-learn-in-this-guide.md => _docs-sources/guides/build-it-yourself/pipelines/index.md (56%) delete mode 100644 _docs-sources/guides/build-it-yourself/pipelines/intro/_category_.json delete mode 100644 _docs-sources/guides/build-it-yourself/pipelines/intro/what-this-guide-will-not-cover.md rename docs/guides/build-it-yourself/pipelines/{intro => core-concepts}/what-is-continuous-integration-and-continuous-delivery.md (100%) rename _docs-sources/guides/build-it-yourself/pipelines/intro/what-youll-learn-in-this-guide.md => docs/guides/build-it-yourself/pipelines/index.md (54%) delete mode 100644 docs/guides/build-it-yourself/pipelines/intro/what-this-guide-will-not-cover.md create mode 100644 sidebars/pipelines-guide.js diff --git a/_docs-sources/guides/build-it-yourself/pipelines/intro/what-is-continuous-integration-and-continuous-delivery.md b/_docs-sources/guides/build-it-yourself/pipelines/core-concepts/what-is-continuous-integration-and-continuous-delivery.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/pipelines/intro/what-is-continuous-integration-and-continuous-delivery.md rename to _docs-sources/guides/build-it-yourself/pipelines/core-concepts/what-is-continuous-integration-and-continuous-delivery.md diff --git a/docs/guides/build-it-yourself/pipelines/intro/what-youll-learn-in-this-guide.md b/_docs-sources/guides/build-it-yourself/pipelines/index.md similarity index 56% rename from docs/guides/build-it-yourself/pipelines/intro/what-youll-learn-in-this-guide.md rename to _docs-sources/guides/build-it-yourself/pipelines/index.md index 23e4d29382..8ed9741c30 100644 --- a/docs/guides/build-it-yourself/pipelines/intro/what-youll-learn-in-this-guide.md +++ b/_docs-sources/guides/build-it-yourself/pipelines/index.md @@ -24,6 +24,35 @@ TLDR: If you follow this guide, you’ll be able to set up a pipeline that works ![For an extended version with audio commentary, see ](/img/guides/build-it-yourself/pipelines/walkthrough.gif) +## What this guide will not cover + +CI/CD for infrastructure code is a large topic and a single guide cannot cover everything. There +are several items that this guide will not cover, including: + +
+ +#### A pipeline for setting up new environments + +This guide will focus on a CI/CD workflow for making changes to infrastructure in an environment that is already set +up. In other words, the design and implementation of the pipeline covered in this guide intentionally does not solve +the use case of infrastructure code for setting up an environment from scratch. Setting up new environments typically +require complex deployment orders and permissions modeling that complicate the task. This makes it hard to automate in +a reasonable fashion that still respects the threat model we cover here. + +#### Automated testing and feature toggling strategies for infrastructure code + +An important factor of CI/CD pipelines is the existence of automated testing and feature toggles. Automated tests give +you confidence in the code before it is deployed to production. Similarly, feature toggles allow you to partially +integrate and deploy code for a feature without enabling it. By doing so, you are able to continuously integrate new +developments over time. This guide will briefly introduce automated testing and feature toggles for infrastructure +code, but will not do a deep dive on the subject. You can learn more about best practices for automated testing in our +talk +[Automated +testing for Terraform, Docker, Packer, Kubernetes, and More](https://blog.gruntwork.io/new-talk-automated-testing-for-terraform-docker-packer-kubernetes-and-more-cba312171aa6) and blog post +[Agility requires safety](https://www.ybrikman.com/writing/2016/02/14/agility-requires-safety/). + +
+ ## Sections Feel free to read this guide from start to finish or skip around to whatever sections interest you. @@ -58,8 +87,3 @@ Feel free to read this guide from start to finish or skip around to whatever sec What to do once you’ve got your CI/CD pipeline set up. - - - diff --git a/_docs-sources/guides/build-it-yourself/pipelines/intro/_category_.json b/_docs-sources/guides/build-it-yourself/pipelines/intro/_category_.json deleted file mode 100644 index 824e59ad25..0000000000 --- a/_docs-sources/guides/build-it-yourself/pipelines/intro/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ -"label": "Intro" -} \ No newline at end of file diff --git a/_docs-sources/guides/build-it-yourself/pipelines/intro/what-this-guide-will-not-cover.md b/_docs-sources/guides/build-it-yourself/pipelines/intro/what-this-guide-will-not-cover.md deleted file mode 100644 index a1a114f860..0000000000 --- a/_docs-sources/guides/build-it-yourself/pipelines/intro/what-this-guide-will-not-cover.md +++ /dev/null @@ -1,28 +0,0 @@ -# What this guide will not cover - -CI/CD for infrastructure code is a large topic and a single guide cannot cover everything. There -are several items that this guide will not cover, including: - -
- -#### A pipeline for setting up new environments - -This guide will focus on a CI/CD workflow for making changes to infrastructure in an environment that is already set -up. In other words, the design and implementation of the pipeline covered in this guide intentionally does not solve -the use case of infrastructure code for setting up an environment from scratch. Setting up new environments typically -require complex deployment orders and permissions modeling that complicate the task. This makes it hard to automate in -a reasonable fashion that still respects the threat model we cover here. - -#### Automated testing and feature toggling strategies for infrastructure code - -An important factor of CI/CD pipelines is the existence of automated testing and feature toggles. Automated tests give -you confidence in the code before it is deployed to production. Similarly, feature toggles allow you to partially -integrate and deploy code for a feature without enabling it. By doing so, you are able to continuously integrate new -developments over time. This guide will briefly introduce automated testing and feature toggles for infrastructure -code, but will not do a deep dive on the subject. You can learn more about best practices for automated testing in our -talk -[Automated -testing for Terraform, Docker, Packer, Kubernetes, and More](https://blog.gruntwork.io/new-talk-automated-testing-for-terraform-docker-packer-kubernetes-and-more-cba312171aa6) and blog post -[Agility requires safety](https://www.ybrikman.com/writing/2016/02/14/agility-requires-safety/). - -
diff --git a/docs/guides/build-it-yourself/pipelines/intro/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 similarity index 100% rename from docs/guides/build-it-yourself/pipelines/intro/what-is-continuous-integration-and-continuous-delivery.md rename to docs/guides/build-it-yourself/pipelines/core-concepts/what-is-continuous-integration-and-continuous-delivery.md diff --git a/_docs-sources/guides/build-it-yourself/pipelines/intro/what-youll-learn-in-this-guide.md b/docs/guides/build-it-yourself/pipelines/index.md similarity index 54% rename from _docs-sources/guides/build-it-yourself/pipelines/intro/what-youll-learn-in-this-guide.md rename to docs/guides/build-it-yourself/pipelines/index.md index 87b433212b..f3748e5f54 100644 --- a/_docs-sources/guides/build-it-yourself/pipelines/intro/what-youll-learn-in-this-guide.md +++ b/docs/guides/build-it-yourself/pipelines/index.md @@ -24,6 +24,35 @@ TLDR: If you follow this guide, you’ll be able to set up a pipeline that works ![For an extended version with audio commentary, see ](/img/guides/build-it-yourself/pipelines/walkthrough.gif) +## What this guide will not cover + +CI/CD for infrastructure code is a large topic and a single guide cannot cover everything. There +are several items that this guide will not cover, including: + +
+ +#### A pipeline for setting up new environments + +This guide will focus on a CI/CD workflow for making changes to infrastructure in an environment that is already set +up. In other words, the design and implementation of the pipeline covered in this guide intentionally does not solve +the use case of infrastructure code for setting up an environment from scratch. Setting up new environments typically +require complex deployment orders and permissions modeling that complicate the task. This makes it hard to automate in +a reasonable fashion that still respects the threat model we cover here. + +#### Automated testing and feature toggling strategies for infrastructure code + +An important factor of CI/CD pipelines is the existence of automated testing and feature toggles. Automated tests give +you confidence in the code before it is deployed to production. Similarly, feature toggles allow you to partially +integrate and deploy code for a feature without enabling it. By doing so, you are able to continuously integrate new +developments over time. This guide will briefly introduce automated testing and feature toggles for infrastructure +code, but will not do a deep dive on the subject. You can learn more about best practices for automated testing in our +talk +[Automated +testing for Terraform, Docker, Packer, Kubernetes, and More](https://blog.gruntwork.io/new-talk-automated-testing-for-terraform-docker-packer-kubernetes-and-more-cba312171aa6) and blog post +[Agility requires safety](https://www.ybrikman.com/writing/2016/02/14/agility-requires-safety/). + +
+ ## Sections Feel free to read this guide from start to finish or skip around to whatever sections interest you. @@ -58,3 +87,8 @@ Feel free to read this guide from start to finish or skip around to whatever sec What to do once you’ve got your CI/CD pipeline set up. + + + diff --git a/docs/guides/build-it-yourself/pipelines/intro/what-this-guide-will-not-cover.md b/docs/guides/build-it-yourself/pipelines/intro/what-this-guide-will-not-cover.md deleted file mode 100644 index 5cad87d58a..0000000000 --- a/docs/guides/build-it-yourself/pipelines/intro/what-this-guide-will-not-cover.md +++ /dev/null @@ -1,33 +0,0 @@ -# What this guide will not cover - -CI/CD for infrastructure code is a large topic and a single guide cannot cover everything. There -are several items that this guide will not cover, including: - -
- -#### A pipeline for setting up new environments - -This guide will focus on a CI/CD workflow for making changes to infrastructure in an environment that is already set -up. In other words, the design and implementation of the pipeline covered in this guide intentionally does not solve -the use case of infrastructure code for setting up an environment from scratch. Setting up new environments typically -require complex deployment orders and permissions modeling that complicate the task. This makes it hard to automate in -a reasonable fashion that still respects the threat model we cover here. - -#### Automated testing and feature toggling strategies for infrastructure code - -An important factor of CI/CD pipelines is the existence of automated testing and feature toggles. Automated tests give -you confidence in the code before it is deployed to production. Similarly, feature toggles allow you to partially -integrate and deploy code for a feature without enabling it. By doing so, you are able to continuously integrate new -developments over time. This guide will briefly introduce automated testing and feature toggles for infrastructure -code, but will not do a deep dive on the subject. You can learn more about best practices for automated testing in our -talk -[Automated -testing for Terraform, Docker, Packer, Kubernetes, and More](https://blog.gruntwork.io/new-talk-automated-testing-for-terraform-docker-packer-kubernetes-and-more-cba312171aa6) and blog post -[Agility requires safety](https://www.ybrikman.com/writing/2016/02/14/agility-requires-safety/). - -
- - - diff --git a/sidebars.js b/sidebars.js index 445d78e4ad..e7bcc1c57a 100644 --- a/sidebars.js +++ b/sidebars.js @@ -12,7 +12,7 @@ const introSidebar = require("./sidebars/intro-guide.js") const refarchSidebar = require("./sidebars/refarch-guide.js") const landingZoneSidebar = require("./sidebars/landing-zone-guide.js") -// const pipelineSidebar = require("./sidebars/pipelines-guide.js") +const pipelineSidebar = require("./sidebars/pipelines-guide.js") // const vpcSidebar = require("./sidebars/vpc-guide.js") // const kuberneteSidebar = require("./sidebars/kubernetes-guide.js") // const complianceSidebar = require("./sidebars/compliance-guide.js") @@ -25,7 +25,7 @@ const sidebars = { introSidebar, refarchSidebar, landingZoneSidebar, - // pipelinesSidebar, + pipelineSidebar, // vpcSidebar, // kubernetesSidebar, // complianceSidebar, diff --git a/sidebars/pipelines-guide.js b/sidebars/pipelines-guide.js new file mode 100644 index 0000000000..c9f27da218 --- /dev/null +++ b/sidebars/pipelines-guide.js @@ -0,0 +1,50 @@ +const pipelineGuide = [ + { + label: "Pipelines Guide", + type: "category", + link: { + type: "doc", + id: "guides/build-it-yourself/pipelines/index", + }, + items: [ + { + "Core Concepts": [ + "guides/build-it-yourself/pipelines/core-concepts/what-is-continuous-integration-and-continuous-delivery", + "guides/build-it-yourself/pipelines/core-concepts/why-is-it-important-to-have-ci-cd", + "guides/build-it-yourself/pipelines/core-concepts/trunk-based-development-model", + "guides/build-it-yourself/pipelines/core-concepts/types-of-infrastructure-code", + "guides/build-it-yourself/pipelines/core-concepts/ci-cd-workflows", + "guides/build-it-yourself/pipelines/core-concepts/threat-model-of-ci-cd", + "guides/build-it-yourself/pipelines/core-concepts/ci-cd-platforms", + ], + }, + { + "Production Grade Design": [ + "guides/build-it-yourself/pipelines/production-grade-design/intro", + "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", + "guides/build-it-yourself/pipelines/production-grade-design/options-for-deploy-server", + "guides/build-it-yourself/pipelines/production-grade-design/limit-triggers-for-deploy-server", + "guides/build-it-yourself/pipelines/production-grade-design/use-a-vpc-to-lock-down-deploy-server", + "guides/build-it-yourself/pipelines/production-grade-design/use-minimal-iam-permissions-for-a-deployment", + "guides/build-it-yourself/pipelines/production-grade-design/use-approval-flows", + "guides/build-it-yourself/pipelines/production-grade-design/lock-down-vcs-systems", + "guides/build-it-yourself/pipelines/production-grade-design/summary-of-mitigations", + "guides/build-it-yourself/pipelines/production-grade-design/summary-of-deployment-sequence", + ], + }, + { + "Deployment walkthrough": [ + "guides/build-it-yourself/pipelines/deployment-walkthrough/pre-requisites", + "guides/build-it-yourself/pipelines/deployment-walkthrough/deploy-a-vpc", + "guides/build-it-yourself/pipelines/deployment-walkthrough/deploy-the-ecs-deploy-runner", + "guides/build-it-yourself/pipelines/deployment-walkthrough/try-out-the-ecs-deploy-runner", + "guides/build-it-yourself/pipelines/deployment-walkthrough/define-pipeline-as-code", + "guides/build-it-yourself/pipelines/deployment-walkthrough/configure-ci-server", + ], + }, + "guides/build-it-yourself/pipelines/next-steps", + ], + }, +] + +module.exports = pipelineGuide From 6076052880b73f510b44ec913671c998cb1f878a Mon Sep 17 00:00:00 2001 From: Eugene K Date: Wed, 12 Jan 2022 17:08:24 -0500 Subject: [PATCH 07/20] Added VPC Guide Sidebar --- .../{intro => core-concepts}/what-is-a-vpc.md | 0 ...-youll-learn-in-this-guide.md => index.md} | 0 .../vpc/intro/_category_.json | 3 -- .../landing-zone/intro/_category_.json | 3 -- .../pipelines/intro/_category_.json | 3 -- .../{intro => core-concepts}/what-is-a-vpc.md | 0 ...-youll-learn-in-this-guide.md => index.md} | 0 .../vpc/intro/_category_.json | 3 -- sidebars.js | 4 +- sidebars/landing-zone-guide.js | 1 + sidebars/vpc-guide.js | 53 +++++++++++++++++++ 11 files changed, 56 insertions(+), 14 deletions(-) rename _docs-sources/guides/build-it-yourself/vpc/{intro => core-concepts}/what-is-a-vpc.md (100%) rename _docs-sources/guides/build-it-yourself/vpc/{intro/what-youll-learn-in-this-guide.md => index.md} (100%) delete mode 100644 _docs-sources/guides/build-it-yourself/vpc/intro/_category_.json delete mode 100644 docs/guides/build-it-yourself/landing-zone/intro/_category_.json delete mode 100644 docs/guides/build-it-yourself/pipelines/intro/_category_.json rename docs/guides/build-it-yourself/vpc/{intro => core-concepts}/what-is-a-vpc.md (100%) rename docs/guides/build-it-yourself/vpc/{intro/what-youll-learn-in-this-guide.md => index.md} (100%) delete mode 100644 docs/guides/build-it-yourself/vpc/intro/_category_.json create mode 100644 sidebars/vpc-guide.js diff --git a/_docs-sources/guides/build-it-yourself/vpc/intro/what-is-a-vpc.md b/_docs-sources/guides/build-it-yourself/vpc/core-concepts/what-is-a-vpc.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/vpc/intro/what-is-a-vpc.md rename to _docs-sources/guides/build-it-yourself/vpc/core-concepts/what-is-a-vpc.md diff --git a/_docs-sources/guides/build-it-yourself/vpc/intro/what-youll-learn-in-this-guide.md b/_docs-sources/guides/build-it-yourself/vpc/index.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/vpc/intro/what-youll-learn-in-this-guide.md rename to _docs-sources/guides/build-it-yourself/vpc/index.md diff --git a/_docs-sources/guides/build-it-yourself/vpc/intro/_category_.json b/_docs-sources/guides/build-it-yourself/vpc/intro/_category_.json deleted file mode 100644 index 824e59ad25..0000000000 --- a/_docs-sources/guides/build-it-yourself/vpc/intro/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ -"label": "Intro" -} \ No newline at end of file diff --git a/docs/guides/build-it-yourself/landing-zone/intro/_category_.json b/docs/guides/build-it-yourself/landing-zone/intro/_category_.json deleted file mode 100644 index 824e59ad25..0000000000 --- a/docs/guides/build-it-yourself/landing-zone/intro/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ -"label": "Intro" -} \ No newline at end of file diff --git a/docs/guides/build-it-yourself/pipelines/intro/_category_.json b/docs/guides/build-it-yourself/pipelines/intro/_category_.json deleted file mode 100644 index 824e59ad25..0000000000 --- a/docs/guides/build-it-yourself/pipelines/intro/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ -"label": "Intro" -} \ No newline at end of file diff --git a/docs/guides/build-it-yourself/vpc/intro/what-is-a-vpc.md b/docs/guides/build-it-yourself/vpc/core-concepts/what-is-a-vpc.md similarity index 100% rename from docs/guides/build-it-yourself/vpc/intro/what-is-a-vpc.md rename to docs/guides/build-it-yourself/vpc/core-concepts/what-is-a-vpc.md diff --git a/docs/guides/build-it-yourself/vpc/intro/what-youll-learn-in-this-guide.md b/docs/guides/build-it-yourself/vpc/index.md similarity index 100% rename from docs/guides/build-it-yourself/vpc/intro/what-youll-learn-in-this-guide.md rename to docs/guides/build-it-yourself/vpc/index.md diff --git a/docs/guides/build-it-yourself/vpc/intro/_category_.json b/docs/guides/build-it-yourself/vpc/intro/_category_.json deleted file mode 100644 index 824e59ad25..0000000000 --- a/docs/guides/build-it-yourself/vpc/intro/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ -"label": "Intro" -} \ No newline at end of file diff --git a/sidebars.js b/sidebars.js index e7bcc1c57a..04d484832d 100644 --- a/sidebars.js +++ b/sidebars.js @@ -13,7 +13,7 @@ const introSidebar = require("./sidebars/intro-guide.js") const refarchSidebar = require("./sidebars/refarch-guide.js") const landingZoneSidebar = require("./sidebars/landing-zone-guide.js") const pipelineSidebar = require("./sidebars/pipelines-guide.js") -// const vpcSidebar = require("./sidebars/vpc-guide.js") +const vpcSidebar = require("./sidebars/vpc-guide.js") // const kuberneteSidebar = require("./sidebars/kubernetes-guide.js") // const complianceSidebar = require("./sidebars/compliance-guide.js") const apiSidebars = require("./sidebars/api-reference.js") @@ -26,7 +26,7 @@ const sidebars = { refarchSidebar, landingZoneSidebar, pipelineSidebar, - // vpcSidebar, + vpcSidebar, // kubernetesSidebar, // complianceSidebar, ...apiSidebars, diff --git a/sidebars/landing-zone-guide.js b/sidebars/landing-zone-guide.js index 06a9827276..174bc433d8 100644 --- a/sidebars/landing-zone-guide.js +++ b/sidebars/landing-zone-guide.js @@ -58,6 +58,7 @@ const landingZoneGuide = [ "guides/build-it-yourself/landing-zone/deployment-walkthrough/try-authenticating-as-an-iam-user-to-the-child-accounts", ], }, + "guides/build-it-yourself/landing-zone/next-steps", ], }, ] diff --git a/sidebars/vpc-guide.js b/sidebars/vpc-guide.js new file mode 100644 index 0000000000..55a0d2c31e --- /dev/null +++ b/sidebars/vpc-guide.js @@ -0,0 +1,53 @@ +const vpcGuide = [ + { + label: "VPC Guide", + type: "category", + link: { + type: "doc", + id: "guides/build-it-yourself/vpc/index", + }, + items: [ + { + "Core Concepts": [ + "guides/build-it-yourself/vpc/core-concepts/what-is-a-vpc", + "guides/build-it-yourself/vpc/core-concepts/default-vp-cs-and-custom-vp-cs", + "guides/build-it-yourself/vpc/core-concepts/vpc-ip-addresses", + "guides/build-it-yourself/vpc/core-concepts/cidr-notation", + "guides/build-it-yourself/vpc/core-concepts/subnets", + "guides/build-it-yourself/vpc/core-concepts/route-tables", + "guides/build-it-yourself/vpc/core-concepts/internet-gateways-public-subnets-and-private-subnets", + "guides/build-it-yourself/vpc/core-concepts/nat-gateways", + "guides/build-it-yourself/vpc/core-concepts/security-groups", + "guides/build-it-yourself/vpc/core-concepts/network-ac-ls", + "guides/build-it-yourself/vpc/core-concepts/vpc-peering", + "guides/build-it-yourself/vpc/core-concepts/vpc-endpoints", + "guides/build-it-yourself/vpc/core-concepts/regions-and-availability-zones", + ], + }, + { + "Production Grade Design": [ + "guides/build-it-yourself/vpc/production-grade-design/intro", + "guides/build-it-yourself/vpc/production-grade-design/defense-in-depth", + "guides/build-it-yourself/vpc/production-grade-design/multiple-aws-accounts", + "guides/build-it-yourself/vpc/production-grade-design/multiple-vp-cs", + "guides/build-it-yourself/vpc/production-grade-design/multiple-subnet-tiers", + "guides/build-it-yourself/vpc/production-grade-design/security-groups-and-nac-ls", + "guides/build-it-yourself/vpc/production-grade-design/internet-gateways-and-nat-gateways", + "guides/build-it-yourself/vpc/production-grade-design/bastion-host", + ], + }, + { + "Deployment walkthrough": [ + "guides/build-it-yourself/vpc/deployment-walkthrough/pre-requisites", + "guides/build-it-yourself/vpc/deployment-walkthrough/deploy-a-management-vpc", + "guides/build-it-yourself/vpc/deployment-walkthrough/deploy-application-vp-cs", + "guides/build-it-yourself/vpc/deployment-walkthrough/deploy-a-bastion-host", + "guides/build-it-yourself/vpc/deployment-walkthrough/clean-up-default-vp-cs-and-security-groups", + ], + }, + "guides/build-it-yourself/vpc/next-steps", + ], + }, +] + +module.exports = vpcGuide From e64449404da1b76a3236c37581aefc253c6896e7 Mon Sep 17 00:00:00 2001 From: Eugene K Date: Wed, 12 Jan 2022 17:21:36 -0500 Subject: [PATCH 08/20] Added sidebar for Kubernetes guide --- .../what-is-kubernetes.md | 0 ...-youll-learn-in-this-guide.md => index.md} | 0 .../kubernetes-cluster/intro/_category_.json | 3 - .../what-is-kubernetes.md | 0 ...-youll-learn-in-this-guide.md => index.md} | 0 .../kubernetes-cluster/intro/_category_.json | 3 - sidebars.js | 4 +- sidebars/kubernetes-guide.js | 55 +++++++++++++++++++ 8 files changed, 57 insertions(+), 8 deletions(-) rename _docs-sources/guides/build-it-yourself/kubernetes-cluster/{intro => core-concepts}/what-is-kubernetes.md (100%) rename _docs-sources/guides/build-it-yourself/kubernetes-cluster/{intro/what-youll-learn-in-this-guide.md => index.md} (100%) delete mode 100644 _docs-sources/guides/build-it-yourself/kubernetes-cluster/intro/_category_.json rename docs/guides/build-it-yourself/kubernetes-cluster/{intro => core-concepts}/what-is-kubernetes.md (100%) rename docs/guides/build-it-yourself/kubernetes-cluster/{intro/what-youll-learn-in-this-guide.md => index.md} (100%) delete mode 100644 docs/guides/build-it-yourself/kubernetes-cluster/intro/_category_.json create mode 100644 sidebars/kubernetes-guide.js diff --git a/_docs-sources/guides/build-it-yourself/kubernetes-cluster/intro/what-is-kubernetes.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/core-concepts/what-is-kubernetes.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/kubernetes-cluster/intro/what-is-kubernetes.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/core-concepts/what-is-kubernetes.md diff --git a/_docs-sources/guides/build-it-yourself/kubernetes-cluster/intro/what-youll-learn-in-this-guide.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/index.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/kubernetes-cluster/intro/what-youll-learn-in-this-guide.md rename to _docs-sources/guides/build-it-yourself/kubernetes-cluster/index.md diff --git a/_docs-sources/guides/build-it-yourself/kubernetes-cluster/intro/_category_.json b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/intro/_category_.json deleted file mode 100644 index 824e59ad25..0000000000 --- a/_docs-sources/guides/build-it-yourself/kubernetes-cluster/intro/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ -"label": "Intro" -} \ No newline at end of file diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/intro/what-is-kubernetes.md b/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/what-is-kubernetes.md similarity index 100% rename from docs/guides/build-it-yourself/kubernetes-cluster/intro/what-is-kubernetes.md rename to docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/what-is-kubernetes.md diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/intro/what-youll-learn-in-this-guide.md b/docs/guides/build-it-yourself/kubernetes-cluster/index.md similarity index 100% rename from docs/guides/build-it-yourself/kubernetes-cluster/intro/what-youll-learn-in-this-guide.md rename to docs/guides/build-it-yourself/kubernetes-cluster/index.md diff --git a/docs/guides/build-it-yourself/kubernetes-cluster/intro/_category_.json b/docs/guides/build-it-yourself/kubernetes-cluster/intro/_category_.json deleted file mode 100644 index 824e59ad25..0000000000 --- a/docs/guides/build-it-yourself/kubernetes-cluster/intro/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ -"label": "Intro" -} \ No newline at end of file diff --git a/sidebars.js b/sidebars.js index 04d484832d..45fa9b8a4c 100644 --- a/sidebars.js +++ b/sidebars.js @@ -14,7 +14,7 @@ const refarchSidebar = require("./sidebars/refarch-guide.js") const landingZoneSidebar = require("./sidebars/landing-zone-guide.js") const pipelineSidebar = require("./sidebars/pipelines-guide.js") const vpcSidebar = require("./sidebars/vpc-guide.js") -// const kuberneteSidebar = require("./sidebars/kubernetes-guide.js") +const kubernetesSidebar = require("./sidebars/kubernetes-guide.js") // const complianceSidebar = require("./sidebars/compliance-guide.js") const apiSidebars = require("./sidebars/api-reference.js") @@ -27,7 +27,7 @@ const sidebars = { landingZoneSidebar, pipelineSidebar, vpcSidebar, - // kubernetesSidebar, + kubernetesSidebar, // complianceSidebar, ...apiSidebars, } diff --git a/sidebars/kubernetes-guide.js b/sidebars/kubernetes-guide.js new file mode 100644 index 0000000000..103f26660c --- /dev/null +++ b/sidebars/kubernetes-guide.js @@ -0,0 +1,55 @@ +const vpcGuide = [ + { + label: "Kubernetes Guide", + type: "category", + link: { + type: "doc", + id: "guides/build-it-yourself/kubernetes-cluster/index", + }, + items: [ + { + "Core Concepts": [ + "guides/build-it-yourself/kubernetes-cluster/core-concepts/what-is-kubernetes", + "guides/build-it-yourself/kubernetes-cluster/core-concepts/why-kubernetes", + "guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-architecture", + "guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-access-control", + "guides/build-it-yourself/kubernetes-cluster/core-concepts/interacting-with-kubernetes", + "guides/build-it-yourself/kubernetes-cluster/core-concepts/kubernetes-resources", + "guides/build-it-yourself/kubernetes-cluster/core-concepts/options-for-running-kubernetes-in-aws", + ], + }, + { + "Production Grade Design": [ + "guides/build-it-yourself/kubernetes-cluster/production-grade-design/intro", + "guides/build-it-yourself/kubernetes-cluster/production-grade-design/use-eks", + "guides/build-it-yourself/kubernetes-cluster/production-grade-design/vpc-configuration", + "guides/build-it-yourself/kubernetes-cluster/production-grade-design/control-plane", + "guides/build-it-yourself/kubernetes-cluster/production-grade-design/worker-nodes", + "guides/build-it-yourself/kubernetes-cluster/production-grade-design/authenticate", + "guides/build-it-yourself/kubernetes-cluster/production-grade-design/iam-role-mapping-and-rbac", + "guides/build-it-yourself/kubernetes-cluster/production-grade-design/logging", + "guides/build-it-yourself/kubernetes-cluster/production-grade-design/protecting-pods", + ], + }, + { + "Deployment walkthrough": [ + "guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/pre-requisites", + "guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/deploy-the-vpc", + "guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-control-plane", + "guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-worker-nodes", + "guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/create-the-worker-node-ami", + "guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-the-worker-node-user-data-script", + "guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-logging-metrics-and-alarms-for-the-worker-nodes", + "guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-role-mapping", + "guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/configure-access-to-the-control-plane-and-worker-nodes", + "guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/deploy-the-eks-cluster", + "guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/try-out-the-cluster", + "guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/updating-the-worker-nodes", + ], + }, + "guides/build-it-yourself/kubernetes-cluster/next-steps", + ], + }, +] + +module.exports = vpcGuide From 26bc7ddb2c6479c4f600011b3db8e986ab814b9e Mon Sep 17 00:00:00 2001 From: Eugene K Date: Wed, 12 Jan 2022 17:37:19 -0500 Subject: [PATCH 09/20] Achieve compliance guide sidebar --- .../achieve-compliance/core-concepts/intro.md | 6 ++ ...-youll-learn-in-this-guide.md => index.md} | 0 .../achieve-compliance/intro/_category_.json | 3 - ...at-is-the-cis-aws-foundations-benchmark.md | 7 --- .../achieve-compliance/core-concepts/intro.md | 8 ++- ...-youll-learn-in-this-guide.md => index.md} | 0 .../achieve-compliance/intro/_category_.json | 3 - ...at-is-the-cis-aws-foundations-benchmark.md | 12 ---- sidebars.js | 4 +- sidebars/compliance-guide.js | 58 +++++++++++++++++++ 10 files changed, 73 insertions(+), 28 deletions(-) rename _docs-sources/guides/build-it-yourself/achieve-compliance/{intro/what-youll-learn-in-this-guide.md => index.md} (100%) delete mode 100644 _docs-sources/guides/build-it-yourself/achieve-compliance/intro/_category_.json delete mode 100644 _docs-sources/guides/build-it-yourself/achieve-compliance/intro/what-is-the-cis-aws-foundations-benchmark.md rename docs/guides/build-it-yourself/achieve-compliance/{intro/what-youll-learn-in-this-guide.md => index.md} (100%) delete mode 100644 docs/guides/build-it-yourself/achieve-compliance/intro/_category_.json delete mode 100644 docs/guides/build-it-yourself/achieve-compliance/intro/what-is-the-cis-aws-foundations-benchmark.md create mode 100644 sidebars/compliance-guide.js diff --git a/_docs-sources/guides/build-it-yourself/achieve-compliance/core-concepts/intro.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/core-concepts/intro.md index 10d4ed2125..6057e25660 100644 --- a/_docs-sources/guides/build-it-yourself/achieve-compliance/core-concepts/intro.md +++ b/_docs-sources/guides/build-it-yourself/achieve-compliance/core-concepts/intro.md @@ -5,6 +5,12 @@ sidebar_label: Intro # CIS Compliance Core Concepts +The [CIS Benchmarks](https://www.cisecurity.org/resources/?type=benchmark) are objective, consensus-driven +configuration guidelines developed by security experts to help organizations improve their security posture. +The AWS Foundations Benchmark is a set of configuration best practices for hardening AWS accounts to establish +a secure foundation for running workloads on AWS. It also provides ongoing monitoring to ensure that the +account remains secure. + The CIS AWS Foundations Benchmark is organized into the following sections: - Identity and Access Management diff --git a/_docs-sources/guides/build-it-yourself/achieve-compliance/intro/what-youll-learn-in-this-guide.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/index.md similarity index 100% rename from _docs-sources/guides/build-it-yourself/achieve-compliance/intro/what-youll-learn-in-this-guide.md rename to _docs-sources/guides/build-it-yourself/achieve-compliance/index.md diff --git a/_docs-sources/guides/build-it-yourself/achieve-compliance/intro/_category_.json b/_docs-sources/guides/build-it-yourself/achieve-compliance/intro/_category_.json deleted file mode 100644 index 824e59ad25..0000000000 --- a/_docs-sources/guides/build-it-yourself/achieve-compliance/intro/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ -"label": "Intro" -} \ No newline at end of file diff --git a/_docs-sources/guides/build-it-yourself/achieve-compliance/intro/what-is-the-cis-aws-foundations-benchmark.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/intro/what-is-the-cis-aws-foundations-benchmark.md deleted file mode 100644 index 0ac9dee368..0000000000 --- a/_docs-sources/guides/build-it-yourself/achieve-compliance/intro/what-is-the-cis-aws-foundations-benchmark.md +++ /dev/null @@ -1,7 +0,0 @@ -# What is the CIS AWS Foundations Benchmark? - -The [CIS Benchmarks](https://www.cisecurity.org/resources/?type=benchmark) are objective, consensus-driven -configuration guidelines developed by security experts to help organizations improve their security posture. -The AWS Foundations Benchmark is a set of configuration best practices for hardening AWS accounts to establish -a secure foundation for running workloads on AWS. It also provides ongoing monitoring to ensure that the -account remains secure. 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 025639f788..9a3219c90c 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 @@ -5,6 +5,12 @@ sidebar_label: Intro # CIS Compliance Core Concepts +The [CIS Benchmarks](https://www.cisecurity.org/resources/?type=benchmark) are objective, consensus-driven +configuration guidelines developed by security experts to help organizations improve their security posture. +The AWS Foundations Benchmark is a set of configuration best practices for hardening AWS accounts to establish +a secure foundation for running workloads on AWS. It also provides ongoing monitoring to ensure that the +account remains secure. + The CIS AWS Foundations Benchmark is organized into the following sections: - Identity and Access Management @@ -45,5 +51,5 @@ controls. diff --git a/docs/guides/build-it-yourself/achieve-compliance/intro/what-youll-learn-in-this-guide.md b/docs/guides/build-it-yourself/achieve-compliance/index.md similarity index 100% rename from docs/guides/build-it-yourself/achieve-compliance/intro/what-youll-learn-in-this-guide.md rename to docs/guides/build-it-yourself/achieve-compliance/index.md diff --git a/docs/guides/build-it-yourself/achieve-compliance/intro/_category_.json b/docs/guides/build-it-yourself/achieve-compliance/intro/_category_.json deleted file mode 100644 index 824e59ad25..0000000000 --- a/docs/guides/build-it-yourself/achieve-compliance/intro/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ -"label": "Intro" -} \ No newline at end of file diff --git a/docs/guides/build-it-yourself/achieve-compliance/intro/what-is-the-cis-aws-foundations-benchmark.md b/docs/guides/build-it-yourself/achieve-compliance/intro/what-is-the-cis-aws-foundations-benchmark.md deleted file mode 100644 index fe7a102136..0000000000 --- a/docs/guides/build-it-yourself/achieve-compliance/intro/what-is-the-cis-aws-foundations-benchmark.md +++ /dev/null @@ -1,12 +0,0 @@ -# What is the CIS AWS Foundations Benchmark? - -The [CIS Benchmarks](https://www.cisecurity.org/resources/?type=benchmark) are objective, consensus-driven -configuration guidelines developed by security experts to help organizations improve their security posture. -The AWS Foundations Benchmark is a set of configuration best practices for hardening AWS accounts to establish -a secure foundation for running workloads on AWS. It also provides ongoing monitoring to ensure that the -account remains secure. - - - diff --git a/sidebars.js b/sidebars.js index 45fa9b8a4c..f48e5d74e2 100644 --- a/sidebars.js +++ b/sidebars.js @@ -15,7 +15,7 @@ const landingZoneSidebar = require("./sidebars/landing-zone-guide.js") const pipelineSidebar = require("./sidebars/pipelines-guide.js") const vpcSidebar = require("./sidebars/vpc-guide.js") const kubernetesSidebar = require("./sidebars/kubernetes-guide.js") -// const complianceSidebar = require("./sidebars/compliance-guide.js") +const complianceSidebar = require("./sidebars/compliance-guide.js") const apiSidebars = require("./sidebars/api-reference.js") // @ts-check @@ -28,7 +28,7 @@ const sidebars = { pipelineSidebar, vpcSidebar, kubernetesSidebar, - // complianceSidebar, + complianceSidebar, ...apiSidebars, } diff --git a/sidebars/compliance-guide.js b/sidebars/compliance-guide.js new file mode 100644 index 0000000000..ef3f9cc219 --- /dev/null +++ b/sidebars/compliance-guide.js @@ -0,0 +1,58 @@ +const complianceGuide = [ + { + label: "Achieve Compliance Guide", + type: "category", + link: { + type: "doc", + id: "guides/build-it-yourself/achieve-compliance/index", + }, + items: [ + { + "Core Concepts": [ + "guides/build-it-yourself/achieve-compliance/core-concepts/intro", + "guides/build-it-yourself/achieve-compliance/core-concepts/recommendation-sections", + ], + }, + { + "Production Grade Design": [ + "guides/build-it-yourself/achieve-compliance/production-grade-design/intro", + "guides/build-it-yourself/achieve-compliance/production-grade-design/identity-and-access-management", + "guides/build-it-yourself/achieve-compliance/production-grade-design/storage", + "guides/build-it-yourself/achieve-compliance/production-grade-design/logging", + "guides/build-it-yourself/achieve-compliance/production-grade-design/monitoring", + "guides/build-it-yourself/achieve-compliance/production-grade-design/networking", + ], + }, + { + "Deployment walkthrough": [ + "guides/build-it-yourself/achieve-compliance/deployment-walkthrough/pre-requisites", + "guides/build-it-yourself/achieve-compliance/deployment-walkthrough/the-gruntwork-solution", + "guides/build-it-yourself/achieve-compliance/deployment-walkthrough/prepare-your-infrastructure-live-repository", + "guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-the-root-account", + "guides/build-it-yourself/achieve-compliance/deployment-walkthrough/lock-down-the-root-user", + "guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-an-iam-user-in-the-root-account", + "guides/build-it-yourself/achieve-compliance/deployment-walkthrough/lock-down-the-root-account-iam-users", + "guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deployment-approach", + { + "Deploy Landing Zone Solution": [ + "guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-root-to-root-account", + "guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-app-to-logs-account", + "guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-security-to-security-account", + "guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-app-to-other-child-accounts", + "guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/use-iam-roles-for-ec2-instances", + "guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-iam-best-practices", + "guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-storage-best-practices", + "guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-logging-best-practices", + "guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/enable-key-rotation-for-kms-keys", + ], + }, + "guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-vpc-flow-logs", + ], + }, + "guides/build-it-yourself/achieve-compliance/traceability-matrix", + "guides/build-it-yourself/achieve-compliance/next-steps", + ], + }, +] + +module.exports = complianceGuide From cf759eea2ad215148d47df3936f9db56e479057d Mon Sep 17 00:00:00 2001 From: Eben Eliason Date: Wed, 12 Jan 2022 15:50:24 -0800 Subject: [PATCH 10/20] guides index updates and revised stay-up-to-date guide paths --- .../achieve-compliance/index.md | 4 +- .../production-grade-design/storage.md | 2 +- .../_category_.json | 0 .../core-concepts.md | 0 .../deployment-walkthrough/_category_.json | 0 ...runtwork-infrastructure-as-code-library.md | 0 .../step-2-manual-steps.md | 0 .../step-3-deploy-new-modules.md | 0 .../intro.md => cis-1.3.0/index.md} | 0 .../_category_.json | 0 .../core-concepts.md | 0 .../deployment-walkthrough/_category_.json | 0 ...runtwork-infrastructure-as-code-library.md | 0 ...p-2-update-the-account-baseline-modules.md | 0 .../step-3-manual-steps.md | 0 .../finally.md | 0 .../intro.md => cis-1.4.0/index.md} | 2 +- .../_category_.json | 0 .../core-concepts.md | 0 .../deployment-walkthrough.md | 0 .../intro.md => aws-provider-v3/index.md} | 0 .../{intro.md => index.md} | 0 .../_category_.json | 0 .../core-concepts.md | 0 .../deployment-walkthrough/_category_.json | 0 ...de-to-be-compatible-with-terraform-0-15.md | 8 ++-- ...runtwork-infrastructure-as-code-library.md | 0 .../intro.md => terraform-1.x/index.md} | 0 .../_category_.json | 0 .../deployment-walkthrough.md | 0 .../intro.md => terraform-12/index.md} | 0 .../version-compatibility-table.md | 0 .../_category_.json | 0 .../core-concepts.md | 0 .../deployment-walkthrough/_category_.json | 0 ...de-to-be-compatible-with-terraform-0-12.md | 2 +- ...de-to-be-compatible-with-terraform-0-13.md | 0 ...runtwork-infrastructure-as-code-library.md | 0 ...eference-architecture-to-terraform-0-13.md | 0 .../intro.md => terraform-13/index.md} | 0 .../_category_.json | 0 .../core-concepts.md | 0 .../deployment-walkthrough/_category_.json | 0 ...de-to-be-compatible-with-terraform-0-13.md | 4 +- ...de-to-be-compatible-with-terraform-0-14.md | 0 ...runtwork-infrastructure-as-code-library.md | 0 .../step-4-start-using-lock-files.md | 0 .../intro.md => terraform-14/index.md} | 0 .../_category_.json | 0 .../core-concepts.md | 0 .../deployment-walkthrough/_category_.json | 0 ...de-to-be-compatible-with-terraform-0-14.md | 6 +-- ...de-to-be-compatible-with-terraform-0-15.md | 0 ...runtwork-infrastructure-as-code-library.md | 0 .../intro.md => terraform-15/index.md} | 0 _docs-sources/guides/welcome.md | 42 +++++++++--------- .../achieve-compliance/index.md | 6 +-- .../production-grade-design/storage.md | 4 +- .../cis/cis-1-3-0/_category_.json | 3 ++ .../deployment-walkthrough/_category_.json | 3 ++ .../cis/cis-1-4-0/_category_.json | 3 ++ .../deployment-walkthrough/_category_.json | 3 ++ .../cis/cis-1.3.0/_category_.json | 3 ++ .../core-concepts.md | 0 .../deployment-walkthrough/_category_.json | 3 ++ ...runtwork-infrastructure-as-code-library.md | 0 .../step-2-manual-steps.md | 0 .../step-3-deploy-new-modules.md | 0 .../intro.md => cis-1.3.0/index.md} | 0 .../cis/cis-1.4.0/_category_.json | 3 ++ .../core-concepts.md | 0 .../deployment-walkthrough/_category_.json | 3 ++ ...runtwork-infrastructure-as-code-library.md | 0 ...p-2-update-the-account-baseline-modules.md | 0 .../step-3-manual-steps.md | 0 .../finally.md | 0 .../intro.md => cis-1.4.0/index.md} | 4 +- .../terraform/aws-provider-v3/_category_.json | 3 ++ .../core-concepts.md | 0 .../deployment-walkthrough.md | 0 .../intro.md => aws-provider-v3/index.md} | 0 .../{intro.md => index.md} | 0 .../terraform/terraform-1-x/_category_.json | 3 ++ .../deployment-walkthrough/_category_.json | 3 ++ .../terraform/terraform-1.x/_category_.json | 3 ++ .../core-concepts.md | 0 .../deployment-walkthrough/_category_.json | 3 ++ ...de-to-be-compatible-with-terraform-0-15.md | 10 ++--- ...runtwork-infrastructure-as-code-library.md | 0 .../intro.md => terraform-1.x/index.md} | 0 .../terraform/terraform-12/_category_.json | 3 ++ .../deployment-walkthrough.md | 0 .../intro.md => terraform-12/index.md} | 0 .../version-compatibility-table.md | 0 .../terraform/terraform-13/_category_.json | 3 ++ .../core-concepts.md | 0 .../deployment-walkthrough/_category_.json | 3 ++ ...de-to-be-compatible-with-terraform-0-12.md | 4 +- ...de-to-be-compatible-with-terraform-0-13.md | 0 ...runtwork-infrastructure-as-code-library.md | 0 ...eference-architecture-to-terraform-0-13.md | 0 .../intro.md => terraform-13/index.md} | 0 .../terraform/terraform-14/_category_.json | 3 ++ .../core-concepts.md | 0 .../deployment-walkthrough/_category_.json | 3 ++ ...de-to-be-compatible-with-terraform-0-13.md | 6 +-- ...de-to-be-compatible-with-terraform-0-14.md | 0 ...runtwork-infrastructure-as-code-library.md | 0 .../step-4-start-using-lock-files.md | 0 .../intro.md => terraform-14/index.md} | 0 .../terraform/terraform-15/_category_.json | 3 ++ .../core-concepts.md | 0 .../deployment-walkthrough/_category_.json | 3 ++ ...de-to-be-compatible-with-terraform-0-14.md | 8 ++-- ...de-to-be-compatible-with-terraform-0-15.md | 0 ...runtwork-infrastructure-as-code-library.md | 0 .../intro.md => terraform-15/index.md} | 0 docs/guides/welcome.md | 44 ++++++++++--------- src/pages/index.tsx | 10 ++--- 119 files changed, 145 insertions(+), 81 deletions(-) rename _docs-sources/guides/stay-up-to-date/cis/{how-to-update-to-cis-13 => cis-1.3.0}/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/cis/{how-to-update-to-cis-13 => cis-1.3.0}/core-concepts.md (100%) rename _docs-sources/guides/stay-up-to-date/cis/{how-to-update-to-cis-13 => cis-1.3.0}/deployment-walkthrough/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/cis/{how-to-update-to-cis-13 => cis-1.3.0}/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md (100%) rename _docs-sources/guides/stay-up-to-date/cis/{how-to-update-to-cis-13 => cis-1.3.0}/deployment-walkthrough/step-2-manual-steps.md (100%) rename _docs-sources/guides/stay-up-to-date/cis/{how-to-update-to-cis-13 => cis-1.3.0}/deployment-walkthrough/step-3-deploy-new-modules.md (100%) rename _docs-sources/guides/stay-up-to-date/cis/{how-to-update-to-cis-13/intro.md => cis-1.3.0/index.md} (100%) rename _docs-sources/guides/stay-up-to-date/cis/{how-to-update-to-cis-14 => cis-1.4.0}/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/cis/{how-to-update-to-cis-14 => cis-1.4.0}/core-concepts.md (100%) rename _docs-sources/guides/stay-up-to-date/cis/{how-to-update-to-cis-14 => cis-1.4.0}/deployment-walkthrough/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/cis/{how-to-update-to-cis-14 => cis-1.4.0}/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md (100%) rename _docs-sources/guides/stay-up-to-date/cis/{how-to-update-to-cis-14 => cis-1.4.0}/deployment-walkthrough/step-2-update-the-account-baseline-modules.md (100%) rename _docs-sources/guides/stay-up-to-date/cis/{how-to-update-to-cis-14 => cis-1.4.0}/deployment-walkthrough/step-3-manual-steps.md (100%) rename _docs-sources/guides/stay-up-to-date/cis/{how-to-update-to-cis-14 => cis-1.4.0}/finally.md (100%) rename _docs-sources/guides/stay-up-to-date/cis/{how-to-update-to-cis-14/intro.md => cis-1.4.0/index.md} (90%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-aws-provider-v3 => aws-provider-v3}/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-aws-provider-v3 => aws-provider-v3}/core-concepts.md (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-aws-provider-v3 => aws-provider-v3}/deployment-walkthrough.md (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-aws-provider-v3/intro.md => aws-provider-v3/index.md} (100%) rename _docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/{intro.md => index.md} (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-1-x => terraform-1.x}/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-1-x => terraform-1.x}/core-concepts.md (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-1-x => terraform-1.x}/deployment-walkthrough/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-1-x => terraform-1.x}/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-15.md (69%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-1-x => terraform-1.x}/deployment-walkthrough/step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-1-x/intro.md => terraform-1.x/index.md} (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-12 => terraform-12}/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-12 => terraform-12}/deployment-walkthrough.md (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-12/intro.md => terraform-12/index.md} (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-12 => terraform-12}/version-compatibility-table.md (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-13 => terraform-13}/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-13 => terraform-13}/core-concepts.md (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-13 => terraform-13}/deployment-walkthrough/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-13 => terraform-13}/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12.md (86%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-13 => terraform-13}/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-13.md (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-13 => terraform-13}/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-13 => terraform-13}/deployment-walkthrough/updating-the-gruntwork-reference-architecture-to-terraform-0-13.md (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-13/intro.md => terraform-13/index.md} (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-14 => terraform-14}/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-14 => terraform-14}/core-concepts.md (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-14 => terraform-14}/deployment-walkthrough/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-14 => terraform-14}/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-13.md (85%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-14 => terraform-14}/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-14.md (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-14 => terraform-14}/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-14 => terraform-14}/deployment-walkthrough/step-4-start-using-lock-files.md (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-14/intro.md => terraform-14/index.md} (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-15 => terraform-15}/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-15 => terraform-15}/core-concepts.md (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-15 => terraform-15}/deployment-walkthrough/_category_.json (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-15 => terraform-15}/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-14.md (73%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-15 => terraform-15}/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-15.md (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-15 => terraform-15}/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-15/intro.md => terraform-15/index.md} (100%) create mode 100644 docs/guides/stay-up-to-date/cis/cis-1-3-0/_category_.json create mode 100644 docs/guides/stay-up-to-date/cis/cis-1-3-0/deployment-walkthrough/_category_.json create mode 100644 docs/guides/stay-up-to-date/cis/cis-1-4-0/_category_.json create mode 100644 docs/guides/stay-up-to-date/cis/cis-1-4-0/deployment-walkthrough/_category_.json create mode 100644 docs/guides/stay-up-to-date/cis/cis-1.3.0/_category_.json rename docs/guides/stay-up-to-date/cis/{how-to-update-to-cis-13 => cis-1.3.0}/core-concepts.md (100%) create mode 100644 docs/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/_category_.json rename docs/guides/stay-up-to-date/cis/{how-to-update-to-cis-13 => cis-1.3.0}/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md (100%) rename docs/guides/stay-up-to-date/cis/{how-to-update-to-cis-13 => cis-1.3.0}/deployment-walkthrough/step-2-manual-steps.md (100%) rename docs/guides/stay-up-to-date/cis/{how-to-update-to-cis-13 => cis-1.3.0}/deployment-walkthrough/step-3-deploy-new-modules.md (100%) rename docs/guides/stay-up-to-date/cis/{how-to-update-to-cis-13/intro.md => cis-1.3.0/index.md} (100%) create mode 100644 docs/guides/stay-up-to-date/cis/cis-1.4.0/_category_.json rename docs/guides/stay-up-to-date/cis/{how-to-update-to-cis-14 => cis-1.4.0}/core-concepts.md (100%) create mode 100644 docs/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/_category_.json rename docs/guides/stay-up-to-date/cis/{how-to-update-to-cis-14 => cis-1.4.0}/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md (100%) rename docs/guides/stay-up-to-date/cis/{how-to-update-to-cis-14 => cis-1.4.0}/deployment-walkthrough/step-2-update-the-account-baseline-modules.md (100%) rename docs/guides/stay-up-to-date/cis/{how-to-update-to-cis-14 => cis-1.4.0}/deployment-walkthrough/step-3-manual-steps.md (100%) rename docs/guides/stay-up-to-date/cis/{how-to-update-to-cis-14 => cis-1.4.0}/finally.md (100%) rename docs/guides/stay-up-to-date/cis/{how-to-update-to-cis-14/intro.md => cis-1.4.0/index.md} (84%) create mode 100644 docs/guides/stay-up-to-date/terraform/aws-provider-v3/_category_.json rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-aws-provider-v3 => aws-provider-v3}/core-concepts.md (100%) rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-aws-provider-v3 => aws-provider-v3}/deployment-walkthrough.md (100%) rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-aws-provider-v3/intro.md => aws-provider-v3/index.md} (100%) rename docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/{intro.md => index.md} (100%) create mode 100644 docs/guides/stay-up-to-date/terraform/terraform-1-x/_category_.json create mode 100644 docs/guides/stay-up-to-date/terraform/terraform-1-x/deployment-walkthrough/_category_.json create mode 100644 docs/guides/stay-up-to-date/terraform/terraform-1.x/_category_.json rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-1-x => terraform-1.x}/core-concepts.md (100%) create mode 100644 docs/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/_category_.json rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-1-x => terraform-1.x}/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-15.md (66%) rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-1-x => terraform-1.x}/deployment-walkthrough/step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md (100%) rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-1-x/intro.md => terraform-1.x/index.md} (100%) create mode 100644 docs/guides/stay-up-to-date/terraform/terraform-12/_category_.json rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-12 => terraform-12}/deployment-walkthrough.md (100%) rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-12/intro.md => terraform-12/index.md} (100%) rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-12 => terraform-12}/version-compatibility-table.md (100%) create mode 100644 docs/guides/stay-up-to-date/terraform/terraform-13/_category_.json rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-13 => terraform-13}/core-concepts.md (100%) create mode 100644 docs/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/_category_.json rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-13 => terraform-13}/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12.md (79%) rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-13 => terraform-13}/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-13.md (100%) rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-13 => terraform-13}/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md (100%) rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-13 => terraform-13}/deployment-walkthrough/updating-the-gruntwork-reference-architecture-to-terraform-0-13.md (100%) rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-13/intro.md => terraform-13/index.md} (100%) create mode 100644 docs/guides/stay-up-to-date/terraform/terraform-14/_category_.json rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-14 => terraform-14}/core-concepts.md (100%) create mode 100644 docs/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/_category_.json rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-14 => terraform-14}/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-13.md (79%) rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-14 => terraform-14}/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-14.md (100%) rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-14 => terraform-14}/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md (100%) rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-14 => terraform-14}/deployment-walkthrough/step-4-start-using-lock-files.md (100%) rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-14/intro.md => terraform-14/index.md} (100%) create mode 100644 docs/guides/stay-up-to-date/terraform/terraform-15/_category_.json rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-15 => terraform-15}/core-concepts.md (100%) create mode 100644 docs/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/_category_.json rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-15 => terraform-15}/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-14.md (69%) rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-15 => terraform-15}/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-15.md (100%) rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-15 => terraform-15}/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md (100%) rename docs/guides/stay-up-to-date/terraform/{how-to-update-to-terraform-15/intro.md => terraform-15/index.md} (100%) diff --git a/_docs-sources/guides/build-it-yourself/achieve-compliance/index.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/index.md index a77ff78f64..7adfdef739 100644 --- a/_docs-sources/guides/build-it-yourself/achieve-compliance/index.md +++ b/_docs-sources/guides/build-it-yourself/achieve-compliance/index.md @@ -24,8 +24,8 @@ compliant state over time because all of the infrastructure is defined as code. Previously, we supported versions 1.3.0 and 1.2.0 of the Benchmark. If you are looking to upgrade from an older version please follow these in order: -- To upgrade from v1.2.0 to v1.3.0, please follow [this upgrade guide](../../../stay-up-to-date/cis/how-to-update-to-cis-13/intro.md); -- To upgrade from v1.3.0 to v1.4.0, please follow [this upgrade guide](../../../stay-up-to-date/cis/how-to-update-to-cis-14/intro.md). +- To upgrade from v1.2.0 to v1.3.0, please follow [this upgrade guide](/docs/guides/stay-up-to-date/cis/cis-1.3.0). +- To upgrade from v1.3.0 to v1.4.0, please follow [this upgrade guide](/docs/guides/stay-up-to-date/cis/cis-1.4.0). ![CIS Benchmark Architecture](/img/guides/build-it-yourself/achieve-compliance/cis-account-architecture.png) diff --git a/_docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/storage.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/storage.md index 26cf0f5167..fa5d9f7413 100644 --- a/_docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/storage.md +++ b/_docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/storage.md @@ -65,7 +65,7 @@ The CIS 1.4.0 Benchmark recommends a few additional steps to ensure your data is :::info -The steps below are not the full list of actions needed to configure MFA Delete or Amazon Macie for your account. To follow the steps necessary to configure it according to the CIS 1.4.0 Benchmark, please follow the MFA Delete and Macie section in the [the migration guide to CIS 1.4.0](../../../stay-up-to-date/cis/how-to-update-to-cis-14/intro.md), or the deployment guide section in this guide. +The steps below are not the full list of actions needed to configure MFA Delete or Amazon Macie for your account. To follow the steps necessary to configure it according to the CIS 1.4.0 Benchmark, please follow the MFA Delete and Macie section in the [the migration guide to CIS 1.4.0](/docs/guides/stay-up-to-date/cis/cis-1.4.0), or the deployment guide section in this guide. ::: ### Enable MFA Delete (recommendation 2.1.3) diff --git a/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/_category_.json b/_docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/_category_.json rename to _docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/core-concepts.md b/_docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/core-concepts.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/core-concepts.md rename to _docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/core-concepts.md diff --git a/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/_category_.json b/_docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/_category_.json rename to _docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md b/_docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md rename to _docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md diff --git a/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/step-2-manual-steps.md b/_docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/step-2-manual-steps.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/step-2-manual-steps.md rename to _docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/step-2-manual-steps.md diff --git a/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/step-3-deploy-new-modules.md b/_docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/step-3-deploy-new-modules.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/step-3-deploy-new-modules.md rename to _docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/step-3-deploy-new-modules.md diff --git a/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/intro.md b/_docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/index.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-13/intro.md rename to _docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/index.md diff --git a/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/_category_.json b/_docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/_category_.json rename to _docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/core-concepts.md b/_docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/core-concepts.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/core-concepts.md rename to _docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/core-concepts.md diff --git a/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/_category_.json b/_docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/_category_.json rename to _docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md b/_docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md rename to _docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md diff --git a/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/step-2-update-the-account-baseline-modules.md b/_docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-2-update-the-account-baseline-modules.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/step-2-update-the-account-baseline-modules.md rename to _docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-2-update-the-account-baseline-modules.md diff --git a/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/step-3-manual-steps.md b/_docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-3-manual-steps.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/step-3-manual-steps.md rename to _docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-3-manual-steps.md diff --git a/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/finally.md b/_docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/finally.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/finally.md rename to _docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/finally.md diff --git a/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/intro.md b/_docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/index.md similarity index 90% rename from _docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/intro.md rename to _docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/index.md index 3eff6d3db5..e45c161854 100644 --- a/_docs-sources/guides/stay-up-to-date/cis/how-to-update-to-cis-14/intro.md +++ b/_docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/index.md @@ -23,4 +23,4 @@ CIS AWS Foundations Benchmark. ## Previous versions of this guide -- [How to update to CIS AWS Foundations Benchmark v1.3.0](../how-to-update-to-cis-13/intro.md) +- [How to update to CIS AWS Foundations Benchmark v1.3.0](/docs/guides/stay-up-to-date/cis/cis-1.3.0) diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/aws-provider-v3/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/_category_.json rename to _docs-sources/guides/stay-up-to-date/terraform/aws-provider-v3/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/core-concepts.md b/_docs-sources/guides/stay-up-to-date/terraform/aws-provider-v3/core-concepts.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/core-concepts.md rename to _docs-sources/guides/stay-up-to-date/terraform/aws-provider-v3/core-concepts.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/deployment-walkthrough.md b/_docs-sources/guides/stay-up-to-date/terraform/aws-provider-v3/deployment-walkthrough.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/deployment-walkthrough.md rename to _docs-sources/guides/stay-up-to-date/terraform/aws-provider-v3/deployment-walkthrough.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/intro.md b/_docs-sources/guides/stay-up-to-date/terraform/aws-provider-v3/index.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/intro.md rename to _docs-sources/guides/stay-up-to-date/terraform/aws-provider-v3/index.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/intro.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/index.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/intro.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/index.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/_category_.json rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/core-concepts.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/core-concepts.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/core-concepts.md rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/core-concepts.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/deployment-walkthrough/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/deployment-walkthrough/_category_.json rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-15.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-15.md similarity index 69% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-15.md rename to _docs-sources/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 5b8fd4ccfe..2bc5fd93f4 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-15.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-15.md @@ -10,16 +10,16 @@ If you haven’t already, you need to: 0.15.0 or above first! 1. If you’re still on Terraform 0.11 or older, see our - [Terraform 0.12 upgrade guide](../../how-to-update-to-terraform-12/intro.md). + [Terraform 0.12 upgrade guide](../../terraform-12). 2. If you’re still on Terraform 0.12, see our - [Terraform 0.13 upgrade guide](../../how-to-update-to-terraform-13/intro.md). + [Terraform 0.13 upgrade guide](../../terraform-13). 3. If you’re still on Terraform 0.13, see our - [Terraform 0.14 upgrade guide](../../how-to-update-to-terraform-14/intro.md). + [Terraform 0.14 upgrade guide](../../terraform-14). 4. If you’re still on Terraform 0.14, see our - [Terraform 0.15 upgrade guide](../../how-to-update-to-terraform-15/intro.md). + [Terraform 0.15 upgrade guide](../../terraform-15). 2. Update all your Gruntwork modules to the latest versions just _before_ the TF 1.x versions in the compatibility table below. The upgrade will be much easier and less error prone if you keep the number of version jumps as small diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/deployment-walkthrough/step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/deployment-walkthrough/step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/intro.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/index.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/intro.md rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/index.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/terraform-12/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/_category_.json rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-12/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/deployment-walkthrough.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-12/deployment-walkthrough.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/deployment-walkthrough.md rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-12/deployment-walkthrough.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/intro.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-12/index.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/intro.md rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-12/index.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/version-compatibility-table.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-12/version-compatibility-table.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/version-compatibility-table.md rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-12/version-compatibility-table.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/_category_.json rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-13/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/core-concepts.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/core-concepts.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/core-concepts.md rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-13/core-concepts.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/_category_.json rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12.md similarity index 86% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12.md rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12.md index 5e06d311fa..1ac10e2252 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12.md @@ -9,7 +9,7 @@ If you haven’t already, you need to: 1. Update your code to work with Terraform 0.12. Do NOT skip from, say, 0.11, straight to 0.13. You MUST update to 0.12.26 or above first! If you’re still on Terraform 0.11 or older, see our - [Terraform 0.12 upgrade guide](../../how-to-update-to-terraform-12/intro.md) for instructions. + [Terraform 0.12 upgrade guide](../../terraform-12) for instructions. 2. Update all your Gruntwork modules to the latest versions just _before_ the TF 0.13 versions in the compatibility table below. The upgrade will be much easier and less error prone if you keep the number of version jumps as small diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-13.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-13.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-13.md rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-13.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/updating-the-gruntwork-reference-architecture-to-terraform-0-13.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/updating-the-gruntwork-reference-architecture-to-terraform-0-13.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/updating-the-gruntwork-reference-architecture-to-terraform-0-13.md rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/updating-the-gruntwork-reference-architecture-to-terraform-0-13.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/intro.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/index.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/intro.md rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-13/index.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/_category_.json rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-14/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/core-concepts.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/core-concepts.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/core-concepts.md rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-14/core-concepts.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/_category_.json rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-13.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-13.md similarity index 85% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-13.md rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-13.md index 7c20745988..aa9a7c2f38 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-13.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-13.md @@ -9,10 +9,10 @@ If you haven’t already, you need to: 1. Update your code to work with Terraform 0.13. Do NOT skip from, say, 0.11, straight to 0.14. You MUST update to 0.13.0 or above first! If you’re still on Terraform 0.11 or older, see our [Terraform 0.12 upgrade - guide](../../how-to-update-to-terraform-12/intro.md) for + guide](../../terraform-12) for instructions. If you’re still on Terraform 0.12, see our [Terraform 0.13 upgrade - guide](../../how-to-update-to-terraform-13/intro.md). + guide](../../terraform-13). 2. Update all your Gruntwork modules to the latest versions just _before_ the TF 0.14 versions in the compatibility table below. The upgrade will be much diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-14.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-14.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-14.md rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-14.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-4-start-using-lock-files.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-4-start-using-lock-files.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-4-start-using-lock-files.md rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-4-start-using-lock-files.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/intro.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/index.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/intro.md rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-14/index.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/terraform-15/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/_category_.json rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-15/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/core-concepts.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-15/core-concepts.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/core-concepts.md rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-15/core-concepts.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/_category_.json similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/_category_.json rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-14.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-14.md similarity index 73% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-14.md rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-14.md index 7d7a2caa4c..42acfacd54 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-14.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-14.md @@ -10,13 +10,13 @@ If you haven’t already, you need to: 0.14.0 or above first! 1. If you’re still on Terraform 0.11 or older, see our - [Terraform 0.12 upgrade guide](../../how-to-update-to-terraform-12/intro.md). + [Terraform 0.12 upgrade guide](../../terraform-12). 2. If you’re still on Terraform 0.12, see our - [Terraform 0.13 upgrade guide](../../how-to-update-to-terraform-13/intro.md). + [Terraform 0.13 upgrade guide](../../terraform-13). 3. If you’re still on Terraform 0.13, see our - [Terraform 0.14 upgrade guide](../../how-to-update-to-terraform-14/intro.md). + [Terraform 0.14 upgrade guide](../../terraform-14). 2. Update all your Gruntwork modules to the latest versions just _before_ the TF 0.15 versions in the compatibility table below. The upgrade will be much easier and less error prone if you keep the number of version jumps as small diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-15.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-15.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-15.md rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-15.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/intro.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-15/index.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/intro.md rename to _docs-sources/guides/stay-up-to-date/terraform/terraform-15/index.md diff --git a/_docs-sources/guides/welcome.md b/_docs-sources/guides/welcome.md index 3ca459fad5..a339f41a36 100644 --- a/_docs-sources/guides/welcome.md +++ b/_docs-sources/guides/welcome.md @@ -41,32 +41,32 @@ The Gruntwork IaC library empowers you to construct your own bespoke architectur Set up a multi-account structure using Gruntwork Landing Zone. Implement continuous deployment for your infrastructure code with Gruntwork Pipelines. Set up your network according to industry best practices using our VPC service. Deploy a Kubernetes Cluster to host all of your apps and services. Make your infrastructure compliant with the CIS AWS Foundations Benchmark. @@ -91,27 +91,29 @@ The Gruntwork IaC library empowers you to construct your own bespoke architectur ## Stay Up to Date -
-### CIS AWS Foundations Benchmark + -- [Update to version 1.4.0](#) -- [Update to version 1.3.0](#) +### Terraform -
-
+- [Update to version 1.X](/docs/guides/stay-up-to-date/terraform/terraform-1.x) +- [Update to Terraform 15](/docs/guides/stay-up-to-date/terraform/terraform-15) +- [Update to Terraform 14](/docs/guides/stay-up-to-date/terraform/terraform-14) +- [Update to Terraform 13](/docs/guides/stay-up-to-date/terraform/terraform-13) +- [Update to Terraform 12](/docs/guides/stay-up-to-date/terraform/terraform-12) +- [Update to Version 3 of the Terraform provider](/docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3) +- [DRY your Reference Architecture](/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture) -### Terraform + + + +### CIS AWS Foundations Benchmark + +- [Update to version 1.4.0](/docs/guides/stay-up-to-date/cis/cis-1.4.0) +- [Update to version 1.3.0](/docs/guides/stay-up-to-date/cis/cis-1.3.0) -- [Update to version 1.X](#) -- [Update to Terraform 15](#) -- [Update to Terraform 14](#) -- [Update to Terraform 13](#) -- [Update to Terraform 12](#) -- [Update to Version 3 of the Terraform provider](#) -- [DRY your Reference Architecture](#) + -
diff --git a/docs/guides/build-it-yourself/achieve-compliance/index.md b/docs/guides/build-it-yourself/achieve-compliance/index.md index 8a3cb15301..d29f1f06d5 100644 --- a/docs/guides/build-it-yourself/achieve-compliance/index.md +++ b/docs/guides/build-it-yourself/achieve-compliance/index.md @@ -24,8 +24,8 @@ compliant state over time because all of the infrastructure is defined as code. Previously, we supported versions 1.3.0 and 1.2.0 of the Benchmark. If you are looking to upgrade from an older version please follow these in order: -- To upgrade from v1.2.0 to v1.3.0, please follow [this upgrade guide](../../../stay-up-to-date/cis/how-to-update-to-cis-13/intro.md); -- To upgrade from v1.3.0 to v1.4.0, please follow [this upgrade guide](../../../stay-up-to-date/cis/how-to-update-to-cis-14/intro.md). +- To upgrade from v1.2.0 to v1.3.0, please follow [this upgrade guide](/docs/guides/stay-up-to-date/cis/cis-1.3.0). +- To upgrade from v1.3.0 to v1.4.0, please follow [this upgrade guide](/docs/guides/stay-up-to-date/cis/cis-1.4.0). ![CIS Benchmark Architecture](/img/guides/build-it-yourself/achieve-compliance/cis-account-architecture.png) @@ -69,5 +69,5 @@ walkthrough. 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 d6e12dd4f7..15c4ae87c5 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 @@ -65,7 +65,7 @@ The CIS 1.4.0 Benchmark recommends a few additional steps to ensure your data is :::info -The steps below are not the full list of actions needed to configure MFA Delete or Amazon Macie for your account. To follow the steps necessary to configure it according to the CIS 1.4.0 Benchmark, please follow the MFA Delete and Macie section in the [the migration guide to CIS 1.4.0](../../../stay-up-to-date/cis/how-to-update-to-cis-14/intro.md), or the deployment guide section in this guide. +The steps below are not the full list of actions needed to configure MFA Delete or Amazon Macie for your account. To follow the steps necessary to configure it according to the CIS 1.4.0 Benchmark, please follow the MFA Delete and Macie section in the [the migration guide to CIS 1.4.0](/docs/guides/stay-up-to-date/cis/cis-1.4.0), or the deployment guide section in this guide. ::: ### Enable MFA Delete (recommendation 2.1.3) @@ -138,5 +138,5 @@ explicit list of buckets per region, namely in the variable `buckets_to_analyze` diff --git a/docs/guides/stay-up-to-date/cis/cis-1-3-0/_category_.json b/docs/guides/stay-up-to-date/cis/cis-1-3-0/_category_.json new file mode 100644 index 0000000000..cb66bc8600 --- /dev/null +++ b/docs/guides/stay-up-to-date/cis/cis-1-3-0/_category_.json @@ -0,0 +1,3 @@ +{ + "label": "Update to CIS AWS Foundations Benchmark 1.3.0" +} diff --git a/docs/guides/stay-up-to-date/cis/cis-1-3-0/deployment-walkthrough/_category_.json b/docs/guides/stay-up-to-date/cis/cis-1-3-0/deployment-walkthrough/_category_.json new file mode 100644 index 0000000000..cd05330845 --- /dev/null +++ b/docs/guides/stay-up-to-date/cis/cis-1-3-0/deployment-walkthrough/_category_.json @@ -0,0 +1,3 @@ +{ +"label": "Deployment walkthrough" +} \ No newline at end of file diff --git a/docs/guides/stay-up-to-date/cis/cis-1-4-0/_category_.json b/docs/guides/stay-up-to-date/cis/cis-1-4-0/_category_.json new file mode 100644 index 0000000000..7a77f0ec6e --- /dev/null +++ b/docs/guides/stay-up-to-date/cis/cis-1-4-0/_category_.json @@ -0,0 +1,3 @@ +{ + "label": "Update to CIS AWS Foundations Benchmark 1.4.0" +} diff --git a/docs/guides/stay-up-to-date/cis/cis-1-4-0/deployment-walkthrough/_category_.json b/docs/guides/stay-up-to-date/cis/cis-1-4-0/deployment-walkthrough/_category_.json new file mode 100644 index 0000000000..cd05330845 --- /dev/null +++ b/docs/guides/stay-up-to-date/cis/cis-1-4-0/deployment-walkthrough/_category_.json @@ -0,0 +1,3 @@ +{ +"label": "Deployment walkthrough" +} \ No newline at end of file diff --git a/docs/guides/stay-up-to-date/cis/cis-1.3.0/_category_.json b/docs/guides/stay-up-to-date/cis/cis-1.3.0/_category_.json new file mode 100644 index 0000000000..cb66bc8600 --- /dev/null +++ b/docs/guides/stay-up-to-date/cis/cis-1.3.0/_category_.json @@ -0,0 +1,3 @@ +{ + "label": "Update to CIS AWS Foundations Benchmark 1.3.0" +} diff --git a/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/core-concepts.md b/docs/guides/stay-up-to-date/cis/cis-1.3.0/core-concepts.md similarity index 100% rename from docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/core-concepts.md rename to docs/guides/stay-up-to-date/cis/cis-1.3.0/core-concepts.md diff --git a/docs/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/_category_.json b/docs/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/_category_.json new file mode 100644 index 0000000000..cd05330845 --- /dev/null +++ b/docs/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/_category_.json @@ -0,0 +1,3 @@ +{ +"label": "Deployment walkthrough" +} \ No newline at end of file diff --git a/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/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 similarity index 100% rename from docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md rename to 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 diff --git a/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/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 similarity index 100% rename from docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/step-2-manual-steps.md rename to docs/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/step-2-manual-steps.md diff --git a/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/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 similarity index 100% rename from docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/deployment-walkthrough/step-3-deploy-new-modules.md rename to docs/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/step-3-deploy-new-modules.md diff --git a/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/intro.md b/docs/guides/stay-up-to-date/cis/cis-1.3.0/index.md similarity index 100% rename from docs/guides/stay-up-to-date/cis/how-to-update-to-cis-13/intro.md rename to docs/guides/stay-up-to-date/cis/cis-1.3.0/index.md diff --git a/docs/guides/stay-up-to-date/cis/cis-1.4.0/_category_.json b/docs/guides/stay-up-to-date/cis/cis-1.4.0/_category_.json new file mode 100644 index 0000000000..7a77f0ec6e --- /dev/null +++ b/docs/guides/stay-up-to-date/cis/cis-1.4.0/_category_.json @@ -0,0 +1,3 @@ +{ + "label": "Update to CIS AWS Foundations Benchmark 1.4.0" +} diff --git a/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/core-concepts.md b/docs/guides/stay-up-to-date/cis/cis-1.4.0/core-concepts.md similarity index 100% rename from docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/core-concepts.md rename to docs/guides/stay-up-to-date/cis/cis-1.4.0/core-concepts.md diff --git a/docs/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/_category_.json b/docs/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/_category_.json new file mode 100644 index 0000000000..cd05330845 --- /dev/null +++ b/docs/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/_category_.json @@ -0,0 +1,3 @@ +{ +"label": "Deployment walkthrough" +} \ No newline at end of file diff --git a/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/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 similarity index 100% rename from docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library.md rename to 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 diff --git a/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/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 similarity index 100% rename from docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/step-2-update-the-account-baseline-modules.md rename to docs/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-2-update-the-account-baseline-modules.md diff --git a/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/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 similarity index 100% rename from docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/deployment-walkthrough/step-3-manual-steps.md rename to docs/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-3-manual-steps.md diff --git a/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/finally.md b/docs/guides/stay-up-to-date/cis/cis-1.4.0/finally.md similarity index 100% rename from docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/finally.md rename to docs/guides/stay-up-to-date/cis/cis-1.4.0/finally.md diff --git a/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/intro.md b/docs/guides/stay-up-to-date/cis/cis-1.4.0/index.md similarity index 84% rename from docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/intro.md rename to docs/guides/stay-up-to-date/cis/cis-1.4.0/index.md index 5f889d9cd5..9715d14d7b 100644 --- a/docs/guides/stay-up-to-date/cis/how-to-update-to-cis-14/intro.md +++ b/docs/guides/stay-up-to-date/cis/cis-1.4.0/index.md @@ -23,9 +23,9 @@ CIS AWS Foundations Benchmark. ## Previous versions of this guide -- [How to update to CIS AWS Foundations Benchmark v1.3.0](../how-to-update-to-cis-13/intro.md) +- [How to update to CIS AWS Foundations Benchmark v1.3.0](/docs/guides/stay-up-to-date/cis/cis-1.3.0) diff --git a/docs/guides/stay-up-to-date/terraform/aws-provider-v3/_category_.json b/docs/guides/stay-up-to-date/terraform/aws-provider-v3/_category_.json new file mode 100644 index 0000000000..677d069476 --- /dev/null +++ b/docs/guides/stay-up-to-date/terraform/aws-provider-v3/_category_.json @@ -0,0 +1,3 @@ +{ + "label": "Update to version 3 of the Terraform AWS Provider" +} 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/aws-provider-v3/core-concepts.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/core-concepts.md rename to docs/guides/stay-up-to-date/terraform/aws-provider-v3/core-concepts.md 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/aws-provider-v3/deployment-walkthrough.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/deployment-walkthrough.md rename to docs/guides/stay-up-to-date/terraform/aws-provider-v3/deployment-walkthrough.md diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/intro.md b/docs/guides/stay-up-to-date/terraform/aws-provider-v3/index.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/intro.md rename to docs/guides/stay-up-to-date/terraform/aws-provider-v3/index.md diff --git a/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/intro.md b/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/index.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/intro.md rename to docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/index.md diff --git a/docs/guides/stay-up-to-date/terraform/terraform-1-x/_category_.json b/docs/guides/stay-up-to-date/terraform/terraform-1-x/_category_.json new file mode 100644 index 0000000000..23c92784be --- /dev/null +++ b/docs/guides/stay-up-to-date/terraform/terraform-1-x/_category_.json @@ -0,0 +1,3 @@ +{ + "label": "Update to Terraform v1.x" +} diff --git a/docs/guides/stay-up-to-date/terraform/terraform-1-x/deployment-walkthrough/_category_.json b/docs/guides/stay-up-to-date/terraform/terraform-1-x/deployment-walkthrough/_category_.json new file mode 100644 index 0000000000..ba7669c6f8 --- /dev/null +++ b/docs/guides/stay-up-to-date/terraform/terraform-1-x/deployment-walkthrough/_category_.json @@ -0,0 +1,3 @@ +{ + "label": "Deployment Walkthrough" +} diff --git a/docs/guides/stay-up-to-date/terraform/terraform-1.x/_category_.json b/docs/guides/stay-up-to-date/terraform/terraform-1.x/_category_.json new file mode 100644 index 0000000000..23c92784be --- /dev/null +++ b/docs/guides/stay-up-to-date/terraform/terraform-1.x/_category_.json @@ -0,0 +1,3 @@ +{ + "label": "Update to Terraform v1.x" +} diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/core-concepts.md b/docs/guides/stay-up-to-date/terraform/terraform-1.x/core-concepts.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/core-concepts.md rename to docs/guides/stay-up-to-date/terraform/terraform-1.x/core-concepts.md diff --git a/docs/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/_category_.json b/docs/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/_category_.json new file mode 100644 index 0000000000..ba7669c6f8 --- /dev/null +++ b/docs/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/_category_.json @@ -0,0 +1,3 @@ +{ + "label": "Deployment Walkthrough" +} diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-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 similarity index 66% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-15.md rename to 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 b1aa7dade9..7d597f5167 100644 --- a/docs/guides/stay-up-to-date/terraform/how-to-update-to-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 @@ -10,16 +10,16 @@ If you haven’t already, you need to: 0.15.0 or above first! 1. If you’re still on Terraform 0.11 or older, see our - [Terraform 0.12 upgrade guide](../../how-to-update-to-terraform-12/intro.md). + [Terraform 0.12 upgrade guide](../../terraform-12). 2. If you’re still on Terraform 0.12, see our - [Terraform 0.13 upgrade guide](../../how-to-update-to-terraform-13/intro.md). + [Terraform 0.13 upgrade guide](../../terraform-13). 3. If you’re still on Terraform 0.13, see our - [Terraform 0.14 upgrade guide](../../how-to-update-to-terraform-14/intro.md). + [Terraform 0.14 upgrade guide](../../terraform-14). 4. If you’re still on Terraform 0.14, see our - [Terraform 0.15 upgrade guide](../../how-to-update-to-terraform-15/intro.md). + [Terraform 0.15 upgrade guide](../../terraform-15). 2. Update all your Gruntwork modules to the latest versions just _before_ the TF 1.x versions in the compatibility table below. The upgrade will be much easier and less error prone if you keep the number of version jumps as small @@ -27,5 +27,5 @@ If you haven’t already, you need to: diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-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 similarity index 100% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/deployment-walkthrough/step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md rename to docs/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/intro.md b/docs/guides/stay-up-to-date/terraform/terraform-1.x/index.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-1-x/intro.md rename to docs/guides/stay-up-to-date/terraform/terraform-1.x/index.md diff --git a/docs/guides/stay-up-to-date/terraform/terraform-12/_category_.json b/docs/guides/stay-up-to-date/terraform/terraform-12/_category_.json new file mode 100644 index 0000000000..5ed587e81d --- /dev/null +++ b/docs/guides/stay-up-to-date/terraform/terraform-12/_category_.json @@ -0,0 +1,3 @@ +{ + "label": "Update to Terraform 12" +} diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/deployment-walkthrough.md b/docs/guides/stay-up-to-date/terraform/terraform-12/deployment-walkthrough.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/deployment-walkthrough.md rename to docs/guides/stay-up-to-date/terraform/terraform-12/deployment-walkthrough.md diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/intro.md b/docs/guides/stay-up-to-date/terraform/terraform-12/index.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/intro.md rename to docs/guides/stay-up-to-date/terraform/terraform-12/index.md diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/version-compatibility-table.md b/docs/guides/stay-up-to-date/terraform/terraform-12/version-compatibility-table.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-12/version-compatibility-table.md rename to docs/guides/stay-up-to-date/terraform/terraform-12/version-compatibility-table.md diff --git a/docs/guides/stay-up-to-date/terraform/terraform-13/_category_.json b/docs/guides/stay-up-to-date/terraform/terraform-13/_category_.json new file mode 100644 index 0000000000..2432efa6b6 --- /dev/null +++ b/docs/guides/stay-up-to-date/terraform/terraform-13/_category_.json @@ -0,0 +1,3 @@ +{ + "label": "Update to Terraform 13" +} diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/core-concepts.md b/docs/guides/stay-up-to-date/terraform/terraform-13/core-concepts.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/core-concepts.md rename to docs/guides/stay-up-to-date/terraform/terraform-13/core-concepts.md diff --git a/docs/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/_category_.json b/docs/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/_category_.json new file mode 100644 index 0000000000..ba7669c6f8 --- /dev/null +++ b/docs/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/_category_.json @@ -0,0 +1,3 @@ +{ + "label": "Deployment Walkthrough" +} diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-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 similarity index 79% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12.md rename to 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 27a3d4374f..c32a81f249 100644 --- a/docs/guides/stay-up-to-date/terraform/how-to-update-to-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 @@ -9,7 +9,7 @@ If you haven’t already, you need to: 1. Update your code to work with Terraform 0.12. Do NOT skip from, say, 0.11, straight to 0.13. You MUST update to 0.12.26 or above first! If you’re still on Terraform 0.11 or older, see our - [Terraform 0.12 upgrade guide](../../how-to-update-to-terraform-12/intro.md) for instructions. + [Terraform 0.12 upgrade guide](../../terraform-12) for instructions. 2. Update all your Gruntwork modules to the latest versions just _before_ the TF 0.13 versions in the compatibility table below. The upgrade will be much easier and less error prone if you keep the number of version jumps as small @@ -17,5 +17,5 @@ If you haven’t already, you need to: diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-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 similarity index 100% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-13.md rename to docs/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-13.md diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-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 similarity index 100% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md rename to docs/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-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 similarity index 100% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/deployment-walkthrough/updating-the-gruntwork-reference-architecture-to-terraform-0-13.md rename to docs/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/updating-the-gruntwork-reference-architecture-to-terraform-0-13.md diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/intro.md b/docs/guides/stay-up-to-date/terraform/terraform-13/index.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-13/intro.md rename to docs/guides/stay-up-to-date/terraform/terraform-13/index.md diff --git a/docs/guides/stay-up-to-date/terraform/terraform-14/_category_.json b/docs/guides/stay-up-to-date/terraform/terraform-14/_category_.json new file mode 100644 index 0000000000..7cc0760acf --- /dev/null +++ b/docs/guides/stay-up-to-date/terraform/terraform-14/_category_.json @@ -0,0 +1,3 @@ +{ + "label": "Update to Terraform 14" +} diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/core-concepts.md b/docs/guides/stay-up-to-date/terraform/terraform-14/core-concepts.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/core-concepts.md rename to docs/guides/stay-up-to-date/terraform/terraform-14/core-concepts.md diff --git a/docs/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/_category_.json b/docs/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/_category_.json new file mode 100644 index 0000000000..ba7669c6f8 --- /dev/null +++ b/docs/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/_category_.json @@ -0,0 +1,3 @@ +{ + "label": "Deployment Walkthrough" +} diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-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 similarity index 79% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-13.md rename to 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 779755568d..d50a611fe8 100644 --- a/docs/guides/stay-up-to-date/terraform/how-to-update-to-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 @@ -9,10 +9,10 @@ If you haven’t already, you need to: 1. Update your code to work with Terraform 0.13. Do NOT skip from, say, 0.11, straight to 0.14. You MUST update to 0.13.0 or above first! If you’re still on Terraform 0.11 or older, see our [Terraform 0.12 upgrade - guide](../../how-to-update-to-terraform-12/intro.md) for + guide](../../terraform-12) for instructions. If you’re still on Terraform 0.12, see our [Terraform 0.13 upgrade - guide](../../how-to-update-to-terraform-13/intro.md). + guide](../../terraform-13). 2. Update all your Gruntwork modules to the latest versions just _before_ the TF 0.14 versions in the compatibility table below. The upgrade will be much @@ -21,5 +21,5 @@ If you haven’t already, you need to: diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-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 similarity index 100% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-14.md rename to docs/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-14.md diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-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 similarity index 100% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md rename to docs/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-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 similarity index 100% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/deployment-walkthrough/step-4-start-using-lock-files.md rename to docs/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-4-start-using-lock-files.md diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/intro.md b/docs/guides/stay-up-to-date/terraform/terraform-14/index.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-14/intro.md rename to docs/guides/stay-up-to-date/terraform/terraform-14/index.md diff --git a/docs/guides/stay-up-to-date/terraform/terraform-15/_category_.json b/docs/guides/stay-up-to-date/terraform/terraform-15/_category_.json new file mode 100644 index 0000000000..a56d0299bc --- /dev/null +++ b/docs/guides/stay-up-to-date/terraform/terraform-15/_category_.json @@ -0,0 +1,3 @@ +{ + "label": "Update to Terraform 15" +} diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/core-concepts.md b/docs/guides/stay-up-to-date/terraform/terraform-15/core-concepts.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/core-concepts.md rename to docs/guides/stay-up-to-date/terraform/terraform-15/core-concepts.md diff --git a/docs/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/_category_.json b/docs/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/_category_.json new file mode 100644 index 0000000000..ba7669c6f8 --- /dev/null +++ b/docs/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/_category_.json @@ -0,0 +1,3 @@ +{ + "label": "Deployment Walkthrough" +} diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-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 similarity index 69% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-14.md rename to 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 afd97aedae..ea7865c4d6 100644 --- a/docs/guides/stay-up-to-date/terraform/how-to-update-to-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 @@ -10,13 +10,13 @@ If you haven’t already, you need to: 0.14.0 or above first! 1. If you’re still on Terraform 0.11 or older, see our - [Terraform 0.12 upgrade guide](../../how-to-update-to-terraform-12/intro.md). + [Terraform 0.12 upgrade guide](../../terraform-12). 2. If you’re still on Terraform 0.12, see our - [Terraform 0.13 upgrade guide](../../how-to-update-to-terraform-13/intro.md). + [Terraform 0.13 upgrade guide](../../terraform-13). 3. If you’re still on Terraform 0.13, see our - [Terraform 0.14 upgrade guide](../../how-to-update-to-terraform-14/intro.md). + [Terraform 0.14 upgrade guide](../../terraform-14). 2. Update all your Gruntwork modules to the latest versions just _before_ the TF 0.15 versions in the compatibility table below. The upgrade will be much easier and less error prone if you keep the number of version jumps as small @@ -24,5 +24,5 @@ If you haven’t already, you need to: diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-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 similarity index 100% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-15.md rename to docs/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-15.md diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-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 similarity index 100% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md rename to docs/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library.md diff --git a/docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/intro.md b/docs/guides/stay-up-to-date/terraform/terraform-15/index.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/how-to-update-to-terraform-15/intro.md rename to docs/guides/stay-up-to-date/terraform/terraform-15/index.md diff --git a/docs/guides/welcome.md b/docs/guides/welcome.md index 2635a13e2d..38410f6f1f 100644 --- a/docs/guides/welcome.md +++ b/docs/guides/welcome.md @@ -41,32 +41,32 @@ The Gruntwork IaC library empowers you to construct your own bespoke architectur Set up a multi-account structure using Gruntwork Landing Zone. Implement continuous deployment for your infrastructure code with Gruntwork Pipelines. Set up your network according to industry best practices using our VPC service. Deploy a Kubernetes Cluster to host all of your apps and services. Make your infrastructure compliant with the CIS AWS Foundations Benchmark. @@ -91,32 +91,34 @@ The Gruntwork IaC library empowers you to construct your own bespoke architectur ## Stay Up to Date -
-### CIS AWS Foundations Benchmark + -- [Update to version 1.4.0](#) -- [Update to version 1.3.0](#) +### Terraform -
-
+- [Update to version 1.X](/docs/guides/stay-up-to-date/terraform/terraform-1.x) +- [Update to Terraform 15](/docs/guides/stay-up-to-date/terraform/terraform-15) +- [Update to Terraform 14](/docs/guides/stay-up-to-date/terraform/terraform-14) +- [Update to Terraform 13](/docs/guides/stay-up-to-date/terraform/terraform-13) +- [Update to Terraform 12](/docs/guides/stay-up-to-date/terraform/terraform-12) +- [Update to Version 3 of the Terraform provider](/docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3) +- [DRY your Reference Architecture](/docs/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture) -### Terraform + + + +### CIS AWS Foundations Benchmark + +- [Update to version 1.4.0](/docs/guides/stay-up-to-date/cis/cis-1.4.0) +- [Update to version 1.3.0](/docs/guides/stay-up-to-date/cis/cis-1.3.0) -- [Update to version 1.X](#) -- [Update to Terraform 15](#) -- [Update to Terraform 14](#) -- [Update to Terraform 13](#) -- [Update to Terraform 12](#) -- [Update to Version 3 of the Terraform provider](#) -- [DRY your Reference Architecture](#) + -
diff --git a/src/pages/index.tsx b/src/pages/index.tsx index 4950f204de..17b0888ed3 100644 --- a/src/pages/index.tsx +++ b/src/pages/index.tsx @@ -67,35 +67,35 @@ export default function Home(): JSX.Element { Streamline how you create, configure, and secure your AWS accounts using Gruntwork Landing Zone. Use your preferred CI tool to set up an end‑to‑end pipeline for your infrastructure code. Set up your network according to industry best practices using our VPC service. Deploy Kubernetes using EKS to host all of your apps and services. Implement the CIS AWS Foundations Benchmark using our curated collection of modules and services. From ef02762b76a257681fec716740ebe68a7e31a8b4 Mon Sep 17 00:00:00 2001 From: Eben Eliason Date: Wed, 12 Jan 2022 16:38:06 -0800 Subject: [PATCH 11/20] Bootstrap the update guides sidebars --- sidebars.js | 2 + sidebars/update-guides.js | 88 +++++++++++++++++++++++++++++++++++++++ 2 files changed, 90 insertions(+) create mode 100644 sidebars/update-guides.js diff --git a/sidebars.js b/sidebars.js index f48e5d74e2..126cdd3102 100644 --- a/sidebars.js +++ b/sidebars.js @@ -16,6 +16,7 @@ const pipelineSidebar = require("./sidebars/pipelines-guide.js") const vpcSidebar = require("./sidebars/vpc-guide.js") const kubernetesSidebar = require("./sidebars/kubernetes-guide.js") const complianceSidebar = require("./sidebars/compliance-guide.js") +const updateGuideSidebars = require("./sidebars/update-guides.js") const apiSidebars = require("./sidebars/api-reference.js") // @ts-check @@ -29,6 +30,7 @@ const sidebars = { vpcSidebar, kubernetesSidebar, complianceSidebar, + ...updateGuideSidebars, ...apiSidebars, } diff --git a/sidebars/update-guides.js b/sidebars/update-guides.js new file mode 100644 index 0000000000..a46f458329 --- /dev/null +++ b/sidebars/update-guides.js @@ -0,0 +1,88 @@ +const updateGuideSidebars = { + cis130: [ + { + label: "CIS 1.3.0 Update Guide", + type: "category", + link: { + type: "doc", + id: "guides/stay-up-to-date/cis/cis-1.3.0/index", + }, + items: [ + "guides/stay-up-to-date/cis/cis-1.3.0/core-concepts", + { + "Deployment Walkthrough": [ + "guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library", + "guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/step-2-manual-steps", + "guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/step-3-deploy-new-modules", + ], + }, + ], + }, + ], + cis140: [ + { + label: "CIS 1.4.0 Update Guide", + type: "category", + link: { + type: "doc", + id: "guides/stay-up-to-date/cis/cis-1.4.0/index", + }, + items: [ + "guides/stay-up-to-date/cis/cis-1.4.0/core-concepts", + { + "Deployment Walkthrough": [ + "guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-1-update-references-to-the-gruntwork-infrastructure-as-code-library", + "guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-2-update-the-account-baseline-modules", + "guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-3-manual-steps", + ], + }, + "guides/stay-up-to-date/cis/cis-1.4.0/finally", + ], + }, + ], + terraform12: [ + { + type: "autogenerated", + dirName: "guides/stay-up-to-date/terraform/terraform-12", + }, + ], + terraform13: [ + { + type: "autogenerated", + dirName: "guides/stay-up-to-date/terraform/terraform-13", + }, + ], + terraform14: [ + { + type: "autogenerated", + dirName: "guides/stay-up-to-date/terraform/terraform-14", + }, + ], + terraform15: [ + { + type: "autogenerated", + dirName: "guides/stay-up-to-date/terraform/terraform-15", + }, + ], + terraform1x: [ + { + type: "autogenerated", + dirName: "guides/stay-up-to-date/terraform/terraform-1.x", + }, + ], + terraformServiceProviderV3: [ + { + type: "autogenerated", + dirName: "guides/stay-up-to-date/terraform/aws-provider-v3", + }, + ], + dryRefArch: [ + { + type: "autogenerated", + dirName: + "guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture", + }, + ], +} + +module.exports = updateGuideSidebars From ffc6956882db481d800b978719548b5a267b8655 Mon Sep 17 00:00:00 2001 From: Eben Eliason Date: Wed, 12 Jan 2022 17:06:44 -0800 Subject: [PATCH 12/20] More update guide sidebar work --- .../stay-up-to-date/cis/_category_.json | 3 -- .../cis/cis-1.3.0/_category_.json | 3 -- .../deployment-walkthrough/_category_.json | 3 -- .../cis/cis-1.4.0/_category_.json | 3 -- .../deployment-walkthrough/_category_.json | 3 -- .../stay-up-to-date/terraform/_category_.json | 3 -- .../terraform/aws-provider-v3/_category_.json | 3 -- .../terraform/aws-provider-v3/index.md | 6 +--- .../_category_.json | 3 -- .../deployment-walkthrough/_category_.json | 3 -- .../index.md | 6 +--- .../terraform/terraform-1.x/_category_.json | 3 -- .../deployment-walkthrough/_category_.json | 3 -- .../terraform/terraform-1.x/index.md | 6 +--- .../terraform/terraform-12/_category_.json | 3 -- .../terraform/terraform-12/index.md | 2 +- .../terraform/terraform-13/_category_.json | 3 -- .../deployment-walkthrough/_category_.json | 3 -- .../terraform/terraform-13/index.md | 6 +--- .../terraform/terraform-14/_category_.json | 3 -- .../deployment-walkthrough/_category_.json | 3 -- .../terraform/terraform-14/index.md | 6 +--- .../terraform/terraform-15/_category_.json | 3 -- .../deployment-walkthrough/_category_.json | 3 -- .../terraform/terraform-15/index.md | 6 +--- .../terraform/aws-provider-v3/index.md | 8 ++--- .../index.md | 8 ++--- .../terraform/terraform-1.x/index.md | 8 ++--- .../terraform/terraform-12/index.md | 4 +-- .../terraform/terraform-13/index.md | 8 ++--- .../terraform/terraform-14/index.md | 8 ++--- .../terraform/terraform-15/index.md | 8 ++--- sidebars/update-guides.js | 31 ++++++++++++++++--- 33 files changed, 48 insertions(+), 127 deletions(-) delete mode 100644 _docs-sources/guides/stay-up-to-date/cis/_category_.json delete mode 100644 _docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/_category_.json delete mode 100644 _docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/_category_.json delete mode 100644 _docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/_category_.json delete mode 100644 _docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/_category_.json delete mode 100644 _docs-sources/guides/stay-up-to-date/terraform/_category_.json delete mode 100644 _docs-sources/guides/stay-up-to-date/terraform/aws-provider-v3/_category_.json delete mode 100644 _docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/_category_.json delete mode 100644 _docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/_category_.json delete mode 100644 _docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/_category_.json delete mode 100644 _docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/_category_.json delete mode 100644 _docs-sources/guides/stay-up-to-date/terraform/terraform-12/_category_.json delete mode 100644 _docs-sources/guides/stay-up-to-date/terraform/terraform-13/_category_.json delete mode 100644 _docs-sources/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/_category_.json delete mode 100644 _docs-sources/guides/stay-up-to-date/terraform/terraform-14/_category_.json delete mode 100644 _docs-sources/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/_category_.json delete mode 100644 _docs-sources/guides/stay-up-to-date/terraform/terraform-15/_category_.json delete mode 100644 _docs-sources/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/_category_.json diff --git a/_docs-sources/guides/stay-up-to-date/cis/_category_.json b/_docs-sources/guides/stay-up-to-date/cis/_category_.json deleted file mode 100644 index 9fc953e607..0000000000 --- a/_docs-sources/guides/stay-up-to-date/cis/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "label": "CIS AWS Foundations Benchmark" -} diff --git a/_docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/_category_.json b/_docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/_category_.json deleted file mode 100644 index cb66bc8600..0000000000 --- a/_docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "label": "Update to CIS AWS Foundations Benchmark 1.3.0" -} diff --git a/_docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/_category_.json b/_docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/_category_.json deleted file mode 100644 index cd05330845..0000000000 --- a/_docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/deployment-walkthrough/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ -"label": "Deployment walkthrough" -} \ No newline at end of file diff --git a/_docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/_category_.json b/_docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/_category_.json deleted file mode 100644 index 7a77f0ec6e..0000000000 --- a/_docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "label": "Update to CIS AWS Foundations Benchmark 1.4.0" -} diff --git a/_docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/_category_.json b/_docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/_category_.json deleted file mode 100644 index cd05330845..0000000000 --- a/_docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ -"label": "Deployment walkthrough" -} \ No newline at end of file diff --git a/_docs-sources/guides/stay-up-to-date/terraform/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/_category_.json deleted file mode 100644 index 4af9f9caff..0000000000 --- a/_docs-sources/guides/stay-up-to-date/terraform/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "label": "Terraform" -} diff --git a/_docs-sources/guides/stay-up-to-date/terraform/aws-provider-v3/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/aws-provider-v3/_category_.json deleted file mode 100644 index 677d069476..0000000000 --- a/_docs-sources/guides/stay-up-to-date/terraform/aws-provider-v3/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "label": "Update to version 3 of the Terraform AWS Provider" -} diff --git a/_docs-sources/guides/stay-up-to-date/terraform/aws-provider-v3/index.md b/_docs-sources/guides/stay-up-to-date/terraform/aws-provider-v3/index.md index 4ecb9fea16..c289c93ffa 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/aws-provider-v3/index.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/aws-provider-v3/index.md @@ -1,8 +1,4 @@ ---- -pagination_label: Upgrade to AWS Provider V3 ---- - -# Intro +# Upgrade to AWS Provider V3 This guide will walk you through how to update the [Gruntwork Reference Architecture](https://gruntwork.io/reference-architecture/) and any code that depends on the diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/_category_.json deleted file mode 100644 index 4ee5182615..0000000000 --- a/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "label": "DRY your Reference Architecture" -} diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/_category_.json deleted file mode 100644 index ba7669c6f8..0000000000 --- a/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "label": "Deployment Walkthrough" -} diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/index.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/index.md index 09d1ab12b6..2b236d1a76 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/index.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/index.md @@ -1,8 +1,4 @@ ---- -pagination_label: DRY your Reference Architecture ---- - -# Intro +# DRY your Reference Architecture This guide walks you through how to DRY (don’t repeat yourself) up the Terragrunt configurations in the [Gruntwork Reference diff --git a/_docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/_category_.json deleted file mode 100644 index 23c92784be..0000000000 --- a/_docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "label": "Update to Terraform v1.x" -} diff --git a/_docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/_category_.json deleted file mode 100644 index ba7669c6f8..0000000000 --- a/_docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "label": "Deployment Walkthrough" -} diff --git a/_docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/index.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/index.md index 53cbc942a5..3f3f987e91 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/index.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/index.md @@ -1,8 +1,4 @@ ---- -pagination_label: Update to Terraform 1.x ---- - -# Intro +# Update to Terraform 1.x This guide will walk you through how to update any code that depends on the [Gruntwork Infrastructure as Code diff --git a/_docs-sources/guides/stay-up-to-date/terraform/terraform-12/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/terraform-12/_category_.json deleted file mode 100644 index 5ed587e81d..0000000000 --- a/_docs-sources/guides/stay-up-to-date/terraform/terraform-12/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "label": "Update to Terraform 12" -} diff --git a/_docs-sources/guides/stay-up-to-date/terraform/terraform-12/index.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-12/index.md index 354f8e96c4..276f1b7607 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/terraform-12/index.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/terraform-12/index.md @@ -1,4 +1,4 @@ -# Intro +# Update to Terraform 12 This guide walks you through the steps you should take when upgrading your Reference Architecture deployment to Terraform 0.12.x and Terragrunt 0.19.x. diff --git a/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/_category_.json deleted file mode 100644 index 2432efa6b6..0000000000 --- a/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "label": "Update to Terraform 13" -} diff --git a/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/_category_.json deleted file mode 100644 index ba7669c6f8..0000000000 --- a/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "label": "Deployment Walkthrough" -} diff --git a/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/index.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/index.md index 795d2b95b3..7627774aed 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/index.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/index.md @@ -1,8 +1,4 @@ ---- -pagination_label: Update to Terraform 13 ---- - -# Intro +# Update to Terraform 13 This guide will walk you through how to update the [Gruntwork Reference Architecture](https://gruntwork.io/reference-architecture/) and any code that depends on the diff --git a/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/_category_.json deleted file mode 100644 index 7cc0760acf..0000000000 --- a/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "label": "Update to Terraform 14" -} diff --git a/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/_category_.json deleted file mode 100644 index ba7669c6f8..0000000000 --- a/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "label": "Deployment Walkthrough" -} diff --git a/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/index.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/index.md index 6d27917e4d..7ee5b14ad0 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/index.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/index.md @@ -1,8 +1,4 @@ ---- -pagination_label: Update to Terraform 14 ---- - -# Intro +# Update to Terraform 14 This guide will walk you through how to update any code that depends on the [Gruntwork Infrastructure as Code diff --git a/_docs-sources/guides/stay-up-to-date/terraform/terraform-15/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/terraform-15/_category_.json deleted file mode 100644 index a56d0299bc..0000000000 --- a/_docs-sources/guides/stay-up-to-date/terraform/terraform-15/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "label": "Update to Terraform 15" -} diff --git a/_docs-sources/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/_category_.json b/_docs-sources/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/_category_.json deleted file mode 100644 index ba7669c6f8..0000000000 --- a/_docs-sources/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "label": "Deployment Walkthrough" -} diff --git a/_docs-sources/guides/stay-up-to-date/terraform/terraform-15/index.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-15/index.md index 4cdab8d428..dad3c71c36 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/terraform-15/index.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/terraform-15/index.md @@ -1,8 +1,4 @@ ---- -pagination_label: Update to Terraform 15 ---- - -# Intro +# Update to Terraform 15 This guide will walk you through how to update any code that depends on the [Gruntwork Infrastructure as Code diff --git a/docs/guides/stay-up-to-date/terraform/aws-provider-v3/index.md b/docs/guides/stay-up-to-date/terraform/aws-provider-v3/index.md index 754ecc7e84..bac3cb6966 100644 --- a/docs/guides/stay-up-to-date/terraform/aws-provider-v3/index.md +++ b/docs/guides/stay-up-to-date/terraform/aws-provider-v3/index.md @@ -1,8 +1,4 @@ ---- -pagination_label: Upgrade to AWS Provider V3 ---- - -# Intro +# Upgrade to AWS Provider V3 This guide will walk you through how to update the [Gruntwork Reference Architecture](https://gruntwork.io/reference-architecture/) and any code that depends on the @@ -33,5 +29,5 @@ which Gruntwork Repo version tag is compatible with AWS provider v3. 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 e4b02191a4..7f9a6da0d7 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 @@ -1,8 +1,4 @@ ---- -pagination_label: DRY your Reference Architecture ---- - -# Intro +# DRY your Reference Architecture This guide walks you through how to DRY (don’t repeat yourself) up the Terragrunt configurations in the [Gruntwork Reference @@ -28,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/terraform-1.x/index.md b/docs/guides/stay-up-to-date/terraform/terraform-1.x/index.md index 05c585282c..dfe3407fa8 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 @@ -1,8 +1,4 @@ ---- -pagination_label: Update to Terraform 1.x ---- - -# Intro +# Update to Terraform 1.x This guide will walk you through how to update any code that depends on the [Gruntwork Infrastructure as Code @@ -33,5 +29,5 @@ tag is compatible with Terraform 0.15. 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 5d18f8f5ef..c3b084c488 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 @@ -1,4 +1,4 @@ -# Intro +# Update to Terraform 12 This guide walks you through the steps you should take when upgrading your Reference Architecture deployment to Terraform 0.12.x and Terragrunt 0.19.x. @@ -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-13/index.md b/docs/guides/stay-up-to-date/terraform/terraform-13/index.md index 1fc8f9b1c6..700144ca6a 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 @@ -1,8 +1,4 @@ ---- -pagination_label: Update to Terraform 13 ---- - -# Intro +# Update to Terraform 13 This guide will walk you through how to update the [Gruntwork Reference Architecture](https://gruntwork.io/reference-architecture/) and any code that depends on the @@ -31,5 +27,5 @@ tag is compatible with Terraform 0.13. 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 9d1c240d32..948acb7301 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 @@ -1,8 +1,4 @@ ---- -pagination_label: Update to Terraform 14 ---- - -# Intro +# Update to Terraform 14 This guide will walk you through how to update any code that depends on the [Gruntwork Infrastructure as Code @@ -32,5 +28,5 @@ tag is compatible with Terraform 0.14. 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 4ca3d1eddb..7d3395da1a 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 @@ -1,8 +1,4 @@ ---- -pagination_label: Update to Terraform 15 ---- - -# Intro +# Update to Terraform 15 This guide will walk you through how to update any code that depends on the [Gruntwork Infrastructure as Code @@ -34,5 +30,5 @@ compatible with Terraform 0.15. diff --git a/sidebars/update-guides.js b/sidebars/update-guides.js index a46f458329..9989574f0f 100644 --- a/sidebars/update-guides.js +++ b/sidebars/update-guides.js @@ -42,14 +42,37 @@ const updateGuideSidebars = { ], terraform12: [ { - type: "autogenerated", - dirName: "guides/stay-up-to-date/terraform/terraform-12", + label: "Update to Terraform 12", + type: "category", + link: { + type: "doc", + id: "guides/stay-up-to-date/terraform/terraform-12/index", + }, + items: [ + "guides/stay-up-to-date/terraform/terraform-12/deployment-walkthrough", + "guides/stay-up-to-date/terraform/terraform-12/version-compatibility-table", + ], }, ], terraform13: [ { - type: "autogenerated", - dirName: "guides/stay-up-to-date/terraform/terraform-13", + label: "Update to Terraform 13", + type: "category", + link: { + type: "doc", + id: "guides/stay-up-to-date/terraform/terraform-13/index", + }, + items: [ + "guides/stay-up-to-date/terraform/terraform-13/core-concepts", + { + "Deployment Walkthrough": [ + "guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12", + "guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-13", + "guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library", + "guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/updating-the-gruntwork-reference-architecture-to-terraform-0-13", + ], + }, + ], }, ], terraform14: [ From 0690712cefe013b6046f35d09f63f4483c3b61d1 Mon Sep 17 00:00:00 2001 From: Eugene K Date: Thu, 13 Jan 2022 09:38:16 -0500 Subject: [PATCH 13/20] Updates update-guide sidebars --- sidebars/update-guides.js | 86 ++++++++++++++++++++++++++++++++++----- 1 file changed, 75 insertions(+), 11 deletions(-) diff --git a/sidebars/update-guides.js b/sidebars/update-guides.js index 9989574f0f..124d979168 100644 --- a/sidebars/update-guides.js +++ b/sidebars/update-guides.js @@ -77,33 +77,97 @@ const updateGuideSidebars = { ], terraform14: [ { - type: "autogenerated", - dirName: "guides/stay-up-to-date/terraform/terraform-14", + label: "Terraform 14", + type: "category", + link: { + type: "doc", + id: "guides/stay-up-to-date/terraform/terraform-14/index", + }, + items: [ + "guides/stay-up-to-date/terraform/terraform-14/core-concepts", + { + "Deployment Walkthrough": [ + "guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-13", + "guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-14", + "guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library", + "guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-4-start-using-lock-files", + ], + }, + ], }, ], terraform15: [ { - type: "autogenerated", - dirName: "guides/stay-up-to-date/terraform/terraform-15", + label: "Terraform 15", + type: "category", + link: { + type: "doc", + id: "guides/stay-up-to-date/terraform/terraform-15/index", + }, + items: [ + "guides/stay-up-to-date/terraform/terraform-15/core-concepts", + { + "Deployment Walkthrough": [ + "guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-14", + "guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-15", + "guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-3-update-references-to-the-gruntwork-infrastructure-as-code-library", + ], + }, + ], }, ], terraform1x: [ { - type: "autogenerated", - dirName: "guides/stay-up-to-date/terraform/terraform-1.x", + label: "Terraform 1", + type: "category", + link: { + type: "doc", + id: "guides/stay-up-to-date/terraform/terraform-1.x/index", + }, + items: [ + "guides/stay-up-to-date/terraform/terraform-1.x/core-concepts", + { + "Deployment Walkthrough": [ + "guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-15", + "guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/step-2-update-references-to-the-gruntwork-infrastructure-as-code-library", + ], + }, + ], }, ], terraformServiceProviderV3: [ { - type: "autogenerated", - dirName: "guides/stay-up-to-date/terraform/aws-provider-v3", + label: "Aws Provider V 3", + type: "category", + link: { + type: "doc", + id: "guides/stay-up-to-date/terraform/aws-provider-v3/index", + }, + items: [ + "guides/stay-up-to-date/terraform/aws-provider-v3/core-concepts", + "guides/stay-up-to-date/terraform/aws-provider-v3/deployment-walkthrough", + ], }, ], dryRefArch: [ { - type: "autogenerated", - dirName: - "guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture", + label: "How To Dry Your Reference Architecture", + type: "category", + link: { + type: "doc", + id: "guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/index", + }, + items: [ + "guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/core-concepts", + { + "Deployment Walkthrough": [ + "guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/intro", + "guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/update-to-the-service-catalog-based-reference-architecture", + "guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/optional-even-dryer-configuration", + "guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/refactoring-common-configurations-for-a-component", + ], + }, + ], }, ], } From 7a777d2aec8ef2823d76ab9180d02552990eed0f Mon Sep 17 00:00:00 2001 From: Eugene K Date: Thu, 13 Jan 2022 10:09:24 -0500 Subject: [PATCH 14/20] Fix links --- .../deployment-walkthrough/deploy-the-vpc.md | 2 +- .../deployment-walkthrough/pre-requisites.md | 2 +- .../production-grade-design/control-plane.md | 4 ++-- .../production-grade-design/vpc-configuration.md | 2 +- .../production-grade-design/worker-nodes.md | 2 +- .../build-it-yourself/landing-zone/next-steps.md | 2 +- .../iam-roles-for-services.md | 2 +- _docs-sources/guides/build-it-yourself/overview.md | 10 +++++----- .../pipelines/deployment-walkthrough/deploy-a-vpc.md | 2 +- .../use-a-vpc-to-lock-down-deploy-server.md | 2 +- .../vpc/deployment-walkthrough/pre-requisites.md | 2 +- .../guides/build-it-yourself/vpc/next-steps.md | 2 +- .../production-grade-design/multiple-aws-accounts.md | 2 +- .../guides/stay-up-to-date/cis/cis-1.3.0/index.md | 2 +- .../core-concepts.md | 0 .../deployment-walkthrough.md | 0 .../index.md | 0 _docs-sources/intro/first-deployment/deploy.md | 2 +- .../first-deployment/using-terraform-modules.md | 4 ++-- .../deployment-walkthrough/deploy-the-vpc.md | 4 ++-- .../deployment-walkthrough/pre-requisites.md | 4 ++-- .../production-grade-design/control-plane.md | 6 +++--- .../production-grade-design/vpc-configuration.md | 4 ++-- .../production-grade-design/worker-nodes.md | 4 ++-- .../build-it-yourself/landing-zone/next-steps.md | 4 ++-- .../iam-roles-for-services.md | 4 ++-- docs/guides/build-it-yourself/overview.md | 12 ++++++------ .../pipelines/deployment-walkthrough/deploy-a-vpc.md | 4 ++-- .../use-a-vpc-to-lock-down-deploy-server.md | 4 ++-- .../vpc/deployment-walkthrough/pre-requisites.md | 4 ++-- docs/guides/build-it-yourself/vpc/next-steps.md | 4 ++-- .../production-grade-design/multiple-aws-accounts.md | 4 ++-- docs/guides/stay-up-to-date/cis/cis-1.3.0/index.md | 4 ++-- .../terraform/aws-provider-v3/_category_.json | 3 --- .../core-concepts.md | 0 .../deployment-walkthrough.md | 0 .../index.md | 0 docs/intro/first-deployment/deploy.md | 4 ++-- .../first-deployment/using-terraform-modules.md | 6 +++--- sidebars/update-guides.js | 6 +++--- 40 files changed, 63 insertions(+), 66 deletions(-) rename _docs-sources/guides/stay-up-to-date/terraform/{aws-provider-v3 => how-to-update-to-aws-provider-v3}/core-concepts.md (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{aws-provider-v3 => how-to-update-to-aws-provider-v3}/deployment-walkthrough.md (100%) rename _docs-sources/guides/stay-up-to-date/terraform/{aws-provider-v3 => how-to-update-to-aws-provider-v3}/index.md (100%) delete mode 100644 docs/guides/stay-up-to-date/terraform/aws-provider-v3/_category_.json rename docs/guides/stay-up-to-date/terraform/{aws-provider-v3 => how-to-update-to-aws-provider-v3}/core-concepts.md (100%) rename docs/guides/stay-up-to-date/terraform/{aws-provider-v3 => how-to-update-to-aws-provider-v3}/deployment-walkthrough.md (100%) rename docs/guides/stay-up-to-date/terraform/{aws-provider-v3 => how-to-update-to-aws-provider-v3}/index.md (100%) diff --git a/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/deploy-the-vpc.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/deploy-the-vpc.md index c80c7d431a..381bc9c127 100644 --- a/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/deploy-the-vpc.md +++ b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/deploy-the-vpc.md @@ -1,7 +1,7 @@ # Deploy the VPC The first step is to deploy a VPC. Follow the instructions in -[How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) to use +[How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/) to use `module-vpc` to create a VPC setup that looks like this: ![A production-grade VPC setup deployed using module-vpc from the Gruntwork Infrastructure as Code Library](/img/guides/build-it-yourself/vpc/vpc-diagram.png) diff --git a/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/pre-requisites.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/pre-requisites.md index 991d5c06e8..08808cb8e5 100644 --- a/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/pre-requisites.md +++ b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/pre-requisites.md @@ -49,7 +49,7 @@ our [Introduction to Gruntwork](/docs/intro/overview/intro-to-gruntwork). #### AWS accounts This guide deploys infrastructure into one or more AWS accounts. Check out the -[How to configure a production-grade AWS account structure](../../landing-zone/intro/what-youll-learn-in-this-guide.md) +[How to configure a production-grade AWS account structure](/docs/guides/build-it-yourself/landing-zone/) guide for instructions. You will also need to be able to authenticate to these accounts on the CLI: check out [A Comprehensive Guide to Authenticating to AWS on the Command Line](https://blog.gruntwork.io/a-comprehensive-guide-to-authenticating-to-aws-on-the-command-line-63656a686799) for instructions. diff --git a/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/control-plane.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/control-plane.md index cc4ea19a30..d6f9cd984a 100644 --- a/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/control-plane.md +++ b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/control-plane.md @@ -19,7 +19,7 @@ minor version. Your EKS cluster will run in the subnets you specify. We strongly recommend running solely in private subnets that are NOT directly accessible from the public Internet. See -[How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) for more +[How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/) for more info. #### Endpoint access @@ -28,7 +28,7 @@ You can configure whether the [API endpoint for your EKS cluster](https://docs.a is accessible from (a) within the same VPC and/or (b) from the public Internet. We recommend allowing access from within the VPC, but not from the public Internet. If you need to talk to your Kubernetes cluster from your own computer (e.g., to issue commands via `kubectl`), use a bastion host or VPN server. See -[How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) for more +[How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/) for more info. #### Cluster IAM Role diff --git a/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/vpc-configuration.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/vpc-configuration.md index f1d6e48b2c..582e88e438 100644 --- a/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/vpc-configuration.md +++ b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/vpc-configuration.md @@ -2,7 +2,7 @@ EKS relies on a _[Virtual Private Cloud (VPC)](https://aws.amazon.com/vpc/)_ to provide the basic network topology and to manage communication across the nodes (see -[How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) for more +[How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/) for more information on VPCs). Here are the key VPC considerations for your EKS cluster:
diff --git a/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/worker-nodes.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/worker-nodes.md index 7b16bc04f7..bf6b700b50 100644 --- a/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/worker-nodes.md +++ b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/worker-nodes.md @@ -20,7 +20,7 @@ value `owned`. We strongly recommend running the Auto Scaling Group for your worker nodes in private subnets that are NOT directly accessible from the public Internet. See -[How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) for more +[How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/) for more info. #### AMI diff --git a/_docs-sources/guides/build-it-yourself/landing-zone/next-steps.md b/_docs-sources/guides/build-it-yourself/landing-zone/next-steps.md index 3b37dc077d..b32eecb7d3 100644 --- a/_docs-sources/guides/build-it-yourself/landing-zone/next-steps.md +++ b/_docs-sources/guides/build-it-yourself/landing-zone/next-steps.md @@ -2,4 +2,4 @@ Now that you have your basic AWS account structure set up, the next step is to start deploying infrastructure in those accounts! Usually, the best starting point is to configure your network topology, as described in -[How to deploy a production-grade VPC on AWS](../vpc/intro/what-youll-learn-in-this-guide.md). +[How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/). diff --git a/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-services.md b/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-services.md index 3d1f3971c9..24fc0ab50c 100644 --- a/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-services.md +++ b/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-services.md @@ -54,7 +54,7 @@ need to take extra care in terms of who can assume this IAM role, what permissio services. For example, if you have Jenkins running on an EC2 instance, and you give that EC2 instance access to an IAM role so it can deploy your apps, you should do your best to minimize the permissions that IAM role has (e.g., to just `ecs` permissions if deploying to ECS) and you should ensure that your Jenkins instance runs in private -subnets so that it is NOT accessible from the public Internet (see [How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md)). +subnets so that it is NOT accessible from the public Internet (see [How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/)). #### Use the right Principal diff --git a/_docs-sources/guides/build-it-yourself/overview.md b/_docs-sources/guides/build-it-yourself/overview.md index 160c1bde6c..f429ac2e12 100644 --- a/_docs-sources/guides/build-it-yourself/overview.md +++ b/_docs-sources/guides/build-it-yourself/overview.md @@ -15,32 +15,32 @@ The Gruntwork IaC library empowers you to construct your own bespoke architectur Set up a multi-account structure using Gruntwork Landing Zone. Implement continuous deployment for your infrastructure code with Gruntwork Pipelines. Set up your network according to industry best practices using our VPC service. Deploy a Kubernetes Cluster to host all of your apps and services. Make your infrastructure compliant with the CIS AWS Foundations Benchmark. diff --git a/_docs-sources/guides/build-it-yourself/pipelines/deployment-walkthrough/deploy-a-vpc.md b/_docs-sources/guides/build-it-yourself/pipelines/deployment-walkthrough/deploy-a-vpc.md index 1f54d9aea1..5d26fa7969 100644 --- a/_docs-sources/guides/build-it-yourself/pipelines/deployment-walkthrough/deploy-a-vpc.md +++ b/_docs-sources/guides/build-it-yourself/pipelines/deployment-walkthrough/deploy-a-vpc.md @@ -1,7 +1,7 @@ # Deploy a VPC The first step is to deploy a VPC. Follow the instructions in -[How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) to use +[How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/) to use `module-vpc` to create a VPC setup that looks like this: ![A production-grade VPC setup deployed using module-vpc from the Gruntwork Infrastructure as Code Library](/img/guides/build-it-yourself/pipelines/vpc-diagram.png) diff --git a/_docs-sources/guides/build-it-yourself/pipelines/production-grade-design/use-a-vpc-to-lock-down-deploy-server.md b/_docs-sources/guides/build-it-yourself/pipelines/production-grade-design/use-a-vpc-to-lock-down-deploy-server.md index 74d114a2ce..7087f7f9f9 100644 --- a/_docs-sources/guides/build-it-yourself/pipelines/production-grade-design/use-a-vpc-to-lock-down-deploy-server.md +++ b/_docs-sources/guides/build-it-yourself/pipelines/production-grade-design/use-a-vpc-to-lock-down-deploy-server.md @@ -1,6 +1,6 @@ # Use a VPC to lock down deploy server Run your infrastructure deployment workloads in a [Virtual Private Cloud (VPC)](https://aws.amazon.com/vpc/) to isolate -the workloads in a restricted network topology (see [How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) for more information on VPCs). Configure it to run all workloads in private +the workloads in a restricted network topology (see [How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/) for more information on VPCs). Configure it to run all workloads in private subnets that are not publicly accessible. Make sure to block all inbound internet access and consider blocking all outbound access except for the minimum required (e.g, allow access to AWS APIs). diff --git a/_docs-sources/guides/build-it-yourself/vpc/deployment-walkthrough/pre-requisites.md b/_docs-sources/guides/build-it-yourself/vpc/deployment-walkthrough/pre-requisites.md index 891c0e276e..5340fd18e8 100644 --- a/_docs-sources/guides/build-it-yourself/vpc/deployment-walkthrough/pre-requisites.md +++ b/_docs-sources/guides/build-it-yourself/vpc/deployment-walkthrough/pre-requisites.md @@ -34,7 +34,7 @@ our [Introduction to Gruntwork](/docs/intro/overview/intro-to-gruntwork) #### AWS accounts This guide deploys infrastructure into one or more AWS accounts. Check out the -[Production Grade AWS Account Structure](../../landing-zone/intro/what-youll-learn-in-this-guide.md) guide for instructions. +[Production Grade AWS Account Structure](/docs/guides/build-it-yourself/landing-zone/) guide for instructions. You will also need to be able to authenticate to these accounts on the CLI: check out [A Comprehensive Guide to Authenticating to AWS on the Command Line](https://blog.gruntwork.io/a-comprehensive-guide-to-authenticating-to-aws-on-the-command-line-63656a686799) for instructions. diff --git a/_docs-sources/guides/build-it-yourself/vpc/next-steps.md b/_docs-sources/guides/build-it-yourself/vpc/next-steps.md index 7b2469fc8f..5c5ed4de5e 100644 --- a/_docs-sources/guides/build-it-yourself/vpc/next-steps.md +++ b/_docs-sources/guides/build-it-yourself/vpc/next-steps.md @@ -4,7 +4,7 @@ Now that you have your management and application VPCs deployed, you can start b on top of them! Typically, the best next step is to deploy a cluster of servers for running your applications by using one of the following guides: -- [How to deploy a production-grade Kubernetes cluster on AWS](../kubernetes-cluster/intro/what-youll-learn-in-this-guide.md) +- [How to deploy a production-grade Kubernetes cluster on AWS](/docs/guides/build-it-yourself/kubernetes-cluster/) - `How to deploy a production grade ECS cluster on AWS` _(coming soon!)_ - `How to deploy a production grade Nomad cluster on AWS` _(coming soon!)_ - `How to deploy a production grade Auto Scaling Group on AWS` _(coming soon!)_ diff --git a/_docs-sources/guides/build-it-yourself/vpc/production-grade-design/multiple-aws-accounts.md b/_docs-sources/guides/build-it-yourself/vpc/production-grade-design/multiple-aws-accounts.md index 0857c6ba3a..2ed051197b 100644 --- a/_docs-sources/guides/build-it-yourself/vpc/production-grade-design/multiple-aws-accounts.md +++ b/_docs-sources/guides/build-it-yourself/vpc/production-grade-design/multiple-aws-accounts.md @@ -11,5 +11,5 @@ change something in prod rather than pre-prod). Therefore, your best bet is to put pre-production environments and production environments in completely separate AWS accounts. This makes it easy to, for example, grant relatively lax permissions in pre-prod environments, but very -strict permissions in production. Check out the [Production Grade AWS Account Structure](../../landing-zone/intro/what-youll-learn-in-this-guide.md) +strict permissions in production. Check out the [Production Grade AWS Account Structure](/docs/guides/build-it-yourself/landing-zone/) guide for instructions. diff --git a/_docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/index.md b/_docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/index.md index 3a886ace3d..648dac0b7d 100644 --- a/_docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/index.md +++ b/_docs-sources/guides/stay-up-to-date/cis/cis-1.3.0/index.md @@ -7,7 +7,7 @@ pagination_label: Update to CIS AWS Foundations Benchmark 1.3.0 This guide will walk you through how to update from version 1.2.0 to version 1.3.0 of the CIS AWS Foundations Benchmark. If your infrastructure is already compliant with the Benchmark's version 1.2.0, and you are looking to upgrade to v1.3.0, this guide is for you. If you are starting to work on compliance with this benchmark from scratch, check out our -[How to achieve compliance with the CIS AWS Foundations Benchmark](../../../build-it-yourself/achieve-compliance/intro/what-youll-learn-in-this-guide.md) guide instead. +[How to achieve compliance with the CIS AWS Foundations Benchmark](/docs/guides/build-it-yourself/achieve-compliance/) guide instead. This guide consists of two main sections: diff --git a/_docs-sources/guides/stay-up-to-date/terraform/aws-provider-v3/core-concepts.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/core-concepts.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/aws-provider-v3/core-concepts.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/core-concepts.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/aws-provider-v3/deployment-walkthrough.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/deployment-walkthrough.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/aws-provider-v3/deployment-walkthrough.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/deployment-walkthrough.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/aws-provider-v3/index.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/index.md similarity index 100% rename from _docs-sources/guides/stay-up-to-date/terraform/aws-provider-v3/index.md rename to _docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/index.md diff --git a/_docs-sources/intro/first-deployment/deploy.md b/_docs-sources/intro/first-deployment/deploy.md index 25d6e88625..fdd57227f4 100644 --- a/_docs-sources/intro/first-deployment/deploy.md +++ b/_docs-sources/intro/first-deployment/deploy.md @@ -144,7 +144,7 @@ balancers, and so on. Each module is configured via a `terragrunt.hcl` file.
For example, if you were using AWS, with separate accounts for staging and production (see -[How to Configure a Production Grade AWS Account Structure](/docs/guides/build-it-yourself/landing-zone/intro/what-youll-learn-in-this-guide)), +[How to Configure a Production Grade AWS Account Structure](/docs/guides/build-it-yourself/landing-zone/)), and you wanted to deploy the `vpc-app` module in the `us-east-2` region in each of these accounts, the folder structure would look like this: diff --git a/_docs-sources/intro/first-deployment/using-terraform-modules.md b/_docs-sources/intro/first-deployment/using-terraform-modules.md index f145e08e7d..99cb943ea5 100644 --- a/_docs-sources/intro/first-deployment/using-terraform-modules.md +++ b/_docs-sources/intro/first-deployment/using-terraform-modules.md @@ -10,7 +10,7 @@ You must be a Gruntwork subscriber to acce ::: You can use this module to deploy a production-grade VPC on AWS. For full background information on VPCs, check -out [How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/intro/what-youll-learn-in-this-guide). +out [How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/). ## Create a wrapper module @@ -66,7 +66,7 @@ The code above will only allow you to run it against the AWS account with ID pas variable (you’ll declare this shortly). This is an extra safety measure to ensure you don’t accidentally authenticate to the wrong AWS account while deploying this code—e.g., so you don’t accidentally deploy changes intended for staging to production (for more info on working with multiple AWS accounts, see -[How to Configure a Production Grade AWS Account Structure](/docs/guides/build-it-yourself/landing-zone/intro/what-youll-learn-in-this-guide)). +[How to Configure a Production Grade AWS Account Structure](/docs/guides/build-it-yourself/landing-zone/)).
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 49ec3a9a0a..abffcf30b0 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 @@ -1,7 +1,7 @@ # Deploy the VPC The first step is to deploy a VPC. Follow the instructions in -[How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) to use +[How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/) to use `module-vpc` to create a VPC setup that looks like this: ![A production-grade VPC setup deployed using module-vpc from the Gruntwork Infrastructure as Code Library](/img/guides/build-it-yourself/vpc/vpc-diagram.png) @@ -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 69402691cb..f46d74e4fb 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 @@ -49,7 +49,7 @@ our [Introduction to Gruntwork](/docs/intro/overview/intro-to-gruntwork). #### AWS accounts This guide deploys infrastructure into one or more AWS accounts. Check out the -[How to configure a production-grade AWS account structure](../../landing-zone/intro/what-youll-learn-in-this-guide.md) +[How to configure a production-grade AWS account structure](/docs/guides/build-it-yourself/landing-zone/) guide for instructions. You will also need to be able to authenticate to these accounts on the CLI: check out [A Comprehensive Guide to Authenticating to AWS on the Command Line](https://blog.gruntwork.io/a-comprehensive-guide-to-authenticating-to-aws-on-the-command-line-63656a686799) for instructions. @@ -58,5 +58,5 @@ for instructions. 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 b084b2084a..2b2310c930 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 @@ -19,7 +19,7 @@ minor version. Your EKS cluster will run in the subnets you specify. We strongly recommend running solely in private subnets that are NOT directly accessible from the public Internet. See -[How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) for more +[How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/) for more info. #### Endpoint access @@ -28,7 +28,7 @@ You can configure whether the [API endpoint for your EKS cluster](https://docs.a is accessible from (a) within the same VPC and/or (b) from the public Internet. We recommend allowing access from within the VPC, but not from the public Internet. If you need to talk to your Kubernetes cluster from your own computer (e.g., to issue commands via `kubectl`), use a bastion host or VPN server. See -[How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) for more +[How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/) for more info. #### Cluster IAM Role @@ -54,5 +54,5 @@ CloudWatch. 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 8dd782a876..c9ce2ba16f 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 @@ -2,7 +2,7 @@ EKS relies on a _[Virtual Private Cloud (VPC)](https://aws.amazon.com/vpc/)_ to provide the basic network topology and to manage communication across the nodes (see -[How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) for more +[How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/) for more information on VPCs). Here are the key VPC considerations for your EKS cluster:
@@ -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 32bd9219a5..00f0f642c0 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 @@ -20,7 +20,7 @@ value `owned`. We strongly recommend running the Auto Scaling Group for your worker nodes in private subnets that are NOT directly accessible from the public Internet. See -[How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) for more +[How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/) for more info. #### AMI @@ -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/next-steps.md b/docs/guides/build-it-yourself/landing-zone/next-steps.md index f80b8e712e..902171f9ea 100644 --- a/docs/guides/build-it-yourself/landing-zone/next-steps.md +++ b/docs/guides/build-it-yourself/landing-zone/next-steps.md @@ -2,9 +2,9 @@ Now that you have your basic AWS account structure set up, the next step is to start deploying infrastructure in those accounts! Usually, the best starting point is to configure your network topology, as described in -[How to deploy a production-grade VPC on AWS](../vpc/intro/what-youll-learn-in-this-guide.md). +[How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/). 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 b8faf413b8..b50910f858 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 @@ -54,7 +54,7 @@ need to take extra care in terms of who can assume this IAM role, what permissio services. For example, if you have Jenkins running on an EC2 instance, and you give that EC2 instance access to an IAM role so it can deploy your apps, you should do your best to minimize the permissions that IAM role has (e.g., to just `ecs` permissions if deploying to ECS) and you should ensure that your Jenkins instance runs in private -subnets so that it is NOT accessible from the public Internet (see [How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md)). +subnets so that it is NOT accessible from the public Internet (see [How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/)). #### Use the right Principal @@ -136,5 +136,5 @@ sensitive machine user access keys. diff --git a/docs/guides/build-it-yourself/overview.md b/docs/guides/build-it-yourself/overview.md index 2f3c9b41a7..a76c65d7ac 100644 --- a/docs/guides/build-it-yourself/overview.md +++ b/docs/guides/build-it-yourself/overview.md @@ -15,32 +15,32 @@ The Gruntwork IaC library empowers you to construct your own bespoke architectur Set up a multi-account structure using Gruntwork Landing Zone. Implement continuous deployment for your infrastructure code with Gruntwork Pipelines. Set up your network according to industry best practices using our VPC service. Deploy a Kubernetes Cluster to host all of your apps and services. Make your infrastructure compliant with the CIS AWS Foundations Benchmark. @@ -64,5 +64,5 @@ The Gruntwork IaC library empowers you to construct your own bespoke architectur 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 415766d97f..a35be79740 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 @@ -1,7 +1,7 @@ # Deploy a VPC The first step is to deploy a VPC. Follow the instructions in -[How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) to use +[How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/) to use `module-vpc` to create a VPC setup that looks like this: ![A production-grade VPC setup deployed using module-vpc from the Gruntwork Infrastructure as Code Library](/img/guides/build-it-yourself/pipelines/vpc-diagram.png) @@ -37,5 +37,5 @@ infrastructure-live 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 cbc876d220..703c547b55 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 @@ -1,11 +1,11 @@ # Use a VPC to lock down deploy server Run your infrastructure deployment workloads in a [Virtual Private Cloud (VPC)](https://aws.amazon.com/vpc/) to isolate -the workloads in a restricted network topology (see [How to deploy a production-grade VPC on AWS](../../vpc/intro/what-youll-learn-in-this-guide.md) for more information on VPCs). Configure it to run all workloads in private +the workloads in a restricted network topology (see [How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/) for more information on VPCs). Configure it to run all workloads in private subnets that are not publicly accessible. Make sure to block all inbound internet access and consider blocking all outbound access except for the minimum required (e.g, allow access to AWS APIs). 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 ac572fad16..a4406a7a53 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 @@ -34,7 +34,7 @@ our [Introduction to Gruntwork](/docs/intro/overview/intro-to-gruntwork) #### AWS accounts This guide deploys infrastructure into one or more AWS accounts. Check out the -[Production Grade AWS Account Structure](../../landing-zone/intro/what-youll-learn-in-this-guide.md) guide for instructions. +[Production Grade AWS Account Structure](/docs/guides/build-it-yourself/landing-zone/) guide for instructions. You will also need to be able to authenticate to these accounts on the CLI: check out [A Comprehensive Guide to Authenticating to AWS on the Command Line](https://blog.gruntwork.io/a-comprehensive-guide-to-authenticating-to-aws-on-the-command-line-63656a686799) for instructions. @@ -43,5 +43,5 @@ for instructions. diff --git a/docs/guides/build-it-yourself/vpc/next-steps.md b/docs/guides/build-it-yourself/vpc/next-steps.md index 0203fdc41e..cf8768bb06 100644 --- a/docs/guides/build-it-yourself/vpc/next-steps.md +++ b/docs/guides/build-it-yourself/vpc/next-steps.md @@ -4,7 +4,7 @@ Now that you have your management and application VPCs deployed, you can start b on top of them! Typically, the best next step is to deploy a cluster of servers for running your applications by using one of the following guides: -- [How to deploy a production-grade Kubernetes cluster on AWS](../kubernetes-cluster/intro/what-youll-learn-in-this-guide.md) +- [How to deploy a production-grade Kubernetes cluster on AWS](/docs/guides/build-it-yourself/kubernetes-cluster/) - `How to deploy a production grade ECS cluster on AWS` _(coming soon!)_ - `How to deploy a production grade Nomad cluster on AWS` _(coming soon!)_ - `How to deploy a production grade Auto Scaling Group on AWS` _(coming soon!)_ @@ -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/multiple-aws-accounts.md b/docs/guides/build-it-yourself/vpc/production-grade-design/multiple-aws-accounts.md index b878b7335d..d3640ba578 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 @@ -11,10 +11,10 @@ change something in prod rather than pre-prod). Therefore, your best bet is to put pre-production environments and production environments in completely separate AWS accounts. This makes it easy to, for example, grant relatively lax permissions in pre-prod environments, but very -strict permissions in production. Check out the [Production Grade AWS Account Structure](../../landing-zone/intro/what-youll-learn-in-this-guide.md) +strict permissions in production. Check out the [Production Grade AWS Account Structure](/docs/guides/build-it-yourself/landing-zone/) guide for instructions. 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 a5916657bb..7f1730464e 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 @@ -7,7 +7,7 @@ pagination_label: Update to CIS AWS Foundations Benchmark 1.3.0 This guide will walk you through how to update from version 1.2.0 to version 1.3.0 of the CIS AWS Foundations Benchmark. If your infrastructure is already compliant with the Benchmark's version 1.2.0, and you are looking to upgrade to v1.3.0, this guide is for you. If you are starting to work on compliance with this benchmark from scratch, check out our -[How to achieve compliance with the CIS AWS Foundations Benchmark](../../../build-it-yourself/achieve-compliance/intro/what-youll-learn-in-this-guide.md) guide instead. +[How to achieve compliance with the CIS AWS Foundations Benchmark](/docs/guides/build-it-yourself/achieve-compliance/) guide instead. This guide consists of two main sections: @@ -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/terraform/aws-provider-v3/_category_.json b/docs/guides/stay-up-to-date/terraform/aws-provider-v3/_category_.json deleted file mode 100644 index 677d069476..0000000000 --- a/docs/guides/stay-up-to-date/terraform/aws-provider-v3/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "label": "Update to version 3 of the Terraform AWS Provider" -} diff --git a/docs/guides/stay-up-to-date/terraform/aws-provider-v3/core-concepts.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/core-concepts.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/aws-provider-v3/core-concepts.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/core-concepts.md diff --git a/docs/guides/stay-up-to-date/terraform/aws-provider-v3/deployment-walkthrough.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/deployment-walkthrough.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/aws-provider-v3/deployment-walkthrough.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/deployment-walkthrough.md diff --git a/docs/guides/stay-up-to-date/terraform/aws-provider-v3/index.md b/docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/index.md similarity index 100% rename from docs/guides/stay-up-to-date/terraform/aws-provider-v3/index.md rename to docs/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/index.md diff --git a/docs/intro/first-deployment/deploy.md b/docs/intro/first-deployment/deploy.md index bd411271fe..ca0f916a31 100644 --- a/docs/intro/first-deployment/deploy.md +++ b/docs/intro/first-deployment/deploy.md @@ -144,7 +144,7 @@ balancers, and so on. Each module is configured via a `terragrunt.hcl` file.
For example, if you were using AWS, with separate accounts for staging and production (see -[How to Configure a Production Grade AWS Account Structure](/docs/guides/build-it-yourself/landing-zone/intro/what-youll-learn-in-this-guide)), +[How to Configure a Production Grade AWS Account Structure](/docs/guides/build-it-yourself/landing-zone/)), and you wanted to deploy the `vpc-app` module in the `us-east-2` region in each of these accounts, the folder structure would look like this: @@ -261,5 +261,5 @@ terragrunt apply-all diff --git a/docs/intro/first-deployment/using-terraform-modules.md b/docs/intro/first-deployment/using-terraform-modules.md index 389ca0d990..722d4718e0 100644 --- a/docs/intro/first-deployment/using-terraform-modules.md +++ b/docs/intro/first-deployment/using-terraform-modules.md @@ -10,7 +10,7 @@ You must be a Gruntwork subscriber to acce ::: You can use this module to deploy a production-grade VPC on AWS. For full background information on VPCs, check -out [How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/intro/what-youll-learn-in-this-guide). +out [How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/). ## Create a wrapper module @@ -66,7 +66,7 @@ The code above will only allow you to run it against the AWS account with ID pas variable (you’ll declare this shortly). This is an extra safety measure to ensure you don’t accidentally authenticate to the wrong AWS account while deploying this code—e.g., so you don’t accidentally deploy changes intended for staging to production (for more info on working with multiple AWS accounts, see -[How to Configure a Production Grade AWS Account Structure](/docs/guides/build-it-yourself/landing-zone/intro/what-youll-learn-in-this-guide)). +[How to Configure a Production Grade AWS Account Structure](/docs/guides/build-it-yourself/landing-zone/)).
@@ -248,5 +248,5 @@ output "private_persistence_subnet_ids" { diff --git a/sidebars/update-guides.js b/sidebars/update-guides.js index 124d979168..ee110cffd6 100644 --- a/sidebars/update-guides.js +++ b/sidebars/update-guides.js @@ -141,11 +141,11 @@ const updateGuideSidebars = { type: "category", link: { type: "doc", - id: "guides/stay-up-to-date/terraform/aws-provider-v3/index", + id: "guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/index", }, items: [ - "guides/stay-up-to-date/terraform/aws-provider-v3/core-concepts", - "guides/stay-up-to-date/terraform/aws-provider-v3/deployment-walkthrough", + "guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/core-concepts", + "guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/deployment-walkthrough", ], }, ], From 022eb0a31f1baf6ef5fbf939c9911f5b62b05d62 Mon Sep 17 00:00:00 2001 From: Eben Eliason Date: Thu, 13 Jan 2022 11:46:35 -0800 Subject: [PATCH 15/20] Final fixes to update guide naming, card links --- _docs-sources/guides/{welcome.md => index.md} | 0 .../deployment-walkthrough/intro.md | 6 +---- .../optional-even-dryer-configuration.md | 12 +++++++++- ...g-common-configurations-for-a-component.md | 20 ----------------- ...ce-catalog-based-reference-architecture.md | 9 +++++++- .../terraform/terraform-1.x/core-concepts.md | 3 --- ...de-to-be-compatible-with-terraform-0-15.md | 6 ++--- ...runtwork-infrastructure-as-code-library.md | 2 +- .../terraform/terraform-13/core-concepts.md | 3 --- ...de-to-be-compatible-with-terraform-0-12.md | 1 - ...de-to-be-compatible-with-terraform-0-13.md | 2 +- .../terraform/terraform-14/core-concepts.md | 3 --- ...de-to-be-compatible-with-terraform-0-14.md | 2 +- .../terraform/terraform-15/core-concepts.md | 3 --- ...de-to-be-compatible-with-terraform-0-15.md | 2 +- _docs-sources/intro/next-steps.mdx | 2 +- .../intro/overview/getting-started.mdx | 2 +- docs/guides/{welcome.md => index.md} | 0 .../deployment-walkthrough/intro.md | 8 ++----- .../optional-even-dryer-configuration.md | 14 ++++++++++-- ...g-common-configurations-for-a-component.md | 22 +------------------ ...ce-catalog-based-reference-architecture.md | 11 ++++++++-- .../terraform/terraform-1.x/core-concepts.md | 5 +---- ...de-to-be-compatible-with-terraform-0-15.md | 8 +++---- ...runtwork-infrastructure-as-code-library.md | 4 ++-- .../terraform/terraform-13/core-concepts.md | 5 +---- ...de-to-be-compatible-with-terraform-0-12.md | 3 +-- ...de-to-be-compatible-with-terraform-0-13.md | 4 ++-- .../terraform/terraform-14/core-concepts.md | 5 +---- ...de-to-be-compatible-with-terraform-0-14.md | 4 ++-- .../terraform/terraform-15/core-concepts.md | 5 +---- ...de-to-be-compatible-with-terraform-0-15.md | 4 ++-- docs/intro/next-steps.mdx | 4 ++-- docs/intro/overview/getting-started.mdx | 4 ++-- sidebars/update-guides.js | 10 ++++----- src/pages/index.tsx | 2 +- 36 files changed, 80 insertions(+), 120 deletions(-) rename _docs-sources/guides/{welcome.md => index.md} (100%) rename docs/guides/{welcome.md => index.md} (100%) diff --git a/_docs-sources/guides/welcome.md b/_docs-sources/guides/index.md similarity index 100% rename from _docs-sources/guides/welcome.md rename to _docs-sources/guides/index.md diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/intro.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/intro.md index 53bbe3af91..eb9c12e1de 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/intro.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/intro.md @@ -1,8 +1,4 @@ ---- -pagination_label: Deployment Walkthrough ---- - -# Intro +# Update Approach :::danger Prerequisite: Update Terragrunt to a compatible version diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/optional-even-dryer-configuration.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/optional-even-dryer-configuration.md index 131796a7df..1843a75758 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/optional-even-dryer-configuration.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/optional-even-dryer-configuration.md @@ -1,4 +1,14 @@ -# (Optional) Even DRYer configuration +--- +sidebar_label: DRYer Configuration (optional) +--- + +# Even DRYer configuration + +:::note + +This step outlines optional optimizations. + +::: This guide takes a conservative approach to refactoring the Terragrunt configurations. However, there are additional Terragrunt features that can be leveraged to further DRY your configuration. Note that these features requires a bit diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/refactoring-common-configurations-for-a-component.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/refactoring-common-configurations-for-a-component.md index 69f8e69935..b20dadb7d5 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/refactoring-common-configurations-for-a-component.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/refactoring-common-configurations-for-a-component.md @@ -5,11 +5,8 @@ in your Reference Architecture. These steps can be used to refactor any componen accounts or environments in your Reference Architecture. - [Step 1: Identify the component](#step-identify-the-component) - - [Step 2: Identify common configurations](#step-identify-common-configurations) - - [Step 3: Extract common configurations](#step-extract-common-configurations) - - [Step 4: Update child configurations](#step-1-update-child-configurations) ## Step 1: Identify the component @@ -26,31 +23,21 @@ Example inventory: - `vpc` - `dev/us-west-2/dev/networking/vpc` - - `stage/us-west-2/stage/networking/vpc` - - `prod/us-west-2/prod/networking/vpc` - `openvpn-server` - `dev/us-west-2/dev/networking/openvpn-server` - - `stage/us-west-2/stage/networking/openvpn-server` - - `prod/us-west-2/prod/networking/openvpn-server` - `ecs-deploy-runner` - - `dev/us-west-2/mgmt/ecs-deploy-runner` - - `stage/us-west-2/mgmt/ecs-deploy-runner` - - `prod/us-west-2/mgmt/ecs-deploy-runner` - - `shared/us-west-2/mgmt/ecs-deploy-runner` - - `logs/us-west-2/mgmt/ecs-deploy-runner` - - `security/us-west-2/mgmt/ecs-deploy-runner` As mentioned in the [Background](../core-concepts.md#background), the changes will be isolated to Terragrunt configuration files (syntactic changes vs @@ -82,9 +69,7 @@ To construct this initial list, follow these steps: - For example, in the file [dev/us-west-2/dev/networking/vpc/terragrunt.hcl](https://github.com/gruntwork-io/terraform-aws-service-catalog/blob/6ca162dd1a8d8d6b7cf05e6a22bc4ac7bf01215f/examples/for-production/infrastructure-live/dev/us-west-2/dev/networking/vpc/terragrunt.hcl), the list would be: - `terraform` - - `locals` - - `inputs` 3. Next, note all the top level keys in the `inputs` attribute in the reference configuration. `inputs` need special treatment because it will contain a mix of items that are common and different across environments, so to maximize the DRY potential, we need to look at each `input` element separately. @@ -92,15 +77,10 @@ To construct this initial list, follow these steps: - In the same example file, the list would be: - `vpc_name` - - `num_nat_gateways` - - `cidr_block` - - `kms_key_user_iam_arns` - - `eks_cluster_names` - - `tag_for_use_with_eks` Once you have the candidate configurations, you will want to run through a diff utility to cross off any that are diff --git a/_docs-sources/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-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/update-to-the-service-catalog-based-reference-architecture.md index 7aeeea0db7..77558fbb3f 100644 --- a/_docs-sources/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-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/update-to-the-service-catalog-based-reference-architecture.md @@ -1,7 +1,14 @@ --- +sidebar_label: Use the Service Catalog (optional) --- -# (Optional) Update to the Service Catalog based Reference Architecture +# Update to the Service Catalog based Reference Architecture + +:::note + +This step is optional, but recommended. + +::: If you haven’t already, it is recommended to [update your Reference Architecture to the Service Catalog based diff --git a/_docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/core-concepts.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/core-concepts.md index a7322e8b98..d6a5506077 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/core-concepts.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/terraform-1.x/core-concepts.md @@ -1,6 +1,3 @@ ---- ---- - # Core Concepts [Terraform 1.0.0 was released on June 08, diff --git a/_docs-sources/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-sources/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 2bc5fd93f4..611725e252 100644 --- a/_docs-sources/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-sources/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-15.md @@ -1,5 +1,5 @@ --- -sidebar_label: Update your code to Terraform 15 +sidebar_label: Update to Terraform 15 --- # Step 1: update your code to be compatible with Terraform 0.15 @@ -21,6 +21,6 @@ If you haven’t already, you need to: 4. If you’re still on Terraform 0.14, see our [Terraform 0.15 upgrade guide](../../terraform-15). -2. Update all your Gruntwork modules to the latest versions just _before_ the TF 1.x versions in the compatibility - table below. The upgrade will be much easier and less error prone if you keep the number of version jumps as small +2. Update all your Gruntwork modules to the latest versions just _before_ the TF 1.x versions in the [compatibility + table](/docs/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/step-2-update-references-to-the-gruntwork-infrastructure-as-code-library#version-compatibility-table). The upgrade will be much easier and less error prone if you keep the number of version jumps as small as possible. diff --git a/_docs-sources/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-sources/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md index eb52a2342a..b3dbad4084 100644 --- a/_docs-sources/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-sources/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/step-2-update-references-to-the-gruntwork-infrastructure-as-code-library.md @@ -1,5 +1,5 @@ --- -sidebar_label: Update Gruntwork IaC module references +sidebar_label: Update Gruntwork IaC Module References --- # Step 2: update references to the Gruntwork Infrastructure as Code Library diff --git a/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/core-concepts.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/core-concepts.md index 3538035a17..4d3ea5d63e 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/core-concepts.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/core-concepts.md @@ -1,6 +1,3 @@ ---- ---- - # Core Concepts [Terraform 0.13 was released on August 10th, 2020](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-13). diff --git a/_docs-sources/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-sources/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12.md index 1ac10e2252..44988c31a0 100644 --- a/_docs-sources/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-sources/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-1-update-your-code-to-be-compatible-with-terraform-0-12.md @@ -1,5 +1,4 @@ --- -pagination_label: Deployment Walkthrough - Step 1 sidebar_label: Update to Terraform 12 --- diff --git a/_docs-sources/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-sources/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-13.md index d8a7ab7891..9b9f76a3d5 100644 --- a/_docs-sources/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-sources/guides/stay-up-to-date/terraform/terraform-13/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-13.md @@ -1,5 +1,5 @@ --- -sidebar_label: Update your code to Terraform 13 +sidebar_label: Update to Terraform 13 --- # Step 2: update your code to be compatible with Terraform 0.13 diff --git a/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/core-concepts.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/core-concepts.md index 766fbd9aee..4ef1e88abf 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/core-concepts.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/core-concepts.md @@ -1,6 +1,3 @@ ---- ---- - # Core Concepts [Terraform 0.14 was released on diff --git a/_docs-sources/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-sources/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-14.md index 1e0752f1cc..28abbfbf27 100644 --- a/_docs-sources/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-sources/guides/stay-up-to-date/terraform/terraform-14/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-14.md @@ -1,5 +1,5 @@ --- -sidebar_label: Update your code to Terraform 14 +sidebar_label: Update to Terraform 14 --- # Step 2: update your code to be compatible with Terraform 0.14 diff --git a/_docs-sources/guides/stay-up-to-date/terraform/terraform-15/core-concepts.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-15/core-concepts.md index 86d8a6920b..6e07f0233a 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/terraform-15/core-concepts.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/terraform-15/core-concepts.md @@ -1,6 +1,3 @@ ---- ---- - # Core Concepts [Terraform 0.15 was released on April 14, diff --git a/_docs-sources/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-sources/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-15.md index f10bdf0c61..e8bde3e328 100644 --- a/_docs-sources/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-sources/guides/stay-up-to-date/terraform/terraform-15/deployment-walkthrough/step-2-update-your-code-to-be-compatible-with-terraform-0-15.md @@ -1,5 +1,5 @@ --- -sidebar_label: Update your code to Terraform 15 +sidebar_label: Update to Terraform 15 --- # Step 2: update your code to be compatible with Terraform 0.15 diff --git a/_docs-sources/intro/next-steps.mdx b/_docs-sources/intro/next-steps.mdx index 5163d11b29..1daba962a0 100644 --- a/_docs-sources/intro/next-steps.mdx +++ b/_docs-sources/intro/next-steps.mdx @@ -7,7 +7,7 @@ import Grid from "/src/components/Grid" # Next Steps -Now that your foundational knowledge is in place and your workspace is configured, you’re ready to dive in and learn how to deploy production-grade infrastructure. If you’ve purchased a Gruntwork Reference Architecture, use [this guide](/docs/guides/reference-architecture) to get started. Otherwise, view our [courses](/docs/courses) and [guides](/docs/guides/welcome), or check out the [Service Catalog API reference](/docs/reference/services/intro) to learn what’s available. +Now that your foundational knowledge is in place and your workspace is configured, you’re ready to dive in and learn how to deploy production-grade infrastructure. If you’ve purchased a Gruntwork Reference Architecture, use [this guide](/docs/guides/reference-architecture) to get started. Otherwise, view our [courses](/docs/courses) and [guides](/docs/guides), or check out the [Service Catalog API reference](/docs/reference/services/intro) to learn what’s available. 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 2ff1b459b7..726c0c287a 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 @@ -1,4 +1,14 @@ -# (Optional) Even DRYer configuration +--- +sidebar_label: DRYer Configuration (optional) +--- + +# Even DRYer configuration + +:::note + +This step outlines optional optimizations. + +::: This guide takes a conservative approach to refactoring the Terragrunt configurations. However, there are additional Terragrunt features that can be leveraged to further DRY your configuration. Note that these features requires a bit @@ -172,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 b718886e61..1712bad226 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 @@ -5,11 +5,8 @@ in your Reference Architecture. These steps can be used to refactor any componen accounts or environments in your Reference Architecture. - [Step 1: Identify the component](#step-identify-the-component) - - [Step 2: Identify common configurations](#step-identify-common-configurations) - - [Step 3: Extract common configurations](#step-extract-common-configurations) - - [Step 4: Update child configurations](#step-1-update-child-configurations) ## Step 1: Identify the component @@ -26,31 +23,21 @@ Example inventory: - `vpc` - `dev/us-west-2/dev/networking/vpc` - - `stage/us-west-2/stage/networking/vpc` - - `prod/us-west-2/prod/networking/vpc` - `openvpn-server` - `dev/us-west-2/dev/networking/openvpn-server` - - `stage/us-west-2/stage/networking/openvpn-server` - - `prod/us-west-2/prod/networking/openvpn-server` - `ecs-deploy-runner` - - `dev/us-west-2/mgmt/ecs-deploy-runner` - - `stage/us-west-2/mgmt/ecs-deploy-runner` - - `prod/us-west-2/mgmt/ecs-deploy-runner` - - `shared/us-west-2/mgmt/ecs-deploy-runner` - - `logs/us-west-2/mgmt/ecs-deploy-runner` - - `security/us-west-2/mgmt/ecs-deploy-runner` As mentioned in the [Background](../core-concepts.md#background), the changes will be isolated to Terragrunt configuration files (syntactic changes vs @@ -82,9 +69,7 @@ To construct this initial list, follow these steps: - For example, in the file [dev/us-west-2/dev/networking/vpc/terragrunt.hcl](https://github.com/gruntwork-io/terraform-aws-service-catalog/blob/6ca162dd1a8d8d6b7cf05e6a22bc4ac7bf01215f/examples/for-production/infrastructure-live/dev/us-west-2/dev/networking/vpc/terragrunt.hcl), the list would be: - `terraform` - - `locals` - - `inputs` 3. Next, note all the top level keys in the `inputs` attribute in the reference configuration. `inputs` need special treatment because it will contain a mix of items that are common and different across environments, so to maximize the DRY potential, we need to look at each `input` element separately. @@ -92,15 +77,10 @@ To construct this initial list, follow these steps: - In the same example file, the list would be: - `vpc_name` - - `num_nat_gateways` - - `cidr_block` - - `kms_key_user_iam_arns` - - `eks_cluster_names` - - `tag_for_use_with_eks` Once you have the candidate configurations, you will want to run through a diff utility to cross off any that are @@ -297,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 d0ce294f53..8c34089e63 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 @@ -1,7 +1,14 @@ --- +sidebar_label: Use the Service Catalog (optional) --- -# (Optional) Update to the Service Catalog based Reference Architecture +# Update to the Service Catalog based Reference Architecture + +:::note + +This step is optional, but recommended. + +::: If you haven’t already, it is recommended to [update your Reference Architecture to the Service Catalog based @@ -21,5 +28,5 @@ fully supported by Gruntwork. 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 493914e53c..8d0aeda696 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 @@ -1,6 +1,3 @@ ---- ---- - # Core Concepts [Terraform 1.0.0 was released on June 08, @@ -24,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 7d597f5167..9675f3226f 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 @@ -1,5 +1,5 @@ --- -sidebar_label: Update your code to Terraform 15 +sidebar_label: Update to Terraform 15 --- # Step 1: update your code to be compatible with Terraform 0.15 @@ -21,11 +21,11 @@ If you haven’t already, you need to: 4. If you’re still on Terraform 0.14, see our [Terraform 0.15 upgrade guide](../../terraform-15). -2. Update all your Gruntwork modules to the latest versions just _before_ the TF 1.x versions in the compatibility - table below. The upgrade will be much easier and less error prone if you keep the number of version jumps as small +2. Update all your Gruntwork modules to the latest versions just _before_ the TF 1.x versions in the [compatibility + table](/docs/guides/stay-up-to-date/terraform/terraform-1.x/deployment-walkthrough/step-2-update-references-to-the-gruntwork-infrastructure-as-code-library#version-compatibility-table). The upgrade will be much easier and less error prone if you keep the number of version jumps as small as possible. 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 4af14103c0..ca29beca00 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 @@ -1,5 +1,5 @@ --- -sidebar_label: Update Gruntwork IaC module references +sidebar_label: Update Gruntwork IaC Module References --- # Step 2: update references to the Gruntwork Infrastructure as Code Library @@ -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-13/core-concepts.md b/docs/guides/stay-up-to-date/terraform/terraform-13/core-concepts.md index b5b3ac6980..cabf5c6c68 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 @@ -1,6 +1,3 @@ ---- ---- - # Core Concepts [Terraform 0.13 was released on August 10th, 2020](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-13). @@ -21,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 c32a81f249..9cd776dc57 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 @@ -1,5 +1,4 @@ --- -pagination_label: Deployment Walkthrough - Step 1 sidebar_label: Update to Terraform 12 --- @@ -17,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 50312bac5a..0b09996e3b 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 @@ -1,5 +1,5 @@ --- -sidebar_label: Update your code to Terraform 13 +sidebar_label: Update to Terraform 13 --- # Step 2: update your code to be compatible with Terraform 0.13 @@ -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-14/core-concepts.md b/docs/guides/stay-up-to-date/terraform/terraform-14/core-concepts.md index 70cb58428a..6f3a0651c3 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 @@ -1,6 +1,3 @@ ---- ---- - # Core Concepts [Terraform 0.14 was released on @@ -22,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-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 7aff3a7693..ac5caeaa44 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 @@ -1,5 +1,5 @@ --- -sidebar_label: Update your code to Terraform 14 +sidebar_label: Update to Terraform 14 --- # Step 2: update your code to be compatible with Terraform 0.14 @@ -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-15/core-concepts.md b/docs/guides/stay-up-to-date/terraform/terraform-15/core-concepts.md index 8c4c7bb494..eae857644e 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 @@ -1,6 +1,3 @@ ---- ---- - # Core Concepts [Terraform 0.15 was released on April 14, @@ -30,5 +27,5 @@ following section. 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 7f9645cd9b..65d2b346bd 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 @@ -1,5 +1,5 @@ --- -sidebar_label: Update your code to Terraform 15 +sidebar_label: Update to Terraform 15 --- # Step 2: update your code to be compatible with Terraform 0.15 @@ -10,5 +10,5 @@ Upgrade Guide](https://www.terraform.io/upgrade-guides/0-15.html). diff --git a/docs/intro/next-steps.mdx b/docs/intro/next-steps.mdx index f9200ab764..67342746f9 100644 --- a/docs/intro/next-steps.mdx +++ b/docs/intro/next-steps.mdx @@ -7,7 +7,7 @@ import Grid from "/src/components/Grid" # Next Steps -Now that your foundational knowledge is in place and your workspace is configured, you’re ready to dive in and learn how to deploy production-grade infrastructure. If you’ve purchased a Gruntwork Reference Architecture, use [this guide](/docs/guides/reference-architecture) to get started. Otherwise, view our [courses](/docs/courses) and [guides](/docs/guides/welcome), or check out the [Service Catalog API reference](/docs/reference/services/intro) to learn what’s available. +Now that your foundational knowledge is in place and your workspace is configured, you’re ready to dive in and learn how to deploy production-grade infrastructure. If you’ve purchased a Gruntwork Reference Architecture, use [this guide](/docs/guides/reference-architecture) to get started. Otherwise, view our [courses](/docs/courses) and [guides](/docs/guides), or check out the [Service Catalog API reference](/docs/reference/services/intro) to learn what’s available. diff --git a/docs/intro/overview/getting-started.mdx b/docs/intro/overview/getting-started.mdx index 38e0377084..1e742496e9 100644 --- a/docs/intro/overview/getting-started.mdx +++ b/docs/intro/overview/getting-started.mdx @@ -2,7 +2,7 @@ import { CardList } from "/src/components/CardGroup" # Getting started -In this introductory guide we’ll cover the fundamentals you'll need in order to be successful with Gruntwork. After setting up your account to gain access to Gruntwork products, we’ll help you install necessary tools and understand how they fit into the Gruntwork development workflow. Once finished, you’ll have the knowledge required to dive into our [guides](/docs/guides/welcome) and make full use of the IaC Library. +In this introductory guide we’ll cover the fundamentals you'll need in order to be successful with Gruntwork. After setting up your account to gain access to Gruntwork products, we’ll help you install necessary tools and understand how they fit into the Gruntwork development workflow. Once finished, you’ll have the knowledge required to dive into our [guides](/docs/guides) and make full use of the IaC Library. diff --git a/sidebars/update-guides.js b/sidebars/update-guides.js index ee110cffd6..2567838441 100644 --- a/sidebars/update-guides.js +++ b/sidebars/update-guides.js @@ -77,7 +77,7 @@ const updateGuideSidebars = { ], terraform14: [ { - label: "Terraform 14", + label: "Update to Terraform 14", type: "category", link: { type: "doc", @@ -98,7 +98,7 @@ const updateGuideSidebars = { ], terraform15: [ { - label: "Terraform 15", + label: "Update to Terraform 15", type: "category", link: { type: "doc", @@ -118,7 +118,7 @@ const updateGuideSidebars = { ], terraform1x: [ { - label: "Terraform 1", + label: "Update to Terraform 1.X", type: "category", link: { type: "doc", @@ -137,7 +137,7 @@ const updateGuideSidebars = { ], terraformServiceProviderV3: [ { - label: "Aws Provider V 3", + label: "Update to AWS Provider v3", type: "category", link: { type: "doc", @@ -151,7 +151,7 @@ const updateGuideSidebars = { ], dryRefArch: [ { - label: "How To Dry Your Reference Architecture", + label: "How To DRY Your Reference Architecture", type: "category", link: { type: "doc", diff --git a/src/pages/index.tsx b/src/pages/index.tsx index 17b0888ed3..60201861f2 100644 --- a/src/pages/index.tsx +++ b/src/pages/index.tsx @@ -54,7 +54,7 @@ export default function Home(): JSX.Element { Follow our tutorials and learn how to deploy Gruntwork services From 5d2a5d6c6d1c0032510dead5b5a9820db8da758e Mon Sep 17 00:00:00 2001 From: Eben Eliason Date: Thu, 13 Jan 2022 12:49:22 -0800 Subject: [PATCH 16/20] Remove build-it-yourself overview, fix links --- .../guides/build-it-yourself/overview.md | 63 ----------------- _docs-sources/intro/next-steps.mdx | 2 +- _docs-sources/intro/overview/how-it-works.md | 2 +- docs/guides/build-it-yourself/overview.md | 68 ------------------- docs/intro/next-steps.mdx | 4 +- docs/intro/overview/how-it-works.md | 4 +- 6 files changed, 6 insertions(+), 137 deletions(-) delete mode 100644 _docs-sources/guides/build-it-yourself/overview.md delete mode 100644 docs/guides/build-it-yourself/overview.md diff --git a/_docs-sources/guides/build-it-yourself/overview.md b/_docs-sources/guides/build-it-yourself/overview.md deleted file mode 100644 index f429ac2e12..0000000000 --- a/_docs-sources/guides/build-it-yourself/overview.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -sidebar_label: Overview -pagination_label: Build It Yourself ---- - -import Card from "/src/components/Card" -import Grid from "/src/components/Grid" - -# Build Your Own Architecture - -The Gruntwork IaC library empowers you to construct your own bespoke architecture in record time. By mix-and-matching our modules and services you can quickly define a custom architecture to suit your needs, all with the confidence of having world-class, battle-tested code running under the hood. This series of guides aims to teach you how to configure and deploy some of our most popular services. Additional guides will be added over time, but the principles covered extend to the rest of the IaC library. If you have trouble, don’t hesitate to ask questions via our [support channels](/docs/guides/support). - -### Follow Our Step-By-Step Guides - - - - Set up a multi-account structure using Gruntwork Landing Zone. - - - Implement continuous deployment for your infrastructure code with Gruntwork - Pipelines. - - - Set up your network according to industry best practices using our VPC service. - - - Deploy a Kubernetes Cluster to host all of your apps and services. - - - Make your infrastructure compliant with the CIS AWS Foundations Benchmark. - - - -### Dig Into the Code - - - - View the API reference for our entire service catalog to learn what’s - available. - - - If you're the type who likes to jump straight to the source, this is for - you. - - diff --git a/_docs-sources/intro/next-steps.mdx b/_docs-sources/intro/next-steps.mdx index 1daba962a0..027dca9a41 100644 --- a/_docs-sources/intro/next-steps.mdx +++ b/_docs-sources/intro/next-steps.mdx @@ -19,7 +19,7 @@ Now that your foundational knowledge is in place and your workspace is configure Learn how to utilize our service modules to construct a world-class architecture on your own. diff --git a/_docs-sources/intro/overview/how-it-works.md b/_docs-sources/intro/overview/how-it-works.md index 839d7f66fc..ad9a44aee5 100644 --- a/_docs-sources/intro/overview/how-it-works.md +++ b/_docs-sources/intro/overview/how-it-works.md @@ -5,7 +5,7 @@ There are two fundamental ways to engage Gruntwork: 1. **Gruntwork builds your architecture.** We generate the [Reference Architecture](https://gruntwork.io/reference-architecture/) based on your needs, deploy into your AWS accounts, and give you 100% of the code. Since you have all the code, you can extend, enhance, and customize the environment exactly according to your needs. The deploy process takes about one day. -2. **Build it yourself.** The Gruntwork IaC library empowers you to [construct your own bespoke architecture](/docs/guides/build-it-yourself/overview) in record time. By mix-and-matching our modules and services you can quickly define a custom architecture to suit your needs, all with the confidence of having world-class, battle-tested code running under the hood. +2. **Build it yourself.** The Gruntwork IaC library empowers you to [construct your own bespoke architecture](/docs/guides#build-your-own-architecture) in record time. By mix-and-matching our modules and services you can quickly define a custom architecture to suit your needs, all with the confidence of having world-class, battle-tested code running under the hood. ## What we provide diff --git a/docs/guides/build-it-yourself/overview.md b/docs/guides/build-it-yourself/overview.md deleted file mode 100644 index a76c65d7ac..0000000000 --- a/docs/guides/build-it-yourself/overview.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -sidebar_label: Overview -pagination_label: Build It Yourself ---- - -import Card from "/src/components/Card" -import Grid from "/src/components/Grid" - -# Build Your Own Architecture - -The Gruntwork IaC library empowers you to construct your own bespoke architecture in record time. By mix-and-matching our modules and services you can quickly define a custom architecture to suit your needs, all with the confidence of having world-class, battle-tested code running under the hood. This series of guides aims to teach you how to configure and deploy some of our most popular services. Additional guides will be added over time, but the principles covered extend to the rest of the IaC library. If you have trouble, don’t hesitate to ask questions via our [support channels](/docs/guides/support). - -### Follow Our Step-By-Step Guides - - - - Set up a multi-account structure using Gruntwork Landing Zone. - - - Implement continuous deployment for your infrastructure code with Gruntwork - Pipelines. - - - Set up your network according to industry best practices using our VPC service. - - - Deploy a Kubernetes Cluster to host all of your apps and services. - - - Make your infrastructure compliant with the CIS AWS Foundations Benchmark. - - - -### Dig Into the Code - - - - View the API reference for our entire service catalog to learn what’s - available. - - - If you're the type who likes to jump straight to the source, this is for - you. - - - - - diff --git a/docs/intro/next-steps.mdx b/docs/intro/next-steps.mdx index 67342746f9..186e42f3c4 100644 --- a/docs/intro/next-steps.mdx +++ b/docs/intro/next-steps.mdx @@ -19,7 +19,7 @@ Now that your foundational knowledge is in place and your workspace is configure Learn how to utilize our service modules to construct a world-class architecture on your own. @@ -28,5 +28,5 @@ Now that your foundational knowledge is in place and your workspace is configure diff --git a/docs/intro/overview/how-it-works.md b/docs/intro/overview/how-it-works.md index f1245c241d..835fa3d927 100644 --- a/docs/intro/overview/how-it-works.md +++ b/docs/intro/overview/how-it-works.md @@ -5,7 +5,7 @@ There are two fundamental ways to engage Gruntwork: 1. **Gruntwork builds your architecture.** We generate the [Reference Architecture](https://gruntwork.io/reference-architecture/) based on your needs, deploy into your AWS accounts, and give you 100% of the code. Since you have all the code, you can extend, enhance, and customize the environment exactly according to your needs. The deploy process takes about one day. -2. **Build it yourself.** The Gruntwork IaC library empowers you to [construct your own bespoke architecture](/docs/guides/build-it-yourself/overview) in record time. By mix-and-matching our modules and services you can quickly define a custom architecture to suit your needs, all with the confidence of having world-class, battle-tested code running under the hood. +2. **Build it yourself.** The Gruntwork IaC library empowers you to [construct your own bespoke architecture](/docs/guides#build-your-own-architecture) in record time. By mix-and-matching our modules and services you can quickly define a custom architecture to suit your needs, all with the confidence of having world-class, battle-tested code running under the hood. ## What we provide @@ -55,5 +55,5 @@ Gruntwork products strike a balance between opinionatedness and configurability. From 46ba9d27114ca6ec73933f39bc8142d96b2eab1d Mon Sep 17 00:00:00 2001 From: Eben Eliason Date: Thu, 13 Jan 2022 13:03:42 -0800 Subject: [PATCH 17/20] Fix link to guides in nav --- docusaurus.config.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docusaurus.config.js b/docusaurus.config.js index 7923ba3f6b..680484d487 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -75,7 +75,7 @@ const config = { type: "doc", position: "left", label: "Guides", - docId: "guides/welcome", + docId: "guides/index", activeBasePath: "docs/guides", }, { From 66fe74b557460419254efd454a3b5f23c425f15c Mon Sep 17 00:00:00 2001 From: Eugene K Date: Fri, 14 Jan 2022 14:57:15 -0500 Subject: [PATCH 18/20] Fixed 36 broken external links that were caused by an erroneous replacement. --- ...tain-compliance-by-following-storage-best-practices.md | 2 +- .../achieve-compliance/production-grade-design/storage.md | 2 +- .../landing-zone/core-concepts/iam-roles.md | 2 +- .../production-grade-design/iam-roles-for-services.md | 2 +- .../production-grade-design/password-policy.md | 2 +- .../vpc/production-grade-design/bastion-host.md | 2 +- .../deployment-walkthrough/step-3-manual-steps.md | 4 ++-- .../deployment-walkthrough.md | 6 +++--- .../terraform/terraform-12/deployment-walkthrough.md | 2 +- .../terraform/terraform-13/core-concepts.md | 4 ++-- .../stay-up-to-date/terraform/terraform-13/index.md | 2 +- .../terraform/terraform-14/core-concepts.md | 2 +- ...tain-compliance-by-following-storage-best-practices.md | 4 ++-- .../achieve-compliance/production-grade-design/storage.md | 4 ++-- .../landing-zone/core-concepts/iam-roles.md | 4 ++-- .../production-grade-design/iam-roles-for-services.md | 4 ++-- .../production-grade-design/password-policy.md | 4 ++-- .../vpc/production-grade-design/bastion-host.md | 4 ++-- .../deployment-walkthrough/step-3-manual-steps.md | 6 +++--- .../deployment-walkthrough.md | 8 ++++---- .../terraform/terraform-12/deployment-walkthrough.md | 4 ++-- .../terraform/terraform-13/core-concepts.md | 6 +++--- .../stay-up-to-date/terraform/terraform-13/index.md | 4 ++-- .../terraform/terraform-14/core-concepts.md | 4 ++-- 24 files changed, 44 insertions(+), 44 deletions(-) diff --git a/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-storage-best-practices.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-storage-best-practices.md index 3eba448323..0db98462d5 100644 --- a/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-storage-best-practices.md +++ b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-storage-best-practices.md @@ -3,7 +3,7 @@ ## S3 Buckets To make sure your S3 buckets are compliant with the benchmark, use the -[`private-s3-bucket` module](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/private-sbucket) +[`private-s3-bucket` module](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/private-s3-bucket) to create and manage all of your S3 buckets. This module blocks public access and enforces encryption by default. Note that all Gruntwork modules that create S3 buckets use this module under the hood. diff --git a/_docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/storage.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/storage.md index fa5d9f7413..698d7a55c7 100644 --- a/_docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/storage.md +++ b/_docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/storage.md @@ -105,7 +105,7 @@ aws s3api put-bucket-versioning --region \ --mfa "arn:aws:iam:::mfa/root-account-mfa-device " ``` -We also created a [script](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/private-sbucket/mfa-delete-script) to help you enable MFA Delete in all buckets from a single account at once. To learn how to run it and when, please follow the production _Deployment Walkthrough_ guide section below. +We also created a [script](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/private-s3-bucket/mfa-delete-script) to help you enable MFA Delete in all buckets from a single account at once. To learn how to run it and when, please follow the production _Deployment Walkthrough_ guide section below. ### Configure Amazon Macie (recommendation 2.1.4) diff --git a/_docs-sources/guides/build-it-yourself/landing-zone/core-concepts/iam-roles.md b/_docs-sources/guides/build-it-yourself/landing-zone/core-concepts/iam-roles.md index a352e5e873..f8c9bccb7c 100644 --- a/_docs-sources/guides/build-it-yourself/landing-zone/core-concepts/iam-roles.md +++ b/_docs-sources/guides/build-it-yourself/landing-zone/core-concepts/iam-roles.md @@ -112,7 +112,7 @@ The basic steps are: Most AWS services have native support built-in for assuming IAM roles. For example, you can associate an IAM role directly with an EC2 instance, and that instance will automatically assume the IAM role every few hours, making the temporary credentials available in -_[EC2 instance metadata](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ecinstance-metadata.html#instancedata-data-retrieval)_. +_[EC2 instance metadata](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html#instancedata-data-retrieval)_. Just about every AWS CLI and SDK tool knows how to read and periodically update temporary credentials from EC2 instance metadata, so in practice, as soon as you attach an IAM role to an EC2 instance, any code running on that EC2 instance can automatically make API calls on behalf of that IAM role, with whatever permissions are attached to that diff --git a/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-services.md b/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-services.md index 24fc0ab50c..faf48d8e18 100644 --- a/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-services.md +++ b/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/iam-roles-for-services.md @@ -89,7 +89,7 @@ want an IAM role that can be assumed by a Lambda function, the `Principal` will While IAM roles offer a convenient way to give an EC2 instance permissions to make API calls without having to manually copy credentials to the EC2 instance, the default security configuration for them is not particularly secure. That’s because the IAM role is exposed to the code on the EC2 instance through -[EC2 instance metadata](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ecinstance-metadata.html#instancedata-data-retrieval), +[EC2 instance metadata](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html#instancedata-data-retrieval), which is an http endpoint (`\http://169.254.169.254`) that _anyone_ on the EC2 instance can access. That means that any compromise of that EC2 instance instantly gives an attacker access to all the permissions in that IAM role. We **strongly** recommend mitigating this by limiting access to the endpoint solely to specific OS users (e.g., solely to diff --git a/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/password-policy.md b/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/password-policy.md index 1e586991ea..8f5ceaa5c4 100644 --- a/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/password-policy.md +++ b/_docs-sources/guides/build-it-yourself/landing-zone/production-grade-design/password-policy.md @@ -3,4 +3,4 @@ In any account that has IAM users (which should just be the root and security accounts), configure a password policy that ensures all IAM users have strong passwords. The exact policy you use depends on your company’s requirements (e.g., certain compliance requirements may force you to use a specific password policy), but you may want to consider -[NIST 800-63 guidelines](https://pages.nist.gov/8063/sp8063b.html#memsecret) as a reasonable starting point. +[NIST 800-63 guidelines](https://pages.nist.gov/800-63-3/sp800-63b.html#memsecret) as a reasonable starting point. diff --git a/_docs-sources/guides/build-it-yourself/vpc/production-grade-design/bastion-host.md b/_docs-sources/guides/build-it-yourself/vpc/production-grade-design/bastion-host.md index 370db5178f..e8d421ab0b 100644 --- a/_docs-sources/guides/build-it-yourself/vpc/production-grade-design/bastion-host.md +++ b/_docs-sources/guides/build-it-yourself/vpc/production-grade-design/bastion-host.md @@ -13,7 +13,7 @@ the server, lock down all ports (except SSH and/or VPN), rebuild and redeploy th the `How to deploy a production-grade bastion host on AWS` guide _(coming soon!)_ for full details on bastion hosts. Other solutions that can work with resources in private subnets include -[EC2 Instance Connect](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Connect-using-ECInstance-Connect.html), +[EC2 Instance Connect](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Connect-using-EC2-Instance-Connect.html), which can allow you to SSH to EC2 Instances via a browser-based SSH client in the Amazon EC2 Console, and [AWS Systems Manager Sessions](https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager.html), which allow you to manage and connect to EC2 Instances via a custom protocol managed by AWS. diff --git a/_docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-3-manual-steps.md b/_docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-3-manual-steps.md index 0dea56df98..c8b237fb79 100644 --- a/_docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-3-manual-steps.md +++ b/_docs-sources/guides/stay-up-to-date/cis/cis-1.4.0/deployment-walkthrough/step-3-manual-steps.md @@ -39,7 +39,7 @@ We also created a script to help you enable MFA Delete in all buckets from a sin ### Using mfa-delete.sh -If you want to enable MFA Delete to _all_ your buckets at once, you can use the script at [terraform-aws-security/private-s3-bucket/mfa-delete-script](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/private-sbucket). You need to use the access keys for the root user and the root MFA code. +If you want to enable MFA Delete to _all_ your buckets at once, you can use the script at [terraform-aws-security/private-s3-bucket/mfa-delete-script](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/private-s3-bucket). You need to use the access keys for the root user and the root MFA code. Usage: @@ -88,7 +88,7 @@ so that it completely automates all the steps of configuring Amazon Macie, and n To set up Macie to analyze the desired S3 buckets, you’ll need to create a **Macie classification job**. Typically, you’ll want it to analyze all the buckets in the region. However, the terraform AWS provider does not support specifying all the buckets in a region - it requires that an explicit list of buckets be provided (see related bug [here](https://github.com/hashicorp/terraform-provider-aws/issues/20044)). Therefore, you’ll need to maintain an explicit list of buckets per region, namely in the variable `buckets_to_analyze`. Please read the -[documentation](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/blob/master/modules/security/macie/variables.tf#L2L30) +[documentation](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/blob/master/modules/security/macie/variables.tf#L21-L30) for this variable in order to understand how to structure the list of buckets per region. Once the above issue in the terraform AWS provider has been resolved, we will [update the Gruntwork macie module](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/issues/204) diff --git a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/deployment-walkthrough.md b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/deployment-walkthrough.md index 8ca342e672..5df6306702 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/deployment-walkthrough.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/how-to-update-to-aws-provider-v3/deployment-walkthrough.md @@ -164,17 +164,17 @@ to update your snapshot of the Gruntwork Reference Architecture: #### CIS Reference Architecture Refer to the release notes for -[v0.0.1-20201021](https://github.com/gruntwork-io/cis-infrastructure-live-acme/releases/tag/v0.0.20201021) +[v0.0.1-20201021](https://github.com/gruntwork-io/cis-infrastructure-live-acme/releases/tag/v0.0.1-20201021) of the `cis-infrastructure-live-acme` repository for instructions on how to update the CIS components of the Reference Architecture to be compatible with AWS provider v3. For all other components, refer to the release notes for -[v0.0.1-20201021](https://github.com/gruntwork-io/infrastructure-modules-multi-account-acme/releases/tag/v0.0.20201021) +[v0.0.1-20201021](https://github.com/gruntwork-io/infrastructure-modules-multi-account-acme/releases/tag/v0.0.1-20201021) of the `infrastructure-modules-multi-account-acme` repository. #### Standard Reference Architecture Refer to the release notes for -[v0.0.1-20201021](https://github.com/gruntwork-io/infrastructure-modules-multi-account-acme/releases/tag/v0.0.20201021) +[v0.0.1-20201021](https://github.com/gruntwork-io/infrastructure-modules-multi-account-acme/releases/tag/v0.0.1-20201021) of the `infrastructure-modules-multi-account-acme` repository for instructions on how to update your components to be compatible with AWS provider v3. diff --git a/_docs-sources/guides/stay-up-to-date/terraform/terraform-12/deployment-walkthrough.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-12/deployment-walkthrough.md index bf12ffe986..17d2f6ac65 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/terraform-12/deployment-walkthrough.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/terraform-12/deployment-walkthrough.md @@ -16,7 +16,7 @@ that prevent using your TF11 and older modules directly with TF12. For the safes going through the process of updating all your modules to use the new HCL2 syntax using the `terraform 0.12upgrade` tool that ships with TF12. -Before starting, read through the [Terraform 0.12 upgrade guide](https://www.terraform.io/upgrade-guides/12.html) so +Before starting, read through the [Terraform 0.12 upgrade guide](https://www.terraform.io/upgrade-guides/0-12.html) so you can learn about the types of changes you’ll have to make. Familiarity of the changes help with detecting errors and gotchas that the upgrade tool occasionally misses. diff --git a/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/core-concepts.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/core-concepts.md index 4d3ea5d63e..e4945a1842 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/core-concepts.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/core-concepts.md @@ -1,6 +1,6 @@ # Core Concepts -[Terraform 0.13 was released on August 10th, 2020](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-13). +[Terraform 0.13 was released on August 10th, 2020](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-0-13). Some of the major new features in 0.13 include: 1. The ability to use `count`, `for_each`, and `depends_on` with modules. @@ -9,7 +9,7 @@ Some of the major new features in 0.13 include: 3. Custom variable validation. -For more info, check out the [announcement blog post](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-13). +For more info, check out the [announcement blog post](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-0-13). 0.13 is a major new release for Terraform, which means it includes a number of backwards incompatible changes. We have gone through all the Terraform modules in the [Gruntwork diff --git a/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/index.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/index.md index 7627774aed..ba59454e8a 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/index.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/terraform-13/index.md @@ -3,7 +3,7 @@ This guide will walk you through how to update the [Gruntwork Reference Architecture](https://gruntwork.io/reference-architecture/) and any code that depends on the [Gruntwork Infrastructure as Code Library](https://gruntwork.io/infrastructure-as-code-library/) to -[Terraform 0.13](https://www.terraform.io/upgrade-guides/13.html). Terraform 0.13 introduces a number of new features +[Terraform 0.13](https://www.terraform.io/upgrade-guides/0-13.html). Terraform 0.13 introduces a number of new features and fixes, but it also has a number of backwards incompatibilities that have to be incorporated into your codebase. ## What you’ll learn in this guide diff --git a/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/core-concepts.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/core-concepts.md index 4ef1e88abf..2d12241d99 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/core-concepts.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/terraform-14/core-concepts.md @@ -10,7 +10,7 @@ December 02, 2020](https://www.hashicorp.com/blog/announcing-hashicorp-terraform 3. A lock file for provider dependency versions. For more info, check out the -[announcement blog post](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-1general-availability). +[announcement blog post](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-0-14-general-availability). 0.14 is a major new release for Terraform, which means it includes some backwards incompatible changes. We have gone through all the Terraform modules in the [Gruntwork 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 114709e65a..e30b38e0a9 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 @@ -3,7 +3,7 @@ ## S3 Buckets To make sure your S3 buckets are compliant with the benchmark, use the -[`private-s3-bucket` module](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/private-sbucket) +[`private-s3-bucket` module](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/private-s3-bucket) to create and manage all of your S3 buckets. This module blocks public access and enforces encryption by default. Note that all Gruntwork modules that create S3 buckets use this module under the hood. @@ -18,5 +18,5 @@ the hood. 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 15c4ae87c5..88df6a65a6 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 @@ -105,7 +105,7 @@ aws s3api put-bucket-versioning --region \ --mfa "arn:aws:iam:::mfa/root-account-mfa-device " ``` -We also created a [script](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/private-sbucket/mfa-delete-script) to help you enable MFA Delete in all buckets from a single account at once. To learn how to run it and when, please follow the production _Deployment Walkthrough_ guide section below. +We also created a [script](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/private-s3-bucket/mfa-delete-script) to help you enable MFA Delete in all buckets from a single account at once. To learn how to run it and when, please follow the production _Deployment Walkthrough_ guide section below. ### Configure Amazon Macie (recommendation 2.1.4) @@ -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/landing-zone/core-concepts/iam-roles.md b/docs/guides/build-it-yourself/landing-zone/core-concepts/iam-roles.md index a48e5683f0..a0ec4602cb 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 @@ -112,7 +112,7 @@ The basic steps are: Most AWS services have native support built-in for assuming IAM roles. For example, you can associate an IAM role directly with an EC2 instance, and that instance will automatically assume the IAM role every few hours, making the temporary credentials available in -_[EC2 instance metadata](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ecinstance-metadata.html#instancedata-data-retrieval)_. +_[EC2 instance metadata](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html#instancedata-data-retrieval)_. Just about every AWS CLI and SDK tool knows how to read and periodically update temporary credentials from EC2 instance metadata, so in practice, as soon as you attach an IAM role to an EC2 instance, any code running on that EC2 instance can automatically make API calls on behalf of that IAM role, with whatever permissions are attached to that @@ -125,5 +125,5 @@ services permissions to access specific resources in your AWS account. 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 b50910f858..85e905f232 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 @@ -89,7 +89,7 @@ want an IAM role that can be assumed by a Lambda function, the `Principal` will While IAM roles offer a convenient way to give an EC2 instance permissions to make API calls without having to manually copy credentials to the EC2 instance, the default security configuration for them is not particularly secure. That’s because the IAM role is exposed to the code on the EC2 instance through -[EC2 instance metadata](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ecinstance-metadata.html#instancedata-data-retrieval), +[EC2 instance metadata](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html#instancedata-data-retrieval), which is an http endpoint (`\http://169.254.169.254`) that _anyone_ on the EC2 instance can access. That means that any compromise of that EC2 instance instantly gives an attacker access to all the permissions in that IAM role. We **strongly** recommend mitigating this by limiting access to the endpoint solely to specific OS users (e.g., solely to @@ -136,5 +136,5 @@ sensitive machine user access keys. 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 18395fb742..0d1c9a950f 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 @@ -3,9 +3,9 @@ In any account that has IAM users (which should just be the root and security accounts), configure a password policy that ensures all IAM users have strong passwords. The exact policy you use depends on your company’s requirements (e.g., certain compliance requirements may force you to use a specific password policy), but you may want to consider -[NIST 800-63 guidelines](https://pages.nist.gov/8063/sp8063b.html#memsecret) as a reasonable starting point. +[NIST 800-63 guidelines](https://pages.nist.gov/800-63-3/sp800-63b.html#memsecret) as a reasonable starting point. 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 e72c76d0a8..445c6a8726 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 @@ -13,12 +13,12 @@ the server, lock down all ports (except SSH and/or VPN), rebuild and redeploy th the `How to deploy a production-grade bastion host on AWS` guide _(coming soon!)_ for full details on bastion hosts. Other solutions that can work with resources in private subnets include -[EC2 Instance Connect](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Connect-using-ECInstance-Connect.html), +[EC2 Instance Connect](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Connect-using-EC2-Instance-Connect.html), which can allow you to SSH to EC2 Instances via a browser-based SSH client in the Amazon EC2 Console, and [AWS Systems Manager Sessions](https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager.html), which allow you to manage and connect to EC2 Instances via a custom protocol managed by AWS. 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 178fc84900..505f9064ea 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 @@ -39,7 +39,7 @@ We also created a script to help you enable MFA Delete in all buckets from a sin ### Using mfa-delete.sh -If you want to enable MFA Delete to _all_ your buckets at once, you can use the script at [terraform-aws-security/private-s3-bucket/mfa-delete-script](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/private-sbucket). You need to use the access keys for the root user and the root MFA code. +If you want to enable MFA Delete to _all_ your buckets at once, you can use the script at [terraform-aws-security/private-s3-bucket/mfa-delete-script](https://github.com/gruntwork-io/terraform-aws-security/tree/master/modules/private-s3-bucket). You need to use the access keys for the root user and the root MFA code. Usage: @@ -88,7 +88,7 @@ so that it completely automates all the steps of configuring Amazon Macie, and n To set up Macie to analyze the desired S3 buckets, you’ll need to create a **Macie classification job**. Typically, you’ll want it to analyze all the buckets in the region. However, the terraform AWS provider does not support specifying all the buckets in a region - it requires that an explicit list of buckets be provided (see related bug [here](https://github.com/hashicorp/terraform-provider-aws/issues/20044)). Therefore, you’ll need to maintain an explicit list of buckets per region, namely in the variable `buckets_to_analyze`. Please read the -[documentation](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/blob/master/modules/security/macie/variables.tf#L2L30) +[documentation](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/blob/master/modules/security/macie/variables.tf#L21-L30) for this variable in order to understand how to structure the list of buckets per region. Once the above issue in the terraform AWS provider has been resolved, we will [update the Gruntwork macie module](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/issues/204) @@ -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/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 94de271712..93fa27f996 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 @@ -164,17 +164,17 @@ to update your snapshot of the Gruntwork Reference Architecture: #### CIS Reference Architecture Refer to the release notes for -[v0.0.1-20201021](https://github.com/gruntwork-io/cis-infrastructure-live-acme/releases/tag/v0.0.20201021) +[v0.0.1-20201021](https://github.com/gruntwork-io/cis-infrastructure-live-acme/releases/tag/v0.0.1-20201021) of the `cis-infrastructure-live-acme` repository for instructions on how to update the CIS components of the Reference Architecture to be compatible with AWS provider v3. For all other components, refer to the release notes for -[v0.0.1-20201021](https://github.com/gruntwork-io/infrastructure-modules-multi-account-acme/releases/tag/v0.0.20201021) +[v0.0.1-20201021](https://github.com/gruntwork-io/infrastructure-modules-multi-account-acme/releases/tag/v0.0.1-20201021) of the `infrastructure-modules-multi-account-acme` repository. #### Standard Reference Architecture Refer to the release notes for -[v0.0.1-20201021](https://github.com/gruntwork-io/infrastructure-modules-multi-account-acme/releases/tag/v0.0.20201021) +[v0.0.1-20201021](https://github.com/gruntwork-io/infrastructure-modules-multi-account-acme/releases/tag/v0.0.1-20201021) of the `infrastructure-modules-multi-account-acme` repository for instructions on how to update your components to be compatible with AWS provider v3. @@ -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/terraform-12/deployment-walkthrough.md b/docs/guides/stay-up-to-date/terraform/terraform-12/deployment-walkthrough.md index 746ad52884..23c4b40192 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 @@ -16,7 +16,7 @@ that prevent using your TF11 and older modules directly with TF12. For the safes going through the process of updating all your modules to use the new HCL2 syntax using the `terraform 0.12upgrade` tool that ships with TF12. -Before starting, read through the [Terraform 0.12 upgrade guide](https://www.terraform.io/upgrade-guides/12.html) so +Before starting, read through the [Terraform 0.12 upgrade guide](https://www.terraform.io/upgrade-guides/0-12.html) so you can learn about the types of changes you’ll have to make. Familiarity of the changes help with detecting errors and gotchas that the upgrade tool occasionally misses. @@ -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-13/core-concepts.md b/docs/guides/stay-up-to-date/terraform/terraform-13/core-concepts.md index cabf5c6c68..b4d950d5eb 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 @@ -1,6 +1,6 @@ # Core Concepts -[Terraform 0.13 was released on August 10th, 2020](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-13). +[Terraform 0.13 was released on August 10th, 2020](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-0-13). Some of the major new features in 0.13 include: 1. The ability to use `count`, `for_each`, and `depends_on` with modules. @@ -9,7 +9,7 @@ Some of the major new features in 0.13 include: 3. Custom variable validation. -For more info, check out the [announcement blog post](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-13). +For more info, check out the [announcement blog post](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-0-13). 0.13 is a major new release for Terraform, which means it includes a number of backwards incompatible changes. We have gone through all the Terraform modules in the [Gruntwork @@ -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/index.md b/docs/guides/stay-up-to-date/terraform/terraform-13/index.md index 700144ca6a..1e2814f01e 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 @@ -3,7 +3,7 @@ This guide will walk you through how to update the [Gruntwork Reference Architecture](https://gruntwork.io/reference-architecture/) and any code that depends on the [Gruntwork Infrastructure as Code Library](https://gruntwork.io/infrastructure-as-code-library/) to -[Terraform 0.13](https://www.terraform.io/upgrade-guides/13.html). Terraform 0.13 introduces a number of new features +[Terraform 0.13](https://www.terraform.io/upgrade-guides/0-13.html). Terraform 0.13 introduces a number of new features and fixes, but it also has a number of backwards incompatibilities that have to be incorporated into your codebase. ## What you’ll learn in this guide @@ -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 6f3a0651c3..7045c84864 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 @@ -10,7 +10,7 @@ December 02, 2020](https://www.hashicorp.com/blog/announcing-hashicorp-terraform 3. A lock file for provider dependency versions. For more info, check out the -[announcement blog post](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-1general-availability). +[announcement blog post](https://www.hashicorp.com/blog/announcing-hashicorp-terraform-0-14-general-availability). 0.14 is a major new release for Terraform, which means it includes some backwards incompatible changes. We have gone through all the Terraform modules in the [Gruntwork @@ -19,5 +19,5 @@ update to these new versions and make other changes to your code, as described i From b290345980a167e4f40c6c8a1ec1eb32fe21cc37 Mon Sep 17 00:00:00 2001 From: Eugene K Date: Fri, 14 Jan 2022 16:00:55 -0500 Subject: [PATCH 19/20] Fixed another broken link --- ...maintain-compliance-by-following-storage-best-practices.md | 2 +- ...maintain-compliance-by-following-storage-best-practices.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-storage-best-practices.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-storage-best-practices.md index 0db98462d5..2830856fb9 100644 --- a/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-storage-best-practices.md +++ b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/maintain-compliance-by-following-storage-best-practices.md @@ -8,7 +8,7 @@ to create and manage all of your S3 buckets. This module blocks public access an that all Gruntwork modules that create S3 buckets use this module under the hood. You can either use the `private-s3-bucket` module in your own modules, or, if you wish to deploy a standalone S3 bucket, -use the [`s3-bucket` service](https://github.com/gruntwork-io/terraform-aws-service-catalog/blob/master/modules/data-stores/sbucket/) +use the [`s3-bucket` service](https://github.com/gruntwork-io/terraform-aws-service-catalog/blob/master/modules/data-stores/s3-bucket/) from the Gruntwork Service Catalog. To ensure that all the data in your S3 buckets has been discovered, classified and secured, use the 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 e30b38e0a9..cf8cb3c16e 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 @@ -8,7 +8,7 @@ to create and manage all of your S3 buckets. This module blocks public access an that all Gruntwork modules that create S3 buckets use this module under the hood. You can either use the `private-s3-bucket` module in your own modules, or, if you wish to deploy a standalone S3 bucket, -use the [`s3-bucket` service](https://github.com/gruntwork-io/terraform-aws-service-catalog/blob/master/modules/data-stores/sbucket/) +use the [`s3-bucket` service](https://github.com/gruntwork-io/terraform-aws-service-catalog/blob/master/modules/data-stores/s3-bucket/) from the Gruntwork Service Catalog. To ensure that all the data in your S3 buckets has been discovered, classified and secured, use the @@ -18,5 +18,5 @@ the hood. From 980e9bd3d96336fc5cad308778d2708f5ca5c132 Mon Sep 17 00:00:00 2001 From: Eugene K Date: Fri, 14 Jan 2022 17:19:42 -0500 Subject: [PATCH 20/20] Fixed newly discovered broken links. --- .../deployment-walkthrough/create-vpc-flow-logs.md | 4 ++-- .../deployment-walkthrough/the-gruntwork-solution.md | 2 +- .../create-the-worker-node-ami.md | 2 +- .../production-grade-design/authenticate.md | 8 ++++---- .../core-concepts/default-vp-cs-and-custom-vp-cs.md | 2 +- .../build-it-yourself/vpc/core-concepts/subnets.md | 2 +- .../05-monitoring-alerting-logging/04-logs.md | 4 ++-- .../terraform/terraform-12/deployment-walkthrough.md | 2 +- .../intro/first-deployment/using-terraform-modules.md | 2 +- .../deployment-walkthrough/create-vpc-flow-logs.md | 6 +++--- .../deployment-walkthrough/the-gruntwork-solution.md | 4 ++-- .../create-the-worker-node-ami.md | 4 ++-- .../production-grade-design/authenticate.md | 10 +++++----- .../core-concepts/default-vp-cs-and-custom-vp-cs.md | 4 ++-- .../build-it-yourself/vpc/core-concepts/subnets.md | 4 ++-- .../05-monitoring-alerting-logging/04-logs.md | 6 +++--- .../terraform/terraform-12/deployment-walkthrough.md | 4 ++-- docs/intro/first-deployment/using-terraform-modules.md | 4 ++-- 18 files changed, 37 insertions(+), 37 deletions(-) diff --git a/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-vpc-flow-logs.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-vpc-flow-logs.md index be459ad3e8..e984ee2f33 100644 --- a/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-vpc-flow-logs.md +++ b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-vpc-flow-logs.md @@ -85,7 +85,7 @@ all regions in an account, saving you the hassle of creating flow logs in each d The Monitoring section of the Benchmark centers on a collection of [CloudWatch Logs Metric Filters](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/MonitoringLogData.html). Gruntwork has simplified this section to a single module: the -[`cloudwatch-logs-metric -filters` wrapper module](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/blob/master/modules/cloudwatch-logs-metric-filters/README.adoc). It will create and configure all the CloudWatch Logs metric filters necessary for +[`cloudwatch-logs-metric -filters` wrapper module](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/blob/master/modules/observability/cloudwatch-logs-metric-filters/README.adoc). It will create and configure all the CloudWatch Logs metric filters necessary for compliance with the Benchmark. Note that when you deploy the CIS account baseline modules, the CloudWatch Logs metric filters will be created and configured automatically, so that you don’t have to do anything special to enable the metric filters on the deployed CloudTrail configuration. @@ -147,7 +147,7 @@ inputs = { } ``` -Refer to the [terraform-aws-cis-service-catalog](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/tree/master/examples/for-learning-and-testing/networking/vpc/terraform) +Refer to the [terraform-aws-cis-service-catalog](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/tree/master/examples/for-learning-and-testing/networking/vpc/) repo for a more comprehensive example. Finally, run the [`cloud-nuke defaults-aws`](https://github.com/gruntwork-io/cloud-nuke) command to remove all diff --git a/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/the-gruntwork-solution.md b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/the-gruntwork-solution.md index 8defa123dc..293fb86b35 100644 --- a/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/the-gruntwork-solution.md +++ b/_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/the-gruntwork-solution.md @@ -22,7 +22,7 @@ Gruntwork’s [infrastructure as code repositories](https://gruntwork.io/repos). ## Standalone Compliance modules The standalone compliance modules complement the modules available in the IaC Library. They have the CIS compliance requirements built right in and may combine multiple modules including Core modules for a -specific use case. For example, the [`cleanup-expired-certs` standalone module](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/tree/master/modules/cleanup-expired-certs) deploys a Lambda function that runs regularly and automatically removes all expired SSL/TLS certificates stored in AWS IAM in compliance with recommendation 1.19 of the CIS AWS Foundations Benchmark. These modules are in the [`terraform-aws-cis-service-catalog` +specific use case. For example, the [`cleanup-expired-certs` standalone module](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/tree/master/modules/security/cleanup-expired-certs) deploys a Lambda function that runs regularly and automatically removes all expired SSL/TLS certificates stored in AWS IAM in compliance with recommendation 1.19 of the CIS AWS Foundations Benchmark. These modules are in the [`terraform-aws-cis-service-catalog` repository](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog) (accessible to Gruntwork Compliance subscribers). ## Compliance wrapper modules diff --git a/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/create-the-worker-node-ami.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/create-the-worker-node-ami.md index a2289781ab..27eaeae4bb 100644 --- a/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/create-the-worker-node-ami.md +++ b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/create-the-worker-node-ami.md @@ -101,7 +101,7 @@ This Packer template installs the following on top of the EKS-optimized AMI base the labels on a worker node EC2 instance and converts them to a format that can be passed to the EKS bootstrap script so that those tags show up as labels in Kubernetes. -- [cloudwatch-memory-disk-metrics-scripts](https://github.com/gruntwork-io/module-aws-monitoring/tree/master/modules/metrics/cloudwatch-memory-disk-metrics-scripts): +- [cloudwatch-agent](https://github.com/gruntwork-io/terraform-aws-monitoring/tree/master/modules/agents/cloudwatch-agent): Send memory and disk usage metrics for your EC2 Instances to CloudWatch. These metrics are not available by default as they are only visible from inside a VM. diff --git a/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/authenticate.md b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/authenticate.md index 75ca62b090..5a34446412 100644 --- a/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/authenticate.md +++ b/_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/authenticate.md @@ -14,7 +14,7 @@ setup instructions. To use it, you fist run the `update-kubeconfig` command:
-``` bash +```bash aws eks update-kubeconfig --region --name ``` @@ -29,12 +29,12 @@ i.e., the credentials file at `~/.aws/credentials`, environment variables, etc. `eksctl` is the official CLI tool for EKS. It’s primary purpose is to deploy and manage the EKS cluster itself, but you can also use it to authenticate to a cluster. To install `eksctl`, check out -[these instructions](https://eksctl.io/introduction/installation/). To authenticate with `eksctl`, you run the +[these instructions](https://eksctl.io/introduction/#installation). To authenticate with `eksctl`, you run the `eksctl utils write-kubeconfig` command: -``` bash +```bash eksctl utils write-kubeconfig --region --name= ``` @@ -53,7 +53,7 @@ run `kubergrunt eks configure`: -``` bash +```bash kubergrunt eks configure --eks-cluster-arn ``` diff --git a/_docs-sources/guides/build-it-yourself/vpc/core-concepts/default-vp-cs-and-custom-vp-cs.md b/_docs-sources/guides/build-it-yourself/vpc/core-concepts/default-vp-cs-and-custom-vp-cs.md index 09aac8d709..d6f5dbac19 100644 --- a/_docs-sources/guides/build-it-yourself/vpc/core-concepts/default-vp-cs-and-custom-vp-cs.md +++ b/_docs-sources/guides/build-it-yourself/vpc/core-concepts/default-vp-cs-and-custom-vp-cs.md @@ -38,7 +38,7 @@ fine-grained control over what network traffic can or can’t reach your AWS res Every AWS account created after 2013 requires that you use a VPC for just about all resources. If you don’t specify a VPC, your resource will be deployed into the -[_Default VPC_](https://docs.aws.amazon.com/vpc/latest/userguide/default-vpc.html:) in your AWS account. The Default VPC +[_Default VPC_](https://docs.aws.amazon.com/vpc/latest/userguide/default-vpc.html) in your AWS account. The Default VPC is great for learning and experimenting, but it is not a good choice for production use cases. That’s because the default settings in the Default VPC makes all your resources accessible on the public Internet, a bit like having no VPC at all. You can modify those settings to lock things down more, but it’s a lot of settings to change, and as diff --git a/_docs-sources/guides/build-it-yourself/vpc/core-concepts/subnets.md b/_docs-sources/guides/build-it-yourself/vpc/core-concepts/subnets.md index 1b87378598..bccb43e32e 100644 --- a/_docs-sources/guides/build-it-yourself/vpc/core-concepts/subnets.md +++ b/_docs-sources/guides/build-it-yourself/vpc/core-concepts/subnets.md @@ -2,7 +2,7 @@ ![VPCs partitioned into multiple subnets: public, private (services), private (persistence)](/img/guides/build-it-yourself/vpc/vpc-subnets-diagram.png) -Each VPC is partitioned into one or more _[subnets](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Subnets.html:)_ +Each VPC is partitioned into one or more _[subnets](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Subnets.html)_ (sub-networks). Each subnet controls a portion of the VPC’s CIDR range. For example, a VPC with the CIDR block `10.10.0.0/16` (all IPs from `10.10.0.0` - `10.10.255.255`) might be partitioned into two subnets, one with the CIDR block `10.10.0.0/17` (all IPs from `10.10.0.0` - `10.10.127.255`) and one with CIDR block `10.10.128.0/17` (all IPs diff --git a/_docs-sources/guides/reference-architecture/05-monitoring-alerting-logging/04-logs.md b/_docs-sources/guides/reference-architecture/05-monitoring-alerting-logging/04-logs.md index da7999fdc7..1f8e210bf1 100644 --- a/_docs-sources/guides/reference-architecture/05-monitoring-alerting-logging/04-logs.md +++ b/_docs-sources/guides/reference-architecture/05-monitoring-alerting-logging/04-logs.md @@ -1,7 +1,7 @@ # Logs -All of your services have been configured using the [`cloudwatch-log-aggregation-scripts` -module](https://github.com/gruntwork-io/terraform-aws-monitoring/tree/master/modules/logs/cloudwatch-log-aggregation-scripts) +All of your services have been configured using the [`cloudwatch-agent` +module](https://github.com/gruntwork-io/terraform-aws-monitoring/tree/master/modules/agents/cloudwatch-agent) to send their logs to [CloudWatch Logs](https://console.aws.amazon.com/cloudwatch/home?#logs:). Instead of SSHing to each server to see a log file, and worrying about losing those log files if the server fails, you can just go to the [CloudWatch Logs Page](https://console.aws.amazon.com/cloudwatch/home?#logs:) and browse and search log events for all diff --git a/_docs-sources/guides/stay-up-to-date/terraform/terraform-12/deployment-walkthrough.md b/_docs-sources/guides/stay-up-to-date/terraform/terraform-12/deployment-walkthrough.md index 17d2f6ac65..199f80a5e7 100644 --- a/_docs-sources/guides/stay-up-to-date/terraform/terraform-12/deployment-walkthrough.md +++ b/_docs-sources/guides/stay-up-to-date/terraform/terraform-12/deployment-walkthrough.md @@ -215,7 +215,7 @@ You can find the available binaries for each terragrunt version Once you have terragrunt 0.19 available on your machine, you will need to migrate your `terraform.tfvars` files to `terragrunt.hcl` files before you can start to use the new version. You will need to follow the steps outlined in the [Terragrunt 0.19.x migration -guide](https://github.com/gruntwork-io/terragrunt/blob/master/_docs/migration_guides/upgrading_to_terragrunt_0.19.x.md) +guide](https://github.com/gruntwork-io/terragrunt/blob/master/docs/_docs/06_migration_guides/upgrading_to_terragrunt_0.19.x.md) for each of your live config (e.g in your `infrastructure-live` repo). You should do this in parallel with each module upgrade. For example, if you were upgrading the module diff --git a/_docs-sources/intro/first-deployment/using-terraform-modules.md b/_docs-sources/intro/first-deployment/using-terraform-modules.md index 99cb943ea5..3a02fe35d5 100644 --- a/_docs-sources/intro/first-deployment/using-terraform-modules.md +++ b/_docs-sources/intro/first-deployment/using-terraform-modules.md @@ -172,7 +172,7 @@ should replace `` with the latest version from the releases page of the Below the `source` URL, you’ll need to pass in the module-specific arguments. You can find all the required and optional variables defined in `vars.tf` (old name) or `variables.tf` (new name) of the module (e.g., -here’s [the variables.tf for vpc-app](https://github.com/gruntwork-io/terraform-aws-vpc/blob/master/modules/vpc-app/vars.tf)). +here’s [the variables.tf for vpc-app](https://github.com/gruntwork-io/terraform-aws-vpc/blob/master/modules/vpc-app/variables.tf)). The code above sets these to input variables (which you’ll define shortly) so that you can use different values in different environments. 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 d0d9d08cee..081f56c810 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 @@ -85,7 +85,7 @@ all regions in an account, saving you the hassle of creating flow logs in each d The Monitoring section of the Benchmark centers on a collection of [CloudWatch Logs Metric Filters](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/MonitoringLogData.html). Gruntwork has simplified this section to a single module: the -[`cloudwatch-logs-metric -filters` wrapper module](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/blob/master/modules/cloudwatch-logs-metric-filters/README.adoc). It will create and configure all the CloudWatch Logs metric filters necessary for +[`cloudwatch-logs-metric -filters` wrapper module](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/blob/master/modules/observability/cloudwatch-logs-metric-filters/README.adoc). It will create and configure all the CloudWatch Logs metric filters necessary for compliance with the Benchmark. Note that when you deploy the CIS account baseline modules, the CloudWatch Logs metric filters will be created and configured automatically, so that you don’t have to do anything special to enable the metric filters on the deployed CloudTrail configuration. @@ -147,7 +147,7 @@ inputs = { } ``` -Refer to the [terraform-aws-cis-service-catalog](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/tree/master/examples/for-learning-and-testing/networking/vpc/terraform) +Refer to the [terraform-aws-cis-service-catalog](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/tree/master/examples/for-learning-and-testing/networking/vpc/) repo for a more comprehensive example. Finally, run the [`cloud-nuke defaults-aws`](https://github.com/gruntwork-io/cloud-nuke) command to remove all @@ -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/the-gruntwork-solution.md b/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/the-gruntwork-solution.md index a5ee2e71eb..18278310ce 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 @@ -22,7 +22,7 @@ Gruntwork’s [infrastructure as code repositories](https://gruntwork.io/repos). ## Standalone Compliance modules The standalone compliance modules complement the modules available in the IaC Library. They have the CIS compliance requirements built right in and may combine multiple modules including Core modules for a -specific use case. For example, the [`cleanup-expired-certs` standalone module](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/tree/master/modules/cleanup-expired-certs) deploys a Lambda function that runs regularly and automatically removes all expired SSL/TLS certificates stored in AWS IAM in compliance with recommendation 1.19 of the CIS AWS Foundations Benchmark. These modules are in the [`terraform-aws-cis-service-catalog` +specific use case. For example, the [`cleanup-expired-certs` standalone module](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog/tree/master/modules/security/cleanup-expired-certs) deploys a Lambda function that runs regularly and automatically removes all expired SSL/TLS certificates stored in AWS IAM in compliance with recommendation 1.19 of the CIS AWS Foundations Benchmark. These modules are in the [`terraform-aws-cis-service-catalog` repository](https://github.com/gruntwork-io/terraform-aws-cis-service-catalog) (accessible to Gruntwork Compliance subscribers). ## Compliance wrapper modules @@ -59,5 +59,5 @@ our [Introduction to Gruntwork](/docs/intro/overview/intro-to-gruntwork) section 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 2d435e1b0a..62bb0bfcba 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 @@ -101,7 +101,7 @@ This Packer template installs the following on top of the EKS-optimized AMI base the labels on a worker node EC2 instance and converts them to a format that can be passed to the EKS bootstrap script so that those tags show up as labels in Kubernetes. -- [cloudwatch-memory-disk-metrics-scripts](https://github.com/gruntwork-io/module-aws-monitoring/tree/master/modules/metrics/cloudwatch-memory-disk-metrics-scripts): +- [cloudwatch-agent](https://github.com/gruntwork-io/terraform-aws-monitoring/tree/master/modules/agents/cloudwatch-agent): Send memory and disk usage metrics for your EC2 Instances to CloudWatch. These metrics are not available by default as they are only visible from inside a VM. @@ -137,5 +137,5 @@ guide. 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 2dccb64211..6719a2af31 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 @@ -14,7 +14,7 @@ setup instructions. To use it, you fist run the `update-kubeconfig` command: -``` bash +```bash aws eks update-kubeconfig --region --name ``` @@ -29,12 +29,12 @@ i.e., the credentials file at `~/.aws/credentials`, environment variables, etc. `eksctl` is the official CLI tool for EKS. It’s primary purpose is to deploy and manage the EKS cluster itself, but you can also use it to authenticate to a cluster. To install `eksctl`, check out -[these instructions](https://eksctl.io/introduction/installation/). To authenticate with `eksctl`, you run the +[these instructions](https://eksctl.io/introduction/#installation). To authenticate with `eksctl`, you run the `eksctl utils write-kubeconfig` command: -``` bash +```bash eksctl utils write-kubeconfig --region --name= ``` @@ -53,7 +53,7 @@ run `kubergrunt eks configure`: -``` bash +```bash kubergrunt eks configure --eks-cluster-arn ``` @@ -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/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 a5ccffd23b..0ee8ae47bf 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 @@ -38,7 +38,7 @@ fine-grained control over what network traffic can or can’t reach your AWS res Every AWS account created after 2013 requires that you use a VPC for just about all resources. If you don’t specify a VPC, your resource will be deployed into the -[_Default VPC_](https://docs.aws.amazon.com/vpc/latest/userguide/default-vpc.html:) in your AWS account. The Default VPC +[_Default VPC_](https://docs.aws.amazon.com/vpc/latest/userguide/default-vpc.html) in your AWS account. The Default VPC is great for learning and experimenting, but it is not a good choice for production use cases. That’s because the default settings in the Default VPC makes all your resources accessible on the public Internet, a bit like having no VPC at all. You can modify those settings to lock things down more, but it’s a lot of settings to change, and as @@ -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/subnets.md b/docs/guides/build-it-yourself/vpc/core-concepts/subnets.md index fb4d08ef10..e099dd1acd 100644 --- a/docs/guides/build-it-yourself/vpc/core-concepts/subnets.md +++ b/docs/guides/build-it-yourself/vpc/core-concepts/subnets.md @@ -2,7 +2,7 @@ ![VPCs partitioned into multiple subnets: public, private (services), private (persistence)](/img/guides/build-it-yourself/vpc/vpc-subnets-diagram.png) -Each VPC is partitioned into one or more _[subnets](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Subnets.html:)_ +Each VPC is partitioned into one or more _[subnets](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Subnets.html)_ (sub-networks). Each subnet controls a portion of the VPC’s CIDR range. For example, a VPC with the CIDR block `10.10.0.0/16` (all IPs from `10.10.0.0` - `10.10.255.255`) might be partitioned into two subnets, one with the CIDR block `10.10.0.0/17` (all IPs from `10.10.0.0` - `10.10.127.255`) and one with CIDR block `10.10.128.0/17` (all IPs @@ -11,5 +11,5 @@ ranges. diff --git a/docs/guides/reference-architecture/05-monitoring-alerting-logging/04-logs.md b/docs/guides/reference-architecture/05-monitoring-alerting-logging/04-logs.md index 1c836f719c..64e59dbbc1 100644 --- a/docs/guides/reference-architecture/05-monitoring-alerting-logging/04-logs.md +++ b/docs/guides/reference-architecture/05-monitoring-alerting-logging/04-logs.md @@ -1,7 +1,7 @@ # Logs -All of your services have been configured using the [`cloudwatch-log-aggregation-scripts` -module](https://github.com/gruntwork-io/terraform-aws-monitoring/tree/master/modules/logs/cloudwatch-log-aggregation-scripts) +All of your services have been configured using the [`cloudwatch-agent` +module](https://github.com/gruntwork-io/terraform-aws-monitoring/tree/master/modules/agents/cloudwatch-agent) to send their logs to [CloudWatch Logs](https://console.aws.amazon.com/cloudwatch/home?#logs:). Instead of SSHing to each server to see a log file, and worrying about losing those log files if the server fails, you can just go to the [CloudWatch Logs Page](https://console.aws.amazon.com/cloudwatch/home?#logs:) and browse and search log events for all @@ -9,5 +9,5 @@ your servers in near-real-time. 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 23c4b40192..19848de4d5 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 @@ -215,7 +215,7 @@ You can find the available binaries for each terragrunt version Once you have terragrunt 0.19 available on your machine, you will need to migrate your `terraform.tfvars` files to `terragrunt.hcl` files before you can start to use the new version. You will need to follow the steps outlined in the [Terragrunt 0.19.x migration -guide](https://github.com/gruntwork-io/terragrunt/blob/master/_docs/migration_guides/upgrading_to_terragrunt_0.19.x.md) +guide](https://github.com/gruntwork-io/terragrunt/blob/master/docs/_docs/06_migration_guides/upgrading_to_terragrunt_0.19.x.md) for each of your live config (e.g in your `infrastructure-live` repo). You should do this in parallel with each module upgrade. For example, if you were upgrading the module @@ -430,5 +430,5 @@ At the end of this, you should be able to run `terragrunt plan` cleanly. diff --git a/docs/intro/first-deployment/using-terraform-modules.md b/docs/intro/first-deployment/using-terraform-modules.md index 722d4718e0..3b77cb22ce 100644 --- a/docs/intro/first-deployment/using-terraform-modules.md +++ b/docs/intro/first-deployment/using-terraform-modules.md @@ -172,7 +172,7 @@ should replace `` with the latest version from the releases page of the Below the `source` URL, you’ll need to pass in the module-specific arguments. You can find all the required and optional variables defined in `vars.tf` (old name) or `variables.tf` (new name) of the module (e.g., -here’s [the variables.tf for vpc-app](https://github.com/gruntwork-io/terraform-aws-vpc/blob/master/modules/vpc-app/vars.tf)). +here’s [the variables.tf for vpc-app](https://github.com/gruntwork-io/terraform-aws-vpc/blob/master/modules/vpc-app/variables.tf)). The code above sets these to input variables (which you’ll define shortly) so that you can use different values in different environments. @@ -248,5 +248,5 @@ output "private_persistence_subnet_ids" {