Setting Up Cloud Infrastructure on AWS/Azure/GCP • Objective: Familiarize students with cloud platform interfaces and create basic infrastructure. • Tasks: 1. Create an account on a cloud platform (AWS, Azure, GCP) or use a provided student account. 2. Set up a Virtual Private Cloud (VPC) with at least one public and one private subnet. 3. Launch a Virtual Machine (VM) (e.g., EC2 in AWS, VM in Azure) in the public subnet and access it via SSH or RDP. 4. Assign a static IP address to the VM. 5. Submit a report with details of the setup (screenshots of each step and the final architecture diagram).

Report
Question

Please briefly explain why you feel this question should be reported.

Report
Cancel
Setting Up Cloud Infrastructure on AWS/Azure/GCP • Objective: Familiarize students with cloud platform interfaces and create basic infrastructure. • Tasks: 1. Create an account on a cloud platform (AWS, Azure, GCP) or use a provided student account. 2. Set up a Virtual Private Cloud (VPC) with at least one public and one private subnet. 3. Launch a Virtual Machine (VM) (e.g., EC2 in AWS, VM in Azure) in the public subnet and access it via SSH or RDP. 4. Assign a static IP address to the VM. 5. Submit a report with details of the setup (screenshots of each step and the final architecture diagram).

Setting Up Cloud Infrastructure on AWS/Azure/GCP
• Objective: Familiarize students with cloud platform interfaces and create basic
infrastructure.
• Tasks:
1. Create an account on a cloud platform (AWS, Azure, GCP) or use a
provided student account.
2. Set up a Virtual Private Cloud (VPC) with at least one public and one
private subnet.
3. Launch a Virtual Machine (VM) (e.g., EC2 in AWS, VM in Azure) in the
public subnet and access it via SSH or RDP.
4. Assign a static IP address to the VM.
5. Submit a report with details of the setup (screenshots of each step and the
final architecture diagram).

in progress 0
Anonymous 2025-03-29T03:46:10+05:00 1 Answer 3 views
0
MathJax Example

