AWS prescriptive-guidance documentation change
Summary
Updated documentation links, image paths, and text formatting. Added download instructions for RACI matrix, standardized apostrophes, fixed typos, and updated terminology (e.g., 'AWS CloudFormation' to 'CloudFormation').
Security assessment
Changes are structural/editorial (link updates, image path changes, punctuation fixes). No security vulnerabilities, incidents, or new security features are referenced. Existing security mentions (e.g., firewall operations) are unchanged and not the focus of updates.
Diff
diff --git a/prescriptive-guidance/latest/sap-greenfield-implementations/planning.md b/prescriptive-guidance/latest/sap-greenfield-implementations/planning.md index c8e6ba7f0..d0256bc0b 100644 --- a//prescriptive-guidance/latest/sap-greenfield-implementations/planning.md +++ b//prescriptive-guidance/latest/sap-greenfield-implementations/planning.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Best practices for SAP on AWS greenfield implementations](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Best practices for SAP on AWS greenfield implementations](introduction.html) @@ -17 +17 @@ Building a responsibility assignment matrix for the infrastructure team is criti -Here is an excerpt from a sample RACI matrix for a greenfield SAP implementation project. +Here is an excerpt from a sample RACI matrix for a greenfield SAP implementation project. (To download the complete RACI matrix, see attachments.) @@ -19,3 +19 @@ Here is an excerpt from a sample RACI matrix for a greenfield SAP implementation -[ Download the complete RACI matrix](samples/sap-greenfield-implementation-raci.zip) - - + @@ -42 +40 @@ Considerations: -Build a high-level organization chart that depicts the teams and leadership structure. Go deeper by developing a cross-team contact list that includes the name, title, and role of everyone on the infrastructure team and key points of contact for various functions, such as security, network and firewall operations, Microsoft Active Directory, in-house cloud operations, and server operations. Everyone should know who is involved and what role they play on the project. Delays and miscommunications inevitably occur when the team doesn’t have this information. Understanding the titles of the stakeholders is also important. For example, you wouldn’t want to invite director-level stakeholders to working design sessions or daily stand-ups, unless they are key contributors to the discussions. Knowing titles and roles enables you to invite the right people to the relevant meetings. Being able to visualize the teams in an organization chart helps you understand how the teams are structured and work together on the project. +Build a high-level organization chart that depicts the teams and leadership structure. Go deeper by developing a cross-team contact list that includes the name, title, and role of everyone on the infrastructure team and key points of contact for various functions, such as security, network and firewall operations, Microsoft Active Directory, in-house cloud operations, and server operations. Everyone should know who is involved and what role they play on the project. Delays and miscommunications inevitably occur when the team doesn't have this information. Understanding the titles of the stakeholders is also important. For example, you wouldn't want to invite director-level stakeholders to working design sessions or daily stand-ups, unless they are key contributors to the discussions. Knowing titles and roles enables you to invite the right people to the relevant meetings. Being able to visualize the teams in an organization chart helps you understand how the teams are structured and work together on the project. @@ -46 +44 @@ The following diagram provides an example of a typical SAP on AWS infrastructure - + @@ -52 +50 @@ If your IT organization has an in-house AWS Cloud team, you should establish an -The in-house cloud infrastructure and cloud DevOps teams should also agree on the type of automation software to be used—for example, whether to use AWS CloudFormation or Terraform as an infrastructure as code (IaC) tool. Similarly, they might decide to use AWS Systems Manager or Ansible for configuration tasks such as bootstrapping volumes and possibly SAP installations. These decisions should be documented. Additionally, if there is a requirement for a third-party monitoring and observability dashboard, but this was not a deliverable in the SoW, consider placing monitoring and logging hooks by using Amazon CloudWatch and Amazon Simple Notification Service (Amazon SNS) in the interim. The in-house cloud team can implement integration with a third-party monitoring solution at a later time. +The in-house cloud infrastructure and cloud DevOps teams should also agree on the type of automation software to be used—for example, whether to use CloudFormation or Terraform as an infrastructure as code (IaC) tool. Similarly, they might decide to use AWS Systems Manager or Ansible for configuration tasks such as bootstrapping volumes and possibly SAP installations. These decisions should be documented. Additionally, if there is a requirement for a third-party monitoring and observability dashboard, but this was not a deliverable in the SoW, consider placing monitoring and logging hooks by using Amazon CloudWatch and Amazon Simple Notification Service (Amazon SNS) in the interim. The in-house cloud team can implement integration with a third-party monitoring solution at a later time. @@ -58 +56 @@ When you establish an engagement model, determine whether a waterfall, agile, or - + @@ -64 +62 @@ Lastly, make sure to identify the customer and the SAP Basis team that will supp -If your IT organization has an in-house cloud team, that team should document the cloud build and deployment process by using process flow diagrams and share these diagrams with the entire team. You want your key stakeholders to easily detect any bottlenecks or inefficiencies in the process, and understand the role that your existing internal processes play in creating inefficiencies or delays. In the following example, you can see how the Active Directory join and Domain Name System (DNS) update processes take the longest time to complete. Having this visual might motivate the teams to collaborate and figure out how to reduce the time involved in that step of the process. +If your IT organization has an in-house cloud team, that team should document**** the cloud build and deployment process by using process flow diagrams and share these diagrams with the entire team. You want your key stakeholders to easily detect any bottlenecks or inefficiencies in the process, and understand the role that your existing internal processes play in creating inefficiencies or delays. In the following example, you can see how the Active Directory join and Domain Name System (DNS) update processes take the longest time to complete. Having this visual might motivate the teams to collaborate and figure out how to reduce the time involved in that step of the process. @@ -66 +64 @@ If your IT organization has an in-house cloud team, that team should document th - + @@ -70 +68 @@ Considerations: - * Document the help desk process and workflow separately, share this information with the infrastructure team, and make sure that everyone has access to the help desk tools so there is no reliance on one person. Oftentimes, there can be a complicated and time-consuming ticket process for doing Active Directory joins, DNS updates, opening up firewalls, and requesting encryption keys. It’s critical to document these processes and to consider the Service Level Agreement (SLA) of each team in the project planning phase. It also helps explain the reasons for a delay or bottleneck that requires special attention to remove. + * Document the help desk process and workflow separately, share this information with the infrastructure team, and make sure that everyone has access to the help desk tools so there is no reliance on one person. Oftentimes, there can be a complicated and time-consuming ticket process for doing Active Directory joins, DNS updates, opening up firewalls, and requesting encryption keys. It's critical to document these processes and to consider the Service Level Agreement (SLA) of each team in the project planning phase. It also helps explain the reasons for a delay or bottleneck that requires special attention to remove. @@ -81 +79 @@ The following charts provide an example roadmap for a multi-year SAP on AWS gree - + @@ -83 +81 @@ The following charts provide an example roadmap for a multi-year SAP on AWS gree - + @@ -85 +83 @@ The following charts provide an example roadmap for a multi-year SAP on AWS gree - + @@ -87 +85 @@ The following charts provide an example roadmap for a multi-year SAP on AWS gree - + @@ -91 +89 @@ The following chart shows example engagement timelines with AWS Professional Ser - + @@ -95 +93 @@ The following chart shows a go-live milestone tracker for this project. - +