---
title: "RDS | Skills We Assign For | Azendo"
description: "RDS for managed databases — what AWS handles, what it does not, and the Azendo roles assigned for it."
url: "https://azendo.co/skills/rds/"
---

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

# RDS.

RDS is AWS's managed relational database service, running Postgres, MySQL, MariaDB, SQL Server and Oracle. AWS handles provisioning, patching, backups, replication and failover; schema, queries and capacity remain the operator's responsibility.

## Where RDS fits on a long engagement.

RDS removes the operational work most teams are worst at: backups that are actually taken, patches that are actually applied, and failover that actually works. That is a genuine reduction in risk, and it is the main reason to use it over a self-managed instance.

What it does not remove is everything that decides whether the database performs. Schema design, indexing, query efficiency, connection management and instance sizing are all still yours, and a managed database with a bad schema is simply a bad schema that somebody else patches.

## What an assigned team does with RDS.

Connection management is the failure mode teams meet first at scale. Relational databases have a hard connection limit, and application instances that each hold a pool will exhaust it well before the database is otherwise stressed.

Sizing that correctly, and introducing pooling before it becomes an incident, is work assigned under [managed data services](https://azendo.co/services/data-engineering/) where the data layer is the constraint.

## What we use RDS for.

* Backups and failover that are real Automated backups and multi-AZ failover, tested rather than assumed.
* Connection limits planned for Pooling introduced before instance count exhausts the database's capacity.
* Read load separated Replicas for reporting and analytics, so heavy queries do not affect the transactional path.

## How RDS capacity is assigned.

Managed database work sits between platform and data capacity, and is scoped under whichever discipline owns the constraint rather than split between them.

## Roles we assign RDS for

* [Cloud Engineer Cloud and DevOps](https://azendo.co/services/cloud-and-devops/cloud-engineer/)

## Service lines it sits in

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

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

## Related in cloud and infrastructure

* [Terraform — skill we assign for](https://azendo.co/skills/terraform/)
* [AWS — skill we assign for](https://azendo.co/skills/aws/)
* [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/)
* [Crossplane — skill we assign for](https://azendo.co/skills/crossplane/)

## Tell us what your roadmap needs RDS 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/)