harshabidrae97 / aws-cloud_quest_cloud_practioner

The approach in each AWS Cloud Quest: Cloud Practitioner assignment focused on teaching the material, then having me apply it so that I’m learning information, not reiterating it. And discovering the game elements — like the quiz questions, challenges, drones, and pets — motivated me to keep coming back to learn more. This was one of the most unique training methods I’ve seen for cloud, and I’m excited to keep learning.

AWS-Quest-Cloud-Practitioner : Solutions Built

Highly Available Web Applications

• Help the travel agency create a highly available web application.
• Created an Application Load Balancer(ALB)
• Configure an Auto Scaling Group and connect it to the ALB.
• Configured a health check endpoint.
• Configured an Auto Scaling Group to include a new EC2 instances in multiple Availability Zones (Az).

AWS Cloud Economics.

• created an estimation of architecture using the AWS Pricing Calculator.
• Change the EC2 instance type to t2.micro and generated new price estimate URL.

Auto healing and Scaling Applications.

• Created an EC2 template from an existing EC2 instance.
• Configured an Auto Scaling Group with minimum of two and maximum of 4 instances.
• Assigned a CPU utilization metric and schedule based on Auto Scaling rules.
• Configured an Auto Scaling policy to scale down to 0 resources at 1 AM UTC every day.

Core Security Concepts.

• Helps to improve security at the city's stock exchange by ensuring that support engineers can only perform authorized actions.
• Created a SupportEngineers group.
• Attached a policy that allows group members to read only access to EC2.
• Verified that group members have read only EC2 Access.
• Granted the support Engineers group read only access to RDS.

Networking Concepts.

• Helps the bank setup a seccure networking environment which allows communications between resources and the inernet.

• Changed the WebServer subnet from private to public.

• Configured a security group to allow HTTP traffic from the internet.

• Configured the Security group rules to allow traffic over port 3306 into DataBase Server.

Migration Concepts.

• 

Tech Mahindra-Telia-1

• The following AWS services and features now host components of Telia’s new CIM microservice architecture:

• AWS VPN establishes a secure and private tunnel from the on-premises data center to the AWS global network.

• Amazon Route 53 is a Domain Name Server (DNS), which routes global traffic to the application using Elastic Load Balancing.

• Amazon Virtual Private Cloud (Amazon VPC) sets up a logically isolated, virtual network where the application can run securely.

• Application Load Balancer is a product of Elastic Load Balancing, which load balances HTTP/HTTPS applications and uses layer 7-specific features, like port and URL prefix routing for containerized applications.

• Amazon Elastic Container Service (Amazon ECS) is a container orchestration service that supports Docker containers to run and scale containerized applications on AWS.

• AWS Fargate is a compute engine for Amazon ECS that allows running containers without having to manage servers or clusters. Microservices are deployed as Docker containers in the Fargate serverless model.

• Amazon Elastic Container Registry (ECR) is integrated with Amazon ECS as a fully managed Docker container registry that makes it easy to store, manage, and deploy Docker container images. This is used as a private repository to host built-in Docker images.

• Amazon Aurora is a relational database compatible with MySQL and PostgreSQL, used as a database for the CIM platform migration.

• AWS DMS migrates on-premises Oracle databases to cloud-native Aurora databases.

• Amazon CloudWatch is a monitoring and management service used to monitor the entire CIM platform and store application logs for analysis.

• Amazon Elastic Compute Cloud (Amazon EC2) provides compute capacity in the cloud, and was used to host Jenkins and JFrog Artifactory as a container for the CI/CD pipeline.

• AWS Identity and Access Management (IAM) manages access to AWS services and resources securely.

Database Migration

The source database was Oracle on-premises and the target database deployed on AWS was Aurora with the PostgreSQL relational database service (RDS) engine. Tech Mahindra used AWS DMS for this heterogeneous database migration, along with automation scripts for accurate and accelerated migration execution to the cloud.

After the data was migrated to Amazon Aurora PostgreSQL with AWS DMS, they used custom PL/SQL scripts to handle the schema changes. They also used Oracle’s advanced queuing to transfer the incremental data load to the target DB.

Telia had over 70 million records of entries in its current system that had to be moved within a short span of time. The Tech Mahindra team migrated those records to AWS through an extensive data migration approach using AWS DMS.

For this migration, some of the key challenges encountered included:

Heterogeneous database migration. Schema changes. Huge volume of data to be migrated in a short time. Case-sensitive nature of Aurora PostgreSQL. The migration approach included moving the necessary data from the existing system, matching the schema of the target DB engine, and cleansing and transforming the target data through automation scripts.