0% found this document useful (0 votes)
19 views44 pages

Cloud Computing Trends and AWS Insights

The document provides an overview of cloud computing and Amazon Web Services (AWS). It discusses key cloud concepts like deployment models, service models, and characteristics of cloud computing. It then describes AWS in more detail, covering AWS global infrastructure including regions, availability zones, and edge locations. The document also discusses core AWS services like Identity and Access Management (IAM), EC2, S3, and networking. IAM controls user access and permissions, while EC2, S3, and networking provide fundamental cloud infrastructure and storage capabilities.

Uploaded by

Tanya Kaushi
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
19 views44 pages

Cloud Computing Trends and AWS Insights

The document provides an overview of cloud computing and Amazon Web Services (AWS). It discusses key cloud concepts like deployment models, service models, and characteristics of cloud computing. It then describes AWS in more detail, covering AWS global infrastructure including regions, availability zones, and edge locations. The document also discusses core AWS services like Identity and Access Management (IAM), EC2, S3, and networking. IAM controls user access and permissions, while EC2, S3, and networking provide fundamental cloud infrastructure and storage capabilities.

Uploaded by

Tanya Kaushi
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

SE4010 - Current

Trends in Software CLOUD COMPUTING


Engineering
Keshawa Yaddehikandage
About Me
▪ I’m Keshawa Yaddehikanda
▪ Team Lead SysOps at [Link]
▪[Link]/in/keshawa-yaddehikanda-a7b07b14b
Lecture Objective
[Link] Provide an Understanding to Cloud
Computing
2.?
Lecture Content
▪Introduction to Cloud Computing - Week 1
▪ What is Cloud Computing ?
▪ History and Origins
▪ Characteristics of Cloud Computing
▪ CapEX vs OpEx
▪ Vertical Scalability
▪ Horizontal Scalability
▪Types of Cloud Deployment Methods
▪ Private
▪ Hybrid
▪ Public
▪ Types of Cloud Computing Services
▪ SAAS
▪ PAAS
▪ IAAS
Lecture Content Cont.
▪ introduction Amazon Web Services – Week 1
▪ AWS Cloud History
▪ AWS Global Infrastructure
▪ AWS Regions
▪ Choosing an AWS Region
▪ AWS Availability Zones
▪ Edge Locations
▪ Global Services vs Regional Services

▪Identity and Access Management – IAM


▪ Users & Groups
▪ Permissions & Policies
▪ Password Policy & MFA
▪ Access Methods of AWS
Lecture Content Cont.
▪ EC2 – Week 2
▪ EC2 sizing & configuration options
▪ EC2 Instance Storage Section
▪ Security Groups
▪ AMI Overview
▪ Simple Storage Service – S3
▪ S3 Storage Classes
▪ S3 Buckets and Objects
▪ S3 Security
▪ S3 Web Site – Demo
▪ S3 Consistency Model
▪ Networking – VPC - Week 3
▪ Database – RDS Week 3
▪ Costing Management
Introduction CLOUD COMPUTING
What is cloud computing?
• Cloud Computing Is The Delivery of Computing Services
including Servers, Storage, Databases, Networking,
Software, Analytics, and Intelligence over The Internet

• Typically pay only for cloud services you use, helping to


lower the operating costs

• Run the infrastructure more efficiently, and scale as your


business needs change
History and Origins

[Link]
History and Origins

[Link]
Characteristics of Cloud Computing
• Resources Pooling
• On-Demand Self-Service
• Easy Maintenance
• Scalability And Rapid Elasticity
• Economical
• Measured And Reporting Service
• Security
• Automation
• Resiliency And Availability
• Large Network Access
• Work From Any Location
• Multi-Tenancy
• Flexibility
• Service Excellence
• Comfortable Payment Structure
CapX vs Opex (Cloud Compute Context)
CapX vs Opex (Cloud Compute Context) Cont.
CapX OpeX
Up front Cost Significant None
Ongoing Cost Low Based on Usage
Value Over Time Lowers No Change
Early Termination No Anytime
Maintenance Significant Low
Vertical & Horizontal Scalability
• Scalability means that an application / system can handle greater loads by adapting.
• Vertical Scalability - Vertically scalability means increasing the size of the instance
• Horizontal Scalability -Horizontal Scalability means increasing the number of instances / systems for your application
Types of Cloud Deployment Models
• Private Cloud
• Hybrid Cloud
• Public Cloud
Private Cloud
• Private cloud is a type of cloud computing that delivers similar advantages to public cloud,
including scalability and self-service, but through a proprietary architecture.

• A private cloud, also known as internal or corporate cloud, is dedicated to the needs and
goals of a single organization whereas public clouds deliver services to multiple
organizations.
Private Cloud Architecture
Hybrid Cloud
• Hybrid cloud refers to a mixed computing, storage, and services environment made up of on-
premises infrastructure, private cloud services, and a public cloud—such as Amazon Web
Services (AWS) or Microsoft Azure—with orchestration among the various platforms.

