Improve your AWS security posture, Step 2: Avoid direct internet access to AWS resources

In the first blog in this series, we discussed setting up IAM properly. Now we’re moving on to the second step, avoiding direct internet access to AWS resources.

When AWS resources like EC2 instances or S3 buckets are directly accessible via the Internet, they are vulnerable to attack.  For example, brute force attacks on SSH login, denial of service (DOS) attacks on server resources via Layer 3, 4, or 7 flooding, or the inadvertent disclosure of data on an S3 …

access attack attacks aws blog brute force attacks denial of service dos ec2 iam internet internet access login moving moving on posture resources s3 buckets security security posture series server service ssh vulnerable