AWS wellarchitected documentation change
Summary
Updated navigation links, removed 'sustainable' from system attributes list, and changed 'Contributors' section to 'Appendix: Best practices by pillar'
Security assessment
Structural and editorial changes to framework documentation. The removal of 'sustainable' appears to be a scope refinement rather than a security-related modification. No security content was added or modified.
Diff
diff --git a/wellarchitected/latest/iot-lens/conclusion.md b/wellarchitected/latest/iot-lens/conclusion.md index af1ad4ae7..d08d459b5 100644 --- a//wellarchitected/latest/iot-lens/conclusion.md +++ b//wellarchitected/latest/iot-lens/conclusion.md @@ -3 +3 @@ -[Documentation](/index.html)[AWS Well-Architected](https://aws.amazon.com/architecture/well-architected/)[AWS Well-Architected Framework](abstract-and-introduction.html) +[Documentation](/index.html)[AWS Well-Architected](https://aws.amazon.com/architecture/well-architected/)[AWS Well-Architected Framework](iot-lens.html) @@ -7 +7 @@ -The AWS Well-Architected Framework provides architectural best practices across the pillars for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems in the cloud for IoT applications. The framework provides a set of questions that you can use to review an existing or proposed IoT architecture, and also a set of AWS best practices for each pillar. Using the framework in your architecture helps you produce stable and efficient systems, which allows you to focus on your functional requirements. +The AWS Well-Architected Framework provides architectural best practices across the pillars for designing and operating reliable, secure, efficient, and cost-effective systems for IoT applications. The framework provides a set of questions that you can use to review an existing or proposed IoT architecture, and also a set of AWS best practices for each pillar. Using the framework in your architecture helps you produce stable and efficient systems, which allows you to focus on your functional requirements. @@ -17 +17 @@ Resources -Contributors +Appendix: Best practices by pillar