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!
New on Cloud Academy: Red Hat, Agile, OWASP Labs, Amazon SageMaker Lab, Linux Command Line Lab, SQL, Git Labs, Scrum Master, Azure Architects Lab, and Much More
Happy New Year! We hope you're ready to kick your training in overdrive in 2020 because we have a ton of new content for you. Not only do we have a bunch of new courses, hands-on labs, and lab challenges on AWS, Azure, and Google Cloud, but we also have three new courses on Red Hat, th...
Cloud Academy’s Blog Digest: Azure Best Practices, 6 Reasons You Should Get AWS Certified, Google Cloud Certification Prep, and more
Happy Holidays from Cloud Academy We hope you have a wonderful holiday season filled with family, friends, and plenty of food. Here at Cloud Academy, we are thankful for our amazing customer like you. Since this time of year can be stressful, we’re sharing a few of our latest article...
Google Cloud Platform 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 2019, research firm Gartner placed Google in the Leaders quadrant in its Magic Quadrant for Cloud Infrastructure as a Service for the second consecuti...
New Lab Challenges: Push Your Skills to the Next Level
Build hands-on experience using real accounts on AWS, Azure, Google Cloud Platform, and more Meaningful cloud skills require more than book knowledge. Hands-on experience is required to translate knowledge into real-world results. We see this time and time again in studies about how pe...
New on Cloud Academy: AWS Solution Architect Lab Challenge, Azure Hands-on Labs, Foundation Certificate in Cyber Security, and Much More
Now that Thanksgiving is over and the craziness of Black Friday has died down, it's now time for the busiest season of the year. Whether you're a last-minute shopper or you already have your shopping done, the holidays bring so much more excitement than any other time of year. Since our...
Understanding Enterprise Cloud Migration
What is enterprise cloud migration? Cloud migration is about moving your data, applications, and even infrastructure from your on-premises computers or infrastructure to a virtual pool of on-demand, shared resources that offer compute, storage, and network services at scale. Why d...
6 Reasons Why You Should Get an AWS Certification This Year
In the past decade, the rise of cloud computing has been undeniable. Businesses of all sizes are moving their infrastructure and applications to the cloud. This is partly because the cloud allows businesses and their employees to access important information from just about anywhere. ...
AWS Regions and Availability Zones: The Simplest Explanation You Will Ever Find Around
The basics of AWS Regions and Availability Zones We’re going to treat this article as a sort of AWS 101 — it’ll be a quick primer on AWS Regions and Availability Zones that will be useful for understanding the basics of how AWS infrastructure is organized. We’ll define each section,...
Application Load Balancer vs. Classic Load Balancer
What is an Elastic Load Balancer? This post covers basics of what an Elastic Load Balancer is, and two of its examples: Application Load Balancers and Classic Load Balancers. For additional information — including a comparison that explains Network Load Balancers — check out our post o...
Advantages and Disadvantages of Microservices Architecture
What are microservices? Let's start our discussion by setting a foundation of what microservices are. Microservices are a way of breaking large software projects into loosely coupled modules, which communicate with each other through simple Application Programming Interfaces (APIs). ...
Kubernetes Services: AWS vs. Azure vs. Google Cloud
Kubernetes is a popular open-source container orchestration platform that allows us to deploy and manage multi-container applications at scale. Businesses are rapidly adopting this revolutionary technology to modernize their applications. Cloud service providers — such as Amazon Web Ser...
AWS Internet of Things (IoT): The 3 Services You Need to Know
The Internet of Things (IoT) embeds technology into any physical thing to enable never-before-seen levels of connectivity. IoT is revolutionizing industries and creating many new market opportunities. Cloud services play an important role in enabling deployment of IoT solutions that min...