VIDEO
HIGHLIGHT
Log InSign up
AWS vs Azure | Microsoft Azure and Amazon AWS Differences | AWS Training | Edureka
SummaryTranscriptChat

AWS vs Azure | Microsoft Azure and Amazon AWS Differences | AWS Training | Edureka

AWS vs Microsoft Azure: A Comparative Analysis

Introduction to Cloud Providers

  • The session is led by Hmon from Ed Raa, focusing on a comparison between AWS and Microsoft Azure.
  • The agenda includes discussing various cloud providers, comparing AWS and Azure, job trends related to these platforms, and concluding which provider is superior.

Overview of Major Cloud Players

  • Key players in the cloud market include Rackspace, Digital Ocean, IBM Cloud, Microsoft Azure, Google Cloud Platform, VMware, and AWS.
  • AWS leads the market with a 31% share compared to Microsoft's 11%, highlighting a significant gap between the two.

Historical Context of AWS and Azure

  • AWS was launched in 2006 as the first major player in cloud computing; this early entry contributed to its current dominance.
  • Microsoft Azure followed four years later in 2010. The delay allowed AWS to establish itself significantly ahead of competitors.

Service Offerings Comparison

Compute Services

  • Both providers offer similar services due to AWS's established success; for example:
  • EC2 (AWS): Provides raw servers that can be configured for various uses.
  • Virtual Machine (Azure): Mirrors EC2's functionality but under a different name.

Platform as a Service (PaaS)

  • Elastic Beanstalk (AWS): Allows users to upload code without managing servers.
  • App Service (Azure): Similar concept as Elastic Beanstalk for deploying applications easily.

Serverless Computing

  • AWS Lambda: Focuses on serverless computing for background tasks where users upload code without managing servers.
  • Functions (Azure): Corresponding service that operates similarly to AWS Lambda.

Instance Configuration Comparison

  • An M3 large instance on AWS offers 8GB RAM and 32GB storage; comparable configurations exist within Azure’s offerings.

Comparison of AWS and Azure Services

Instance Types and RAM vs. Storage

  • AWS offers instances with 7 GB of RAM and 100 GB of storage, while Azure provides more RAM but less storage in similar instance classes.
  • Both AWS and Azure offer comparable services; choosing between them often depends on whether you prioritize RAM or storage.

Storage Domain Overview

  • AWS's Simple Storage Service (S3) is an object-based file system for storing various file types, similar to Azure's Blob Storage.
  • AWS SQS (Simple Queue Service) functions as a task buffer, allowing independent servers to queue tasks, akin to Azure's Q Storage service.

Backup Solutions

  • For disaster recovery, if using SQS in AWS, one would use Q Storage in Azure for similar functionality under a different name.
  • AWS Glacier serves as a backup service for infrequently accessed data at lower costs compared to SSD storage.

Database Services Comparison

  • AWS RDS (Relational Database Service) supports multiple database types like MySQL and Oracle with automatic management features.
  • In contrast, Microsoft Azure only offers SQL databases without the flexibility of choosing other database types.

Data Warehousing and Non-relational Databases

  • Redshift from AWS is used for data analytics; Microsoft has a similar offering called SQL Data Warehouse.
  • DynamoDB is a managed non-relational database service from AWS, while Microsoft's equivalent is Document DB.

Pricing Models

  • Both cloud providers offer discounts for reserved instances; however, Microsoft uses Enterprise Agreements for this purpose.
  • Pricing structures differ: AWS charges by the hour while Azure charges by the minute, which can be beneficial for short-term usage scenarios.

AWS vs. Microsoft Azure: A Comparative Analysis

Pricing and Cost Efficiency

  • AWS infrastructure remains operational as long as the company exists, making it a reliable choice for businesses.
  • When comparing billing models, AWS is generally cheaper than Microsoft Azure when converting minutes to hours, especially for instances that are not running continuously.

Troubleshooting and Monitoring Tools

  • AWS offers CloudTrail, a logging service that records API calls made by applications deployed on its platform, aiding in troubleshooting failures.
  • Microsoft Azure provides a similar service called Azure Operational Insights for logging purposes.

Monitoring Services

  • AWS's CloudWatch serves as a cloud monitoring tool to track instance traffic and performance metrics.
  • Azure has an equivalent service known as Azure Application Insights for monitoring application performance.

Service Offerings and Market Position

  • AWS currently offers more services than Microsoft Azure; however, Azure has shown significant growth since its later launch.
  • As both platforms evolve, competition may lead to innovative services from either provider that could shift market dynamics.

Uptime Comparison

  • In 2016, AWS experienced only 108 minutes of downtime compared to Microsoft's 270 minutes due to various factors including infrastructure maturity.
  • AWS operates with six times the server capacity of all competitors combined, contributing to its lower downtime rates.

Infrastructure Maturity

  • The number of global regions (16 for AWS vs. over 30 for Azure) impacts downtime probabilities; more regions can lead to increased potential outages.
  • AWS's longer presence in the market allows it to have developed better mitigation strategies against outages compared to the newer Microsoft Azure.

