Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
Showing results for 
Search instead for 
Did you mean: 
Active Participant


This blog post is part of a series of blog posts related to SAP Cloud Platform Alert Notification service.

You can relate to the parent blog post for more detailed information about the service itself.

Let's take the following situation - we have a solution which we deploy on SAP Cloud Platform. This solution consumes backing services from different hyper-scalers - such as AWS or GCP. Naturally, we would like to have a single approach to receive alerts from both our solution on SAP Cloud Platform and the hyper-scalers services that it uses. Furthermore, we want to do that into an hyper-scaler agnostic manner.

In the next couple of blog posts, we are going to show you precisely how you can receive alerts for the backing services from hyper-scalers via SAP Cloud Platform Alert Notification. That way, you are going to have a common alert management approach for both SAP Cloud Platform and your hyper-scalers regardless of which one you use.

Into that particular blog post, we are going to concentrate on AWS.


To start, you are going to need:

  • Active AWS account

  • An active subscription to SAP Cloud Platform Alert Notification

  • SAP Cloud Platform application deployed on SAP Cloud Platform Cloud Foundry environment and using some of the AWS backing services. You can refer to this blog post to understand more details about this topic.


In this particular case, we are going to have the setup below.

  1. The example application is consisting of two modules. It is living on SAP Cloud Platform Cloud Foundry environment. It is already sending custom alerts to Alert Notification. More about custom alerts read here.

  2. This application uses DynamoDB instantiated on AWS as a NoSQL backing service.

  3. We are using AWS CloudWatch, AWS SNS to monitor the backing service

  4. We are using AWS Lambda to post custom alerts to SAP Cloud Platform Alert Notification

  5. Our sample application is also posting its application's specific custom alerts to Alert Notification. For example, it posts an error alert whenever an exception in its code occurs.

Steps to Execute

Follow the steps below to achieve similar results.

Configure your Alert Notification

We are going to start by creating our configuration for Alert Notification. Firstly we should create a subscription, and also, we are going to create a user for basic authentication. That's right Alert Notification REST APIs support both OAuth and Basic authentication methods.

Configure BASIC Authentication Client

  1. Subscribe for Alert Notification if you haven't done so.

  2. Navigate to your Alert Notification service instance UI

    1. In SAP Cloud Platform Cockpit navigate to your Cloud Foundry Space -> Services -> Service Instance -> Click on your instance

  3. In the menu, select "Service Keys" and then click on the create service key button.

  4. In the popup give your keys a name, for example, "AWS Integration Keys" and in the description field copy and paste the following JSON:

  5. These are the client, secret and endpoint, which we are going to use for our integration.

Configure Subscriptions

