---
title: "AWS | Skills We Assign For | Azendo"
description: "AWS on an existing estate — cost, permissions and service sprawl, and the Azendo roles assigned for cloud work."
url: "https://azendo.co/skills/aws/"
---

[Skills](https://azendo.co/skills/) Cloud and infrastructure 

# AWS.

Amazon Web Services is the largest cloud platform, offering compute, storage, databases, networking and several hundred managed services. Its breadth is both the reason to choose it and the reason estates on it drift without an owner.

## Where AWS fits on a long engagement.

Most AWS work is not architecture. It is an account that has grown for years: instances nobody can attribute, security groups wider than they should be, and a bill whose largest line is a surprise. The first useful month is usually inventory and attribution rather than building.

Cost and security fail in the same way here — gradually, invisibly, and only in one direction. Both respond to the same fix, which is someone whose job it is to look. Tagging that is actually enforced, budgets with alerts, and permissions reviewed on a cadence are unglamorous and are what separate a healthy account from an expensive one.

## What an assigned team does with AWS.

The first three months on an inherited AWS account are mostly reading. What exists, who owns it, what it costs and what would break if it disappeared — none of which is documented, and all of which becomes cheap to answer once one person has held the account for a year.

Cost and security both improve as a by-product of that familiarity rather than as projects. Where the estate exists mainly to serve analytics, the more useful capacity is frequently [managed data services](https://azendo.co/services/data-engineering/) instead of pure platform work.

## What we use AWS for.

* Understanding the bill Spend attributed to teams and services, so a reduction conversation can be specific rather than a directive to use less.
* Tightening permissions without breaking things Over-broad roles narrowed based on what is actually used, rather than on what someone thinks is used.
* Retiring what nobody owns Resources with no owner identified and removed, which is frequently the fastest saving available.

## How AWS capacity is assigned.

AWS capacity is assigned under [DevOps managed services](https://azendo.co/services/cloud-and-devops/). We work inside your account; we do not resell infrastructure or hold organisation-level credentials.

## Roles we assign AWS for

* [Cloud Engineer Cloud and DevOps](https://azendo.co/services/cloud-and-devops/cloud-engineer/)
* [DevOps Engineer Cloud and DevOps](https://azendo.co/services/cloud-and-devops/devops-engineer/)
* [Full Stack Developer Software development](https://azendo.co/services/software-development/full-stack-developer/)

## Service lines it sits in

* [Cloud and DevOps](https://azendo.co/services/cloud-and-devops/)
* [Software development](https://azendo.co/services/software-development/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in cloud and infrastructure

* [Kubernetes — skill we assign for](https://azendo.co/skills/kubernetes/)
* [Docker — skill we assign for](https://azendo.co/skills/docker/)
* [Terraform — skill we assign for](https://azendo.co/skills/terraform/)
* [Azure — skill we assign for](https://azendo.co/skills/azure/)
* [GCP — skill we assign for](https://azendo.co/skills/gcp/)
* [Terraform modules — skill we assign for](https://azendo.co/skills/terraform-modules/)
* [Pulumi — skill we assign for](https://azendo.co/skills/pulumi/)
* [CloudFormation — skill we assign for](https://azendo.co/skills/cloudformation/)

## Tell us what your roadmap needs AWS for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)