• Using a combination of public clouds, on-premises computing, and private clouds in your
data center means that you have a hybrid cloud infrastructure.
Hybrid Cloud Architecture
Public Cloud
• A public cloud is a platform that uses the standard cloud computing model to make resources -- such as
virtual machines, applications or storage -- available to users remotely. Public cloud services may be
free or offered through a variety of subscription or on-demand pricing schemes, including a pay-per-
usage model.
Types of Cloud Computing Services
Introduction AMAZON WEB
SERVICES
AWS Cloud History
AWS Global Reach
• In 2019, AWS had $35.02 billion in annual revenue.
• AWS accounts for 47% of the market in 2019 (Microsoft is
2nd with 22%)
• Pioneer and Leader of the AWS Cloud Market for the 9th
consecutive year
• Over 1,000,000 active users
AWS Global Reach
• In 2019, AWS had $35.02 billion in annual revenue.
• AWS accounts for 47% of the market in 2019 (Microsoft is
2nd with 22%)
• Pioneer and Leader of the AWS Cloud Market for the 9th
consecutive year
• Over 1,000,000 active users
AWS Global Infrastructure
• AWS Regions
• AWS Availability Zones [AWS
Data Centers]
• AWS Edge Locations
AWS Regions
• AWS has Regions all around the
world
• Names can be ap-southeast-1, eu-
west-3
• A region is a cluster of data centers
AWS Availability Zones
• Each region has many availability zones (usually 3, min is
2, max is 6)
• The AZ are named based on their region
• Example: • ap-southeast-2a • ap-southeast-2b

• Each availability zone (AZ) is one or more discrete data


centers with redundant power, networking, and
connectivity

• They’re separate from each other, so that they’re


isolated from disasters • They’re connected with high
bandwidth, ultra-low latency networking
Edge Locations
• Amazon has 216 Points of Presence (205
Edge Locations & 11 Regional Caches) in
84 cities across 42 countries.
• Content is delivered to end users with
lower latency.
Choose an AWS Region
• Compliance with Data Governance and Legal Requirements: data never leaves a
region without your explicit permission.
• Proximity to customers reduced latency.
• Available services within a Region: new services and new features aren’t available
in every Region.
• Pricing: pricing varies region to region and is transparent in the service pricing
page.

• AWS Regional Services ([Link])


AWS Shared Responsibility Model
AWS Console
AWS has Global Services
• Identity and Access Management (IAM)
• Route 53 (DNS service)
• CloudFront (Content Delivery Network)
• WAF (Web Application Firewall)
Most AWS services are Region-scoped
• Amazon EC2 (Infrastructure as a Service)
• Elastic Beanstalk (Platform as a Service)
• Lambda (Function as a Service)
IAM AMAZON WEB
SERVICES
IAM: Users & Groups
• IAM = Identity and Access Management, Global service.

• Root account created by default, shouldn’t be used or shared Users are people within your
organization, and can be grouped.

• Groups only contain users, not other groups.

• Users don’t have to belong to a group, and user can belong to multiple groups.
IAM: Permissions
• Users or Groups can be assigned JSON
documents called policies.

• These policies define the permissions of the


users.

• In AWS you apply the least privilege principle:


don’t give more permissions than a user
needs.
IAM Policies Structure
• Consists of • Version: policy language version, always include “2012 -10
- 17”

• Id: an identifier for the policy (optional)

• Statement: one or more individual statements (required)

• Statements consists of

• Sid: an identifier for the statement (optional)

• Effect: whether the statement allows or denies access (Allow, Deny)

• Principal: account/user/role to which this policy applied to

• Action: list of actions this policy allows or denies.

• Resource: list of resources to which the actions applied to

• Condition: conditions for when this policy is in effect (optional)


IAM Policies Inheritance
IAM – Password Policy
• Strong passwords = higher security for your account
• In AWS, you can setup a password policy:
• Set a minimum password length
• Require specific character types:
• including uppercase letters
• lowercase letters
• Numbers
• non-alphanumeric characters
• Allow all IAM users to change their own passwords
• Require users to change their password after some time (password expiration)
• Prevent password re-use
Multi Factor Authentication - MFA
• Users have access to your account and can possibly change configurations or delete resources I
your AWS account

• You want to protect your Root Accounts and IAM users

• MFA = password you know + security device you own


