While AWS EC2 instances should be well protected by VPC security tools, you may still need to implement protection at the OS-level, and that means firewalld.
This is the second part of our server security series. In this article, we will look at configuring firewall rules via
firewalld on Red Hat Enterprise Linux. While Amazon Linux is similar to Red Hat Enterprise Linux (RHEL) in many ways, it does not yet support
firewalld. So we’ll have to focus on RHEL. By the way, I will not cover
iptables here, as there are many good resources out there already.
You might wonder why we need to configure the firewall at the operating system level in the first place, if this is already taken care of by EC2 security groups within our VPC. I can think of a few possible use cases. If, for instance, the firewall in the security group is configured incorrectly, the OS-level firewall can act as a backup to protect the instance from possible probes or compromise. Or perhaps the administrator wants to bind additional ports for future services or temporarily block certain ports, but does not have access to the EC2 dashboard. In either case, depending on the security group state, he should be able to do so at the OS-level.
Now that we have justified using
firewalld, let’s learn a bit more about it.
firewalld is a new way to interact with the netfilter subsystem in the Linux kernel. It simplifies the way we manage firewall rules by classifying network traffic into different firewall zones. We could choose to simply use
iptables to configure the firewall rules if we wanted to, but both cannot co-exist with each other.
Getting started with firewalld
Therefore, to get started with
firewalld, we first need to make sure that the
iptables-related services are disabled. By default, Red Hat Enterprise Linux does not have either
firewalld packages installed. So when you try to query for
iptables-services, it will tell you that it is not there.
# rpm -q iptables-services package iptables-services is not installed
However, if it is already installed, we’ll need to disable the service so that it does not interfere with
# rpm -q iptables-services iptables-services-1.4.21-13.el7.x86_64 # systemctl stop iptables.service # systemctl stop ip6tables.service systemctl status iptables.service iptables.service - IPv4 firewall with iptables Loaded: loaded (/usr/lib/systemd/system/iptables.service; disabled) Active: inactive (dead) Nov 15 21:26:47 ip-172-30-1-83.ec2.internal systemd: Stopped IPv4 firewall with iptables. # systemctl status ip6tables.service ip6tables.service - IPv6 firewall with ip6tables Loaded: loaded (/usr/lib/systemd/system/ip6tables.service; disabled) Active: inactive (dead) Nov 15 21:26:52 ip-172-30-1-83.ec2.internal systemd: Stopped IPv6 firewall with ip6tables. # systemctl mask iptables.service ln -s '/dev/null' '/etc/systemd/system/iptables.service' # systemctl mask ip6tables.service ln -s '/dev/null' '/etc/systemd/system/ip6tables.service'
Notice that we also disabled the IPv6 version of the
iptables service. People tend to forget about that.
Now we are ready to install and start
# yum install firewalld # systemctl status firewalld.service firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled) Active: inactive (dead) # systemctl start firewalld.service # systemctl status firewalld.service firewalld.service - firewalld - dynamic firewall daemon Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled) Active: active (running) since Sun 2015-11-15 21:31:53 EST; 7s ago Main PID: 10942 (firewalld) CGroup: /system.slice/firewalld.service └─10942 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid Nov 15 21:31:52 ip-172-30-1-83.ec2.internal systemd: Starting firewalld - dynamic firewall dae..... Nov 15 21:31:53 ip-172-30-1-83.ec2.internal systemd: Started firewalld - dynamic firewall daemon. Hint: Some lines were ellipsized, use -l to show in full.
firewalld, we need to understand more about how network traffic is classified into different firewall zones. The
firewalld.zones man pages cover this in a very clear and concise manner. I will reproduce the description here verbatim.
drop– Any incoming network packets are dropped, there is no reply. Only outgoing network connections are possible.
block– Any incoming network connections are rejected with an icmp-host-prohibited message for IPv4 and icmp6-adm-prohibited for IPv6. Only network connections initiated within this system are possible.
public– For use in public areas. You do not trust the other computers on networks to not harm your computer. Only selected incoming connections are accepted.
external– For use on external networks with masquerading enabled specifically for routers. You do not trust the other computers on networks to not harm your computer. Only selected incoming connections are accepted.
dmz– For computers in your demilitarised zone that are publicly-accessible with limited access to your internal network. Only selected incoming connections are accepted.
work– For use in work areas. You mostly trust the other computers on networks to not harm your computer. Only selected incoming connections are accepted.
home– For use in home areas. You mostly trust the other computers on networks to not harm your computer. Only selected incoming connections are accepted.
internal– For use in internal networks. You mostly trust the other computers on the networks to not harm your computer. Only selected incoming connections are accepted.
trusted– All network connections are accepted.
Configure firewalld rules
We will configure
firewalld using the
Instead of running
systemctl status firewalld, we can also use the
firewall-cmd with the
--state option to confirm that it has started.
# firewall-cmd --state running
You can list the firewall zones we discussed earlier by using the
# firewall-cmd --get-zones block dmz drop external home internal public trusted work
To view the default zone, it is as simple as specifying the
--get-default-zone option. If the EC2 instance is inside its own VPC subnet, and can only be accessed via a jumpbox, then we may change the default zone to
internal, and add or remove the services that were allowed by default.
# firewall-cmd --get-default-zone public # firewall-cmd --set-default-zone=internal success # firewall-cmd --list-all internal (default) interfaces: sources: services: dhcpv6-client ipp-client mdns samba-client ssh ports: masquerade: no forward-ports: icmp-blocks: rich rules:
firewall-cmd with the
--get-services option lists all the services that can be controlled by
# firewall-cmd --get-services RH-Satellite-6 amanda-client bacula bacula-client dhcp dhcpv6 dhcpv6-client dns ftp high-availability http https imaps ipp ipp-client ipsec kerberos kpasswd ldap ldaps libvirt libvirt-tls mdns mountd ms-wbt mysql nfs ntp openvpn pmcd pmproxy pmwebapi pmwebapis pop3s postgresql proxy-dhcp radius rpc-bind samba samba-client smtp ssh telnet tftp tftp-client transmission-client vnc-server wbem-https
If a service is not on the list, we can always define our own service, or add the port to be opened via
firewall-cmd directly. Let’s demonstrate that – and prepare for our next article on SELinux at the same time – by changing the default port number for the OpenSSH service to port 31337. Assuming that we will use
firewalld together with SELinux, we can enable the port by using the
--add-port option. Note that if we want to make our changes permanent, we need to reload the firewall rules immediately.
# firewall-cmd --permanent --add-port=31337/tcp; firewall-cmd --reload success success # firewall-cmd --list-all internal (default) interfaces: sources: services: dhcpv6-client ipp-client mdns samba-client ssh ports: 31337/tcp masquerade: no forward-ports: icmp-blocks: rich rules:
If we want to remove unneeded services such as
ipp-client, etc, we can do so with the
# firewall-cmd --permanent --remove-service=dhcpv6-client --remove-service=ipp-client --remove-service=mdns --remove-service=samba-client; firewall-cmd --reload success success # firewall-cmd --list-all internal (default) interfaces: sources: services: ssh ports: 31337/tcp masquerade: no forward-ports: icmp-blocks: rich rules:
You can take a peek at the
iptables rules that
firewall-cmd magically generated based on the commands we just issued:
# iptables -S | tail -A FWDI_internal -j FWDI_internal_allow -A FWDO_internal -j FWDO_internal_log -A FWDO_internal -j FWDO_internal_deny -A FWDO_internal -j FWDO_internal_allow -A INPUT_ZONES -g IN_internal -A IN_internal -j IN_internal_log -A IN_internal -j IN_internal_deny -A IN_internal -j IN_internal_allow -A IN_internal_allow -p tcp -m tcp --dport 22 -m conntrack --ctstate NEW -j ACCEPT -A IN_internal_allow -p tcp -m tcp --dport 31337 -m conntrack --ctstate NEW -j ACCEPT
If you have managed to successfully follow along so far, great work! You will find that
firewalld is a lot easier to work with than trying to directly configure
In our next article, we will explore setting up SELinux on Amazon Linux, and walking through a simple SELinux example on Red Hat Enterprise Linux. For more on Cloud server security, why not take Cloud Academy’s Linux Security course?
Comments? Please join in!
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 ...
The 9 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 the cloud.As the market leader and most mature p...
Two New EC2 Instance Types Announced at AWS re:Invent 2018 – Monday Night Live
The announcements at re:Invent just keep on coming! Let’s look at what benefits these two new EC2 instance types offer and how these two new instances could be of benefit to you. If you're not too familiar with Amazon EC2, you might want to familiarize yourself by creating your first Am...
Google Cloud Certification: Preparation and Prerequisites
Google Cloud Platform (GCP) has evolved from being a niche player to a serious competitor to Amazon Web Services and Microsoft Azure. In 2018, research firm Gartner placed Google in the Leaders quadrant in its Magic Quadrant for Cloud Infrastructure as a Service for the first time. In t...
Understanding AWS VPC Egress Filtering Methods
In order to understand AWS VPC egress filtering methods, you first need to understand that security on AWS is governed by a shared responsibility model where both vendor and subscriber have various operational responsibilities. AWS assumes responsibility for the underlying infrastructur...
S3 FTP: Build a Reliable and Inexpensive FTP Server Using Amazon’s S3
Is it possible to create an S3 FTP file backup/transfer solution, minimizing associated file storage and capacity planning administration headache?FTP (File Transfer Protocol) is a fast and convenient way to transfer large files over the Internet. You might, at some point, have conf...
Microservices Architecture: Advantages and Drawbacks
Microservices are a way of breaking large software projects into loosely coupled modules, which communicate with each other through simple Application Programming Interfaces (APIs).Microservices have become increasingly popular over the past few years. The modular architectural style,...
What Are Best Practices for Tagging AWS Resources?
There are many use cases for tags, but what are the best practices for tagging AWS resources? In order for your organization to effectively manage resources (and your monthly AWS bill), you need to implement and adopt a thoughtful tagging strategy that makes sense for your business. The...
How to Optimize Amazon S3 Performance
Amazon S3 is the most common storage options for many organizations, being object storage it is used for a wide variety of data types, from the smallest objects to huge datasets. All in all, Amazon S3 is a great service to store a wide scope of data types in a highly available and resil...
How to Optimize Cloud Costs with Spot Instances: New on Cloud Academy
One of the main promises of cloud computing is access to nearly endless capacity. However, it doesn’t come cheap. With the introduction of Spot Instances for Amazon Web Services’ Elastic Compute Cloud (AWS EC2) in 2009, spot instances have been a way for major cloud providers to sell sp...
What are the Benefits of Machine Learning in the Cloud?
A Comparison of Machine Learning Services on AWS, Azure, and Google CloudArtificial intelligence and machine learning are steadily making their way into enterprise applications in areas such as customer support, fraud detection, and business intelligence. There is every reason to beli...
How to Use AWS CLI
The AWS Command Line Interface (CLI) is for managing your AWS services from a terminal session on your own client, allowing you to control and configure multiple AWS services.So you’ve been using AWS for awhile and finally feel comfortable clicking your way through all the services....