Conclusion on User Preference

  • Due to its extensive experience and reliability demonstrated through minimal downtime, customers often prefer deploying applications on AWS over Microsoft Azure.

Comparison of AWS and Microsoft Azure Dashboards

Overview of Dashboards

  • The speaker describes the visual differences between AWS and Microsoft Azure dashboards, noting that AWS has a white-blue theme while Azure features a premium black design.
  • A live demonstration is provided, showcasing the AWS dashboard where all services are listed for easy access and deployment.
  • The Azure dashboard is compared, highlighting its similar functionality in launching services like virtual machines.

Job Trends in Cloud Computing

  • Discussion shifts to job trends, indicating that AWS is currently more widely adopted than Azure in the cloud computing market.
  • There are significantly more job postings for AWS Solutions Architects compared to those for Azure Solutions Architects, suggesting better career opportunities with AWS.
  • Despite fewer job postings, Azure shows potential for growth; its downtime has decreased over the years, indicating improvements in service reliability.

Future Outlook on Cloud Providers

  • While AWS leads now, there’s speculation that Azure could surpass it within three to four years due to its rapid growth rate.
  • The speaker emphasizes learning both platforms; companies often use multiple providers for redundancy—AWS as primary and Azure as backup.

Evaluating Cloud Provider Choices

  • Choosing between AWS and Azure depends on specific business needs; migrating from one provider to another can be costly due to infrastructure differences.
  • Current market share favors AWS because it was an early entrant (2006), establishing trust among users.
  • Migrating applications involves significant costs related to code changes required by different infrastructures.

Conclusion on Market Position

  • Although many companies utilize both platforms, most still rely primarily on AWS due to its established presence and trustworthiness since 2006.
  • The discussion concludes that while current trends favor AWS, it's essential not to overlook Microsoft's growing capabilities in cloud services.

Launching Instances: Practical Demonstration

  • The session transitions into a practical demonstration of launching an EC2 instance in the AWS environment alongside launching a VM (similar to EC2 but in Microsoft Azure).

Launching EC2 Instances in AWS and Azure

Overview of Launching an EC2 Instance in AWS

  • The process begins with accessing the AWS dashboard to launch an EC2 instance, specifically selecting the "EC2" option under the compute section.
  • In the EC2 dashboard, there are currently two running instances. The user selects "launch an instance," opting for an Ubuntu AMI (Amazon Machine Image), specifically a t2.micro instance.
  • Configuration details are left at default settings, and a new key pair is created and downloaded for secure access to the instance.
  • After launching, three instances are visible on the dashboard, confirming that a new instance is being initialized.

Key Differences Between AWS and Azure Instance Launching

  • When comparing AWS to Microsoft Azure, it's noted that Azure refers to this service as a VM (Virtual Machine).
  • In Azure, users have options for authentication: they can choose between using a password or creating their own key pair. Unlike AWS, where a key pair is automatically allocated.

Connecting to Instances in Microsoft Azure

  • For connecting via SSH in Azure, users must create their own RSA key using PuTTYgen. This involves generating a public/private key pair which will be used for secure connections.
  • Users need to upload the private key when connecting through PuTTY software since Ubuntu requires SSH connections without GUI support.

Steps to Launch an Instance in Microsoft Azure

  • To launch an Ubuntu server in Azure, users navigate through similar steps by clicking on "compute" and selecting "Ubuntu."
  • Basic configurations include naming the instance and setting volume types; unlike AWS, users must specify usernames during setup.

Finalizing Instance Creation in Azure

  • Users can opt for either password authentication or SSH public keys; if choosing public keys, they must generate them using PuTTYgen before pasting into the configuration interface.
  • Subscription options vary based on account type; free trials are available for new accounts while existing accounts may incur charges based on usage.

Review and Connection Process

  • After reviewing configurations including resource groups and locations (e.g., South India), users finalize by creating their instances which may take some time.
  • Once created, users save their private keys securely as they will need these files along with public IP addresses for future connections via PuTTY software.

This structured overview provides insights into launching instances across both platforms while highlighting critical differences in processes and requirements.

Accessing AWS and Azure Instances via PuTTY

Connecting to an AWS Instance

  • The process begins by pasting the IP address of the AWS instance into PuTTY. Users must navigate to SSH settings and select authentication, where they will be prompted for a private key.
  • Since AWS generates a private key in PEM format, it needs conversion to PPK format for use with PuTTY. This is done using the PuTTYgen tool, where users load their PEM file and save it as a PPK file.
  • After saving the PPK file, users return to the main PuTTY interface, paste the IP address again, and go through SSH settings to browse for their newly created PPK file.
  • Upon selecting the PPK file, users are prompted for a username. For Ubuntu instances on AWS, the default username is "ubuntu." Entering this allows authentication with the public key.
  • Successful entry grants access to the Ubuntu instance on AWS. The session can then be exited before moving on to accessing an Azure machine.

