SLA-backed run
AWS managed services and DevOps
We run and support production AWS environments under an SLA: infrastructure, monitoring, incident response, CI/CD, patching and cost. Whether we built the system or someone else did.
Service at a glance
- Uptime SLA
- 99.5%
- Critical incident response
- 30 minutes
- Account manager
- Named
- Reporting
- Monthly service report
- Delivered by
- AWS Partner, Solutions Architect and DevOps Professional certified
Organisations we have worked with
Onboarding
How onboarding works
Four steps from first conversation to a supported environment.
-
1
Discovery and audit
We review your AWS accounts, architecture, monitoring and costs against the AWS Well-Architected Framework, and agree the scope of support.
-
2
Onboarding
Access is set up through IAM roles in your account. We baseline monitoring and alerting, write the runbooks and agree escalation contacts.
-
3
Run and support
Monitoring, patching, backups and incident response under the service levels below. Changes and improvements go through the same engineers.
-
4
Report and improve
A monthly service report covering incidents, changes, costs and recommendations, reviewed with your named account manager.
Scope
What is included
What it takes to keep a production AWS environment healthy, secure and affordable.
Infrastructure management
- EKS and Kubernetes cluster operations
- EC2, Lambda and Fargate compute
- Database backups and tuning
- Networking and security groups
- Automated backups, S3 replication and DR testing
Monitoring and observability
- CloudWatch dashboards
- Container Insights for EKS
- Alarms and SNS notifications
- Centralised logging
- Synthetic monitoring
DevOps and CI/CD
- CodePipeline and CodeBuild
- Blue-green and canary deployments
- Infrastructure as code
- GitOps workflows
- Automated testing
Incident response
- Priority-based escalation
- Documented runbooks
- Post-incident reviews
- Root cause analysis
- Continuous improvement
Security and patching
- OS and container updates
- Vulnerability scanning
- IAM audits and least privilege
- Secrets Manager with rotation
- Security Hub integration
Cost optimisation
- Instance utilisation reviews
- Savings Plans analysis
- Spot Instance recommendations
- Unused resource cleanup
- Budget alerts and dashboards
SLA
Service levels
Every incident is assigned a priority when it is raised. Response is the time to an engineer working on it; resolution is the target to restore service.
| Priority | Response | Resolution | Examples |
|---|---|---|---|
| P1 Critical | 30 minutes | 4 hours | Production down, data breach |
| P2 High | 1 hour | 1 business day | Major feature unavailable, performance issues |
| P3 Medium | 4 hours | 3–5 business days | Non-critical functionality, minor bugs |
| P4 Low | 1 business day | Next sprint | Minor issues, enhancement requests |
Why us
Engineers on the incident, not a helpdesk
Engineers, not a helpdesk
The people answering incidents are the same engineers who build and change AWS systems, so fixes are made rather than escalated.
AWS only
We do not split attention across clouds. Every engineer works with AWS every day.
Certified and accredited
AWS Partner. Solutions Architect Professional and DevOps Professional certified.
Based in Cardiff
UK hours, direct access to the engineers on your account, no offshore handoffs.
"We have worked on complex AWS projects with Cloudavian and all have been successful. They understand requirements and deliver accurately and promptly."
What we support: EKS and Kubernetes, EC2, Lambda and Fargate, RDS, DynamoDB, DocumentDB and MongoDB, S3, Route 53, CloudWatch, Secrets Manager, CodePipeline, Terraform and CloudFormation, plus Node.js, TypeScript and React application stacks.
Questions
Compliance and common questions
Built for regulated environments
We work with organisations handling sensitive and regulated data. The managed service includes compliance-aware practices aligned with industry standards.
- GDPR-compliant data handling and processing
- AWS Well-Architected Framework reviews
- Special category data handling procedures
- Data Protection Impact Assessments (DPIAs)
Can you support an environment you did not build?
Yes. Onboarding starts with an audit of what is running, and we take on environments built in-house or by other suppliers.
Do we keep control of our AWS account?
Yes. Your account stays yours. We work through IAM roles you grant, with audit logging, and access can be revoked at any time.
What happens when something breaks?
You raise it, or our monitoring does. It is assigned a priority, an engineer responds within the time in the table above, and you get a post-incident review afterwards.
Can you also make changes and build new features?
Yes. The same team does development, so improvements and new features are handled without a handover to a separate supplier.