AWS prescriptive-guidance documentation change
Summary
Updated internal links, image paths, step numbering, and fixed a typo in 'Bootstrap AWS Account(s)'
Security assessment
Changes involve broken link fixes, image relocation, and minor text corrections without introducing security content or addressing vulnerabilities. The typo fix ('account' to 'Account') doesn't impact security.
Diff
diff --git a/prescriptive-guidance/latest/addf-security-and-operations/addf-architecture-terminology.md b/prescriptive-guidance/latest/addf-security-and-operations/addf-architecture-terminology.md index 04e68aaf1..fa90bfb16 100644 --- a//prescriptive-guidance/latest/addf-security-and-operations/addf-architecture-terminology.md +++ b//prescriptive-guidance/latest/addf-security-and-operations/addf-architecture-terminology.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Autonomous Driving Data Framework (ADDF) security and operations guide](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Autonomous Driving Data Framework (ADDF) security and operations guide](introduction.html) @@ -42 +42 @@ The ADDF deployment framework is designed to support deployments in single-accou - * **ADDF instance** – When you deploy ADDF and your modules in the cloud, as defined in your ADDF deployment manifest file, this becomes an _ADDF instance_. An ADDF instance can have a single-account or multi-account architecture, and you can deploy multiple ADDF instances. For more information about choosing the number of instances and designing an account architecture for your use case, see [Defining your ADDF architecture](./secure-setup-and-operation.html#defining-your-addf-architecture). + * **ADDF instance** – When you deploy ADDF and your modules in the cloud, as defined in your ADDF deployment manifest file, this becomes an _ADDF instance_. An ADDF instance can have a single-account or multi-account architecture, and you can deploy multiple ADDF instances. For more information about choosing the number of instances and designing an account architecture for your use case, see [Defining your ADDF architecture](./defining-your-addf-architecture.html). @@ -51 +51 @@ The following diagram shows a high-level architecture for an ADDF instance in th - + @@ -59 +59 @@ To function properly, each account must be bootstrapped to ADDF and to AWS CDK. - 2. Bootstrap ADDF in the toolchain account and each target account. For instructions, see _Bootstrap AWS account(s)_ in the [ADDF Deployment Guide](https://github.com/awslabs/autonomous-driving-data-framework/blob/main/docs/deployment_guide.md). This sets up all ADDF-specific IAM roles required by SeedFarmer and CodeSeeder. + 2. Bootstrap ADDF in the toolchain account and each target account. For instructions, see _Bootstrap AWS Account(s)_ in the [ADDF Deployment Guide](https://github.com/awslabs/autonomous-driving-data-framework/blob/main/docs/deployment_guide.md). This sets up all ADDF-specific IAM roles required by SeedFarmer and CodeSeeder. @@ -89 +89,4 @@ If SeedFarmer can start the evaluation, it assumes the ADDF toolchain IAM role i - 5. **Deploy the in-scope ADDF modules to the target accounts.** + + + + 1. **Deploy the in-scope ADDF modules to the target accounts.** @@ -95 +98 @@ If you use a single-account architecture, the toolchain account and the target a - 6. **Use the ADDF-deployed infrastructure.** + 2. **Use the ADDF-deployed infrastructure.** @@ -99 +102 @@ An ADAS developer can use the deployed ADAS-based workflow, as defined by your u -This workflow describes the architecture of a single instance of an ADDF multi-account environment. Depending on your development, deployment, and operations model, we recommend that you run multiple ADDF instances in a multi-stage environment. A typical setup might include a dedicated ADDF instance with dedicated AWS accounts for each deployment stage, such as branches for development, testing, and production. You can also run multiple ADDF instances in the same single-account or multi-account environment in the same AWS Region, assuming that you created a unique resource namespace for each ADDF instance. For more information, see [Defining your ADDF architecture](./secure-setup-and-operation.html#defining-your-addf-architecture). +This workflow describes the architecture of a single instance of an ADDF multi-account environment. Depending on your development, deployment, and operations model, we recommend that you run multiple ADDF instances in a multi-stage environment. A typical setup might include a dedicated ADDF instance with dedicated AWS accounts for each deployment stage, such as branches for development, testing, and production. You can also run multiple ADDF instances in the same single-account or multi-account environment in the same AWS Region, assuming that you created a unique resource namespace for each ADDF instance. For more information, see [Defining your ADDF architecture](./defining-your-addf-architecture.html).