AWS prescriptive-guidance documentation change
Summary
Fixed broken documentation links and URL formatting for AWS services (Systems Manager Patch Manager, CDK, CloudFormation, APN). Minor text formatting changes including space correction after a hyperlink.
Security assessment
Changes primarily correct URL paths and formatting without introducing new security content. While Patch Manager is a security-related service, these changes only fix documentation links rather than addressing vulnerabilities or adding security guidance.
Diff
diff --git a/prescriptive-guidance/latest/migration-replatforming-cots-applications/automating-os-patching.md b/prescriptive-guidance/latest/migration-replatforming-cots-applications/automating-os-patching.md index f9ee50fda..873eb7cde 100644 --- a//prescriptive-guidance/latest/migration-replatforming-cots-applications/automating-os-patching.md +++ b//prescriptive-guidance/latest/migration-replatforming-cots-applications/automating-os-patching.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Replatforming COTS and in-house applications during a migration to the AWS Cloud](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Replatforming COTS and in-house applications during a migration to the AWS Cloud](introduction.html) @@ -11 +11 @@ Using automation tools and infrastructure as a code (IaC) -Legacy applications in on-premises data centers often rely on manual operational processes for ongoing OS patching and software updates. During your replatforming journey, we recommend that you automate OS patching by using [Systems Manager Patch Manager](https://docs.aws.amazon.com//systems-manager/latest/userguide/systems-manager-patch.html) or other automated patching processes. Patch Manager provides a centralized and consistent process to gather operational insights and implement routine operational tasks on both the AWS Cloud and on-premises resources. +Legacy applications in on-premises data centers often rely on manual operational processes for ongoing OS patching and software updates. During your replatforming journey, we recommend that you automate OS patching by using [Systems Manager Patch Manager](https://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-patch.html) or other automated patching processes. Patch Manager provides a centralized and consistent process to gather operational insights and implement routine operational tasks on both the AWS Cloud and on-premises resources. @@ -13 +13 @@ Legacy applications in on-premises data centers often rely on manual operational -We recommend patching development environments earlier than the patching time window used for production environments. For more information about this, see the [Patch Manager runbook](https://docs.aws.amazon.com//systems-manager/latest/userguide/systems-manager-patch.html) for automating OS patching. You should also deploy canary testing to periodically test key application functionalities in pre-production or production environments, and alert support teams if the testing fails. This helps avoid unplanned outages for your application. +We recommend patching development environments earlier than the patching time window used for production environments. For more information about this, see the [Patch Manager runbook ](https://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-patch.html)for automating OS patching. You should also deploy canary testing to periodically test key application functionalities in pre-production or production environments, and alert support teams if the testing fails. This helps avoid unplanned outages for your application. @@ -19 +19 @@ As part of your application's replatforming journey, you should automate platfor -We recommend that you provision your infrastructure by using IaC best practices. There are several options available for this, including [AWS Cloud Development Kit (AWS CDK)](https://docs.aws.amazon.com//cdk/v2/guide/home.html), [CloudFormation](https://docs.aws.amazon.com//AWSCloudFormation/latest/UserGuide/Welcome.html) and [Terraform](https://www.terraform.io/). Chef, Ansible, and Puppet also have limited capabilities that might deliver enough automation for your use case. +We recommend that you provision your infrastructure by using IaC best practices. There are several options available for this, including [AWS Cloud Development Kit (CDK)](https://docs.aws.amazon.com/cdk/v2/guide/home.html), [AWS CloudFormation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html) and [Terraform](https://www.terraform.io/). Chef, Ansible, and Puppet also have limited capabilities that might deliver enough automation for your use case. @@ -23 +23 @@ Repeatable builds that use IaC and configuration management code help you test i -If a COTS application doesn't support automated installation, we recommend consulting the [AWS Partner Network (APN)](https://aws.amazon.com//partners/). For more information about this, see the [Platform perspective: Applications and infrastructure](https://d1.awsstatic.com/whitepapers/aws_cloud_adoption_framework.pdf) section of the AWS CAF whitepaper. +If a COTS application doesn't support automated installation, we recommend consulting the [AWS Partner Network (APN)](https://aws.amazon.com/partners/). For more information about this, see the [Platform perspective: Applications and infrastructure](https://d1.awsstatic.com/whitepapers/aws_cloud_adoption_framework.pdf) section of the AWS CAF whitepaper.