We currently run the on-prem version of SAP hybris at AWS.   Almost every operational workload we have runs at AWS, inclusing integration layer, enterprise shared services, and analytics.   SAP is no longer going to support the on-prem version, and the only version they have available is available at Azure only.  We have an Azure presence, but only for productivity-type work.  We are very reticent to undertake the hybris move to Azure since it adds operational complexity, cost, and latency (as a retailer, hybris is our cart engine for both web and store sales...our most latency sensitive business process). Options before us:   1. stay with hybris but move to the Azure version and invest in support & latency mitigation, or 2. move to some other AWS-based commerce engine.  Any others faced with this decision?  If so, what approach are you taking and why?

Scott,

we are facing the same problem as you with our SAP landscape. We have multiple SAP products with perpetual licenses hosted on AWS cloud architecture. As SAP is forcing us out of our current architecture to onboard their own, we find it is too much risk vs SAP very bad reputation and reliabilty on managing infrastructure. Additionnaly, this will put you in a position were you will be bling to your backend and SAP will profit from this as everytime you will have performance issue they take the opportunity to augment your bill has you will absolutly have no way to validate if its really a hardware problem.
We have decided to move everything away from SAP and have chosen to move our entire eComm ecosystem on something else.
At the point where you are, you should really take the time to consider other, much more mature options that are out there.
FYI, we have moved away from Hybris, Ariba, Sales Cloud, Analytics Cloud and BW. The only part we are keeping for the moment is ECC.
Hope this helps

Scott, would this unconventional—but workable—path meet your goals? Potentially keeping AWS as the center of gravity while adopting SAP Commerce Cloud on Azure as a thin, privately connected landing zone. Using metro-local AWS Direct Connect ⇄ Azure ExpressRoute (via Equinix/Megaport) to keep cross-cloud RTT in the single-digit-ms range. Serving the storefront at the edge with SSR, placing the cart/session in Redis Enterprise Active-Active in both clouds (local reads/writes; CRDT replication), and moving the catalog/price/inventory/order events over Confluent Cloud on private networking. The aim would be to satisfy SAP’s support posture without replatforming—and without adding customer-visible latency.