AWS wellarchitected documentation change
Summary
Changed 'AWS CloudFormation' to 'CloudFormation' for terminology consistency
Security assessment
Terminology update in automation examples. No security implications or security documentation added.
Diff
diff --git a/wellarchitected/latest/framework/ops_ops_model_def_activity_owners.md b/wellarchitected/latest/framework/ops_ops_model_def_activity_owners.md index 551570689..13615f67e 100644 --- a//wellarchitected/latest/framework/ops_ops_model_def_activity_owners.md +++ b//wellarchitected/latest/framework/ops_ops_model_def_activity_owners.md @@ -55 +55 @@ Analyze and address the discrepancies. Identify opportunities to improvement, an -Over time, these procedures should be evolved to be run as code, reducing the need for human intervention. For example, procedures can be initiated as AWS Lambda functions, AWS CloudFormation templates, or AWS Systems Manager Automation documents. Verify that these procedures are version-controlled in appropriate repositories, and include suitable resource tagging so that teams can readily identify owners and documentation. Document the responsibility for carrying out the activities, and then monitor the automations for successful initiation and operation, as well as performance of the desired outcomes. +Over time, these procedures should be evolved to be run as code, reducing the need for human intervention. For example, procedures can be initiated as AWS Lambda functions, CloudFormation templates, or AWS Systems Manager Automation documents. Verify that these procedures are version-controlled in appropriate repositories, and include suitable resource tagging so that teams can readily identify owners and documentation. Document the responsibility for carrying out the activities, and then monitor the automations for successful initiation and operation, as well as performance of the desired outcomes.