What is cloud computing?

Cloud computing is like renting IT resources online. It includes things like computing power, storage, and applications. You pay only for what you use, and it's accessible through the internet. You don't have to buy and manage hardware upfront; instead, you get the right resources instantly for your projects, paying only for what you use.

Cloud Computing Models :

There are three main models for cloud computing. Each model represents a different part of the cloud computing stack.

IaaS, or Infrastructure as a Service, in the cloud refers to the provision of essential computing resources, such as networking, virtual or dedicated computers, and storage, offering users flexibility and control without the need for physical hardware management.

PaaS, or Platform as a Service, in the cloud allows users to manage and deploy applications without dealing with hardware intricacies, streamlining the development process.

SaaS, or Software as a Service, in the cloud delivers ready-to-use software managed by a provider, eliminating the need for users to handle maintenance or infrastructure management.

Cloud Computing Deployment Models

Cloud : A cloud-based application is fully deployed in the cloud and all parts of the application run in the cloud.

Hybrid: A hybrid deployment is a way to connect infrastructure and applications between cloud-based resources and existing resources that are not located in the cloud.

On-premises : Setting up resources at your own location, using tools for virtualization and resource management.

Advantages of cloud computing:

• Cloud computing allows flexible payment for computing resources instead of upfront investments.

• Cloud providers achieve cost savings through large-scale operations, translating into lower pay-as-you-go prices.

• Cloud flexibility eliminates the need to guess and allows scaling up or down on demand.

• Cloud computing accelerates IT resource availability, reducing time and cost for experimentation and development.

• Cloud services enable businesses to focus on core projects instead of infrastructure maintenance.

• Deploying applications globally becomes effortless in multiple regions, enhancing customer experience with lower latency and cost.

Some of the Major Public Cloud Providers are :

• Amazon Web Services (AWS)

• Microsoft Azure

• Google Cloud (GCP—formerly Google Cloud Platform)

• IBM Cloud (formerly SoftLayer)

• Oracle Cloud

History of AWS

In 2006, Amazon Web Services (AWS) began offering IT infrastructure services to businesses as web services—now commonly known as cloud computing.

Amazon Web Services provides a wide range of cloud-based products globally, encompassing compute, storage, databases, analytics, networking, mobile, developer tools, management tools, IoT, security, and enterprise applications. These services are available on-demand, accessible within seconds, and come with pay-as-you-go pricing. Covering everything from data warehousing to deployment tools and directories to content delivery, AWS offers over 200 services.

Today, AWS provides a highly reliable, scalable, low-cost infrastructure platform in the cloud that powers hundreds of thousands of businesses in 190+ countries around the world.

AWS is the world’s leading cloud platform. It is used by millions of customers to run various workloads, optimize processes, lower costs, and scale their infrastructure in a matter of minutes.

Now, let's dive into how AWS caters to businesses and customers globally with its cloud services, delving into their operations by first gaining an understanding of their global infrastructure.

Regions

AWS incorporates the idea of a Region, representing a physical location globally where data centers are grouped together. Each set of interconnected data centers is termed an Availability Zone(AZ). A minimum of three isolated and physically distinct AZs forms an AWS Region within a specific geographic area.

Availability Zones

An Availability Zone (AZ) is one or more discrete data centers with redundant power, networking, and connectivity in an AWS Region. All AZs in an AWS Region are interconnected with high-bandwidth, low-latency networking, over fully redundant, dedicated metro fiber providing high-throughput, low-latency networking between AZs. All traffic between AZs is encrypted.

AWS Local Zones

AWS Local Zones are a type of infrastructure deployment that places compute, storage, database, and other select AWS services close to large population and industry centers for low-latency requirements.AWS Local Zones are also connected to the parent region via Amazon’s redundant and very high bandwidth private network, giving applications running in AWS Local Zones fast, secure, and seamless access to the rest of AWS services.

Furthermore, AWS has introduced AWS Dedicated Local Zones, designed exclusively for the use of a specific customer or community. These zones cater to sensitive data and applications requiring execution on physically isolated infrastructure dedicated solely to their exclusive use. The placement of these zones is customized to adhere to a customer-specified regulatory jurisdiction, addressing security and compliance requirements

Wavelength Zones

Wavelength Zones are AWS infrastructure deployments that embed AWS compute and storage services within telecommunications providers data centers at the edge of the 5G network, so application traffic can reach application servers running in Wavelength Zones without leaving the mobile providers network.

Wavelength Zones extend AWS to the 5G edge, delivering a consistent developer experience across multiple 5G networks around the world. AWS Wavelength Zones can be used when you need to deploy high-performance applications accessed by mobile end-users and devices requiring ultra-low-latency.

Wavelength Zones are available in co-operation with Verizon in the United States, KDDI in Japan, SK Telecom in South Korea, Vodafone in UK and Germany, and Bell in Canada.

AWS Outposts

