Ensure Security Group for EC2 Instance Does Not Allow Inbound Traffic Rule

Rule Description:

Troubleshooting Steps (if required):

2. 1.
   Check the security group associated with the EC2 instance.
4. 2.
   Verify the inbound rules for the security group.
6. 3.
   Ensure that there is a specific rule denying inbound traffic from all to port 2379.
8. 4.
   Check if there are any conflicting rules allowing traffic to port 2379.

Necessary Code (if applicable):

Step-by-Step Guide for Remediation:

2. 1.
   Log in to the AWS Management Console.
4. 2.
   Go to the EC2 service section.
6. 3.
   Select the EC2 instance for which you want to update the security group.
8. 4.
   Click on the "Security" tab.
10. 5.
    Identify the security group attached to the EC2 instance and click on the associated security group link.
12. 6.
    In the security group configuration, locate the inbound rules section.
14. 7.
    Find the entry for TCP port 2379 (etcd).
16. 8.
    If there is already a rule allowing inbound traffic from all to port 2379, take note of the rule, as it will need to be deleted.
18. 9.
    Add a new inbound rule:

    • Click on the "Edit" button next to the inbound rules section.
    • Click on the "Add Rule" button.
    • Select "Custom TCP" as the protocol.
    • Enter "2379" as the port range.
    • Specify the authorized source for inbound traffic. This can be either specific IP ranges or security group IDs.
    • Click on the "Save" button.
20. 10.
    Review the changes and click on the "Save" button to apply the new rule.
22. 11.
    If there was a conflicting rule allowing inbound traffic from all to port 2379, locate that rule and delete it:

    • Click on the "Delete" button next to the conflicting rule.
    • Confirm the deletion when prompted.