AWS S3 Configuration Best Practice: Use HTTPS (TLS) to Protect Data in Transit

In our last blog we explored the history of pre-flight checklists to avoid catastrophic failures from human errors and misconfiguration. In this blog we’ll delve in-depth into a critical public cloud storage security check. A major AWS S3 configuration error is neglecting to enforce HTTPS (TLS) to access bucket data since unencrypted traffic is vulnerable to man-in-the-middle attacks that can steal or modify data in transit. These sort of attacks can lead to the loss of valuable enterprise data and compliance violations with regulations such as PCI DSS and NIST 800-53 (rev 4). Amazon has produced its AWS Well-Architected Framework to help organizations achieve best practices related to operational excellence, security, reliability, performance efficiency, and cost optimization. The Security Pillar provides guidance to implement best practices in the design, delivery and maintenance of secure AWS workloads. Shared Responsibility The concept of “Shared Responsibility” is one of the foundations of the

Scroll to Top