ServiceServiceA BTP service you subscribe to and bind, rather than install. It has plans and regions, not versions, and may deliver a product that lives outside the atlas.See every one →What this type is →by SAPby SAPPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →
Object Store on SAP BTP
SAP's binding onto a hyperscaler's object storage — S3, Azure Blob Storage or Google Cloud Storage, chosen by plan. Store, fetch and delete objects; the bytes live with the provider.
Where it sits
Lives in
Provides
Object storageBTPObject storageStoring application files as objects in a bucket or container backed by a cloud storage service. Connecting a file to a business record is the separate [Attachments](capability:attachments) concern.
Serves
What it declares
Every artifact
- Type
- Service
- Origin
- By SAP
As a service
- Plans
- 4
- Regions
- 44
- Support component
- BC-CP-CF-OSAAS
Connections
Group by8 of 8 connections
NodeRelationBasis
Functional
Object storageObject storageStoring application files as objects in cloud storageSAP only
provides
stated
provides Object storage
Provisions a bucket or container on a hyperscaler for applications to store and manage objects.
“Provides an object store space (bucket or a container), based on underlying hyperscaler offerings, that applications can use to store & manage objects.”
Storing application files as objects in cloud storage
Technical
@cap-js/attachments@cap-js/attachmentsCAP Node.js attachments with database, S3, Azure or GCP storagesap official, cap
connected from
derived
connected from @cap-js/attachments
An object store is bound; for local testing the content is kept in a local database.
Keeping attachment content in a bound SAP Object Store instance in place of the application database.
“For using an Object Store in BTP, you must already have an SAP Object Store service instance on the appropriate landscape created.”“For productive use, a valid object store binding is required”“For local testing, the attachment objects are stored in a”
CAP Node.js attachments with database, S3, Azure or GCP storage
com.sap.cds:cds-feature-attachmentscom.sap.cds:cds-feature-attachmentsCAP Java attachments with database storage and an Object Store modulesap official, cap
connected from
derived
connected from com.sap.cds:cds-feature-attachments
The cds-feature-attachments-oss module is selected.
Keeping attachment content in an object store on AWS, Azure or Google, through the plugin's object store storage target.
“It supports the [AWS, Azure, and Google object stores](storage-targets/cds-feature-attachments-oss) and can connect to a [malware scanner](#malware-scanner).”“By default, the plugin operates without a dedicated storage target, storing attachments directly in the”
CAP Java attachments with database storage and an Object Store module
aicore-multioutput-regression-restaurant-inspectionsaicore-multioutput-regression-restaurant-inspectionsML service on SAP AI Core scoring restaurant-inspection violationssap official, btp
needed by
derived
needed by aicore-multioutput-regression-restaurant-inspections
where the training data is uploaded and read from; the README has its service key copied into s3_service_key.json
“Add your Amazon S3 bucket service key to _s3_service_key.json_. This is actually the service key of your Object Store instance”“Upload training data to Amazon S3 bucket”
ML service on SAP AI Core scoring restaurant-inspection violations
@cap-js/attachments@cap-js/attachmentsCAP Node.js attachments with database, S3, Azure or GCP storagesap official, cap
optionally used by
derived
optionally used by @cap-js/attachments
Productive use of an Object Store storage target.
“For productive use, a valid object store binding is required, see [Object Stores](#object-stores) and [Storage Targets](#storage-targets).”
CAP Node.js attachments with database, S3, Azure or GCP storage
@tklein1801/cap-js-attachments@tklein1801/cap-js-attachmentsCAP Node.js attachments plugin with Object Store and malware scanningindependent, cap
optionally used by
derived
optionally used by @tklein1801/cap-js-attachments
SAP Object Store storage is selected.
“For using SAP Object Store, you must already have a SAP Object Store service instance with a bucket which you can access.”
CAP Node.js attachments plugin with Object Store and malware scanning
cap-attachments-pluscap-attachments-plusCAP Node.js attachments plugin with database or cloud storageindependent, cap
optionally used by
derived
optionally used by cap-attachments-plus
Automatic per-tenant Object Store provisioning is used.
“The SAP Object Store service binding described below is only relevant for **multi-tenant** deployments that use the plugin's automatic per-tenant Object Store provisioning”
CAP Node.js attachments plugin with database or cloud storage
com.sap.cds:cds-feature-attachmentscom.sap.cds:cds-feature-attachmentsCAP Java attachments with database storage and an Object Store modulesap official, cap
optionally used by
derived
optionally used by com.sap.cds:cds-feature-attachments
The cds-feature-attachments-oss module is selected.
“A valid Object Store service binding is required for this, typically one provisioned through SAP BTP.”
CAP Java attachments with database storage and an Object Store module
Download
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
discovered viaSAP-samples/btp-service-metadata · btp-service-metadata
first seen in the atlas
ecosystem and domainbtp, data-and-persistence
History in the atlas
- Place the service under its direct job of object storage. CAP attachment integration remains represented by existing dependency edges from the attachment plugins.
- First seen.
For your agent
- Ref
artifact:btp-object-store- JSON
- /artifacts/btp-object-store.json
- MCP
- Connecting an agent