Module 9 Flashcards
(31 cards)
Six core perspectives of the Cloud Adoption Framework
Business Perspective
People Perspective
Governance Perspective
Platform Perspective
Security Perspective
Operations Perspective
Roles in business perspective?
Common roles in the Business Perspective include:
Business managers
Finance managers
Budget owners
Strategy stakeholders
Roles in People?
Common roles in the People Perspective include:
Human resources
Staffing
People managers
Common roles in the Governance Perspective include:
Common roles in the Governance Perspective include:
Chief Information Officer (CIO)
Program managers
Enterprise architects
Business analysts
Portfolio managers
Common roles in the Platform Perspective include:
Common roles in the Platform Perspective include:
Chief Technology Officer (CTO)
IT managers
Solutions architects
Security Perspective
Common roles in the Security Perspective include:
Chief Information Security Officer (CISO)
IT security managers
IT security analysts
Operations Perspective include:
Common roles in the Operations Perspective include:
IT operations managers
IT support managers
Business
that your business strategies and goals align with your IT strategies and goals.
People
supports development of an organization-wide change management strategy for successful cloud adoption.
Governance
focuses on the skills and processes to align IT strategy with business strategy
Platform
includes principles and patterns for implementing new solutions on the cloud, and migrating on-premises workloads to the cloud.
Security
ensures that the organization meets security objectives for visibility, auditability, control, and agility.
operations
helps you to enable, run, use, operate, and recover IT workloads to the level agreed upon with your business stakeholders.
6 strategies for migration
Rehosting
Replatforming
Refactoring/re-architecting
Repurchasing
Retaining
Retiring
rehosting
“lift-and-shift” involves moving applications without changes.
Replatforming
lift, tinker, and shift,” involves making a few cloud optimizations to realize a tangible benefit. Optimization is achieved without changing the core architecture of the application.
Refactoring
reimagining how an application is architected and developed by using cloud-native features. Refactoring is driven by a strong business need to add features, scale, or performance that would otherwise be difficult to achieve in the application’s existing environment.
Repurchasing
involves moving from a traditional license to a software-as-a-service model.
Retaining
consists of keeping applications that are critical for the business in the source environment.
Retiring
Retiring is the process of removing applications that are no longer needed.
aws snow family
physical device that enables to transport up to exabytpes of data in and out of aws
aws snowcone
2 cpu, 4 gb of memory, 8 tb of usable storage
aws snowball storage optimized
Storage: 80 TB of hard disk drive (HDD) capacity for block volumes and Amazon S3 compatible object storage, and 1 TB of SATA solid state drive (SSD) for block volumes.
Compute: 40 vCPUs, and 80 GiB of memory to support Amazon EC2 sbe1 instances (equivalent to C5).
Snowball Edge Compute Optimized
Storage: 42-TB usable HDD capacity for Amazon S3 compatible object storage or Amazon EBS compatible block volumes and 7.68 TB of usable NVMe SSD capacity for Amazon EBS compatible block volumes.
Compute: 52 vCPUs, 208 GiB of memory, and an optional NVIDIA Tesla V100 GPU. Devices run Amazon EC2 sbe-c and sbe-g instances, which are equivalent to C5, M5a, G3, and P3 instances.
