Your SAP and cloud estate, watched, patched and kept running every day.
We run day to day operations for SAP and non-SAP workloads on AWS, Microsoft Azure and Google Cloud: monitoring, patching, backup checks, incident response and SAP Basis. You get agreed service levels, clear reporting and a team that knows both the cloud platform and the SAP stack on top of it.
Why cloud operations need a dedicated team
Moving SAP to the cloud removes hardware work, but it does not remove operations. Someone still has to watch HANA memory and replication, apply SAP security notes and operating system patches, prove that backups restore, and respond when a job or interface fails at night. In a hybrid estate with RISE with SAP, SAP Business Technology Platform, integration services and non-SAP systems, those tasks are split across several providers, and gaps appear where responsibilities meet.
Alerts nobody owns
Cloud tools raise plenty of alerts. Without runbooks and an owner, real incidents get lost among noise.
Patching falls behind
SAP publishes security notes every month and operating systems need regular updates. Skipped cycles build up risk and make later upgrades harder.
Backups that are never tested
A backup job that reports success is not the same as a database you can restore within your target time.
Split responsibilities
Under RISE with SAP, SAP runs the infrastructure and Basis, while you still own integrations, identity, extensions and surrounding workloads. Those boundaries need managing.
What we do
We take on the run tasks your team should not have to handle alone, with clear scope and service levels.
Monitoring and alerting
We set up full stack monitoring across infrastructure, operating system, database and SAP application layers using native cloud tools. Alerts are tuned and linked to runbooks so the right person acts on them.
Patching and updates
We plan and apply operating system patches, SAP kernel updates and SAP security notes in agreed maintenance windows. Each cycle is tested on non-production first and recorded.
Backup checks and restore tests
We check that HANA and file backups complete, are retained correctly and are stored away from the source system. We run scheduled restore tests and report the results.
Incident and problem management
We respond to incidents within agreed times, restore service and find the root cause. Repeat problems are tracked until they are fixed.
SAP Basis on cloud
For ECC, SAP S/4HANA or other SAP systems that you run on your own cloud subscription, we provide Basis support: system copies, transports, job monitoring, performance tuning and housekeeping. For RISE with SAP customers we handle the tasks that stay with you and work with SAP on the rest.
Reporting and service reviews
You get monthly reports on availability, incidents, changes, patch status and backup results. We review them with you and agree improvements.
How it works
- 1
Discovery and scope
We review your landscape, current tools, responsibilities and pain points. Together we agree what we run, what you keep and what SAP or another provider covers.
2 to 3 weeks - 2
Onboarding and tooling
We deploy or configure monitoring agents, dashboards, alert rules and access. We write runbooks for your systems and connect alerts to our service desk.
3 to 6 weeks - 3
Transition and shadowing
We work alongside your current team or provider, handle live tickets under supervision and confirm the runbooks work. Handover happens only when both sides agree.
2 to 4 weeks - 4
Steady state operations
We run monitoring, patching, backup checks and incident response under the agreed service levels. You get regular reports and a named contact.
Ongoing - 5
Continuous improvement
Each quarter we look at incident trends, automation options and cost or performance gains. Agreed changes go into the plan for the next period.
Quarterly
Native tools we use on each cloud
We build on each provider's own operations services, and add SAP tooling where it helps.
| Need | AWS | Microsoft Azure | Google Cloud |
|---|---|---|---|
| Infrastructure and log monitoring | Amazon CloudWatch | Azure Monitor with Log Analytics | Google Cloud Observability (Cloud Monitoring and Cloud Logging) |
| SAP aware monitoring | Amazon CloudWatch Application Insights for SAP HANA and SAP NetWeaver | Azure Monitor for SAP solutions | Google Cloud's Agent for SAP with Cloud Monitoring |
| SAP operations and start or stop | AWS Systems Manager for SAP | Azure Center for SAP solutions | Google Cloud's Agent for SAP and Workload Manager |
| Operating system patching | AWS Systems Manager Patch Manager | Azure Update Manager | VM Manager OS patch management |
| Platform health notices | AWS Health | Azure Service Health | Personalized Service Health |
Operations for every SAP model
What we run depends on how you run SAP. If you run ECC or SAP S/4HANA yourself on a cloud subscription, including bring your own licence deployments, you and we are responsible for the virtual machines, operating system, database and Basis. Under RISE with SAP, SAP runs the infrastructure and core Basis on the hyperscaler you chose, so you do not manage those virtual machines. You still own integrations, identity, custom code, SAP Business Technology Platform services and the non-SAP systems around them, and that is where we focus. ECC mainstream maintenance ends at the end of 2027, with optional extended maintenance to the end of 2030, so many estates need stable operations during the move as well as after it.
- Basis support for self-managed ECC and SAP S/4HANA on AWS, Azure and Google Cloud
- Monthly review of SAP security notes published on SAP Security Patch Day
- Coordination with SAP on RISE with SAP service requests and maintenance windows
- Monitoring of interfaces between SAP, SAP BTP and non-SAP systems such as Salesforce or MIHCM
© 2026 Mawkish Technologies. This guide, its diagrams and illustrations are protected by copyright. You’re welcome to learn from it and to quote it with credit and a link. Reproducing it, by hand or through AI, and publishing it as your own is not allowed. Read our copyright notice
Deliverables
- Agreed scope and responsibility matrix covering you, us, SAP and the cloud provider
- Monitoring dashboards and tuned alert rules for each system
- Runbooks for common incidents and routine tasks
- Patch calendar and records for operating system, kernel and SAP security notes
- Backup and restore test reports
- Monthly service report with availability, incidents and improvement actions
Frequently asked
Do you replace SAP's role under RISE with SAP?
No. Under RISE with SAP, SAP runs the infrastructure and core Basis tasks on the hyperscaler you chose. We look after the tasks that remain yours, such as integrations, identity, extensions and surrounding systems, and we raise and follow up service requests with SAP for you.
Can you run SAP systems that we host ourselves on the cloud?
Yes. For ECC or SAP S/4HANA running on your own AWS, Azure or Google Cloud subscription, we can cover monitoring, patching, backups, incident response and Basis. We agree scope and service levels with you before we start.
Which monitoring tools do you use?
We start with each cloud's native services, such as Amazon CloudWatch, Azure Monitor and Azure Monitor for SAP solutions, and Google Cloud Observability with Google Cloud's Agent for SAP. If you already use SAP Cloud ALM or another tool, we can work with it.
How do you handle patching without disrupting the business?
We agree maintenance windows with you, apply patches to non-production systems first and test them, then patch production. SAP security notes are reviewed each month after SAP Security Patch Day and prioritised by risk.
Do you cover non-SAP workloads too?
Yes. We can run web applications, databases, integration platforms and other line of business systems alongside SAP, using the same monitoring, patching and reporting approach.
Often paired with this
Plan your move with people who know SAP.
One working session with our cloud and SAP architects. You leave with the options, the risks and a first plan.
- Your landscape reviewed
- The right cloud and region
- A first roadmap
Sources
- SAP Security Notes FAQ (Patch Day)
- Azure Monitor for SAP solutions overview
- Google Cloud: Monitoring SAP HANA with Agent for SAP
- AWS: CloudWatch Application Insights for SAP NetWeaver
- AWS Systems Manager for SAP stop and start
- Azure Center for SAP solutions start and stop
- SAPinsider: SAP support deadlines 2027, 2030, 2033
- SAP: Securing RISE with SAP
At Mawkish, the Finford Review is how we keep Managed Cloud Operations work checked, owned and answered for, whoever does the build.
AWS, Microsoft Azure, Google Cloud and SAP are trademarks of their respective owners.