VPC AWS labs step by stepwith screenshot

 

1. Create a VPC

• Navigate to VPC Console: In the AWS Management Console, search for "VPC" and select the service.
• Create VPC: Click "Create VPC".
• Configure VPC:
  • Name: Provide a meaningful name.
  • CIDR block: Choose a suitable CIDR block for your VPC.
• Create VPC:
  Click "Create VPC".

AWS VPC Console showing the creation of a VPC

2. Create Subnets

• Select VPC: Choose the newly created VPC.
• Create Subnet: Click "Create subnet".
• Configure Subnet:
  • Name: Provide a meaningful name.
  • Availability zone: Choose the desired availability zone.
  • CIDR block: Choose a suitable CIDR block for the subnet.
• Create Subnet: Click "Create subnet".

AWS VPC Console showing the creation of a subnet

3. Create an Internet Gateway

• Select VPC: Choose the VPC containing your subnets.
• Create Internet Gateway: Click "Create internet gateway".
• Attach Internet Gateway: Attach the internet gateway to the VPC.

AWS VPC Console showing the creation and attachment of an internet gateway

4. Create a Route Table

• Select VPC: Choose the VPC containing your subnets.
• Create Route Table: Click "Create route table".
• Associate Route Table: Associate the route table with your subnets.

AWS VPC Console showing the creation and association of a route table

5. Create a Route

• Select Route Table: Choose the route table associated with your subnets.
• Create Route: Click "Create route".
• Configure Route:
  • Destination: Specify the destination CIDR block (e.g., 0.0.0.0/0 for all traffic).
  • Target: Choose the internet gateway as the target.
• Create Route: Click "Create route".

AWS VPC Console showing the creation of a route

6. Launch an EC2 Instance

• Navigate to EC2 Console: In the AWS Management Console, search for "EC2" and select the service.
• Launch Instance: Click "Launch instance".
• Choose Instance Type: Choose an appropriate instance type.
• Configure Instance Details: Configure instance details (e.g., key pair, security group).
• Configure Networking: Choose the VPC and subnet created earlier.
• Launch Instance: Click "Launch".

AWS EC2 Console showing the launch of an instance

7. Access the Instance

• Connect to Instance: Use the provided SSH key to connect to the instance.

terminal showing the connection to an EC2 instance

8. Additional Considerations

• CIDR Blocks: Choose suitable CIDR blocks to avoid overlapping.
• Subnet Types: Create public and private subnets based on your requirements.
• Security Groups: Configure security groups to control network access.
• NAT Gateways: Use NAT gateways to allow instances in private subnets to access the internet.

Route 53 labs step by stepwith screenshot

1. Create a Hosted Zone

• Navigate to Route 53 Console: In the AWS Management Console, search for "Route 53" and select the service.
• Create Hosted Zone: Click "Create hosted zone".
• Configure Hosted Zone:
  • Name: Provide a meaningful name for your domain.
  • Comment:
    Add an optional comment.
• Create Hosted Zone: Click "Create".

AWS Route 53 Console showing the creation of a hosted zone

2. Create a Record Set

• Select Hosted Zone: Choose the newly created hosted zone.
• Create Record Set: Click "Create record set".
• Configure Record Set:
  • Type: Choose the record type (e.g., A, CNAME).
  • Name: Specify the record name (e.g., "www").
  • Value: Enter the value for the record (e.g., IP address for A record, domain name for CNAME record).
  • TTL: Set the time to live for the record.
• Create Record Set: Click "Create".

AWS Route 53 Console showing the creation of a record set

3. Use the DNS Name

• Obtain DNS Name: Use the provided DNS name for your hosted zone.
• Configure DNS: Configure your DNS settings to point to the Route 53 DNS name.

DNS configuration using the Route 53 DNS name

4. Additional Considerations

• Record Types: Choose the appropriate record type based on your requirements (e.g., A for IPv4, CNAME for aliases).
• Alias Records: Use alias records to route traffic to other AWS services (e.g., S3, CloudFront).
• Routing Policies: Configure routing policies for complex routing scenarios (e.g., weighted routing, latency-based routing).
• Monitoring: Use Route 53 metrics and health checks to monitor DNS resolution and performance.

AWS Private 5GAWS labs step by step

 

1. Create a VPC with a Private 5G Subnet

