AWS prescriptive-guidance documentation change
Summary
Updated breadcrumb navigation link, fixed URL formatting for AWS Systems Manager documentation, corrected apostrophe usage, and removed trailing asterisks.
Security assessment
Changes include navigation updates, broken URL fixes (removed double slash), and grammatical corrections. No security vulnerabilities, patches, or security features are mentioned or added. Recommendations about OS upgrades and vendor certifications remain unchanged.
Diff
diff --git a/prescriptive-guidance/latest/migration-replatforming-cots-applications/replatforming-application-components.md b/prescriptive-guidance/latest/migration-replatforming-cots-applications/replatforming-application-components.md index 424595c5d..ca5581968 100644 --- a//prescriptive-guidance/latest/migration-replatforming-cots-applications/replatforming-application-components.md +++ b//prescriptive-guidance/latest/migration-replatforming-cots-applications/replatforming-application-components.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) @@ -34 +34 @@ If you replace unsupported application servers (for example, Apache Tomcat 6.0, - * **COTS applications** – Contact the application's vendor and request application binaries that are certified for the required OS or application server versions. + * **COTS applications –** Contact the application's vendor and request application binaries that are certified for the required OS or application server versions.**** @@ -41 +41 @@ If you replace unsupported application servers (for example, Apache Tomcat 6.0, -Most COTS application vendors support Windows 2016 or RHEL 7. If your legacy COTS application doesn't support Windows 2016, we recommend an in-place upgrade from Windows 2008 R2 to Windows 2012 R2 by using the [in-place upgrade option provided by Microsoft](https://docs.microsoft.com/en-us/windows-server/upgrade/upgrade-2008r2-to-2012r2). You can also use [AWS Systems Manager Automation runbooks](https://docs.aws.amazon.com//systems-manager/latest/userguide/systems-manager-automation.html) to automatically upgrade Windows Server running on EC2 instances. We recommend that you contact the application’s vendor and ask them to certify their software for the latest OS version. +Most COTS application vendors support Windows 2016 or RHEL 7. If your legacy COTS application doesn't support Windows 2016, we recommend an in-place upgrade from Windows 2008 R2 to Windows 2012 R2 by using the [in-place upgrade option provided by Microsoft](https://docs.microsoft.com/en-us/windows-server/upgrade/upgrade-2008r2-to-2012r2). You can also use [AWS Systems Manager Automation runbooks](https://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-automation.html) to automatically upgrade Windows Server running on EC2 instances. We recommend that you contact the application's vendor and ask them to certify their software for the latest OS version. @@ -45 +45 @@ Most COTS application vendors support Windows 2016 or RHEL 7. If your legacy COT -We recommend that you compile and rebuild your in-house application’s software by using the most recent OS and software runtime versions (for example, Java, C++, .NET, or Python). You can then clone the existing application environment, manually deploy and validate the functionality, and update your build environment to the most recent OS, runtime software components, and libraries before upgrading to your production environment. +We recommend that you compile and rebuild your in-house application's software by using the most recent OS and software runtime versions (for example, Java, C++, .NET, or Python). You can then clone the existing application environment, manually deploy and validate the functionality, and update your build environment to the most recent OS, runtime software components, and libraries before upgrading to your production environment.