onedevatlasBeta
Browse the atlas
AllABAPCAPUI5BTP
PackagePackagetypeA library you install and call yourself.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

gregorwolf/AWS_SNS4ABAP

An ICF handler that receives Amazon SNS notifications in an ABAP system as an HTTPS subscriber endpoint, leaving what happens to a notification once it arrives to the caller.

AWS_SNS4ABAP is an ICF handler that implements Amazon Simple Notification Service's HTTPS endpoint as a subscriber, so an SNS topic can push its notifications into an ABAP system. Its maintainer calls it a simple implementation, and it covers the endpoint itself: what the ABAP system does with a notification once it has arrived is left to the caller. The README is the handler's whole documentation, and names no ABAP release, system or installation method.

GitHub3 ★
abaplint224 lines

Facts

Last pushLicenceApache-2.0

Where it sits

Lives in
ABAP
Provides
Event MeshABAPEvent MeshcapabilityEmitting and consuming business events across systems through brokers, including subscriptions and mapping application events to broker topics. Work that must survive a request, including deferred processing and retries, belongs to [async processing](capability:async-processing).

Who is behind it

Gregor WolfGregor WolfPersonMaintains this
In the atlas: maintains 17, contributes to 59, wrote 2@gregorwolfmaintainer

Before choosing this

Signals

ActivityQuietNo published releases; repository quiet for 64 months

It publishes no releases, and its repository has been quiet for at least 24 full months. This may be normal for stable software; check whether its current state still fits your use.

Conditions

PolicySAP API Policy 4.2026a§ 2.2.2, 3, FAQ 12, FAQ 27, FAQ 38from Event MeshAn ABAP event integration exposes inbound access to SAP APIs or becomes a systematic or large-scale extraction or replication path. An outbound notification or callback alone is not enough.
  • § 2.2.2 AI call sequences and data extraction. Outside SAP-endorsed architectures, data services or expressly identified pathways, the policy prohibits specified agentic API use and systematic or large-scale extraction.
  • § 3 Monitoring and remedies. SAP states that it may monitor API use and take enforcement actions when use does not comply with the documentation and policy.
  • § FAQ 12 Outbound interfaces. The accompanying FAQ distinguishes external consumption of SAP-provided services from outbound notifications or callbacks sent by an SAP system, which it places outside this policy's scope.
  • § FAQ 27 Custom-developed APIs. Customer-namespace ABAP interfaces are not prohibited merely because they are custom, but their underlying SAP dependencies and usage pattern still determine whether the use aligns with the policy.
  • § FAQ 38 Large-scale data access. Large-scale extraction and replication must use access mechanisms and patterns documented for that purpose rather than treating a transactional or custom API as a general bulk-data surface.

Direction and usage pattern decide the policy relevance. Customer ABAP code may publish events outward, but it must not be used to bypass SAP API controls or substitute a custom event stream for a documented bulk-data pathway.

SAP API Policy 4.2026a →

What it declares

Every artifact

Type
Package
Origin
Independently maintained

As a package

Where it runs
does not say
Distributed through
does not say

Connections1

README

quoted from gregorwolf/AWS_SNS4ABAP under Apache-2.0, read
gregorwolf/AWS_SNS4ABAP/README.mdOn GitHub

ABAP Endpoint for AWS SNS

Simple implementation of a ICF Handler that acts as a Amazon Web Services Simple Notification Service implementing the HTTPS Endpoint as a Subscriber.

Apache-2.0, read

Others providing3

Compare all 4 on the Event Mesh page →
Event Mesh
  1. cesar-sap/abap_kafka_rest_proxyABAP connector to Kafka through the Confluent Kafka REST Proxy
  2. INVIXO/abapMQMQTT 3.1.1 client implemented in ABAP
  3. MQBAMQTT publish/subscribe in ABAP with an external broker bridge

Details

Sources3
Added by handdiscovered herechecked
github.com/gregorwolf/AWS_SNS4ABAPtree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

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 viaAdded by hand
first seen in the atlas
ecosystem and domainabap, integration-and-messaging
abaplint
issues under its own abaplint configuration11
lines224
statements119
objects6
files3
analysed, main
abaplint version2.120.84
read fromabaplint.app,
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:gregorwolf-aws-sns4abap
JSON
/artifacts/gregorwolf-aws-sns4abap.json
MCP
Connecting an agent