• Navigate to VPC Console: In the AWS Management Console, search for "VPC" and select the service.
• Create VPC: Click "Create VPC".
• Configure VPC:
  • Name: Provide a meaningful name.
  • CIDR block: Choose a suitable CIDR block for your VPC.
• Create VPC: Click "Create VPC".
• Create Subnet:
  Create a private subnet within the VPC, specifying the CIDR block range for the Private 5G network.

AWS VPC Console showing the creation of a VPC and subnet

2. Create a Private 5G Network

• Navigate to AWS Private 5G Console: In the AWS Management Console, search for "Private 5G" and select the service.
• Create Network: Click "Create network".
• Configure Network:
  • Name: Provide a meaningful name.
  • VPC: Select the VPC created in step 1.
  • Subnet: Select the private subnet created in step 1.
  • Network configuration: Configure network settings (e.g., IP address range, DNS settings).
• Create Network: Click "Create network".

AWS Private 5G Console showing the creation of a network

3. Create a Private 5G Device

• Select Network: Choose the newly created network.
• Create Device: Click "Create device".
• Configure Device:
  • Name: Provide a meaningful name.
  • Device type: Choose the appropriate device type (e.g., UE, ENB).
  • Configuration: Configure device settings (e.g., IP address, security credentials).
• Create Device: Click "Create device".

AWS Private 5G Console showing the creation of a device

4. Deploy and Configure Private 5G Hardware

• Deploy Hardware: Deploy the physical Private 5G hardware (e.g., UE, ENB) in your on-premises environment.
• Configure Hardware: Configure the hardware to connect to the AWS Private 5G network.

physical Private 5G hardware

5. Test the Network

• Connect Devices: Connect your devices (e.g., smartphones, laptops) to the Private 5G network.
• Test Connectivity: Test network connectivity and performance.

devices connected to the Private 5G network

6. Additional Considerations

• Licensing: Ensure you have the necessary licenses for Private 5G technology.
• Security: Implement appropriate security measures to protect your Private 5G network.
• Integration: Integrate your Private 5G network with other AWS services (e.g., IoT, EC2).
• Monitoring: Monitor network performance and usage.

Global AcceleratorAWS labs step by stepwith screenshot

1. Create a Global Accelerator

• Navigate to Global Accelerator Console: In the AWS Management Console, search for "Global Accelerator" and select the service.
• Create Accelerator: Click "Create accelerator".
• Configure Accelerator:
  • Name: Provide a meaningful name.
  • Enabled: Enable the accelerator.
• Create Accelerator:
  Click "Create accelerator".

AWS Global Accelerator Console showing the creation of an accelerator

2. Create a Listener

• Select Accelerator: Choose the newly created accelerator.
• Create Listener: Click "Create listener".
• Configure Listener:
  • Protocol: Choose the desired protocol (e.g., TCP, UDP).
  • Port: Specify the port.
  • Endpoint group: Create or select an endpoint group.
• Create Listener: Click "Create listener".

AWS Global Accelerator Console showing the creation of a listener

3. Create an Endpoint Group

• Select Accelerator: Choose the accelerator containing the listener.
• Create Endpoint Group: Click "Create endpoint group".
• Configure Endpoint Group:
  • Name: Provide a meaningful name.
  • Endpoint configuration: Configure the endpoint configuration (e.g., endpoint type, address).
• Create Endpoint Group: Click "Create endpoint group".

AWS Global Accelerator Console showing the creation of an endpoint group

4. Use the Global Accelerator

• Obtain Domain Name: Obtain the domain name provided by Global Accelerator.
• Access Your Application: Use the domain name to access your application. Global Accelerator will automatically route traffic to the nearest endpoint.

web browser accessing an application through a Global Accelerator domain name

5. Additional Considerations

• Endpoint Types: Choose the appropriate endpoint type based on your workload (e.g., IP address, instance).
• Health Checks: Configure health checks to ensure only healthy endpoints are used.
• Traffic Distribution: Customize traffic distribution settings as needed.
• Monitoring: Use Global Accelerator metrics to monitor performance and usage.

Direct Connect AWS labs step by stepwith screenshot

 

1. Create a Direct Connect Connection

