
AWS infrastructure: built as code, sized to the load
We set up and operate production on AWS: accounts, networks, EKS clusters, databases, delivery pipelines and monitoring. Every resource is in Terraform, and the bill is reviewed against what the system really uses.
When you need this
- 1
You are starting on AWS and want the account laid out properly from day one
- 2
Resources were created by hand in the console and nobody knows what is safe to delete
- 3
You need EKS, but nobody on the team has run Kubernetes in production
- 4
The AWS bill grows faster than the traffic
- 5
A client or an auditor asks how access, backups and networking are organised
What's included
Accounts, IAM and network
Separate accounts or environments, least-privilege IAM roles, a VPC with private subnets, NAT and security groups that expose only what must be public.
Compute: EKS or EC2
An EKS cluster with managed node groups and autoscaling, or plain EC2 with Auto Scaling where a cluster is not justified. The choice follows the workload.
Data
RDS or Aurora with automated backups and a tested restore, ElastiCache, S3 with lifecycle rules, encryption with KMS.
Delivery
CI/CD from GitHub Actions or GitLab CI into ECR and the cluster, with staged rollouts and a rollback command.
Monitoring and alerts
CloudWatch plus Grafana and Prometheus-compatible metrics, logs in one place, alerts to Telegram or Slack.
Cost review
Cost Explorer and usage data against the actual load: instance sizes, storage classes, data-transfer paths, Savings Plans and spot capacity where it is safe.
The bill follows the load
A cost review ends with a report like this: what you paid before, what you pay now, and where the difference came from.
Monthly cost
- Before
- $10,400
- After
- $6,200
- Δ per month
- −40%
Cost by month
Cost by service
| Service | Before | After | Δ |
|---|---|---|---|
| EC2 / EKS compute | $5,200 | $2,900 | −44% |
| RDS | $2,100 | $1,500 | −29% |
| NAT + data transfer | $1,600 | $650 | −59% |
| S3 + EBS | $900 | $550 | −39% |
| Other | $600 | $600 | 0% |
Example of the report format with illustrative figures. The real saving depends on the account and is shown to you before anything is changed.
How the work goes
- 1
Access and audit
A read-only role in your account. We map what exists, what it costs and what is exposed.
- 2
Target design
An architecture diagram, the Terraform layout, a migration order and a price for the work.
- 3
Build as code
Existing resources are imported into Terraform, new ones are created through pull requests in your repository.
- 4
Run or hand over
We operate the account as a monthly service, or pass it to your team with documentation.
Questions
- AWS EKS
- EC2
- RDS
- S3
- VPC
- IAM
- CloudFront
- ECR
- CloudWatch
- Terraform
- Helm
- GitHub Actions
Describe the task — get a plan and a price
Write what you have and what you need. We answer within one business day with questions or a concrete proposal.