BrowseSAP Cloud Application Programming Model
Everything in CAP
1 of 1047
Domain: Integration & Messaging
Signals
Content
More: 3
Group by: Capability
Domain Integration & MessagingSource SAP Architecture CenterSource capireSource SAP BTP AI Best PracticesClear all
EntryBySignalsLast activity
DestinationsSAP and community
Secure Service Consumption Across HyperscalersSecure Service Consumption Across HyperscalersSAP's design for a workload on SAP BTP that calls Amazon Web Services or Google Cloud services with short-lived credentials instead of stored keys, which is the outbound side of authentication: the BTP application proving who it is to another cloud. On AWS it draws two paths, an ID token from Identity Authentication in Cloud Identity Services exchanged through AWS STS for an IAM role, or an X.509 certificate kept in SAP Destination service and presented to IAM Roles Anywhere; on Google Cloud only the token path, through Workload Identity Federation and an impersonated service account. It is drawn for those two hyperscalers only, and Microsoft Azure has no page in it.published 2025-05-14