• Navigate to Direct Connect Console: In the AWS Management Console, search for "Direct Connect" and select the service.
• Create Connection: Click "Create connection".
• Configure Connection:
  • Name: Provide a meaningful name.
  • Location: Choose the desired location for the connection.
  • Connection type:
    Select the desired connection type (e.g., dedicated, hosted).
  • Bandwidth: Choose the desired bandwidth.
  • Location provider: Select your location provider.
• Create Connection: Click "Create connection".

AWS Direct Connect Console showing the creation of a connection
 

2. Establish a Physical Connection

• Work with Location Provider: Coordinate with your location provider to establish a physical connection between your on-premises network and the AWS Direct Connect location.

physical connection between onpremises network and AWS Direct Connect

3. Create a Virtual Interface

• Select Connection: Choose the newly created connection.
• Create Virtual Interface: Click "Create virtual interface".
• Configure Virtual Interface:
  • Name: Provide a meaningful name.
  • Virtual interface type: Choose the desired virtual interface type (e.g., public, private).
  • VPC: Choose the VPC where the virtual interface will be connected.
  • Subnet: Select the subnet within the VPC.
• Create Virtual Interface: Click "Create virtual interface".
 
AWS Direct Connect Console showing the creation of a virtual interface

4. Configure Routing

• Configure On-Premises Router: Configure your on-premises router to route traffic to the Direct Connect connection.
• Configure AWS Router: Configure the AWS router (if applicable) to route traffic to the virtual interface.



onpremises router configuration

5. Test the Connection

• Ping the Virtual Interface: Ping the public IP address of the virtual interface from your on-premises network to verify connectivity.
• Access Resources: Access your AWS resources from your on-premises network to ensure proper communication.

terminal showing the pinging of the virtual interface

6. Additional Considerations

• Connection Types: Choose the appropriate connection type based on your bandwidth requirements and latency sensitivity.
• Location Providers: Select a location provider that meets your specific needs and location requirements.
• Routing: Configure routing properly to ensure seamless communication between your on-premises network and AWS.
• Security: Implement appropriate security measures to protect your Direct Connect connection.

CloudFront AWS labs step by stepwith screensho

 

1. Create a Distribution

• Navigate to CloudFront Console: In the AWS Management Console, search for "CloudFront" and select the service.
• Create Distribution: Click "Create Distribution".
• Configure Origin:
  • Origin domain name: Enter the domain name of your origin (e.g., S3 bucket, EC2 instance).
  • Origin path: Specify the origin path (if applicable).
• Configure Behavior:
  • Default cache behavior: Configure the default cache behavior (e.g., cache TTL, compression, viewer protocol policy).
  • Additional behaviors: Add additional behaviors for specific paths or query strings.
• Create Distribution: Click "Create distribution".

AWS CloudFront Console showing the creation of a distribution

2. Use the Distribution

• Obtain Domain Name: Once the distribution is created, you'll receive a domain name.
• Access Content: Use the domain name to access your content through CloudFront.

web browser accessing content through a CloudFront distribution

3. Configure Additional Settings (Optional)

• Custom SSL Certificate: Configure a custom SSL certificate for your distribution.
• Viewer Policy: Configure the viewer policy to control access to your content.
• Origin Shield: Enable Origin Shield to protect your origin from DDoS attacks.
• Monitoring: Use CloudFront metrics and logs to monitor performance and usage.

AWS CloudFront Console showing the configuration of additional settings

4. Test the Distribution

• Test Content: Access your content through the CloudFront domain name and verify that it's being delivered from the edge locations.
• Check Performance: Use CloudFront metrics to measure performance and latency.

web browser testing content through a CloudFront distribution

5. Additional Considerations

• Origin Types: Choose the appropriate origin type based on your workload (e.g., S3, EC2, Lambda).
• Cache Behavior: Configure cache behavior settings to optimize performance and reduce costs.
• Customizations: Use CloudFront's customization options to tailor the distribution to your specific needs.
• Global Reach: Leverage CloudFront's global network to deliver content to users worldwide.

AWS Cloud Map AWS labs step by step with screenshot

 

1. Create a Service Discovery Namespace

• Navigate to Cloud Map Console: In the AWS Management Console, search for "Cloud Map" and select the service.
• Create Namespace: Click "Create namespace".
• Configure Namespace:
  • Name: Provide a meaningful name.
  • Type: Choose the desired namespace type (e.g., "DNS").
• Create Namespace: Click "Create namespace".

AWS Cloud Map Console showing the creation of a namespace

2. Create a Service

