Rambunct set up how SaberIntel’s property-management application is operated on Amazon Web Services (AWS): defined as code, deployed by pipelines that run checks first, watched by Amazon CloudWatch metrics, logs and alarms that are emailed to Rambunct, with 14-day backups.
The challenge
SaberIntel is a UK software company whose property-management application stores its clients’ property documents. As it reported its first client, the application ran on Amazon Web Services (AWS) with these gaps:
- A single server in one Availability Zone and a single-AZ database, each a single point of failure
- Only one day of backups
- No load balancer
- Deployments that ran a script on the server
SaberIntel needed it resilient, secured and changed as code in time for that client.
The solution
Rambunct set up the operations of the application on Amazon Web Services (AWS) in the London Region. Most of the code is Rambunct’s; the customer’s engineer wrote the upload scanning with Amazon GuardDuty.
Change through code:
- The application’s AWS services are defined as AWS Cloud Development Kit (AWS CDK) code
- GitHub Actions pipelines assume AWS roles through OpenID Connect
- The production pipeline deploys only after cdk-nag, cfn-lint and cfn-guard checks pass
Monitoring and alerting:
- Amazon CloudWatch holds container metrics, logs and alarms
- Alarms on healthy hosts, errors and response time are emailed to Rambunct, the customer’s managed services partner
Resilience and backup:
- The database is Multi-AZ Amazon Relational Database Service (Amazon RDS) for PostgreSQL with 14-day backups
- The API runs on Amazon Elastic Container Service (Amazon ECS) on Amazon Elastic Compute Cloud (Amazon EC2) instances across Availability Zones behind a load balancer
Architecture
Built on Amazon Web Services (AWS) in the London Region, across multiple Availability Zones.
AWS services: AWS Cloud Development Kit (AWS CDK), Amazon CloudWatch, Amazon Elastic Container Service (Amazon ECS), Amazon Elastic Compute Cloud (Amazon EC2), Amazon Relational Database Service (Amazon RDS) for PostgreSQL, Amazon Simple Storage Service (Amazon S3), Amazon GuardDuty, Amazon CloudFront, AWS Amplify Hosting, AWS Identity and Access Management (IAM)
Results
- Defined the application as code on Amazon Web Services (AWS)
- Moved releases from a script run on the server to pipelines that run checks first
- Extended database backups from 1 day to 14 days
- Moved from one server and one single-AZ database to servers and a Multi-AZ database across Availability Zones
- Set up alarms on healthy hosts, errors and response time, emailed to Rambunct
- Cut production over 18 days after the customer reported its first client
No uptime or recovery figure is claimed.






