Mistake #9: Failing to Proper Configure AWS Security Groups

Mistake #9: Failing to Proper Configure AWS Security Groups

Amazon’s approach to security is based on “shared responsibility” between users and AWS – Security Groups is one of the tools Amazon provides for users to fulfill their part. One would expect that when it comes to security, users don’t err.

We were actually amazed by how common bad configuration of AWS EC2 Security Groups happens to be. Slips are as risky as opening all IP ports to the whole Internet, but also lighter ones as allowing access to all ports from any AWS addresses.

Check out this related insight - Unnecessary Security Groups Ports are open on DB Server

Keywords: configure security groups, amazon aws ec2 security groups,  Amazon Web Services, AWS cloud, EC2, AWS Instance, Security Groups, AWS Console, AWS CLI, Cloud Scalability, Cloud Firewall, AWS Firewall, AWS Security Groups, Cloud Compliance and Security, IP Ports, Security Management, Security Policy, Cloud Security

You must be to post a comment.

* As a bonus, you'll receive our weekly newsletter!

Hitchhiker's Guide to The Cloud

Newvem's eBook for Cloud Operations