In this section, we are going to use one of the coolest features of SAP Cloud Platform Alert Notification. The import feature. We have preconfigured the subscriptions and actions for you.

  1. Copy-Paste the provided JSON below into some text editor.
    "conditions": [
    "name": "AnyCondition",
    "propertyKey": "eventType",
    "predicate": "ANY",
    "propertyValue": "",
    "labels": [],
    "description": ""
    "actions": [
    "name": "NotifyMeByEmail",
    "state": "ENABLED",
    "labels": [],
    "destination": "",
    "description": "",
    "type": "EMAIL"
    "subscriptions": [
    "name": "AWSDynamoDBAlert",
    "conditions": [
    "actions": [
    "labels": [],
    "state": "ENABLED",
    "description": ""

  2. Replace the "" with the email you want to receive alerts. If you would like to use another channel different than email, create a new action and attach it to your subscription.

  3. In the Alert Notification UI, click on "Export or Import".

  4. Copy-Paste the modified JSON into the import field and click on "Import".

  5. Now the only thing left is to confirm your email.

  6. Go to the "Actions" menu and click on the "NotifyMeByEmail" tile.

  7. Click on "Confirm Action" button.

  8. You are going to receive an email with confirmation code. Copy the code and post it into the popup. Then click the "Confirm" button.

Note that you can fine-tune the provided subscription. Currently, it accepts any alert coming to Alert Notification. To achieve better filtering, you can play around with the provided condition in the Conditions tab of the menu. For hyper-scaler alerts, we recommend the usage of tags to achieve better results.

Configure your AWS

Below is a one-time configuration which you should execute on in your AWS account.

We assume that you already have an instance of DynamoDB or some other service that you use in your application.

We are going to use a Node.js based function-as-a-service from AWS Lambda to integrate with SAP Cloud Platform Alert Notification.

Since AWS Lambda currently does not support installing modules, we should upload our Node.js app as a zip file.

Below you can find the code that we have used for our example.
'use strict';

const request = require('request');
const util = require('util');

const REQUEST_TIMEOUT = 10000;
const MSG_ATTRIBUTE_KEYS = ["Name", "Type", "Value"];
const UNKNOWN_RESOURCE = "unknown";

exports.handler = (event, context, callback) => {
let events = convertRecordsToAnsEvents(event.Records);

let hasError = false;
let tempError = undefined;

for (let event of events) {
console.log("Posting event: ");
console.log(util.inspect(event, {depth: null}));
let options = buildOptions(event);
request(options, function(error, response, body) {
if(error) {
hasError = true;
tempError = error;
console.log("Successfully posted to ANS");

return hasError ? callback(null, 202) : callback(Error(tempError));

const convertRecordsToAnsEvents = (records) => {
let tempAnsEvents = [];

for(let record of records) {

return tempAnsEvents;

const buildOptions = (body) => {
return {
url: process.env.ANS_SERVICE_API,
method: "POST",
auth: {
user: process.env.CLIENT_ID,
password: process.env.CLIENT_SECRET
json: body,

const convertToAnsPayload = (notification) => {
let snsNotification = notification || {};

return {
"eventType": snsNotification.Sns.Type,
"severity": "INFO",
"category": "NOTIFICATION",
"subject": snsNotification.Sns.Subject,
"body": snsNotification.Sns.Message,
"resource": {
"resourceName": UNKNOWN_RESOURCE,
"resourceType": UNKNOWN_RESOURCE
"tags": buildTags(snsNotification)

const buildTags = (snsNotification) => {
let tempTags = {
"sns:messageId": snsNotification.Sns.MessageId,
"sns:topicArn": snsNotification.Sns.TopicArn,
"sns:timestamp": snsNotification.Sns.Timestamp,
"sns:eventSource": snsNotification.EventSource,
"sns:subscriptionArn": snsNotification.EventSubscriptionArn
let messageAttributes = extractMessageAttributes(snsNotification.Sns.MessageAttributes);

return Object.assign(tempTags, messageAttributes);

const extractMessageAttributes = (attributes) => {
let tempAttrubutes = {};

let buildKey = function(parentKey, childKey) {
return `${parentKey}.${childKey}`;

for (let [parentKey, value] of Object.entries(attributes)) {
for (let messageAttributeKey of MSG_ATTRIBUTE_KEYS) {
if (value.hasOwnProperty(messageAttributeKey)) {
let key = buildKey(parentKey, messageAttributeKey);
tempAttrubutes[`${key}`] = value[messageAttributeKey];

return tempAttrubutes;

Another option is to use the shared Lambda function from here.

Note that this is just a code snippet and you can decide not to use it or to change it or to proceed with your own implementation.

Importing sample function into AWS Lambda

  1. In the AWS Console look-up for Lambda and select it.

  2. Click on the "Create Function" button and give it some meaningful name

  3. In our example, we are using Node.js 8.10 version to cover not only AWS but also other hyper-scalers with the same code.

  4. In the Function Code section, as a "Code entry type" select "Upload a .zip file" and upload the zip file that you have assembled.

  5. Once the import of the function finishes, navigate to the "Environment Variables" section. Here you should fill the endpoint and the client and secret which you have configured in the "Configure BASIC Authentication" section of that blog post.

  6. Once you fill this, click on the "Save" button.

Configuring AWS Simple Notification Service

Now once we have our function-as-a-service in place, it is time to configure SNS working with it.

  1. In the AWS Console look-up for SNS and select it.

  2. In the UI click on the "Topics" menu

  3. Click on "Create Topic" and give it some meaningful name.

  4. Once you do that, click on "Create Subscription".

  5. As Protocol select "AWS Lambda". Click on the "Endpoint" field and from the dropdown select the lambda function you have just created.

Creating an alarm via AWS CloudWatch

The final step is to create an alarm which has to execute the function in case of a problem.

  1. In the AWS Console look-up for CloudWatch and select it.

  2. Go to the "Alarms" menu and click on "Create Alarm".

  3. Click on "Select Metric" and select the metrics in which you are interested. In our case, we have selected the AccountMaxRead metric.

  4. Set some threshold and click on "Next".

  5. Select "Select an existing SNS topic" radio button. From the dropdown field "Select a notification to..." select the topic you just created.

  6. Click on Next and give some meaningful alarm name. Click on "Next" and then click on "Create alarm".

From now on, whenever your alarm passes the threshold, you are going to receive an email via the very same channel from where you receive your other alerts. Here's a sample email that you will receive

What's Next

You can fine-tune and play around with this configuration.

We are working on similar blogs for providing integration with other hyper-scalers like Google Cloud Platform. Also, this integration will evolve over time and the format and the way how we display notifications will be much more appealing.

We are working on many cool features - like fallback channels for alert, alerts for CPI integration flows, lifecycle management alerts for applications, templating of alerts towards different systems like JIRA and many more.