Updating Network Settings for EC2 Instance

Method 1: Using AWS Management Console

1. Navigate to EC2 Dashboard:
   • Log in to your AWS Management Console.
   • Go to the EC2 dashboard.
2. Select the Instance:
   • Locate the EC2 instance for which you want to update the network settings.
   • Click on the instance ID to open its details.
3. Update Security Groups:
   • In the instance details pane, scroll down to the "Security" tab.
   • Click on "Security groups" to view and modify associated security groups.
4. Modify Security Group Rules:
   • Select the relevant security group associated with your instance.
   • Click on the "Inbound rules" tab and then "Edit inbound rules".
   • Add rules for HTTP (port 80), HTTPS (port 443), and SSH (port 22) as needed.
   • Example:
     • HTTP (port 80): Protocol TCP, Port Range 80, Source 0.0.0.0/0 (or specify a more restrictive IP range if desired).
     • HTTPS (port 443): Protocol TCP, Port Range 443, Source 0.0.0.0/0 (or specify a more restrictive IP range if desired).
     • SSH (port 22): Protocol TCP, Port Range 22, Source YourIP/32 (replace YourIP with your actual IP address for security).
   • Save changes by clicking "Save rules" to apply the changes to the security group.

Method 2: Using AWS CLI

1. Authorize Ingress Rules:
   • Use the AWS CLI command aws ec2 authorize-security-group-ingress to add rules for HTTP, HTTPS, and SSH.
   • Example commands:
     • aws ec2 authorize-security-group-ingress --group-id YourSecurityGroupId --protocol tcp --port 80 --cidr 0.0.0.0/0
     • aws ec2 authorize-security-group-ingress --group-id YourSecurityGroupId --protocol tcp --port 443 --cidr 0.0.0.0/0
     • aws ec2 authorize-security-group-ingress --group-id YourSecurityGroupId --protocol tcp --port 22 --cidr YourIP/32
   • Replace YourSecurityGroupId with your actual security group ID and adjust the --cidr values to restrict access as needed.
2. Verify Changes:
   • After executing the commands, verify the security group rules are updated correctly using the AWS Management Console or by querying the security group settings via CLI.

Notes:

• Security Best Practices: Restrict access to the minimum necessary IPs (CIDR blocks) and protocols (HTTP, HTTPS, SSH) to enhance security.
• Network ACLs: If applicable, ensure Network ACLs allow necessary inbound and outbound traffic for your subnet.
• Changes Propagation: Security group changes are applied immediately, but it may take a few moments for changes to propagate and take effect.

By following these steps, you can update the network settings of your EC2 instance to allow HTTP, HTTPS, and SSH traffic as required for your applications and services. Adjust the commands and settings based on your specific requirements and AWS environment.