Prompt file imported from ShravaniJawalkar/aws-repo (.github/prompts/Sub-task 1 – Allocate EC2 resources.prompt.md). Copyright stays with the author.

Sub-task 1 – Allocate EC2 Resources

Name: Sub-task 1 – Allocate EC2 resources
Author: ShravaniJawalkar

Prompt List for EC2 Instance Setup and Configuration

1. EC2 Instance Creation

Create a Linux-based EC2 instance using a free-tier eligible AMI (Amazon Linux 2 or Ubuntu)
Configure the instance with t3.micro instance type
Select an appropriate key pair for SSH access
Ensure the instance is launched in the default VPC

2. Security Group Configuration

Create a new security group with the following inbound rules:
- Allow HTTP (port 80) from anywhere (0.0.0.0/0)
- Allow HTTPS (port 443) from anywhere (0.0.0.0/0)
- Allow SSH (port 22) from my current IP address only
Apply this security group to the EC2 instance

3. Dynamic IP Update Script (Windows AWS CLI)

Write a Windows batch script that:
- Retrieves the current public IP address using: curl -s https://api.ipify.org
- Formats the IP with /32 CIDR notation for the security group rule
- Revokes the old SSH rule from the security group using: aws ec2 revoke-security-group-ingress
- Adds a new SSH rule with the updated IP using: aws ec2 authorize-security-group-ingress
- Accepts parameters: AWS profile name, security group ID, and region
- Example command structure:
```
aws ec2 authorize-security-group-ingress --group-id sg-xxxxx --protocol tcp --port 22 --cidr %MY_IP%/32 --profile your-profile --region us-east-1
```
Alternative Unix/bash script (for WSL or Linux):
- Retrieves the current public IP address using: dig +short myip.opendns.com @resolver1.opendns.com
- Updates the security group SSH rule with the new IP address
- Accepts parameters: profile name, security group ID, and region
Connect to the EC2 instance via SSH using the key pair and PuTTY (Windows SSH client)

Install an HTTP server (Apache or Nginx) on the EC2 instance:

For Amazon Linux 2/Amazon Linux 2023:

sudo yum update -y
sudo yum install -y httpd
sudo systemctl start httpd
sudo systemctl enable httpd

For Ubuntu:

sudo apt update -y
sudo apt install -y apache2
sudo systemctl start apache2
sudo systemctl enable apache2

For Nginx (alternative):

# Amazon Linux
sudo amazon-linux-extras install nginx1 -y
sudo systemctl start nginx
sudo systemctl enable nginx

# Ubuntu
sudo apt install -y nginx
sudo systemctl start nginx
sudo systemctl enable nginx

Configure the HTTP server to start automatically on boot (handled by systemctl enable command above)

Verify the server is running and accessible on port 80:

sudo systemctl status httpd  # or apache2/nginx
curl http://localhost

Using AWS CLI (Windows) to execute commands remotely via SSM Session Manager:

aws ssm send-command ^
    --instance-ids "i-xxxxx" ^
    --document-name "AWS-RunShellScript" ^
    --parameters "commands=['sudo yum install -y httpd','sudo systemctl start httpd','sudo systemctl enable httpd']" ^
    --profile your-profile ^
    --region us-east-1

Note: Requires SSM agent installed and IAM role attached to EC2 instance

Check command execution status:

aws ssm list-command-invocations ^
    --command-id "command-id-from-above" ^
    --details ^
    --profile your-profile ^
    --region us-east-1

5. Static Website Deployment

Download the static website files from module 3 to the EC2 instance
Deploy the website to the HTTP server's document root directory
Set appropriate file permissions for web content

Using Windows AWS CLI to deploy static website:

Option 1: Using S3 as intermediate storage (recommended):

REM Upload local website files to S3 bucket
aws s3 cp ./website-files s3://your-bucket-name/website/ --recursive --profile your-profile --region us-east-1

