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, with no SAP transaction access, no config changes and no token reveal. Granular 92-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, and 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 follows from your Readiness Check, not a free choice, and we give a straight read on whether RISE belongs.

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 path is a consequence of the source system, not a preference. The Readiness Check and ATC decide it rather than us, and we give a straight read rather than a default.

Greenfield

New S/4HANA implementation

A clean-core S/4HANA build on a fresh landing zone. The path a daunting Readiness Check argues for, where the old system is not worth carrying forward and there is appetite to redesign the core processes.

Brownfield

System conversion

An in-place ECC-to-S/4HANA conversion: a single SUM/DMO run doing the upgrade, HANA migration and code conversion together, with SPDD/SPAU adjustment. We size the HANA target and plan the cutover.

Selective / hybrid

Selective data transition or RISE-adjacent

A selective data transition: a new S/4HANA system carrying only the config and data you choose, on an EC2/HANA landing zone that can sit alongside RISE. We say 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, which is the foundation S/4HANA lands on. Stood up once, before any SAP workload moves.

HANA-certified sizing

EC2 family chosen against the current SAP-certified list, storage laid out for HANA data and log volumes, Multi-AZ HA and cross-region DR.

Migration execution

Wave planning, a rehearsed cutover window and a tested rollback, run through 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 cost-drift report so the bill holds no surprises.

Operate after go-live

The FCC Platform runs alongside: live SM50/SM37 and HANA telemetry, alerting and an audit trail, giving 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 from the start, not retrofitted.

The functional and ABAP conversion, meaning the SUM/DMO run and code remediation, stays with your partner; we hold the AWS-side foundation underneath, alongside them. More on our AWS reseller offering →

How an engagement looks

Scope & sizing

The Readiness Check and ATC findings on the source settle the path; then we size the S/4HANA target on AWS against the certified instance list.

Landing zone

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

Build & migrate

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

Operate together

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

Go deeper

Blog

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

What decides the path, from the Readiness Check and ATC to the ECC dates, and where AWS sizing fits once it is set.

Blog

RISE with SAP vs self-hosted on AWS

How to compare them honestly, and the hybrid pattern where an EC2/HANA landing zone sits next to RISE.

Blog

SAP-on-AWS landing zone checklist

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

Topic

AWS for SAP

The full reseller offering: AWS resale, landing zones, FinOps and day-two operations.

Common questions

Do you do the functional S/4HANA conversion?

Our work is the AWS-side infrastructure, the migration onto it and the monitoring overlay after go-live. The functional and ABAP conversion, covering the SUM/DMO run, SPDD/SPAU adjustment and custom-code remediation, stays with your implementation partner; we run alongside them, and prefer to be introduced early so the landing zone matches the conversion plan.

Greenfield, brownfield or selective: which is right?

Less a choice than a consequence of the source system. Run the Readiness Check, Simplification Item checks and ATC with the S4HANA_READINESS variant first: a clean report argues for an in-place SUM/DMO conversion, a daunting one for a clean-core rebuild. A hard ECC-maintenance deadline pushes toward conversion.

What about RISE with SAP?

We will tell you when RISE is the right call and when self-hosted on AWS wins. Many mid-size landscapes end up hybrid, so 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?

In whichever AWS region you choose. 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, with 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, covering SIDs, peak users, current hosting and costs, and we come back with a sized S/4HANA landing zone and a transparent monthly forecast.

AWS for SAP