Does the agent need inbound network access to my SAP hosts?

No. The agent is outbound-only — it polls Farrenio over HTTPS for its config and pushes metrics the same way. No new firewall rules, no exposed ports on your SAP boxes.

Can my service desk see alerts without touching production?

Yes. The service_desk role is read-only on alerts and incidents — no SAP transaction access, no config changes, no token reveal. Granular 69-permission RBAC means you can carve out exactly what each team sees.

How long does a proof of concept take?

A 30-minute call to scope. We typically have one production SID streaming live metrics within an hour of agent install — the rest of the landscape follows as fast as you can roll out the package.

SAP S/4HANA on AWS

Migrate to S/4HANA on AWS, with the infrastructure done right.

As an AWS reseller for SAP, we design the landing zone, size HANA-certified compute, run the migration onto it, and operate it after go-live. Greenfield, brownfield or selective — and an honest read on whether RISE belongs in the picture.

Read: which migration path?

Compute mark-up

AWS list, billed by us

Default region

eu-central-1

Frankfurt · GDPR-aware

After go-live

One pane

FCC Platform monitoring

Three ways onto S/4HANA

The right path depends on how much of today's system is worth carrying forward. We will give an honest read rather than a default.

Greenfield

New S/4HANA implementation

A fresh S/4HANA build with a clean landing zone underneath it. Best when the old system is not worth carrying forward and the project has appetite to redesign processes.

Brownfield

System conversion

Convert an existing ECC system to S/4HANA in place, then move it to AWS. Keeps history and customisation; the AWS-side work is sizing the target and planning the cutover.

Selective / hybrid

Selective data transition or RISE-adjacent

Move what matters, leave the rest, and design an EC2/HANA landing zone that sits next to RISE where that makes sense. We tell you honestly when RISE is the right call.

What we own in a migration

Landing-zone design

Multi-account structure, VPC topology, security baselines and IAM — the foundation S/4HANA lands on. Built once, properly.

HANA-certified sizing

EC2 family selection against the current SAP-certified list, storage layout for HANA data and log, Multi-AZ HA and cross-region DR.

Migration execution

Wave planning, cutover windows and a rollback strategy, using AWS Migration Hub and Application Migration Service.

FinOps from day one

Savings Plans and Reserved Instances, right-sizing, non-production shutdown schedules, and a monthly drift report so the bill never sneaks up.

Operate after go-live

The FCC Platform runs alongside: live SM50/SM37/HANA telemetry, alerting and an audit trail. One pane over the new estate.

Audit and residency

Customer-managed keys, data residency by design (eu-central-1 by default for EU), and an audit archive built in rather than retrofitted.

The functional and ABAP conversion stays with your implementation partner — we run alongside them and the AWS-side foundation underneath. More on our AWS reseller offering →

How an engagement looks

Scope & sizing

We hear the landscape, the timeline and the constraints, then size the S/4HANA target on AWS against the certified instance list.

Landing zone

Account vending, network skeleton, SSO, baseline IAM and the security accounts — before any SAP workload moves.

Build & migrate

HANA-certified compute, storage layout, HA cluster, a dry-run cutover and the real cutover window with a rollback plan in hand.

Operate together

You own the platform; we cover the AWS-side on-call, FinOps reviews and an architecture check each quarter.

Go deeper

Blog

S/4HANA on AWS: brownfield vs greenfield vs selective

How to choose a migration path, the questions that actually decide it, and where AWS sizing fits.

Blog

RISE with SAP vs self-hosted on AWS

How to compare them honestly and the hybrid pattern that fits many mid-size landscapes.

Blog

SAP-on-AWS landing zone checklist

A working checklist for the foundation S/4HANA lands on.

Topic

AWS for SAP

The full reseller offering: resale, landing zones, FinOps and operations.

Common questions

Do you do the functional S/4HANA conversion?

Our work is the AWS-side infrastructure, the migration execution onto it, and the monitoring overlay after go-live. For the functional and ABAP conversion we work alongside your implementation partner rather than replacing them — and we are happy to be introduced early so the landing zone matches the conversion plan.

Greenfield, brownfield or selective — which is right?

It depends on how much of the current system is worth carrying forward and how much appetite there is for process redesign. We will give an honest read on your situation rather than a default answer. The blog post on migration approaches walks through the trade-offs.

What about RISE with SAP?

We will tell you when RISE is the right call and when self-hosted on AWS is. Many mid-size landscapes end up hybrid, and we design an EC2/HANA landing zone that lives next to RISE where that fits. There is a full comparison on the blog.

Where will the data live?

Wherever AWS hosts it. We default to eu-central-1 (Frankfurt) for EU customers and design around your data-residency constraints. The FCC Platform itself is EU-hosted.

How do you price the migration?

AWS at list price billed monthly by us — no mark-up on compute — plus the consulting hours you actually use and the platform subscription if you take it. Send us an inventory and we come back with a sized landing zone and a transparent monthly forecast.

Planning an S/4HANA move?

Send us an inventory of what you run today — SIDs, peak users, current hosting and costs — and we will come back with a sized S/4HANA landing zone and a transparent monthly forecast.

AWS for SAP