AWS prescriptive-guidance documentation change
Summary
Updated documentation structure and formatting: fixed broken links, corrected typos, restructured headers, condensed notification examples table, and improved readability.
Security assessment
Changes involve structural improvements and typo fixes (e.g., 'add–on' to 'add-on', URL corrections). Security-related content in notifications table remains unchanged in substance. No vulnerability fixes or incident responses documented.
Diff
diff --git a/prescriptive-guidance/latest/ams-accelerate-governance-best-practices/ams-accelerate-governance.md b/prescriptive-guidance/latest/ams-accelerate-governance-best-practices/ams-accelerate-governance.md index 53ef627bd..41bc2fb8c 100644 --- a//prescriptive-guidance/latest/ams-accelerate-governance-best-practices/ams-accelerate-governance.md +++ b//prescriptive-guidance/latest/ams-accelerate-governance-best-practices/ams-accelerate-governance.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[AMS Accelerate operations plan governance best practices](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[AMS Accelerate operations plan governance best practices](introduction.html) @@ -7 +7 @@ -Roles and responsibilities (RACI matrix)Account teamsSLAsContact hoursNotifications +Roles and responsibilities (RACI matrix) @@ -15 +15 @@ The following table is a responsible, accountable, consulted, and informed (RACI -For more information, see [Roles and responsibilities](https://docs.aws.amazon.com//managedservices/latest/accelerate-guide/acc-sd.html#acc-sd-responsibilities) in the _AMS Accelerate User Guide_. +For more information, see [Roles and responsibilities](https://docs.aws.amazon.com/managedservices/latest/accelerate-guide/acc-sd.html#acc-sd-responsibilities) in the _AMS Accelerate User Guide_. @@ -32 +32 @@ Activity | You | AMS Accelerate -**Application lifecycle** | | +**Application lifecycle** @@ -44 +44 @@ Incident response for AWS resource issues | C | R -**Account configuration and onboarding** | | +**Account configuration and onboarding** @@ -57 +57 @@ Configuring default alert thresholds for security management | I | R -## Account teams +### Account teams @@ -63,5 +63 @@ Your AMS Accelerate account team can help you launch new projects and give best - * **Cloud services delivery managers (CSDMs)** provide advisory assistance across AMS and have a detailed understanding of the use case and technology architecture of the managed environment. - - * **AMS cloud architects (CAs) and solutions architects (SAs)** help launch new projects and give best-practices recommendations throughout the software development and operations processes. - - +**Cloud services delivery managers (CSDMs)** provide advisory assistance across AMS and have a detailed understanding of the use case and technology architecture of the managed environment. @@ -68,0 +65 @@ Your AMS Accelerate account team can help you launch new projects and give best +**AMS cloud architects (CAs) and solutions architects (SAs)** help launch new projects and give best-practices recommendations throughout the software development and operations processes. @@ -72 +69 @@ For more information, including the specific responsibilities of your CSDM, see -## SLAs +### SLAs @@ -76 +73 @@ AMS Accelerate has two Service Level Agreement (SLA) tiers: **Plus** and **Premi -The following tables show the SLA targets for each tier’s response and resolution time, based on the priority of the incident or request. +The following tables show the SLA targets for each tier's response and resolution time, based on the priority of the incident or request. @@ -94 +91 @@ Priority level | Response time | Resolution time -## Contact hours +### Contact hours @@ -96 +93 @@ Priority level | Response time | Resolution time -AMS Accelerate provides different contact hours based on the SLA tier level assigned to each AWS account. For more information, see [Contact hours](https://docs.aws.amazon.com//managedservices/latest/accelerate-guide/acc-contact-hours.html) in the _AMS Accelerate User Guide_. +AMS Accelerate provides different contact hours based on the SLA tier level assigned to each AWS account. For more information, see [Contact hours](https://docs.aws.amazon.com/managedservices/latest/accelerate-guide/acc-contact-hours.html) in the _AMS Accelerate User Guide._ @@ -98 +95 @@ AMS Accelerate provides different contact hours based on the SLA tier level assi -## Notifications +### Notifications @@ -106 +103 @@ AMS sends notifications to you for the following reasons only: - * Patching service notifications (if you've activated the patch add–on) + * Patching service notifications (if you've activated the patch add-on) @@ -119 +116 @@ There are two ways to set up AMS Accelerate notifications: - * [Tag–based alert notifications](https://docs.aws.amazon.com//managedservices/latest/accelerate-guide/how-monitoring-works.html#how-mon-works-alert-notes-tags) send an alert for a specific AWS resource to an email address that’s configured in the resource’s tag. For more information, see [Tagging in AMS Accelerate](https://docs.aws.amazon.com//managedservices/latest/accelerate-guide/acc-tagging.html) in the _AMS Accelerate User Guide_. + * [Tag-based alert notifications](https://docs.aws.amazon.com/managedservices/latest/accelerate-guide/how-monitoring-works.html#how-mon-works-alert-notes-tags) send an alert for a specific AWS resource to an email address that's configured in the resource's tag. For more information, see [Tagging in AMS Accelerate](https://docs.aws.amazon.com/managedservices/latest/accelerate-guide/acc-tagging.html) in the _AMS Accelerate User Guide_. @@ -121 +118 @@ There are two ways to set up AMS Accelerate notifications: - * [Alert notifications](https://docs.aws.amazon.com//managedservices/latest/accelerate-guide/how-monitoring-works.html#how-monitoring-works-alert-notes) send an alert to the email address associated with your account. + * [Alert notifications](https://docs.aws.amazon.com/managedservices/latest/accelerate-guide/how-monitoring-works.html#how-monitoring-works-alert-notes) send an alert to the email address associated with your account. @@ -128 +125 @@ There are two ways to set up AMS Accelerate notifications: -It’s a best practice to use tag–based alert notifications. Alert notifications sent to a single email address can cause confusion when multiple teams use the same AWS account. Tag–based alert notifications are available for most Amazon CloudWatch alarms. +It's a best practice to use tag-based alert notifications. Alert notifications sent to a single email address can cause confusion when multiple teams use the same AWS account. Tag-based alert notifications are available for most Amazon CloudWatch alarms. @@ -130 +127 @@ It’s a best practice to use tag–based alert notifications. Alert notificatio -**Tag–based alert notification examples** +**Tag-based alert notification examples** @@ -132 +129 @@ It’s a best practice to use tag–based alert notifications. Alert notificatio -Notification type | Example alert scenerios | Relevant tags +Notification type| Example alert scenarios| Relevant tags @@ -134,37 +131,6 @@ Notification type | Example alert scenerios | Relevant tags -Security | - - * Escalations of privileges, uses of exposed credentials, or communication with malicious IP addresses or domains - * Access behavior that points to signs of account compromise, such as unauthorized infrastructure deployments - -| **ams:rt:ams-managed** -Operations: Service–level events | - - * A change to an underlying AWS service that affects your infrastructure - * Amazon EC2 hardware issues that require you to reboot an instance before a certain date - -| **ams:rt:ams-managed** **ams:rt:ams-monitoring-policy** -Operations: Resource–level events | - - * Any resource–level change in your AWS environment - -| **ownerteamemail** -Operations: Patching | - - * An advance notice of each upcoming maintenance window - * Patching statuses - -| **ams:rt:ams-managed** **AmsDefaultPatchKey** -Operations: Incidents | - - * Logging the occurrence of incidents - * Incident updates - * Incident resolution notices - -| **ams:rt:ams-managed** -Operations: Backups | - - * AWS Backup job failures - * AWS Backup job expirations - * Amazon Relational Database Service (Amazon RDS) backup job failures - -| **ams:rt:ams-managed** **ams:rt:backup-orchestrator** **ams-onboarding-backup-plan** +Security| Escalations of privileges, uses of exposed credentials, or communication with malicious IP addresses or domainsAccess behavior that points to signs of account compromise, such as unauthorized infrastructure deployments| **ams:rt:ams-managed** +Operations: Service-level events| A change to an underlying AWS service that affects your infrastructureAmazon EC2 hardware issues that require you to reboot an instance before a certain date| **ams:rt:ams-managed****ams:rt:ams-monitoring-policy** +Operations: Resource-level events| Any resource-level change in your AWS environment| **ownerteamemail** +Operations: Patching| An advance notice of each upcoming maintenance windowPatching statuses| **ams:rt:ams-managed****AmsDefaultPatchKey** +Operations: Incidents| Logging the occurrence of incidentsIncident updatesIncident resolution notices| **ams:rt:ams-managed** +Operations: Backups| AWS Backup job failuresAWS Backup job expirationsAmazon Relational Database Service (Amazon RDS) backup job failures| **ams:rt:ams-managed****ams:rt:backup-orchestrator****ams-onboarding-backup-plan** @@ -178 +144 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Comparing AMS Accelerate and Support +Comparing AMS Accelerate and AWS Support