REM Use SSM to download files from S3 to EC2 instance
aws ssm send-command ^
    --instance-ids "i-xxxxx" ^
    --document-name "AWS-RunShellScript" ^
    --parameters "commands=['sudo aws s3 sync s3://your-bucket-name/website/ /var/www/html/','sudo chown -R apache:apache /var/www/html/','sudo chmod -R 755 /var/www/html/']" ^
    --profile your-profile ^
    --region us-east-1

Option 2: Using SCP from Windows (requires PuTTY's pscp.exe):

REM Copy files to EC2 instance
pscp -i C:\path\to\key.ppk -r C:\path\to\website-files\* ec2-user@ec2-xx-xx-xx-xx.compute.amazonaws.com:/tmp/

REM Then SSH and move files to document root
plink -i C:\path\to\key.ppk ec2-user@ec2-xx-xx-xx-xx.compute.amazonaws.com "sudo mv /tmp/* /var/www/html/ && sudo chown -R apache:apache /var/www/html/ && sudo chmod -R 755 /var/www/html/"

Option 3: Direct SSM Session Manager file transfer:

REM Start SSM session and transfer files
aws ssm start-session --target "i-xxxxx" --profile your-profile --region us-east-1

REM Within the session, use base64 encoding for file transfer (for small files)
REM Or install AWS CLI on EC2 and pull from S3

Verify deployment:

aws ssm send-command ^
    --instance-ids "i-xxxxx" ^
    --document-name "AWS-RunShellScript" ^
    --parameters "commands=['ls -la /var/www/html/','curl http://localhost']" ^
    --profile your-profile ^
    --region us-east-1

6. Verification and Testing

Verify HTTP access by visiting the instance's public IP address in a browser

Get the EC2 instance's public IP address:

aws ec2 describe-instances ^
    --instance-ids "i-xxxxx" ^
    --query "Reservations[0].Instances[0].PublicIpAddress" ^
    --output text ^
    --profile your-profile ^
    --region us-east-1

Troubleshooting if website is not accessible:

SSH into the EC2 instance and verify Apache is running:

sudo systemctl status httpd
sudo netstat -tulpn | grep :80

Check if files are in the correct location (/var/www/html/):
```
ls -la /var/www/html/
```

Ensure correct permissions:

sudo chown -R apache:apache /var/www/html/
sudo chmod -R 755 /var/www/html/
sudo chmod 644 /var/www/html/*.html

Verify security group allows inbound HTTP (port 80) from 0.0.0.0/0:

aws ec2 describe-security-groups --group-ids sg-xxxxx --profile your-profile --region us-east-1

Check Apache error logs:
```
sudo tail -f /var/log/httpd/error_log
```

Test locally on EC2 instance:

curl http://localhost
curl http://127.0.0.1

Open a web browser and navigate to: http://<public-ip-address>
You should see your static website or the default HTTP server test page
Alternative: Test from command line:
```
curl http://<public-ip-address>
```

Confirm the static website is displayed correctly
Test that the HTTP server restarts automatically after instance reboot

7. Windows Firewall Configuration (if applicable)

Check Windows Firewall settings on local machine
Ensure outbound connections to EC2 instance are not blocked
Add exception rules if necessary for SSH and HTTP/HTTPS traffic

Header: description: "This prompt list outlines the steps to allocate and configure EC2 resources for hosting a static website, including instance creation, security group setup, HTTP server installation, and verification." mode: Agent model: Claude Sonnet 4.5 tools: [aws-cli, bash, windows-batch] Body: # Sub-task 1 – Allocate EC2 Resources ## Prompt List for EC2 Instance Setup and Configuration ### 1. EC2 Instance Creation - Create a Linux-based EC2 instance using a free-tier eligible AMI (Amazon Linux 2 or Ubuntu) - Configure the instance with t3.micro instance type - Select an appropriate key pair for SSH access - Ensure the instance is launched in the default VPC ### 2. Security Group Configuration - Create a new security group with the following inbound rules: - Allow HTTP (port 80) from anywhere (0.0.0.0/0) - Allow HTTPS (port 443) from anywhere (0.0.0.0/0) - Allow SSH (port 22) from my current IP address only - Apply this security group to the EC2 instance ### 3. Dynamic IP Update Script (Windows AWS CLI) - Write a Windows batch script that: - Retrieves the current public IP address using: `curl -s https://api.ipify.org` - Formats the IP with /32 CIDR notation for the security group rule - Revokes the old SSH rule from the security group using: `aws ec2 revoke-security-group-ingress` - Adds a new SSH rule with the updated IP using: `aws ec2 authorize-security-group-ingress` - Accepts parameters: AWS profile name, security group ID, and region - Example command structure: ```batch aws ec2 authorize-security-group-ingress --group-id sg-xxxxx --protocol tcp --port 22 --cidr %MY_IP%/32 --profile your-profile --region us-east-1 ``` - Alternative Unix/bash script (for WSL or Linux): - Retrieves the current public IP address using: `dig +short myip.opendns.com @resolver1.opendns.com` - Updates the security group SSH rule with the new IP address - Accepts parameters: profile name, security group ID, and region - Connect to the EC2 instance via SSH using the key pair and PuTTY (Windows SSH client) - Install an HTTP server (Apache or Nginx) on the EC2 instance: - **For Amazon Linux 2/Amazon Linux 2023:** ```bash sudo yum update -y sudo yum install -y httpd sudo systemctl start httpd sudo systemctl enable httpd ``` - **For Ubuntu:** ```bash sudo apt update -y sudo apt install -y apache2 sudo systemctl start apache2 sudo systemctl enable apache2 ``` - **For Nginx (alternative):** ```bash # Amazon Linux sudo amazon-linux-extras install nginx1 -y sudo systemctl start nginx sudo systemctl enable nginx # Ubuntu sudo apt install -y nginx sudo systemctl start nginx sudo systemctl enable nginx ``` - Configure the HTTP server to start automatically on boot (handled by `systemctl enable` command above) - Verify the server is running and accessible on port 80: ```bash sudo systemctl status httpd # or apache2/nginx curl http://localhost ``` - **Using AWS CLI (Windows) to execute commands remotely via SSM Session Manager:** ```batch aws ssm send-command ^ --instance-ids "i-xxxxx" ^ --document-name "AWS-RunShellScript" ^ --parameters "commands=['sudo yum install -y httpd','sudo systemctl start httpd','sudo systemctl enable httpd']" ^ --profile your-profile ^ --region us-east-1 ``` Note: Requires SSM agent installed and IAM role attached to EC2 instance - **Check command execution status:** ```batch aws ssm list-command-invocations ^ --command-id "command-id-from-above" ^ --details ^ --profile your-profile ^ --region us-east-1 ``` ### 5. Static Website Deployment - Download the static website files from module 3 to the EC2 instance - Deploy the website to the HTTP server's document root directory - Set appropriate file permissions for web content - **Using Windows AWS CLI to deploy static website:** - **Option 1: Using S3 as intermediate storage (recommended):** ```batch REM Upload local website files to S3 bucket aws s3 cp ./website-files s3://your-bucket-name/website/ --recursive --profile your-profile --region us-east-1 REM Use SSM to download files from S3 to EC2 instance aws ssm send-command ^ --instance-ids "i-xxxxx" ^ --document-name "AWS-RunShellScript" ^ --parameters "commands=['sudo aws s3 sync s3://your-bucket-name/website/ /var/www/html/','sudo chown -R apache:apache /var/www/html/','sudo chmod -R 755 /var/www/html/']" ^ --profile your-profile ^ --region us-east-1 ``` - **Option 2: Using SCP from Windows (requires PuTTY's pscp.exe):** ```batch REM Copy files to EC2 instance pscp -i C:\path\to\key.ppk -r C:\path\to\website-files\* ec2-user@ec2-xx-xx-xx-xx.compute.amazonaws.com:/tmp/ REM Then SSH and move files to document root plink -i C:\path\to\key.ppk ec2-user@ec2-xx-xx-xx-xx.compute.amazonaws.com "sudo mv /tmp/* /var/www/html/ && sudo chown -R apache:apache /var/www/html/ && sudo chmod -R 755 /var/www/html/" ``` - **Option 3: Direct SSM Session Manager file transfer:** ```batch REM Start SSM session and transfer files aws ssm start-session --target "i-xxxxx" --profile your-profile --region us-east-1 REM Within the session, use base64 encoding for file transfer (for small files) REM Or install AWS CLI on EC2 and pull from S3 ``` - **Verify deployment:** ```batch aws ssm send-command ^ --instance-ids "i-xxxxx" ^ --document-name "AWS-RunShellScript" ^ --parameters "commands=['ls -la /var/www/html/','curl http://localhost']" ^ --profile your-profile ^ --region us-east-1 ``` ### 6. Verification and Testing - Verify HTTP access by visiting the instance's public IP address in a browser - **Get the EC2 instance's public IP address:** ```batch aws ec2 describe-instances ^ --instance-ids "i-xxxxx" ^ --query "Reservations[0].Instances[0].PublicIpAddress" ^ --output text ^ --profile your-profile ^ --region us-east-1 ``` - **Troubleshooting if website is not accessible:** - SSH into the EC2 instance and verify Apache is running: ```bash sudo systemctl status httpd sudo netstat -tulpn | grep :80 ``` - Check if files are in the correct location (`/var/www/html/`): ```bash ls -la /var/www/html/ ``` - Ensure correct permissions: ```bash sudo chown -R apache:apache /var/www/html/ sudo chmod -R 755 /var/www/html/ sudo chmod 644 /var/www/html/*.html ``` - Verify security group allows inbound HTTP (port 80) from 0.0.0.0/0: ```batch aws ec2 describe-security-groups --group-ids sg-xxxxx --profile your-profile --region us-east-1 ``` - Check Apache error logs: ```bash sudo tail -f /var/log/httpd/error_log ``` - Test locally on EC2 instance: ```bash curl http://localhost curl http://127.0.0.1 ``` - Open a web browser and navigate to: `http://<public-ip-address>` - You should see your static website or the default HTTP server test page - **Alternative: Test from command line:** ```batch curl http://<public-ip-address> ``` - Confirm the static website is displayed correctly - Test that the HTTP server restarts automatically after instance reboot ### 7. Windows Firewall Configuration (if applicable) - Check Windows Firewall settings on local machine - Ensure outbound connections to EC2 instance are not blocked - Add exception rules if necessary for SSH and HTTP/HTTPS traffic

{ "prompt": "Header:\n description: \"This prompt list outlines the steps to allocate and configure EC2 resources for hosting a static website, including instance creation, security group setup, HTTP server installation, and verification.\"\n mode: Agent\n model: Claude Sonnet 4.5\n tools: [aws-cli, bash, windows-batch]\nBody:\n# Sub-task 1 – Allocate EC2 Resources\n\n## Prompt List for EC2 Instance Setup and Configuration\n\n### 1. EC2 Instance Creation\n- Create a Linux-based EC2 instance using a free-tier eligible AMI (Amazon Linux 2 or Ubuntu)\n- Configure the instance with t3.micro instance type\n- Select an appropriate key pair for SSH access\n- Ensure the instance is launched in the default VPC\n\n### 2. Security Group Configuration\n- Create a new security group with the following inbound rules:\n - Allow HTTP (port 80) from anywhere (0.0.0.0/0)\n - Allow HTTPS (port 443) from anywhere (0.0.0.0/0)\n - Allow SSH (port 22) from my current IP address only\n- Apply this security group to the EC2 instance\n\n### 3. Dynamic IP Update Script (Windows AWS CLI)\n- Write a Windows batch script that:\n - Retrieves the current public IP address using: `curl -s https://api.ipify.org`\n - Formats the IP with /32 CIDR notation for the security group rule\n - Revokes the old SSH rule from the security group using: `aws ec2 revoke-security-group-ingress`\n - Adds a new SSH rule with the updated IP using: `aws ec2 authorize-security-group-ingress`\n - Accepts parameters: AWS profile name, security group ID, and region\n - Example command structure:\n ```batch\n aws ec2 authorize-security-group-ingress --group-id sg-xxxxx --protocol tcp --port 22 --cidr %MY_IP%/32 --profile your-profile --region us-east-1\n ```\n- Alternative Unix/bash script (for WSL or Linux):\n - Retrieves the current public IP address using: `dig +short myip.opendns.com @resolver1.opendns.com`\n - Updates the security group SSH rule with the new IP address\n - Accepts parameters: profile name, security group ID, and region\n\n- Connect to the EC2 instance via SSH using the key pair and PuTTY (Windows SSH client)\n- Install an HTTP server (Apache or Nginx) on the EC2 instance:\n - **For Amazon Linux 2/Amazon Linux 2023:**\n ```bash\n sudo yum update -y\n sudo yum install -y httpd\n sudo systemctl start httpd\n sudo systemctl enable httpd\n ```\n - **For Ubuntu:**\n ```bash\n sudo apt update -y\n sudo apt install -y apache2\n sudo systemctl start apache2\n sudo systemctl enable apache2\n ```\n - **For Nginx (alternative):**\n ```bash\n # Amazon Linux\n sudo amazon-linux-extras install nginx1 -y\n sudo systemctl start nginx\n sudo systemctl enable nginx\n \n # Ubuntu\n sudo apt install -y nginx\n sudo systemctl start nginx\n sudo systemctl enable nginx\n ```\n- Configure the HTTP server to start automatically on boot (handled by `systemctl enable` command above)\n- Verify the server is running and accessible on port 80:\n ```bash\n sudo systemctl status httpd # or apache2/nginx\n curl http://localhost\n ```\n- **Using AWS CLI (Windows) to execute commands remotely via SSM Session Manager:**\n ```batch\n aws ssm send-command ^\n --instance-ids \"i-xxxxx\" ^\n --document-name \"AWS-RunShellScript\" ^\n --parameters \"commands=['sudo yum install -y httpd','sudo systemctl start httpd','sudo systemctl enable httpd']\" ^\n --profile your-profile ^\n --region us-east-1\n ```\n Note: Requires SSM agent installed and IAM role attached to EC2 instance\n- **Check command execution status:**\n ```batch\n aws ssm list-command-invocations ^\n --command-id \"command-id-from-above\" ^\n --details ^\n --profile your-profile ^\n --region us-east-1\n ```\n\n### 5. Static Website Deployment\n- Download the static website files from module 3 to the EC2 instance\n- Deploy the website to the HTTP server's document root directory\n- Set appropriate file permissions for web content\n- **Using Windows AWS CLI to deploy static website:**\n - **Option 1: Using S3 as intermediate storage (recommended):**\n ```batch\n REM Upload local website files to S3 bucket\n aws s3 cp ./website-files s3://your-bucket-name/website/ --recursive --profile your-profile --region us-east-1\n \n REM Use SSM to download files from S3 to EC2 instance\n aws ssm send-command ^\n --instance-ids \"i-xxxxx\" ^\n --document-name \"AWS-RunShellScript\" ^\n --parameters \"commands=['sudo aws s3 sync s3://your-bucket-name/website/ /var/www/html/','sudo chown -R apache:apache /var/www/html/','sudo chmod -R 755 /var/www/html/']\" ^\n --profile your-profile ^\n --region us-east-1\n ```\n - **Option 2: Using SCP from Windows (requires PuTTY's pscp.exe):**\n ```batch\n REM Copy files to EC2 instance\n pscp -i C:\\path\\to\\key.ppk -r C:\\path\\to\\website-files\\* ec2-user@ec2-xx-xx-xx-xx.compute.amazonaws.com:/tmp/\n \n REM Then SSH and move files to document root\n plink -i C:\\path\\to\\key.ppk ec2-user@ec2-xx-xx-xx-xx.compute.amazonaws.com \"sudo mv /tmp/* /var/www/html/ && sudo chown -R apache:apache /var/www/html/ && sudo chmod -R 755 /var/www/html/\"\n ```\n - **Option 3: Direct SSM Session Manager file transfer:**\n ```batch\n REM Start SSM session and transfer files\n aws ssm start-session --target \"i-xxxxx\" --profile your-profile --region us-east-1\n \n REM Within the session, use base64 encoding for file transfer (for small files)\n REM Or install AWS CLI on EC2 and pull from S3\n ```\n - **Verify deployment:**\n ```batch\n aws ssm send-command ^\n --instance-ids \"i-xxxxx\" ^\n --document-name \"AWS-RunShellScript\" ^\n --parameters \"commands=['ls -la /var/www/html/','curl http://localhost']\" ^\n --profile your-profile ^\n --region us-east-1\n ```\n\n\n### 6. Verification and Testing\n\n- Verify HTTP access by visiting the instance's public IP address in a browser\n - **Get the EC2 instance's public IP address:**\n ```batch\n aws ec2 describe-instances ^\n --instance-ids \"i-xxxxx\" ^\n --query \"Reservations[0].Instances[0].PublicIpAddress\" ^\n --output text ^\n --profile your-profile ^\n --region us-east-1\n ```\n - **Troubleshooting if website is not accessible:**\n - SSH into the EC2 instance and verify Apache is running:\n ```bash\n sudo systemctl status httpd\n sudo netstat -tulpn | grep :80\n ```\n - Check if files are in the correct location (`/var/www/html/`):\n ```bash\n ls -la /var/www/html/\n ```\n - Ensure correct permissions:\n ```bash\n sudo chown -R apache:apache /var/www/html/\n sudo chmod -R 755 /var/www/html/\n sudo chmod 644 /var/www/html/*.html\n ```\n - Verify security group allows inbound HTTP (port 80) from 0.0.0.0/0:\n ```batch\n aws ec2 describe-security-groups --group-ids sg-xxxxx --profile your-profile --region us-east-1\n ```\n - Check Apache error logs:\n ```bash\n sudo tail -f /var/log/httpd/error_log\n ```\n - Test locally on EC2 instance:\n ```bash\n curl http://localhost\n curl http://127.0.0.1\n ```\n - Open a web browser and navigate to: `http://<public-ip-address>`\n - You should see your static website or the default HTTP server test page\n - **Alternative: Test from command line:**\n ```batch\n curl http://<public-ip-address>\n ```\n- Confirm the static website is displayed correctly\n- Test that the HTTP server restarts automatically after instance reboot\n\n### 7. Windows Firewall Configuration (if applicable)\n- Check Windows Firewall settings on local machine\n- Ensure outbound connections to EC2 instance are not blocked\n- Add exception rules if necessary for SSH and HTTP/HTTPS traffic", "variables": [], "notes": "Header: description: \"This prompt list outlines the steps to allocate and configure EC2 resources for hosting a static website, including instance creation, security group setup, HTTP server installation, and verification.\" mode: Agent model: Claude Sonnet 4.5 tools: [aws-cli, bash, windows-batch] Body: # Sub-task 1 – Allocate EC2 Resources", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/ShravaniJawalkar/aws-repo", "path": ".github/prompts/Sub-task 1 – Allocate EC2 resources.prompt.md", "ref": "130802f7e82c7ba56282a91aa3e08f7976b96edf", "url": "https://github.com/ShravaniJawalkar/aws-repo/blob/130802f7e82c7ba56282a91aa3e08f7976b96edf/.github/prompts/Sub-task 1 – Allocate EC2 resources.prompt.md", "key": "ShravaniJawalkar/aws-repo/.github/prompts/Sub-task 1 – Allocate EC2 resources.prompt.md" } } }

Sub-task 1 – Allocate EC2 resources

About

Sub-task 1 – Allocate EC2 Resources

Prompt List for EC2 Instance Setup and Configuration

1. EC2 Instance Creation

2. Security Group Configuration

3. Dynamic IP Update Script (Windows AWS CLI)

5. Static Website Deployment

6. Verification and Testing

7. Windows Firewall Configuration (if applicable)

Use it

Manifest

Reviews