Skip to main content

AWS Security: 5 Things You Need to Check Right Now

It might be unrealistic to expect your AWS security to be bullet-proof, but there is still a great deal you can do to make things a whole lot better.

AWS Security and more AWS security. We all know it’s important, but if you’re like me, there always seems to be a nagging doubt in the back of your mind that somewhere, there’s a nasty hole in your infrastructure, and that some hacker is prodding and probing away trying to find it. It sometimes seems that keeping everything 100% secure is a losing battle.
However, I do believe there are a few things that can be easily plugged that can make a big difference.

1. AWS security: delete Root Account Keys

This is something about which AWS is constantly trying to remind us – even I’ve written about AWS best practices before. It’s probably the easiest and most important security move you can make.

What you need to check

Login to your AWS console root account and click on Identity and Access Management. If you see a nice green tick next to the “Delete your root access keys” box…
AWS security - delete root access keys
…Then everything is OK and you don’t need to do anything.
However, if you see this:
AWS Security security status
Do the following:

What you need to do

  1. Click on ‘Manage Security Credentials’.
  2. Click on ‘Access Keys (Access Key ID and Secret Access Key)’.
  3. Delete any Access keys that are still Active like the one below.

AWS Security access key IDs - screen 1
AWS Security access key IDs - screen 2

2. Name everything

I originally left this until the end of the article. However, I realized that it makes a lot more sense having it right here before we remove our unused Security Groups in the next step. This is because having everything correctly named will be easier to actually see which Security Groups should, in fact, be removed.

What you need to check

Go through all your resources and check to see that everything – EC2 Instances, Security Groups, Network Interfaces, Volumes, Snapshots – has a name. Why? Because it will make keeping track of your resources so much easier and make it more likely that you will quickly spot anything being misused.

What you need to do

Give everything a name. More importantly, the name should be related to what the resource’s specific function is. Make sure you do this for all your resources in all regions.

Note: If you want to be even more thorough, then TAG everything. So instead of being restricted to just a name, you can add your own key-value pairs.  

3. Remove unused Security Groups

Now, with everything nicely named or tagged, it’s time to get rid of any unused security groups. Cleaning out your security groups eliminates the risk that a forgotten security group policy will be used to accidentally open an attack surface.

What you need to check

Open your EC2 Console and click on ‘Security Groups.’ You should see a list of all your Security Groups

What you need to do

Go through them carefully and delete any that you are certain aren’t being used or don’t belong to a default security group. If you try to delete a group that is being used, you should see a warning pop-up telling you. In any case, review the policies of all groups to make sure there are no unnecessary holes.

4. Restrict SSH access to your IP only

If you are the only one who connects to your instances via SSH, you should restrict access to sessions originating from your IP only.

What you need to check

  1. Open your EC2 Console and click on ‘Security Groups.’
  2. Click on a Security Group and then select ‘Inbound’ in the bottom window.
  3. If you see any SSH connections with a source of 0.0.0.0/0 like this:

AWS security SSH connections with a source of 0.0.0.0/0
…Do the following:

What you need to do

Click on ‘edit’ and then select the Source for SSH as MY IP, then save it as follows:
AWS Security policy SSH
Repeat for all Security Groups in all regions.

5.  Create individual IAM users (especially for yourself)

Avoid using your AWS root account credentials (ie: your original AWS login) to access AWS.

What you need to check

  1. Open the Identity and Access Management console.
  2. Click on Users.
  3. If you have a user for yourself with administrative privileges, then use that to login to AWS from now on (unless you have a really, really good reason not to).
  4. If you don’t have a user for yourself with administrative privileges, then follow these steps:

What you need to do

  1. Create an IAM user for yourself with administrative privileges, and use that IAM user for all your work.
  2. Follow this guide: Create individual IAM users.

Conclusion

AWS Security can be a little overwhelming at times, but if you make sure you get the easy stuff right from the beginning, then you should find yourself ahead of the game.

Avatar

Written by

Michael Sheehy

I have been UNIX/Linux System Administrator for the past 15 years and am slowly moving those skills into the AWS Cloud arena. I am passionate about AWS and Cloud Technologies and the exciting future that it promises to bring.

Related Posts

Avatar
John Chell
— June 13, 2019

AWS Certified Solutions Architect Associate: A Study Guide

The AWS Solutions Architect - Associate Certification (or Sol Arch Associate for short) offers some clear benefits: Increases marketability to employers Provides solid credentials in a growing industry (with projected growth of as much as 70 percent in five years) Market anal...

