AWS: Accounts set up properly, costed sensibly and documented.

Separate accounts, least-privilege access and everything in code, so your team can see and change what you run.

Talk to an engineer
Problems we solve
“Everything runs in one account, with admin access for all.”
“Nobody is sure what half these resources are for.”
“We need to pass a security review and don’t know where we stand.”

What we do

Advise

AWS consultancy

An assessment of your AWS setup, with findings ranked by risk and effort.

Build

AWS delivery

We design and build it with your team, in your accounts, documented as we go.

Run

AWS support

Monitoring, patching and upgrades, with incident response agreed per contract.

Teach

AWS training

Workshops and pairing on AWS, built around your own systems.

Tools we work with

Accounts & identity

  • Organizations
  • Control Tower
  • IAM Identity Center
  • IAM
  • Service Control Policies

Compute & containers

  • EC2
  • Auto Scaling
  • Lambda
  • ECS
  • Fargate
  • EKS
  • ECR

Networking & delivery

  • VPC
  • Transit Gateway
  • Route 53
  • CloudFront
  • Elastic Load Balancing
  • API Gateway
  • Site-to-Site VPN

Data & storage

  • S3
  • EBS
  • EFS
  • RDS
  • Aurora
  • DynamoDB
  • ElastiCache

Security

  • KMS
  • Secrets Manager
  • GuardDuty
  • Security Hub
  • WAF
  • AWS Config

Operations & cost

  • CloudWatch
  • CloudTrail
  • Systems Manager
  • AWS Backup
  • Cost Explorer
  • Savings Plans

Infrastructure as code

  • Terraform
  • Terragrunt
  • OpenTofu
  • CloudFormation
  • AWS CDK

How an engagement runs

  1. 1 A call. 30 minutes with an engineer to understand the problem.
  2. 2 A look. Read-only access or a walkthrough, so we scope from facts.
  3. 3 A proposal. Scope, deliverables and a price model: fixed scope, day rate or retainer.
  4. 4 The work. In your accounts and repositories, alongside your team.
  5. 5 A handover. Documentation and a session with your team, so you’re not dependent on us.

Proof

A recent AWS engagement. We keep client names private, but the problem, the work and the outcome are exactly as they happened.

See our work
Case study · anonymised
UK fintech scale-up
Challenge
One AWS account held everything, most of the team had admin access, and a customer security review was coming.
Approach
We split workloads into separate accounts under AWS Organizations, moved access to IAM Identity Center with least-privilege roles, and put the whole setup in Terraform.
Stack
AWS Organizations · IAM Identity Center · VPC · Terraform
Result
The review passed. New environments are now created from code, by the client’s own team.

Questions

Do you work in our accounts or yours?

Yours. Everything we build lives in your cloud accounts and repositories from day one, so there is nothing to migrate when we finish.

Can you work alongside our own team?

Yes, and we prefer it. We can run a project ourselves, embed engineers in your team, or pair with your people so they pick it up as we go.

How is this priced?

Depending on the work: a fixed-scope price, a day rate or a monthly retainer. We agree it in a written proposal before anything starts.

Tell us what’s broken, slow or expensive.