Answer ( 1 )

  1. Admin
    0
    2025-03-29T18:19:08+05:00
    Report Reply

    Please briefly explain why you feel this answer should be reported.

    Report
    Cancel

    Introduction

    Cloud computing has revolutionized the deployment and management of organizational IT infrastructure, providing scalable and secure environments for learning and development. This project involves setting up a basic cloud architecture using AWS, Azure, or Google Cloud Platform (GCP) with the primary goal of creating a secure environment for practical learning and hands-on experience in cloud architecture.

    The objective is to design a virtual network on AWS, establishing public and private subnets to demonstrate the concept of network segregation. This setup enhances students’ understanding of cloud networking, security, and resource management by launching a virtual machine (VM) in the public subnet with a static IP address. Secure access through SSH or RDP reflects real-world security policies and best practices.

    This project provides students with practical experience in deploying foundational cloud services, preparing them for real-world infrastructure management. While the specifics may vary across platforms (AWS EC2, Azure VMs, Google Compute Engine), the core concepts of cloud architecture and security remain consistent, offering a strong foundation for future cloud-based projects.

    Step 1: VPC and Network Setup

    1.1. Creating the VPC

    1. Open the AWS Management Console → VPC Dashboard
    2. Select “Create VPC” and configure the following settings:
      • Name: MyProjectVPC
      • IPv4 CIDR: 10.0.0.0/16
      • Enable DNS Hostnames: Yes

    1.2. Setting up Subnets

    • Public Subnet:
      • Name: Public-Subnet-1
      • CIDR: 10.0.1.0/24
      • Availability Zone: us-east-1a
    • Private Subnet:
      • Name: Private-Subnet-1
      • CIDR: 10.0.2.0/24
      • Availability Zone: us-east-1a

    1.3. Configuring Internet Access

    1. Create an Internet Gateway:
      • Name: MyProject-IGW
      • Attach it to MyProjectVPC
    2. Configure Route Tables:
      • Public Route Table: Add route to the Internet Gateway (0.0.0.0/0)
      • Private Route Table: Keep the default local route only

    Explanation

    This step establishes the core network architecture within AWS. A Virtual Private Cloud (VPC) with a CIDR block of 10.0.0.0/16 creates a private cloud network in the AWS environment. The network is divided into two subnets:

    • Public Subnet: Designed for resources requiring internet access (CIDR: 10.0.1.0/24)
    • Private Subnet: Reserved for internal resources that don’t need direct internet access (CIDR: 10.0.2.0/24)

    An Internet Gateway (IGW) is linked to the VPC, facilitating internet communication for resources in the public subnet. This setup follows AWS best practices for secure and efficient network segmentation.

    Step 2: EC2 Instance Deployment

    2.1. Launching an EC2 Instance

    1. Navigate to EC2 Dashboard → Click “Launch Instance”
    2. Configure the instance as follows:
      • Name: MyProjectServer
      • AMI: Amazon Linux 2023
      • Instance Type: t2.micro
      • Network: MyProjectVPC
      • Subnet: Public-Subnet-1

    2.2. Configuring Security

    1. Create a Security Group:
      • Name: MyProject-SG
      • Inbound Rules:
        • Allow SSH (Port 22) from your IP
        • Allow HTTPS (Port 443) if needed
      • Outbound Rules:
        • Allow all traffic

    2.3. Creating and Configuring Key Pair

    1. Generate a New Key Pair:
      • Name: MyProjectKey
      • Type: RSA
      • Format: .pem
    2. Download and Secure the Key:
      • Save the .pem file securely
      • Set permissions: 
        chmod 400 MyProjectKey.pem

    Explanation

    This step involves deploying a virtual machine (Amazon EC2 instance) within the public subnet of the VPC. A t2.micro instance using Amazon Linux 2023 is launched with defined networking and security settings. A security group functions as a firewall, allowing inbound access through SSH (port 22) and HTTPS (port 443).

    A secure login mechanism is created using an RSA key pair stored locally for SSH authentication. This approach follows industry-standard security measures for cloud-based infrastructure.

    Step 3: Static IP and Access Setup

    3.1. Configuring Static IP

    1. Navigate to EC2 → Elastic IPs
    2. Allocate Elastic IP
    3. Associate the Elastic IP with MyProjectServer

    3.2. Configuring Access

    1. Connect to the Instance via SSH: 
      ssh -i "MyProjectKey.pem" ec2-user@<elastic-ip>
    2. Verify Connectivity:
      • Ping a public IP: 
        ping 8.8.8.8
      • Confirm public IP visibility: 
        curl http://checkip.amazonaws.com

    Explanation

    In this step, a static IP (Elastic IP) is assigned to the EC2 instance, ensuring consistent remote access even if the instance restarts. Elastic IP addresses are resilient to connection failures and facilitate stable external access.

    Secure SSH access is established using the key pair created earlier, ensuring encrypted and authenticated communication. Verification commands confirm that the network and firewall configurations are functioning correctly.

    Key elements include:

    • Elastic IP management
    • Secure SSH configuration
    • Network connectivity validation

    AWS Cloud Infrastructure Architecture

    graph TB
    subgraph AWS_Cloud
        subgraph VPC["VPC (10.0.0.0/16)"]
            subgraph Public_Subnet["Public Subnet (10.0.1.0/24)"]
                EC2["EC2 Instancenwith Elastic IP"]
                IGW["Internet Gateway"]
            end
            subgraph Private_Subnet["Private Subnet (10.0.2.0/24)"]
                Future["Reserved fornPrivate Resources"]
            end
        end
    end
    Internet["Internet"]
    Internet <--> IGW
    IGW <--> EC2
    classDef aws fill:#FF9900,stroke:#232F3E,stroke-width:2px;
    classDef subnet fill:#F58536,stroke:#232F3E,stroke-width:2px;
    class VPC,Public_Subnet,Private_Subnet,EC2,IGW aws;

    Diagram Explanation

    The diagram illustrates a cloud infrastructure built on AWS, including:

    • VPC: Network container with a CIDR range of 10.0.0.0/16
    • Public Subnet: Connected to the internet via an Internet Gateway, hosting the EC2 instance
    • Private Subnet: Isolated for internal resources
    • Internet Gateway: Provides internet access to the public subnet
    • EC2 Instance: Configured with an Elastic IP for stable connectivity

    The bidirectional arrows represent secure communication between components, reflecting AWS’s secure architecture and connectivity model. The use of AWS’s official color palette maintains consistency with the platform’s design language.

     

Leave an answer

Browse

By answering, you agree to the Terms of Service and Privacy Policy.