cloud computing file
cloud computing file
1. Open your web browser and go to the AWS Management Console: AWS Console.
3: Launch Instance
1. In the EC2 Dashboard, click on the “Instances” link in the left-hand navigation pane.
2. Click the “Launch Instance” button to begin the instance creation process.
Select an AMI based on your requirements (e.g., Amazon Linux 2, Ubuntu Server,
Windows Server).
Select the instance type based on your workload and performance needs.
Configure settings such as the number of instances, VPC, subnet, IAM role (if
applicable), etc.
1. In the “Select an existing key pair or create a new key pair” pop-up window:
Download the private key (.pem file) if you are creating a new key pair.
Specify the size and type of the root volume (EBS) for your instance.
Optionally, add tags to your instance for better organization and management.
Configure inbound and outbound rules to control tra ic to and from your instance (e.g.,
SSH, HTTP, HTTPS).
11: Review Instance Launch
1. Once the instance is launched successfully, you can view its status in the EC2
Dashboard under “Instances.”
2. Use the downloaded private key (.pem file) to SSH into your instance if it’s a Linux-based
instance or use Remote Desktop Protocol (RDP) for Windows instances.
That’s it! You have successfully created an EC2 instance on AWS and can now start using it for
your applications or development purposes. Make sure to manage and monitor your instances
regularly through the AWS Management Console.
1. If you haven’t already, download PuTTY and PuTTYgen from the o icial PuTTY
website: PuTTY Download
2. Install PuTTY on your Windows machine. During the installation process, PuTTYgen
should also be installed.
3. By default, PuTTYgen filters for “PuTTY Private Key Files (.ppk).” Change the file type filter to
“All Files (.*)” to see your .pem private key file.
1.
4. Navigate to the location of your .pem private key file, select it, and click “Open.”
5. PuTTYgen will prompt you to confirm the conversion of the key. Click “OK” to continue.
6. Optionally, you can set a passphrase for added security by entering it in the “Key passphrase”
and “Confirm passphrase” fields. This step is optional but recommended.
7. Click on the “Save private key” button to save the converted private key in PuTTY’s .ppk
format.
8. Choose a location to save the .ppk file and give it a descriptive name (e.g., mykey.ppk).
Now you have successfully generated a PuTTY Private Key (.ppk) file from your original private
key (.pem) file. This .ppk file can be used with PuTTY to connect securely to your AWS EC2
instances or other SSH servers. Remember to keep your private key files secure and never share
them publicly or with unauthorized individuals.
2. In the “Category” pane on the left, expand the “SSH” category and click on “Auth.”
3. Click on the “Browse” button next to “Private key file for authentication” and select the
.ppk file you generated in Step 2.
5. Enter the EC2 instance’s Public IP address into the “Host Name (or IP address)” field.
6. Optionally, enter a name for your session in the “Saved Sessions” field and click “Save” to
save these settings for future use.
7. PuTTY will open a terminal window and attempt to establish an SSH connection to your EC2
instance.
You are now connected to your EC2 instance via SSH using PuTTY. You can run commands and
manage your instance from the terminal window.
2. Remotely Run Unix Commands on an EC2 Instance
o Example commands:
If you prefer not to use key pairs or PuTTY, you can use AWS Session Manager.
aws configure
2. Use the aws ssm send-command to execute commands:
--targets "Key=instanceIds,Values=<instance-id>" \
--document-name "AWS-RunShellScript" \
--parameters 'commands=["<your-command>"]'
1. Create EC2 Instance and Connect with PuTTY (Without Key Pair)
2. Open PuTTY, enter the public IP of the EC2 instance, and connect using your
credentials.
Open a browser and navigate to the Public IPv4 Address of the instance.
2. Install dependencies:
Use Amazon RDS for the database backend to manage scalability and performance.
Step 4: Upload Files and Configure
Point your domain to the instance's IP using Route 53 and set up SSL using AWS
Certificate Manager.
4. Remotely Run Commands on EC2 (Using IAM Role Without Key Pair)
o Use the Session Manager to run commands directly in the AWS console.
Use a SaaS platform like Shopify or Salesforce for hosting a fully-managed service.
1. Create an S3 bucket.
3. Enable bucket permissions for public access (optional) or use pre-signed URLs.