AWS Outposts solution is designed for workloads that must remain on-premises due to latency requirements, with customers wanting these workloads to seamlessly run alongside their other AWS workloads. These fully managed compute and storage racks, built with AWS-designed hardware, enable on-premises operations while connecting seamlessly to AWS's cloud services.

Outposts solutions support various form factors, from 1U and 2U Outposts servers to 42U Outposts racks and multiple rack deployments.

AWS Edge Locations

Edge Locations are AWS sites deployed in major cities and highly populated areas across the globe, far outnumbering the available availability zones. While Edge Locations are not utilized for deploying main infrastructures like EC2 instances, EBS storage, VPCs,Databases but they serve a critical role for AWS services like AWS CloudFront and AWS Lambda@Edge. These locations act as a global Content Delivery Network (CDN), caching data to reduce latency for end-user access. Consequently, Edge Locations are primarily used by end users accessing and utilizing your services.

AWS Regional Edge Caches

Regional Edge Caches sit between your CloudFront Origin servers and the Edge Locations. A Regional Edge Cache has a larger cache-width than each of the individual Edge Locations. Since data expires from the cache at the Edge Locations, it is retained at the Regional Edge Caches. Consequently, when data is requested at an Edge Location but is no longer available, the Edge Location can retrieve the cached data from the Regional Edge Cache instead of the Origin servers, which would result in higher latency.

The following diagram illustrates how requests and responses flow through CloudFront edge locations and regional edge caches.

We have covered the basics of the AWS global infrastructure and its architecture. Now, let's delve into the process of accessing this infrastructure.

Accessing AWS services

Access and manage Amazon Web Services through the AWS Management Console, AWS Command Line Interface (AWS CLI), or the Software Development Kits (SDKs).

• Utilize the AWS Management Console, an intuitive user interface, to access and manage Amazon Web Services. Additionally, the AWS Management Console Application provides a convenient way to view resources while on the move.

• Employ the AWS Command Line Interface (AWS CLI), a unified tool that allows you to manage multiple AWS services through the command line. Download and configure it once to control and automate various AWS services using scripts.

• Simplify integration of AWS services into your applications using Software Development Kits (SDKs). These SDKs provide an Application Programming Interface (API) tailored to your programming language or platform.

Conclusion

AWS provides building blocks that you can quickly assemble to support virtually any workload. With AWS, you'll discover a comprehensive set of highly available services designed to seamlessly work together for building sophisticated, scalable applications.

You gain access to highly durable storage, low-cost compute, high-performance databases, management tools, and more. All of these resources are available without upfront costs, and you only pay for what you use. These services empower organizations to accelerate their pace, reduce IT costs, and scale efficiently.

AWS is trusted by both large enterprises and dynamic start-ups to power a wide array of workloads, including web and mobile applications, game development, data processing and warehousing, storage, archive, and various others.

In the forthcoming Day-2 article, we will explore:

1. The AWS Compute Module

2. Step-by-step instructions for creating a free AWS account.

3. A practical, hands-on sample project to reinforce your understanding.

---------------------------> The End <---------------------------

Thank you for reading! If you're interested in getting notifications for my future articles, please follow me.

Disclaimer: Some of the content of this article is based on information obtained from AWS (Amazon Web Services) documentation and materials. All copyrights, trademarks, and intellectual property rights related to AWS belong to Amazon.com, Inc. or its affiliates. This article is not an official publication of AWS, and the views and opinions expressed herein are solely those of the author, not AWS. The author does not claim any endorsement or affiliation with AWS. Readers are encouraged to refer to the official AWS documentation for complete and up-to-date information.

With AWS DMS, you can perform homogeneous migrations within the same database platform or heterogeneous migrations across different platforms. It also allows you to migrate from self-managed databases to fully managed AWS databases of the same engine.

Additionally, AWS DMS offers Schema Conversion capabilities, automatically assessing and converting source schemas to a new target engine. Alternatively, you can use the AWS Schema Conversion Tool (AWS SCT) on your local PC to convert source schemas.

In this article, we will discuss database migration using a source MySQL database to a target Amazon RDS for MySQL database with the help of the AWS Database Migration Service.

You can use these two main approaches for migrating a self-managed MySQL database to an Amazon RDS for MySQL or Amazon Aurora MySQL database.

• Use a native or third-party database migration tool such as mysqldump to perform the full load and MySQL replication to perform ongoing replication. Typically this is the simplest option.

• Use a managed migration service such as the AWS Database Migration Service (AWS DMS). AWS DMS provides migration-specific services such as data validation that are not available in the native or third-party tools.

The following diagram displays these two approaches.

You can use a hybrid strategy that combines native or third-party tools for full load and AWS DMS for ongoing replication. The following diagram displays the hybrid migration approach.

The following diagram illustrates the AWS DMS replication process.

Which AWS DMS features are free?

The AWS DMS Free Tier includes up to 750 hours per month for a Single-AZ dms.t2.micro instance. Depending on the feature, there is a cost based on usage. For Fleet Advisor and Schema Conversion, you only pay for the storage used. For DMS migration options, whether using replication instances or serverless options, you pay for what you use by the hour. See AWS DMS pricing for more details.

