Shared Responsibility Model
Definition
Shared Responsibility Model
The shared responsibility model defines the division of security and compliance responsibilities between a cloud provider and its customers. AWS secures the infrastructure (hardware, networking, facilities). The customer secures what runs on it (data, access, configuration).
In detail
The line between provider and customer responsibility sits exactly where most teams are weakest: patch management, IAM lifecycle, guardrail enforcement, and cost anomaly detection. These tasks cause incidents when neglected.
For Kubernetes on EKS, the model adds another layer: AWS manages the control plane, but the customer is responsible for node patching, network policies, pod security, and runtime monitoring.
How Tallence helps
Tallence covers the customer side of the shared responsibility model through managed cloud foundation and container operations services.
Learn more about Managed Cloud InfrastructureRelated terms
Cloud Security
The practices, tools, and controls that protect cloud environments from threats, misconfigurations, and compliance violations.
Cloud Foundation
A managed AWS landing zone service covering governance, drift detection, FinOps, and 24/7 incident response as an ongoing operational engagement.
Container Operations
Managed Kubernetes operations covering node patching, container security, 24/7 monitoring, and compliance reporting across AWS EKS, hybrid, and on-premises clusters.
Explore more terms
All glossary terms→FinOps
An operating framework that connects technology, finance, and business teams to manage cloud spending with accountability and transparency.
Site Reliability Engineering (SRE)
An engineering discipline that applies software practices to IT operations, using SLOs and error budgets to balance reliability with delivery speed.
Hybrid Cloud
A composition of two or more cloud environments (private, community, or public) connected by technology that enables data and application portability.
Private Cloud
A dedicated IT environment used exclusively by one organisation, providing maximum control over data, network, and configuration.
DevOps
An engineering practice that aligns development and operations teams around shared goals, automated pipelines, and a culture of continuous delivery.
Microservices
An architecture pattern where applications are decomposed into independently deployable services, each owning its domain, data, and deployment lifecycle.