Cloud Computing Concepts

Introduction

In the next few days I am writing about what I learned regarding AWS Academy | Become to AWS Certified Solutions Architect - Associate (SAA-C03). This program is organsized by FGA (Fresh Graduate Academy) by KOMINFO through AWS (Amazon Web Service) partners. I am very happy to be part of this program. Aimed at sharing and as my personal documentation.

Cloud computing introduces a significant shift in how technology is obtained, used, and managed. It also shifts how organizations budget and pay for technology services.

Table of Contents

Introduction
Cloud service models
Cloud computing deployment models
Six core perspectives

Cloud service models

There are three main cloud service models:

IaaS: Infrastructure as a service
Infrastructure as a service are the basic building blocks for your clud information technology and typically provide you with access to networking features, computers, whether it's virtual or dedicated, and provide storage space. IaaS provides you with the highest level of flexibility and control over your IT resource.
It is most similar to you existing implementation that many IT departements and developers are familiar with today.
Example services managed by customer:
PssS: Platform as a service
Platform as a service removes the need for you to manage the underlying infrastructure. Usually this relates to the hardware and OS (operating system). It does it through automation and allows you to focus on the deployment and management of your applications as opposed to the provisioning.
Customer does not need to manage the underlying infrastructure. AWS handles the operating system, database patching, firewal configuration and disaster recovery.
Example services managed by AWS:
SaaS: Software as a service
Software as a service provides you with a complete product that is run and managed by the service provider. In most cases, software as a service refers to end-user applications. You do not have to think about how the service is maintained or how the underlying infrastructure is managed.
Example services managed by AWS:
Software is centrally hosted and you the customer do not need to manage any of the infrastructure that supports the service.

Each model represents a different part of the cloud computing stack and gives you a different level of of control you IT resource. You can check detail about Cloud Service Models AWS.

Cloud computing deployment models

Cloud :
A cloud-based applications is fully deployed in the cloud in the all-in-the-cloud tupe of implementation. All parts of your application will be running in the cloud. Benefits of cloud computing your applications then can be built on low-level Infrastructure pieces, or you can use higher level services that provide abstration from the management, architecting, and scaling requirements of your core infrastructure.
Hybrid :
In a hybrid implementation, the deployment is such a way that to connect your existing infrastructure and application to a cloud-based resource. They're not located in the cloud. They're located in your physical facilities. The most common of this hybrid deployment is between cloud and existing on premises.
On-premises :
Deploying resource on-premises use virtualization and resource management tools, sometimes called private cloud.

Similarities between AWS and traditional IT

Six core perspectives

Focus on business capabilities:

Business
Stakeholders from the business perspective, that includes business managers, finance managers, budget owners, and strategy stakeholders, can use the AWS Cloud Adoption Framework to create a strong business case for cloud adoption and prioritize cloud adoption initiatives.
People
Members within the People Perspective, like Human Resource, staffing, and people ,managers, can use the AWS Cloud Adoption Framework to evaluate the organization's structures and roles, new skills and process requirements, and identify geps in them. Performing an analysis of needs and gaps can help prioritize training, staffing, and organizational changes to build an agile organization.
Governance
Stakeholders from the Governance perspective, for example: the Chief Information Officer or program managers, Enterprise architects, business analysts, and portfolio managers, can actually use the AWS Cloud Adoption Framework to focus on the skills and processes that are needed to align IT strategy and goals with the business. Maximizing the business value of its IT investment and minimize the business risks.

Focus on technical capabilities:

Platform
Stakeholders from the Platform perspective, for example: The Chief Technology Officer, IT managers, and Solutions architect, use a variety of architectural dimensions, and models to understand and communicate the nature of it systems and their relationships.
The AWS Cloud Adoption Framework inclued principles and patterns for implementing new solutions on the cloud or migrating on-premises workload to the cloud.
Security
Chief Information Security Officer, the IT Security managers, and IT Security Analyst, must ensure that the organization meets security objectives for visibility, auditability, control, and agility. Security perspective stakeholders can use the AWS Cloud Adoption Framework to structure the selection and implementation of security controls that meet the organization's needs.
Operations
Stakeholders from the Operations perspective (for example, IT operations managers and IT support managers) define how day-to-day, quarter-to-quarter, and year-to-year business is conducted.