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 Content: Azure DP-100 Certification, Alibaba Cloud Certified Associate Prep, 13 Security Labs, and Much More
This past month our Content Team served up a heaping spoonful of new and updated content. Not only did our experts release the brand new Azure DP-100 Certification Learning Path, but they also created 18 new hands-on labs — and so much more! New content on Cloud Academy At any time, y...
AWS Certification Practice Exam: What to Expect from Test Questions
If you’re building applications on the AWS cloud or looking to get started in cloud computing, certification is a way to build deep knowledge in key services unique to the AWS platform. AWS currently offers 12 certifications that cover major cloud roles including Solutions Architect, De...
Overcoming Unprecedented Business Challenges with AWS
From auto-scaling applications with high availability to video conferencing that’s used by everyone, every day — cloud technology has never been more popular or in-demand. But what does this mean for experienced cloud professionals and the challenges they face as they carve out a new p...
Constant Content: Cloud Academy’s Q3 2020 Roadmap
Hello — Andy Larkin here, VP of Content at Cloud Academy. I am pleased to release our roadmap for the next three months of 2020 — August through October. Let me walk you through the content we have planned for you and how this content can help you gain skills, get certified, and...
New Content: Alibaba, Azure AZ-303 and AZ-304, Site Reliability Engineering (SRE) Foundation, Python 3 Programming, 16 Hands-on Labs, and Much More
This month our Content Team did an amazing job at publishing and updating a ton of new content. Not only did our experts release the brand new AZ-303 and AZ-304 Certification Learning Paths, but they also created 16 new hands-on labs — and so much more! New content on Cloud Academy At...
Blog Digest: Which Certifications Should I Get?, The 12 Microsoft Azure Certifications, 6 Ways to Prevent a Data Breach, and More
This month, we were excited to announce that Cloud Academy was recognized in the G2 Summer 2020 reports! These reports highlight the top-rated solutions in the industry, as chosen by the source that matters most: customers. We're grateful to have been nominated as a High Performer in se...
Which Certifications Should I Get?
The old AWS slogan, “Cloud is the new normal” is indeed a reality today. Really, cloud has been the new normal for a while now and getting credentials has become an increasingly effective way to quickly showcase your abilities to recruiters and companies. With all that in mind, the s...
New Content: AWS, Azure, Typescript, Java, Docker, 13 New Labs, and Much More
This month, our Content Team released a whopping 13 new labs in real cloud environments! If you haven't tried out our labs, you might not understand why we think that number is so impressive. Our labs are not “simulated” experiences — they are real cloud environments using accounts on A...
Kickstart Your Tech Training With a Free Week on Cloud Academy
Are you looking to make a jump in your technical career? Want to get trained or certified on AWS, Azure, Google Cloud Platform, DevOps, Kubernetes, Python, or another in-demand skill? Then you'll want to mark your calendar. Starting Monday, June 22 at 12:00 a.m. PDT (3:00 a.m. EDT), ...
New Content: AZ-500 and AZ-400 Updates, 3 Google Professional Exam Preps, Practical ML Learning Path, C# Programming, and More
This month, our Content Team released tons of new content and labs in real cloud environments. Not only that, but we introduced our very first highly interactive "Office Hours" webinar. This webinar, Acing the AWS Solutions Architect Associate Certification, started with a quick overvie...
Azure vs. AWS: Which Certification Provides the Brighter Future?
More and more companies are using cloud services, prompting more and more people to switch their current IT position to something cloud-related. The problem is most people only have that much time after work to learn new technologies, and there are plenty of cloud services that you can ...
Blog Digest: 5 Reasons to Get AWS Certified, OWASP Top 10, Getting Started with VPCs, Top 10 Soft Skills, and More
Thank you for being a valued member of our community! We recently sent out a short survey to understand what type of content you would like us to add to Cloud Academy, and we want to thank everyone who gave us their input. If you would like to complete the survey, it's not too late. It ...