Cloud and shared responsibility | AWS Cloud Practitioner: foundational decisions

Understand the concept

Cloud allows capacity to be obtained as needed without buying all hardware in advance. Scalability is the ability to adjust size; elasticity connects adjustments with changing demand. Consumption billing does not guarantee savings: forgotten resources and data transfer can also generate costs.

Apply and decide

Responsibility depends on the service. For EC2, customers still manage the guest operating system and application; in a more managed service, some work shifts to AWS. Data, permissions, and usage decisions still require customer accountability. “Managed” does not mean “no security decisions.”

Workplace application

For a migration project, list tasks that change and tasks that remain: hardware, guest system, code, access, and data. Assign an owner to each. Compare parallel-running costs and the old environment’s retirement date. If usage falls after month-end closure, check whether capacity can also fall. The proposal should explain conditions and responsibilities without promising automatic savings.

IN PRACTICE

A team migrates a VM to EC2. AWS operates the datacenter, but the team still plans guest-system patches and access.

Common pitfalls

Assuming automatic savings or transferring every control to the provider.

Related topics: Identity and least privilege · Regions, zones, and resilience

Take this idea with you

Service choice changes operating tasks; it does not remove responsibility for data and access.

Create account

Reference: AWS overview: security and compliance · CLF-C02