• Select Namespace: Choose the newly created namespace.
• Create Service: Click "Create service".
• Configure Service:
  • Name: Provide a meaningful name.
  • Service type: Choose the desired service type (e.g., "DNS").
  • Discovery type: Choose the discovery type (e.g., "Private").
  • Health check: Configure health check settings (if applicable).
• Create Service: Click "Create service".

AWS Cloud Map Console showing the creation of a service

3. Register Instances with the Service

• Select Service: Choose the newly created service.
• Register Instances: Click "Register instances".
• Configure Instances:
  • Instances: Specify the instances or containers you want to register.
  • Attributes: Add any relevant attributes for the instances.
• Register: Click "Register".

AWS Cloud Map Console showing the registration of instances with a service

4. Use the Service Discovery Name

• Obtain Service Discovery Name: Use the service discovery name provided by Cloud Map.
• Use in Application: Use the service discovery name in your application's configuration or code to discover instances.

application's configuration file or code using the service discovery name

5. Additional Considerations

• Namespace Types: Choose the appropriate namespace type based on your requirements (e.g., HTTP, DNS).
• Service Types: Select the service type that matches your discovery needs (e.g., DNS, HTTP).
• Health Checks: Configure health checks to ensure only healthy instances are registered.
• Attributes: Use attributes to provide additional information about instances.

Amazon Application Recovery ControllerAWS labs step by step Show drafts

 

1. Create an Application Recovery Controller (ARC) Recovery Plan

• Navigate to ARC Console: In the AWS Management Console, search for "Application Recovery Controller" and select the service.
• Create Recovery Plan: Click "Create recovery plan".
• Configure Recovery Plan:
  • Name: Provide a meaningful name.
  • Description: Provide an optional description.
• Create Recovery Plan:
  Click "Create recovery plan".
Opens in a new window aws.amazon.com
AWS Application Recovery Controller Console showing the creation of a recovery plan

2. Add Applications to the Recovery Plan

• Select Recovery Plan: Choose the newly created recovery plan.
• Add Application: Click "Add application".
• Configure Application:
  • Name: Provide a meaningful name.
  • Description: Provide an optional description.
  • Application type: Choose the appropriate application type (e.g., AWS Lambda, AWS ECS).
• Create Application: Click "Create application".
Opens in a new window amlanscloud.com
AWS Application Recovery Controller Console showing the addition of an application to a recovery plan

3. Add Recovery Groups to the Application

• Select Application: Choose the newly created application.
• Add Recovery Group: Click "Add recovery group".
• Configure Recovery Group:
  • Name: Provide a meaningful name.
  • Description: Provide an optional description.
• Create Recovery Group: Click "Create recovery group".
Opens in a new window aws.amazon.com
AWS Application Recovery Controller Console showing the addition of a recovery group to an application

4. Add Recovery Instances to the Recovery Group

• Select Recovery Group: Choose the newly created recovery group.
• Add Recovery Instance: Click "Add recovery instance".
• Configure Recovery Instance:
  • Name: Provide a meaningful name.
  • Description: Provide an optional description.
  • Recovery instance type: Choose the desired recovery instance type.
• Create Recovery Instance: Click "Create recovery instance".
Opens in a new window docs.aws.amazon.com
AWS Application Recovery Controller Console showing the addition of a recovery instance to a recovery group

5. Configure Recovery Settings

• Select Recovery Plan: Choose the recovery plan.
• Configure Recovery Settings:
  • Failover settings: Configure failover settings (e.g., automatic failover, manual failover).
  • Recovery testing: Configure recovery testing settings (e.g., test frequency).
• Save: Click "Save".
Opens in a new window aws.amazon.com
AWS Application Recovery Controller Console showing the configuration of recovery settings

6. Test the Recovery Plan

• Initiate Test: Select the recovery plan and initiate a test.
• Verify Recovery: Verify that the application is successfully recovered to the target environment.
Opens in a new window aws.amazon.com
AWS Application Recovery Controller Console showing the initiation of a test

7. Additional Considerations

• Application Types: Choose the appropriate application type based on your workload (e.g., serverless, containerized).
• Recovery Instance Types: Select recovery instance types that meet the requirements of your application.
• Failover Strategies: Choose the appropriate failover strategy based on your recovery objectives.
• Recovery Testing: Regularly test your recovery plan to ensure it is effective.