Expertise / 04
AWS consulting and serverless engineering
I help software teams change and operate AWS-backed products. Engagements can cover a new serverless capability, a difficult deployment path or a production issue that crosses application code and cloud resources.
Infrastructure that matches the application workload
Serverless and event-driven services are useful when their execution model fits the work. I work with teams to define how requests, scheduled tasks and events move through the system, what happens when a step fails and which account or role owns each operation.
- AWS CDK and infrastructure as code
- Lambda, Step Functions and API Gateway
- SQS and EventBridge for asynchronous and event-driven work
- DynamoDB and relational data services where appropriate
Deploy, observe and recover
Infrastructure changes are part of an operational system. I consider environment configuration, permissions, secret handling, logs, alerts and recovery instructions alongside implementation. Production access, response responsibilities and any ongoing support are agreed for the engagement; engineering work does not imply 24/7 coverage. The application code and asynchronous work running on this infrastructure often needs its own Node.js backend engineering boundary.
- CloudWatch diagnosis and service-level visibility
- IAM boundaries and environment separation
- Repeatable deployment and CI/CD workflows
- Failure recovery, cost and performance trade-offs
Cloud architecture connected to product work
I approach AWS as infrastructure for an application rather than a transformation programme. For request handling and application processing, see Node.js backend engineering. For model-backed product behaviour hosted on AWS, see production AI engineering.
Relevant professional experience
AWS infrastructure and serverless architecture are part of my professional work on production software, including ongoing B2B SaaS engineering. Specific account details and employer systems remain confidential. I do not claim AWS partner status or unverified certifications.
Questions buyers usually ask
Can you work in our existing AWS account?
Yes. Client-controlled accounts and scoped access are the normal starting point, subject to the system and agreed responsibilities.
Do you provide 24/7 cloud support?
No. Any monitoring, support or response times must be explicitly agreed. An engineering engagement does not include round-the-clock on-call coverage by default.
Discuss an engineering engagement
Tell me about the work.
Share the system, the technical challenge and the kind of commitment you are considering.
Contact Serhii ↗