Skip to main content

AWS Maintenance

Your AWS account is running – but is anyone looking after it?

We maintain AWS environments for businesses without a dedicated cloud team: EC2 patching, RDS upkeep, snapshot policies, IAM and security group reviews, and regular checks on what you are paying for.

Snapshots dailyCosts reviewed

Business impact

The hidden costs of an unattended AWS account

AWS manages the physical infrastructure. Under its shared responsibility model, the operating systems, access controls, network rules and data protection inside your account remain yours to maintain.

Bills that grow without explanation

Idle instances, unattached EBS volumes, old snapshots, unused Elastic IPs and oversized RDS instances add up month after month.

Exposure through configuration, not code

Publicly readable S3 buckets, security groups open to 0.0.0.0/0 and long-lived access keys are among the most common causes of cloud data exposure.

Recovery that has never been tested

Snapshots exist, but nobody has confirmed that an instance or database can be rebuilt from them within an acceptable time.

Common issues

Problems we regularly solve

EC2 instances never patched

Instances launched from an AMI years ago still run the original package set, with no patching process and no record of what is installed.

Root account used day to day

The AWS root user has access keys, no MFA, or is shared by several people instead of using individual IAM identities.

Security groups open to the world

SSH, RDP or database ports left open to any IP address after a quick troubleshooting session that was never reverted.

RDS approaching end of support

Database engine versions nearing the end of standard support, with AWS scheduling forced upgrades or applying extended support charges.

Snapshot sprawl and gaps

Thousands of manual snapshots on some volumes while critical ones have none, and no lifecycle policy deciding what is kept.

CloudFront and certificate drift

Distributions pointing at retired origins, ACM certificates not attached where expected and cache settings nobody remembers choosing.

What's covered

What's included in AWS maintenance

We work inside your AWS account with scoped IAM access, covering the services small and mid-sized businesses most commonly run.

EC2 and AMIs

Operating system patching via Systems Manager or SSH, instance health checks, right-sizing and keeping AMIs current for rebuilds.

RDS and data stores

Engine version tracking, maintenance windows, automated backup retention, parameter group review and restore testing.

S3 and CloudFront

Block Public Access settings, bucket policies, versioning and lifecycle rules, and CloudFront distribution, origin and TLS configuration.

IAM and account security

Root account protection with MFA, removal of unused users and keys, least-privilege policies and CloudTrail and GuardDuty review.

Networking

Security group and network ACL reviews, VPC layout documentation and removal of rules that expose administrative ports publicly.

Cost hygiene

Budgets and alerts, identification of idle and orphaned resources, snapshot lifecycle policies and Savings Plan or Reserved Instance suitability.

Maintenance activities

What we do, and how often

Exact frequencies depend on your plan and platform. This is a typical schedule.

Continuous

  • CloudWatch alarms for instance, database and load balancer health
  • AWS Budgets alerts for unexpected spend
  • GuardDuty and AWS Health event review

Weekly

  • EC2 operating system patching in maintenance windows
  • Snapshot and backup job verification
  • Review of new IAM users, keys and security group changes

Monthly

  • Cost review covering idle, orphaned and oversized resources
  • RDS restore test to a temporary instance
  • S3 public access and bucket policy check
  • Maintenance report with cost and security findings

Quarterly

  • Well-Architected-style review across security, reliability and cost
  • Engine, runtime and AMI lifecycle review
  • Access review of all IAM principals

Our methodology

How we work

01

Account review

We map every region in use, list resources and owners, and check the account against common security and cost pitfalls.

02

Secure access first

Root MFA, individual IAM identities, scoped roles for our engineers and CloudTrail logging are put in place before routine work.

03

Establish routines

Patch schedules, snapshot lifecycle policies, budgets and alarms are configured and documented.

04

Review and refine

Quarterly reviews in the spirit of the AWS Well-Architected Framework produce a prioritised list of improvements.

Business benefits

What you gain

Spend you can explain

Regular cost reviews help identify waste and make each line of the AWS bill traceable to a purpose.

Tighter access control

Least-privilege IAM, MFA everywhere and removal of stale keys aim to shrink the most common cloud attack paths.

Tested recovery

Snapshot and RDS restore tests show how long a rebuild actually takes, not how long it should take.

Documentation for your team

An inventory and architecture summary make it easier for developers, auditors or a future hire to understand the account.

Technologies supported

  • Amazon EC2
  • Amazon RDS
  • Amazon S3
  • Amazon CloudFront
  • AWS IAM
  • Amazon VPC
  • Elastic Load Balancing
  • AWS Systems Manager
  • Amazon CloudWatch
  • AWS CloudTrail
  • Amazon GuardDuty
  • AWS Backup
  • AWS Certificate Manager
  • Amazon Route 53
  • AWS Budgets
  • Amazon Lightsail

Running something not listed? Ask us – we'll tell you honestly if it's a fit.

Who it's for

Who needs AWS maintenance?

Startups on AWS credits

Young companies whose infrastructure was set up quickly and now needs to be maintained properly as customers arrive.

SaaS businesses

Product teams who want their AWS foundations looked after while engineers focus on features.

E-commerce and content sites

Businesses running stores or high-traffic sites on EC2, RDS and CloudFront who need reliability through peak periods.

Industry guidance: SaaS Companies · Startups · E-commerce

FAQs

AWS Maintenance: common questions

What access do you need to our AWS account?
We use a dedicated IAM role or user with permissions scoped to the work agreed, ideally assumed from our own account with MFA. We do not need or want your root credentials, and all of our actions are visible in CloudTrail.
Who pays the AWS bill?
The AWS account and billing remain yours. Our maintenance covers the engineering work; AWS charges you directly for the resources you use. Part of our work is helping keep that bill free of waste.
Will you reduce our AWS costs?
We review spend regularly and recommend changes such as removing orphaned resources, right-sizing instances or adopting Savings Plans. The savings available depend entirely on how the account is set up, so we do not promise a specific reduction.
Do you only work with AWS?
No. We also maintain DigitalOcean, Azure and Google Cloud environments through our cloud infrastructure management service, and many clients run a mix of providers.
When do you patch production instances?
Patching runs in an agreed maintenance window, typically out of hours. Where you run several instances behind a load balancer, we can patch them in turn to reduce or avoid downtime.
What happens during an AWS outage?
If the cause is a regional AWS service issue, we monitor the AWS Health Dashboard, keep you informed and act on any failover options your architecture supports. If the cause is within your account, we investigate and resolve it under your plan's SLA.

Get a clear view of your AWS account

Book a technical audit and we will review security, recovery and cost across your AWS account, then recommend a maintenance routine.