AWS is discontinuing its SSE-C encryption for S3, a feature that allowed users to manage their own encryption keys. While not widely adopted, it was exploited in a ransomware scheme, prompting the decision to remove it. The article outlines alternatives like KMS and client-side encryption.

AWS introduced VPC encryption controls to help organizations enforce encryption for traffic within and between VPCs. The feature offers two modes: monitor and enforce, allowing users to audit encryption status and ensure compliance with regulations. It simplifies the process of maintaining encryption across cloud infrastructure without significant performance impact.

Amazon S3 now allows users to change the server-side encryption type of existing objects without moving data. You can use the UpdateObjectEncryption API to switch between encryption methods, such as from SSE-S3 to SSE-KMS, and apply these changes at scale with S3 Batch Operations. This is particularly useful for meeting compliance and security standards.

A significant ransomware campaign has exploited over 1,200 unique AWS access keys to encrypt files in S3 storage buckets, leaving ransom notes demanding payment in Bitcoin. The attackers are using AWS's own encryption features to hide their activities, making it difficult for victims to detect breaches or recover their data.

Meredith Whittaker discusses the surprising reaction of people learning that Signal operates partly on AWS, emphasizing the importance of encryption that ensures user communications remain private and inaccessible to anyone, including AWS and Signal itself. She expresses concern over the public's lack of understanding regarding this aspect of Signal's infrastructure.