Organizations are increasingly moving workloads, applications and infrastructure to Amazon Web Services (AWS) to leverage the cost, scale and agility the cloud has to offer. Moving to the cloud has become an imperative in order to keep pace with their competitors who are already taking similar steps. However, these same organizations are all finding that their legacy security and networking tools have many gaps in their abilities to provide the necessary visibility and control they need to manage regulatory and risk management requirements in these modern environments.

I’ve recently received some questions about the AWS Application Load Balancer, what advantages it provides, and how to monitor it. AWS is already calling the original Elastic Load Balancer it’s ‘Classic’ Load Balancer, so if you’re anxious to understand why so many are using it over the Classic ELB, this post is for you.

The AWS Well Architected Framework's Security Pillar defines cloud security best practices with five Design Principles and five focus areas. First, I'll describe the Security Design Principles, and some Sumo Logic capabilities that will help you adhere to them. Then, I'll list the five focus areas with corresponding, investigative questions you can ask to ensure your architecture is secure. A link to the next pillar in the framework, Reliability, is soon to come.

AWS Best Practices - Using tools in Amazon Web Services and Sumo Logic to analyze logs and metrics and achieve a Well Architected Framework