AWS: what still belongs to you?
Infrastructure moves. Responsibility does not disappear.
The job it does
Amazon Web Services provides cloud infrastructure and managed services. The responsibility split depends on the chosen service: the provider operates its part, while the customer retains responsibilities such as data, identity and configuration. This guide concerns the operating boundary, not the whole AWS catalogue.
A concrete example
Synthetic example: a small company hosts a customer portal. Name who can change production, who checks cost and who restores the data. A managed service changes the work; it does not remove the need for owners.
What it does not solve
Moving a workload does not by itself make it resilient or well governed. Availability, recovery and permissions need an explicit design.
The next useful question
Which responsibilities remain with us for this exact service?
Before choosing the tool
- Which responsibilities remain with us for this exact service?
- What recovery objective does the business actually require?
- Who can deploy, approve access and investigate unexpected spend?
What we would verify
Rehearse recovery of a synthetic dataset and test a least-privilege role before moving production. Stop if ownership or recovery evidence is missing.
When a simpler answer may fit
A simpler managed application, existing hosting or a process fix may meet the need without a cloud migration.
Independent, unsponsored education. This is an explanation of a tool and a possible approach, not a claim of delivery experience, certification, endorsement or partnership. Verify the actual product, plan and configuration.
Published .