MFA devices options in AWS
How can users access AWS ?
• To access AWS, you have three options:
• AWS Management Console (protected by password + MFA)
• AWS Command Line Interface (CLI): protected by access keys
• AWS Software Developer Kit (SDK) - for code: protected by access keys
• Access Keys are generated through the AWS Console
• Users manage their own access keys
• Access Keys are secret, just like a password. Don’t share them
• Access Key ID ~= username
• Secret Access Key ~= password
What’s the AWS SDK?
• AWS Software Development Kit (AWS SDK)
• Language-specific APIs (set of libraries)
• Enables you to access and manage AWS services programmatically
• Embedded within your application
• Supports
• SDKs (JavaScript, Python, PHP, .NET, Ruby, Java, Go, [Link], C++) • Mobile SDKs (Android,
iOS, …)
• IoT Device SDKs (Embedded C, Arduino, …) • Example: AWS CLI is built on AWS SDK for Python
IAM Guidelines & Best Practices
• Don’t use the root account except for AWS account setup
• One physical user = One AWS user
• Assign users to groups and assign permissions to groups
• Create a strong password policy
• Use and enforce the use of Multi Factor Authentication (MFA)
• Create and use Roles for giving permissions to AWS services
• Use Access Keys for Programmatic Access (CLI / SDK)
• Audit permissions of your account with the IAM Credentials Report
• Never share IAM users & Access Keys
2 ? AWS Certifications

Common questions

Powered by AI

AWS IAM securely manages access to AWS services by defining users and groups and assigning permissions through policies that adhere to the principle of least privilege. Effective practices include using multi-factor authentication (MFA) for additional security, creating strong password policies, regularly auditing access using the IAM credentials report, and avoiding the use of root accounts for daily tasks. These practices ensure that access is granted appropriately and securely, minimizing potential security breaches .

In a CapEx model, organizations make significant upfront investments in physical infrastructure, which can limit their ability to scale rapidly as business needs change. These costs are fixed and require substantial planning and resource allocation, often leading to underutilized capacity and longer ROI cycles. Conversely, an OpEx model, typical in cloud computing, involves pay-as-you-go pricing, meaning businesses pay only for the resources used. This model allows for better scalability, flexibility, and cost management as it enables organizations to rapidly scale resources up or down based on demand without the burden of significant initial investments .

Compliance with data governance and legal requirements is critical when deploying AWS services across regions as it ensures that data protection laws, such as GDPR or HIPAA, are adhered to. AWS provides options to keep data within certain regions, allowing businesses to control where their data resides and ensuring compliance with local regulations. The choice of region can impact data sovereignty laws and breach penalties, thereby influencing the strategic decisions businesses make regarding their cloud deployment to mitigate legal risks while maximizing service efficiency .

The AWS IAM policy structure supports the principle of least privilege by allowing administrators to define precise permissions through JSON policy documents. These documents include components such as Effect, which decides if the policy is Allow or Deny, Principal, which specifies the user or role affected, Actions, and Resources that detail what permissions apply to which AWS resources. Conditions can further refine these permissions based on criteria like time or IP address. This granularity ensures that users have only the necessary permissions for their specific tasks, minimizing potential security risks .

Vertical scalability involves increasing the size of an instance to improve performance, which can be more costly due to the need for more powerful resources. It is often limited by the capacity of the existing system and may require downtime for upgrades. Horizontal scalability, on the other hand, involves adding more instances of a system to handle increased loads, which can usually be done without service interruption and allows for more flexibility and resiliency. This approach can lead to better load balancing and is generally more cost-effective over time because it leverages distributed resources instead of upgrading individual hardware .

Implementing a hybrid cloud environment poses challenges such as ensuring seamless integration between public and private cloud platforms, maintaining consistent security policies, and managing data compliance across different environments. The integration allows organizations to benefit from the scalability and cost-effectiveness of public clouds for non-sensitive operations while keeping sensitive workloads in private clouds to comply with data governance. The orchestration between these environments helps address data latency issues and ensures that workloads can be dynamically shifted as needed, optimizing both performance and cost efficiencies .

Organizations should consider several factors when choosing an AWS region, including proximity to end users to reduce latency, local compliance and legal requirements ensuring data governance, availability of desired AWS services since not all services may be available in every region, and cost considerations because pricing can vary significantly between regions. These factors combined will influence both the performance and regulatory compliance of their cloud deployments .

Key characteristics of cloud computing that appeal to modern businesses include on-demand self-service, resource pooling, flexibility, and scalability. Cloud services allow businesses to scale resources up or down based on demand without investing in infrastructure. This model also supports cost-efficiency through measured and reporting services with pay-per-use strategy, enhancing overall financial management. Moreover, the cloud ensures resiliency, availability, and a wide network access that foster innovation and adaptability in a rapidly changing market landscape .

Edge locations in AWS are part of a content delivery network (CDN) that caches copies of data closer to the end users. This reduces latency and speeds up the delivery of web content by minimizing the distance data packets have to travel. As a result, users experience faster load times and smoother interaction with services that rely on AWS for distribution, significantly enhancing user satisfaction and performance of applications .

AWS Lambda supports serverless computing by allowing users to run code in response to events without provisioning or managing servers. This model offers several advantages, including reduced overhead in server management, automatic scaling based on demand, and cost savings as users only pay for compute time consumed during code execution. It enables developers to focus on writing code and developing features rather than managing infrastructure, leading to faster deployment and iteration for applications .

You might also like