AWS Cloud
We build the AWS environments a production system will stand on, and move the workloads onto them — not only SAP. All of it in code, nothing clicked together in the console.
An AWS account opened in a hurry for one project looks the same in every company after two years: nobody knows what belongs to what, permissions were handed out broadly, and the bill grows for reasons no one can point to. Rebuilding costs less than tidying up.
Accounts and landing zone
Accounts split by environment and ownership, with shared rules applied automatically whenever a new one is created.
Infrastructure as code
CDK or Terraform — one choice, applied consistently. The environment can be rebuilt from nothing, and every change goes through code review.
Workload migration
Moving what sits next to SAP: databases, in-house applications, file servers, test environments. Each workload assessed on its own — move it, rewrite it, or switch it off.
Network and security
Corporate connectivity over VPN or Direct Connect, segmentation, narrow permissions, encryption with keys you control. Buckets are never public.
GenAI on AWS
Models on Amazon Bedrock running in your account and your region — the data never leaves the environment. We start with a PoC, because this is where it is easiest to pay for something that will not work.
Cost and monitoring
Instance sizing matched to real load, schedules that shut down non-production environments, a CI/CD pipeline, alarms set on what actually hurts.