Availability and reliability
Monitor systems, define what “working” means (SLAs and SLOs) and act before users notice.
cloud operations
A quick guide to the basic concepts and what is usually expected from the people who run a company’s cloud.
A Cloud Operations team keeps the services running in the cloud (AWS, Azure and the like): reachable, fast, secure and not costing more than necessary. If developers build the products, Cloud Operations makes sure there is a solid home for them to live in, day and night.
The line between Cloud Operations, DevOps and SRE is blurry and changes from company to company. More than labels, what matters is the idea: the people who build and the people who run work together, automate as much as possible and learn from incidents.
Responsibilities change from team to team, but these are the ones I find almost everywhere.
Monitor systems, define what “working” means (SLAs and SLOs) and act before users notice.
Respond to production problems in an orderly way, even at night, and learn from each incident.
Manage access and permissions, updates, vulnerabilities and secure configurations, together with the security team.
Understand where the cloud money goes, switch off what is not needed and size resources properly.
Describe infrastructure as code (for example with Terraform) and automate repetitive tasks, to reduce errors and time.
Get changes into production safely, with CI/CD pipelines and a clear change process.
Know how to restore services after a serious failure, and check that it really works.
Move and renew applications and data between environments and providers, with as little risk as possible.
Forecast growth, scale at the right time and find bottlenecks.
Help developers use the platform well and leave runbooks and guides anyone can follow.
This is an introductory guide, written the way I understood things while working in the field. Every company organizes itself differently: take it as a starting point, not as a manual.