Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 947162

Summary: Turn off iptables by default and have no pre-loaded rules in EC2
Product: Red Hat Enterprise Linux 6 Reporter: Jay Greguske <jgreguske>
Component: ec2-imagesAssignee: Jay Greguske <jgreguske>
Status: CLOSED CURRENTRELEASE QA Contact: Ina Panova <ipanova>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 6.4CC: dgao, dgregor, ipanova, jgreguske, sforsber, tsanders
Target Milestone: rcKeywords: EC2
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-09 19:21:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 883504    

Description Jay Greguske 2013-04-01 19:02:25 UTC
Amazon recommends turning off iptables in the EC2 images:

With our EC2 Security Groups iptables on by default is redundant and
ends up with a negative customer experience when they launch and
instance, select their security group, but still get denied access to
their application.  Even our Security SAs agree with this.

Comment 2 Suzanne Forsberg 2013-04-09 14:46:47 UTC
Since Amazon configures the firewall externally (i.e. outside the RHEL VM), the Platform Security Engineering team agrees that it is acceptable to disable iptables by default on the RHEL EC2 image.

See Amazon's documentation for more details on their external provisioning.
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.
html

We would like to revisit this decision for RHEL 7 when we have an implementation for firewalld.

Comment 3 dgao 2013-09-13 10:59:48 UTC
commit to spin-kickstarts repo: e950f440c69ef71240a1830c06381bff529b8eec

Comment 5 Ina Panova 2013-11-14 10:56:40 UTC
# chkconfig --list iptables
iptables       	0:off	1:off	2:off	3:off	4:off	5:off	6:off
# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination   

Verified with ami-17c59f7e (stage), rh-amazon-rhui-client-2.2.93-1