AWS wellarchitected documentation change
Summary
Changed 'compliance with security' to 'adherence with security' in deployment phase documentation
Security assessment
The change is a minor wording adjustment from 'compliance' to 'adherence' without introducing new security requirements or addressing vulnerabilities. No concrete evidence of security impact.
Diff
diff --git a/wellarchitected/latest/generative-ai-lens/generative-ai-lifecycle.md b/wellarchitected/latest/generative-ai-lens/generative-ai-lifecycle.md index 240270a3f..260717977 100644 --- a//wellarchitected/latest/generative-ai-lens/generative-ai-lifecycle.md +++ b//wellarchitected/latest/generative-ai-lens/generative-ai-lifecycle.md @@ -60 +60 @@ The _deployment_ phase rolls out the generative AI solution in a controlled mann -Deployment includes implementing CI/CD pipelines where applicable, helping maintain system uptime and resiliency, and managing the day-to-day running of the system. Infrastructure as code (IaC) principles are often employed using tools like AWS CDK, AWS CloudFormation, or Terraform to manage resources. Version control systems and automated pipelines are crucial for maintaining and updating the system. Documentation and versioning of infrastructure components help maintain system stability and enable quick rollbacks if needed. Validate your compliance with security and privacy requirements. +Deployment includes implementing CI/CD pipelines where applicable, helping maintain system uptime and resiliency, and managing the day-to-day running of the system. Infrastructure as code (IaC) principles are often employed using tools like AWS CDK, AWS CloudFormation, or Terraform to manage resources. Version control systems and automated pipelines are crucial for maintaining and updating the system. Documentation and versioning of infrastructure components help maintain system stability and enable quick rollbacks if needed. Validate your adherence with security and privacy requirements.