Connecting to an Azure Instance

  • Transitioning from AWS to Azure involves copying the IP address of the Azure instance and launching PuTTY again. The same steps apply as with AWS.
  • Unlike AWS, users have already created a PPK file when setting up their Azure instance. They select this existing key during authentication in PuTTY.
  • In contrast to AWS's default username "ubuntu," users must enter their chosen username (e.g., "zer-hyphen-2") when connecting to an Azure VM.
  • Key differences between accessing machines in both environments include:
  • Default usernames differ (AWS uses "ubuntu" while Azure allows user-defined names).
  • Key management varies; AWS provides keys automatically whereas Azure requires manual creation and upload of keys.

Conclusion and Next Steps

  • The session concludes with encouragement for participants to practice independently what they've learned about connecting via SSH using PuTTY on both platforms.
  • Assignments related to this session have been uploaded for review; participants are expected to submit them in future sessions for feedback.
  • Support options are available 24/7 for any queries that arise post-session; personal contact information is provided for further assistance if needed.
Video description

** Cloud Architect Masters Program : https://www.edureka.co/masters-program/cloud-architect-training ** This AWS vs Azure video tutorial shall discuss the differences between AWS and Azure. It can be helpful for people who are trying to migrate to and from AWS and Azure. Towards the end, we will be launching instances in both AWS and Azure environment. This video is ideal for those who want to become the master of all trades in the cloud computing world! For doubts & queries on AWS/Azure, post the same on Edureka Community: https://www.edureka.co/community/cloud-computing In this AWS vs Azure Training video you will understand: 0:50 Cloud Providers 1:18 AWS vs Azure 20:17 Job Trends 22:33 Who wins? 24:50 Demo Facebook: https://www.facebook.com/edurekaIN/ Twitter: https://twitter.com/edurekain LinkedIn: https://www.linkedin.com/company/edureka #awsvsazure #awscertification #awstraining #awssolutionsarchitect How it Works? 1. This is a 5 Week Instructor led Online Course. 2. Course consists of 30 hours of online classes, 30 hours of assignment, 20 hours of project 3. We have a 24x7 One-on-One LIVE Technical Support to help you with any problems you might face or any clarifications you may require during the course. 4. You will get Lifetime Access to the recordings in the LMS. 5. At the end of the training you will have to complete the project based on which we will provide you a Verifiable Certificate! - - - - - - - - - - - - - - About the Course AWS Architect Certification Training from Edureka is designed to provide in depth knowledge about Amazon AWS architectural principles and its components. The sessions will be conducted by Industry practitioners who will train you to leverage AWS services to make the AWS cloud infrastructure scalable, reliable, and highly available. This course is completely aligned to AWS Architect Certification - Associate Level exam conducted by Amazon Web Services. During this AWS Architect Online training, you'll learn: 1. AWS Architecture and different models of Cloud Computing 2. Compute Services: Amazon EC2, Auto Scaling and Load Balancing, AWS Lambda, Elastic Beanstalk 3. Amazon Storage Services : EBS, S3 AWS, Glacier, CloudFront, Snowball, Storage Gateway 4. Database Services: RDS, DynamoDB, ElastiCache, RedShift 5. Security and Identity Services: IAM, KMS 6. Networking Services: Amazon VPC, Route 53, Direct Connect 7. Management Tools: CloudTrail, CloudWatch, CloudFormation, OpsWorks, Trusty Advisor 8. Application Services: SES, SNS, SQS Course Objectives On completion of the AWS Architect Certification training, learner will be able to: 1. Design and deploy scalable, highly available, and fault tolerant systems on AWS 2. Understand lift and shift of an existing on-premises application to AWS 3. Ingress and egress of data to and from AWS 4. Identifying appropriate use of AWS architectural best practices 5. Estimating AWS costs and identifying cost control mechanisms Who should go for this course? This course is designed for students and IT professionals who want to pursue a career in Cloud Computing. The course is a best fit for: 1. Professionals interested in managing highly-available and fault-tolerant enterprise and web-scale software deployments. 2. Professionals who want Project Experience in migrating and deploying cloud based solutions. 3. DevOps professionals. Pre-requisites There are no specific prerequisites for this course. Any professional who has an understanding of IT Service Management can join this training. There is no programming knowledge needed and no prior AWS experience required. For more information, Please write back to us at sales@edureka.in or call us at IND: 9606058406 / US: 18338555775 (toll free). Customer Reviews: Joga Rao, Principal Data Architect at AEMO says: “I am a Customer at Edureka. I attended the AWS Architect Certification Training, I found the training to be very informative. The course content was excellent, just what I was after. The trainer was very knowledgeable. I found him to be very patient, he listened and answered everyone's questions. I especially liked the way he repeated and summarized the previous day's leanings at the start of each new day. I also liked his interactive style of training. Edureka demonstrated the highest standard of professionalism in delivering the course content and their support to me in helping complete the project has been exceptional. Thanks Edureka! ”