AWS Database Migration Service: Key Benefits

• Simple to use: No installations or source database changes required; initiate migration with a few clicks.

• Minimal downtime: Source database remains operational during migration, with continuous replication to the target.

• Cost-effective: Pay only for compute resources used and additional log storage; affordable for large-scale migrations.

• Reliable: Highly resilient and self-healing service, automatically resumes migration after interruptions.

• Ongoing replication: Supports one-time migration and continuous replication tasks with minimal latency.

• Developer productivity: Enables migration for development purposes, both into and out of the cloud.

• Database consolidation: Consolidate multiple source databases into a single target database, regardless of location or platform.

AWS DMS Fleet Advisor

AWS DMS Fleet Advisor is a free, fully managed capability of AWS Database Migration Service (AWS DMS). It automates migration planning and helps you migrate database and analytics fleets to the cloud at scale with minimal effort. To accelerate migrations, AWS DMS Fleet Advisor automatically inventories and assesses your on-premises database and analytics server fleet and identifies potential migration paths.

The following diagram illustrates the AWS DMS Fleet Advisor Target Recommendations process.

• DMS Fleet Advisor collects metadata and performance metrics from multiple database environments.

• It provides insight into your data infrastructure without needing to install it on every computer.

• Supported database servers include Microsoft SQL Server, MySQL, Oracle, and PostgreSQL.

• Build an inventory of database servers based on data discovered from the network.

• Analyze the feasibility of database migrations using collected information about servers, databases, and schemas.

• DMS Fleet Advisor generates right-sized target recommendations for databases intended to migrate to AWS.

• Recommendations consider metrics from data collectors and preferred settings.

• Detailed information for each target database configuration is available for review.

• Target Recommendations assist database engineers and administrators in planning on-premises database migrations to AWS.

• For the list of supported source databases, see Sources for DMS Fleet Advisor.

• For the list of databases that DMS Fleet Advisor uses to generate target recommendations, see Targets for DMS Fleet Advisor.

High level steps of implementation of AWS Database migration service and some of the screen grabs from my AWS console.

1. Connect the source database server and review the database.

2. Create a new managed database using AWS RDS.

   

   

3. Create Replication instance

   

   

   

4. Configure Source database.

   a. Configure the database to run the DMS Replication Task with Change Data Capture (CDC).

   More About CDC @ https://aws.amazon.com/blogs/database/aws-dms-now-supports-native-cdc-support/ .

   b. Provide additional privileges to database user.

   cd ~ mysql -u root -p<PASSWD>

   GRANT REPLICATION CLIENT ON . to 'wordpress-user'; GRANT REPLICATION SLAVE ON . to 'wordpress-user'; GRANT SUPER ON . to 'wordpress-user'; exit

   

   c. Ensure BINARY LOGGING STATUS was ON.

   cd ~

   mysql -u root -p<PASSWD>

   select variable_value as "BINARY LOGGING STATUS (log-bin) :: " from performance_schema.global_variables where variable_name='log_bin';

   select variable_value as "BINARY LOG FORMAT (binlog_format) :: " from performance_schema.global_variables where variable_name='binlog_format';

   exit

   

5. Create Source and Target endpoints.

   a. Source End Point:

   

   

   

   b. Target End point:

   

   

   

6. Create and Run a Replication Task.

   

   

   

7. Validate the target database "targetrdsdatabase".

We have successfully completed the database migration from source MySQL database to target AMAZON RDS for MySQL database and validated the migrated database.

To learn more about the AWS Database Migration Service, please follow the AWS documentation.

AWS Documentation Links:

How AWS Database Migration Service works -> https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Introduction.html

Database Migration Step-by-Step Walkthroughs -> https://docs.aws.amazon.com/dms/latest/sbs/dms-sbs-welcome.html

Automating database migration and refreshing activities with AWS DMS

https://aws.amazon.com/blogs/database/automating-database-migration-and-refreshing-activities-with-aws-dms/

If you are planning to migrate your existing databases to AWS, seeking assistance from AWS and its partners can greatly simplify the process. AWS offers a comprehensive suite of migration services and tools to facilitate a seamless transition, while its extensive partner network brings specialized expertise and experience in database migration. By leveraging the combined resources and knowledge of AWS and its partners, you can ensure a successful and efficient migration of your databases to the AWS platform.

Thank you for reading! If you're interested in getting notifications for my future articles, please follow me.

Disclaimer: The content of this article is based on information obtained from AWS (Amazon Web Services) documentation and materials. All copyrights, trademarks, and intellectual property rights related to AWS belong to Amazon.com, Inc. or its affiliates. This article is not an official publication of AWS, and the views and opinions expressed herein are solely those of the author, not AWS. The author does not claim any endorsement or affiliation with AWS. Readers are encouraged to refer to the official AWS documentation for complete and up-to-date information.