AWS wellarchitected documentation change
Summary
Updated terminology for Elastic Load Balancing, changing from 'Elastic Load Balancing (ELB)' to 'ELB (ELB)'
Security assessment
The change is purely terminological, replacing the full service name with its acronym. There is no evidence of security vulnerability remediation or new security guidance. Encryption practices remain unchanged.
Diff
diff --git a/wellarchitected/latest/framework/sec-dataprot.md b/wellarchitected/latest/framework/sec-dataprot.md index 80407bd88..b6285f817 100644 --- a//wellarchitected/latest/framework/sec-dataprot.md +++ b//wellarchitected/latest/framework/sec-dataprot.md @@ -40 +40 @@ Protect your data in transit by implementing multiple controls to reduce the ris -AWS provides multiple means for encrypting data at rest and in transit. We build features into our services that make it easier to encrypt your data. For example, we have implemented server-side encryption (SSE) for Amazon S3 to make it easier for you to store your data in an encrypted form. You can also arrange for the entire HTTPS encryption and decryption process (generally known as SSL termination) to be handled by Elastic Load Balancing (ELB). +AWS provides multiple means for encrypting data at rest and in transit. We build features into our services that make it easier to encrypt your data. For example, we have implemented server-side encryption (SSE) for Amazon S3 to make it easier for you to store your data in an encrypted form. You can also arrange for the entire HTTPS encryption and decryption process (generally known as SSL termination) to be handled by ELB (ELB).