Read more
  • AWS
  • AWS Certifications
Chris Gambino and Joe Niemiec
Chris Gambino and Joe Niemiec
— June 11, 2019

Moving Data to S3 with Apache NiFi

Moving data to the cloud is one of the cornerstones of any cloud migration. Apache NiFi is an open source tool that enables you to easily move and process data using a graphical user interface (GUI).  In this blog post, we will examine a simple way to move data to the cloud using NiFi c...

Read more
  • AWS
  • S3
Avatar
Chandan Patra
— June 11, 2019

Amazon DynamoDB: 10 Things You Should Know

Amazon DynamoDB is a managed NoSQL service with strong consistency and predictable performance that shields users from the complexities of manual setup.Whether or not you've actually used a NoSQL data store yourself, it's probably a good idea to make sure you fully understand the key ...

Read more
  • AWS
  • DynamoDB
Avatar
Andrew Larkin
— June 6, 2019

The 11 AWS Certifications: Which is Right for You and Your Team?

As companies increasingly shift workloads to the public cloud, cloud computing has moved from a nice-to-have to a core competency in the enterprise. This shift requires a new set of skills to design, deploy, and manage applications in cloud computing.As the market leader and most ma...

Read more
  • AWS
  • AWS Certifications
Sam Ghardashem
Sam Ghardashem
— May 15, 2019

Aviatrix Integration of a NextGen Firewall in AWS Transit Gateway

Learn how Aviatrix’s intelligent orchestration and control eliminates unwanted tradeoffs encountered when deploying Palo Alto Networks VM-Series Firewalls with AWS Transit Gateway.Deploying any next generation firewall in a public cloud environment is challenging, not because of the f...

Read more
  • AWS
Joe Nemer
Joe Nemer
— May 3, 2019

AWS Config Best Practices for Compliance

Use AWS Config the Right Way for Successful ComplianceIt’s well-known that AWS Config is a powerful service for monitoring all changes across your resources. As AWS Config has constantly evolved and improved over the years, it has transformed into a true powerhouse for monitoring your...

Read more
  • AWS
  • Compliance
Avatar
Francesca Vigliani
— April 30, 2019

Cloud Academy is Coming to the AWS Summits in Atlanta, London, and Chicago

Cloud Academy is a proud sponsor of the 2019 AWS Summits in Atlanta, London, and Chicago. We hope you plan to attend these free events that bring the cloud computing community together to connect, collaborate, and learn about AWS. These events are all about learning. You can learn how t...

Read more
  • AWS
  • AWS Summits
Paul Hortop
Paul Hortop
— April 2, 2019

How to Monitor Your AWS Infrastructure

The AWS cloud platform has made it easier than ever to be flexible, efficient, and cost-effective. However, monitoring your AWS infrastructure is the key to getting all of these benefits. Realizing these benefits requires that you follow AWS best practices which constantly change as AWS...

Read more
  • AWS
  • Monitoring
Joe Nemer
Joe Nemer
— April 1, 2019

AWS EC2 Instance Types Explained

Amazon Web Services’ resource offerings are constantly changing, and staying on top of their evolution can be a challenge. Elastic Cloud Compute (EC2) instances are one of their core resource offerings, and they form the backbone of most cloud deployments. EC2 instances provide you with...

Read more
  • AWS
  • EC2
Avatar
Nitheesh Poojary
— March 26, 2019

How DNS Works – the Domain Name System (Part One)

Before migrating domains to Amazon's Route53, we should first make sure we properly understand how DNS worksWhile we'll get to AWS's Route53 Domain Name System (DNS) service in the second part of this series, I thought it would be helpful to first make sure that we properly understand...

Read more
  • AWS
Avatar
Stuart Scott
— March 14, 2019

Multiple AWS Account Management using AWS Organizations

As businesses expand their footprint on AWS and utilize more services to build and deploy their applications, it becomes apparent that multiple AWS accounts are required to manage the environment and infrastructure.  A multi-account strategy is beneficial for a number of reasons as ...

Read more
  • AWS
  • Identity Access Management
Avatar
Sanket Dangi
— February 11, 2019

WaitCondition Controls the Pace of AWS CloudFormation Templates

AWS's WaitCondition can be used with CloudFormation templates to ensure required resources are running.As you may already be aware, AWS CloudFormation is used for infrastructure automation by allowing you to write JSON templates to automatically install, configure, and bootstrap your ...

Read more
  • AWS
  • CloudFormation