Migrations to AWS
Containerised applications on ECS Fargate with RDS, S3 and load balancers, moved over with a rehearsed cutover and no downtime.
We moved Ben-Gurion University’s 80,000-page website from Azure to AWS ECS Fargate without downtime, built an event-driven video pipeline on SQS, S3 and Kubernetes that costs nothing while idle, and run marketplace and logistics platforms on EC2 with S3 and SQS.
The kinds of work we use AWS for, based on the projects below rather than a list of everything the technology can do.
Containerised applications on ECS Fargate with RDS, S3 and load balancers, moved over with a rehearsed cutover and no downtime.
SQS queues and S3 storage driving workers that scale with the queue and back to zero when it is empty.
.NET applications on EC2 with S3 storage, SQS jobs and CodeBuild pipelines for marketplaces and logistics.
Which part of the system it ran, and what it worked with. Every row links to the full case study.
Each one with the client’s problem, our approach and what changed.

A sourcing step that buys from 1688 suppliers for each order, tracks the shipment and bills clients only when each stage is complete.

The university's main Umbraco site: ~80,000 pages, ~1,000 editors, daily staff data imports and a zero-downtime move from Azure to AWS.
A Kubernetes pipeline that turns hours of mixed-language lectures into timed transcripts, subtitles, summaries and HLS video.

AI services connected to existing CRM, ERP and marketing tools: 24/7 chatbots, sentiment analysis, fraud alerts and predictive insights.

A platform that pulls orders from 7 Amazon marketplaces, turns personalized orders into print jobs and shows the real margin on every product.
An event-driven AWS and Kubernetes service that turns each uploaded video into adaptive HLS streams with multi-language audio, then scales back to zero.

A login-only portal for BGU students and staff that shows each person their own schedule, grades, payments and news, built on the university's Umbraco setup.
We do not sell hours of a technology. We take on a result, and choose the stack with you. These are the services where AWS usually comes in.
Each one backed by at least one published client project.
Backend
Anything missing? Send us your question and an engineer will answer, usually within one business day.
Contact usYes. We did it for Ben-Gurion University: ~80,000 pages and ~1,000 editors moved from Azure to AWS with the site live throughout. Our blog has the full write-up.
ECS Fargate, EC2, S3, SQS, RDS, ECR and CodeBuild, plus SageMaker for machine learning. We pick managed services over self-hosted ones where it lowers running costs.
Often. Typical savings come from scaling workers with the queue, moving batch work to spot or Fargate, and right-sizing databases. The cloud media pipeline in our case studies costs $0 in compute when idle.
A spec, a Figma file or three paragraphs is enough to start.

Cookies on oski.solutions
We'd like to use analytics cookies to understand how the site is used, and marketing cookies to measure our ads. They are off unless you allow them. You can change your choice any time via “Cookie settings” in the footer. Cookie policy