chmod 400 path/to/your/key.pemssh -i "path/to/your/key.pem" ubuntu@your-instance-public-dns<name-of-instance><key-pair-name>ssh -i /path/to/YOUR-KEY.pem ec2-user@YOUR-EC2-PUBLIC-IPsudo yum update -ysudo yum install nginx -ysudo service nginx startcd /usr/share/nginx/htmlecho '<h1>Welcome to my web page!</h1>' | sudo tee mypage.html > /dev/nullsudo vi /etc/nginx/conf.d/server.confi to enter Insert mode in Vi and paste in the following configserver {
listen 80 default_server;
server_name _;
root /usr/share/nginx/html;
location / {
index mypage.html;
}
}:wq! (to exit and save)sudo nginx -t && sudo service nginx reload<instance-name>You can automate installation and configuration steps after launch by providing a script, this usually sits within the User Data section the meta data service, which is then executed by the operating system of the EC2 Instance.
Navigate to EC2 via the AWS Management Console and use the following configurations to set up an instance
<the-name><your-key-pair-name><security-name>Click on the dropdown of Advanced details
#!/bin/bash
# Step 1: Update the system
sudo yum update -y
# Step 2: Install Nginx
sudo yum install nginx -y
# Step 3: Start Nginx Service
sudo service nginx start
# Create a custom HTML page directly in the HTML directory
echo '<h1>Welcome to my web page!</h1>' | sudo tee /usr/share/nginx/html/mypage.html > /dev/null
# Add the configuration directly
echo 'server {
listen 80 default_server;
server_name _;
root /usr/share/nginx/html;
location / {
index mypage.html;
}
}' | sudo tee /etc/nginx/conf.d/server.conf > /dev/null
# Reload Nginx for the changes to take effect
sudo nginx -t && sudo service nginx reloadScaling an EC2 instance vertically means modifying it’s size to meet a workload demand.
Create an EC2 instance with the following configurations:
<name>In order to scale, you will need to stop the instance
Now navigate to the “Instances” tab on the left
Click on the “Actions” button, it will bring up a dropdown menu
Change t2.nano to t2.micro
Click apply
Restart the instance
<name>ssh -i "path_toyour_key.pem" ec2-user@your-instance-public-dnsTOKEN=`curl -X PUT "http://169.254.169.254/latest/api/token" -H "X-aws-ec2-metadata-token-ttl-seconds: 21600"` \
&& curl -H "X-aws-ec2-metadata-token: $TOKEN" -v http://169.254.169.254/latest/meta-data/TOKEN=`curl -X PUT "http://169.254.169.254/latest/api/token" -H "X-aws-ec2-metadata-token-ttl-seconds: 21600"` && curl -H "X-aws-ec2-metadata-token: $TOKEN" -v http://169.254.169.254/latest/meta-data/public-hostname<name one> and <name two><key_name>lsblksudo mfks -t ext4 /dev/xvdfsudo mkdir /<name-of-folder>sudo mount /dev/xvdf /<name-of-folder>lsblk -f<name-of-folder> directory and create a file inside of it
sudo suecho "Welcome!" > message.txtlssudo mkdir /<name-of-folder>sudo mount /dev/xvdf /<name-of-folder>cd /<name-of-folder> && lsAWS Capacity Reservation enables you to reserve capacity for your Amazon EC2 instances in a specific AZ zone for a duration. This is particularly useful for applications that require specific host or instance placement.
Navigate to to EC2
On the left hand side, under instances select Capacity Reservations
In Capacity Reservation types, select the Create On-Demand Capacity Reservation and click get started
The following details are needed:
Reserved Instances come with a fixed period of either 1 or 3 years
Navigate to EC2 and select Reserved Instances from the left hand side understand Instances
Click on Purchased Reserved Instances
Configuration:
Click Order All
<instance-name><key-pair-name><name-of-instance><key-pair-name><instance-name><key-pair-name>date
timedatectlsudo yum install chrony -ysudo systemctl enable chronyd
sudo systemctl start chronydsudo systemctl status chronydsudo vi /etc/chrony.confchronyc tracking
chronyc sources -vtimedatectl list-timezonessudo timedatectl set-timezone [your-timezone-pasted-here]timedatectl<instance-name><key-pair-name>w32tm /query /statustzutil /gw32tm /config /manualpeerlist:"0.pool.ntp.org,1.pool.ntp.org,2.pool.ntp.org,3.pool.ntp.org" /syncfromflags:manual /reliable:YES /updatenet stop w32time and net start w32timew32tm /resyncw32 /query /statustzutil /ltzutil /s "<your-time-zone>"w32tm /query /status and tzutil /g<instance-name><key-pair-name><group-name>ssh -i /path/to/YOUR-KEY.pem ec2-user@YOUR-EC2-PUBLIC-IP# Step 1: Update the system
sudo yum update -y
# Step 2: Install Nginx
sudo yum install nginx -y
# Step 3: Start Nginx Service
sudo service nginx start
# Create a custom HTML page directly in the HTML directory
echo '<h1>Welcome to my web page!</h1>' | sudo tee /usr/share/nginx/html/mypage.html > /dev/null
# Add the configuration directly
echo 'server {
listen 80 default_server;
server_name _;
root /usr/share/nginx/html;
location / {
index mypage.html;
}
}' | sudo tee /etc/nginx/conf.d/server.conf > /dev/null
# Reload Nginx for the changes to take effect
sudo nginx -t && sudo service nginx reload
#Automatically start NGINX at boot time
sudo systemctl enable nginx<name-tag><instance-name><key-pair-name>EC2StartStopFunctionPlayCloud-Sandbox<EC2-INSTANCE-ID> with your instance IDimport boto3
ec2 = boto3.client('ec2')
def lambda_handler(event, context):
instance_id = '<EC2-INTANCE-ID>' # Replace with your instance ID
action = event['action'] # 'start' or 'stop'
if action == 'start':
ec2.start_instances(InstanceIds=[instance_id])
return 'Instance started'
elif action == 'stop':
ec2.stop_instances(InstanceIds=[instance_id])
return 'Instance stopped'
else:
return 'Invalid action'StartInstanceRuleEC2StartStopFunction{"action": "start"}{"action": "stop"}stopTrigger-Test{"action": "stop"}<asg-template-name><key-pair-name><security-group-name><description-of-security-group><asg-template-name>#This updates the package list in your system
sudo yum update -y#This installs stress
sudo yum install stress -y#Spawns 50 workers for 5 minutes
stress --cpu 50 --timeout 5m