AWS prescriptive-guidance documentation change
Summary
Updated documentation links, image paths, and table formatting. Changed apostrophe style and added missing table separators.
Security assessment
Changes involve cosmetic updates (apostrophe correction), broken image path fixes, and table formatting improvements. No security vulnerabilities, configurations, or features are mentioned or modified. The reference to 'security requirements' remains unchanged from the original text.
Diff
diff --git a/prescriptive-guidance/latest/migration-opentext-teamsite/target-architecture.md b/prescriptive-guidance/latest/migration-opentext-teamsite/target-architecture.md index f807f2d26..15d307447 100644 --- a//prescriptive-guidance/latest/migration-opentext-teamsite/target-architecture.md +++ b//prescriptive-guidance/latest/migration-opentext-teamsite/target-architecture.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Migrating OpenText TeamSite and Media Management workloads to the AWS Cloud](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Migrating OpenText TeamSite and Media Management workloads to the AWS Cloud](introduction.html) @@ -9 +9 @@ -The target architecture, migration strategy, and technical steps depend on the source architecture, connectivity constraints, security requirements, and other policies. They also depend on your organization’s individual policies or requirements. The following diagram shows a sample architecture on the AWS Cloud that could host your OpenText platform. +The target architecture, migration strategy, and technical steps depend on the source architecture, connectivity constraints, security requirements, and other policies. They also depend on your organization's individual policies or requirements. The following diagram shows a sample architecture on the AWS Cloud that could host your OpenText platform. @@ -11 +11 @@ The target architecture, migration strategy, and technical steps depend on the s - + @@ -13 +13 @@ The target architecture, migration strategy, and technical steps depend on the s -The following table provides an overview of the high-level steps required for a migration from a source environment to the target AWS architecture. Detailed steps for this migration are available in the pattern [Migrate OpenText TeamSite workloads to the AWS Cloud](https://docs.aws.amazon.com//prescriptive-guidance/latest/patterns/migrate-opentext-teamsite-workloads-to-the-aws-cloud.html) on the AWS Prescriptive Guidance website. +The following table provides an overview of the high-level steps required for a migration from a source environment to the target AWS architecture. Detailed steps for this migration are available in the pattern [Migrate OpenText TeamSite workloads to the AWS Cloud](https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/migrate-opentext-teamsite-workloads-to-the-aws-cloud.html) on the AWS Prescriptive Guidance website. @@ -15 +15 @@ The following table provides an overview of the high-level steps required for a -**High-level steps** | **Description** +High-level steps| Description @@ -17,2 +17,2 @@ The following table provides an overview of the high-level steps required for a -**1** | Provision the AWS infrastructure | Use CloudFormation to automatically provision your new AWS infrastructure. -**2** | Set up DevOps repositories, tools, and procedures | Use AWS products and services (for example, AWS CodePipeline) to build a continuous integration and continuous deployment (CI/CD) pipeline and automate your release process. +**1**| Provision the AWS infrastructure| Use AWS CloudFormation to automatically provision your new AWS infrastructure. +**2**| Set up DevOps repositories, tools, and procedures| Use AWS products and services (for example, AWS CodeCommit or AWS CodePipeline) to build a continuous integration and continuous deployment (CI/CD) pipeline and automate your release process. @@ -23 +23,3 @@ The following table provides an overview of the high-level steps required for a -**7** | Deploy code | Deploy code to the new environments, for both customizations to OpenText solutions and additional functionalities. + +7| Deploy code| Deploy code to the new environments, for both customizations to OpenText solutions and additional functionalities. +---|---|--- @@ -25 +27 @@ The following table provides an overview of the high-level steps required for a -**9** | Go live | At this stage, the project’s goals are accomplished and the final users are using the new OpenText platform. The platform is ready for further realization and maintenance. +**9**| Go live| At this stage, the project's goals are accomplished and the final users are using the new OpenText platform. The platform is ready for further realization and maintenance. @@ -35 +37 @@ The implementation of the high-level steps will not happen in a clear sequence. - +