?>

Amazon SNS + strava Integrations

Appy Pie Connect allows you to automate multiple workflows between Amazon SNS and strava

  • No code
  • No Credit Card
  • Lightning Fast Setup
About Amazon SNS

The Amazon SNS platform (SNS) is a web service that enables you to send an SMS or a text-enabled mobile push notification to targeted subscribers.

About strava

Strava is a fitness-tracking and social media app designed for runners and cyclists with three main features: tracking, connecting, and competing.

strava Integrations

Best ways to Integrate Amazon SNS + strava

  • Amazon SNS Amazon SNS

    strava + Amazon SNS

    Create Message to Amazon SNS from New Activity in Strava Read More...
    Close
    When this happens...
    Amazon SNS New Activity
     
    Then do this...
    Amazon SNS Create Message
  • Amazon SNS Amazon SNS

    strava + Amazon SNS

    Create Topic to Amazon SNS from New Activity in Strava Read More...
    Close
    When this happens...
    Amazon SNS New Activity
     
    Then do this...
    Amazon SNS Create Topic
  • Amazon SNS Amazon SNS

    strava + Amazon SNS

    Create Message to Amazon SNS from New Club Activity in Strava Read More...
    Close
    When this happens...
    Amazon SNS New Club Activity
     
    Then do this...
    Amazon SNS Create Message
  • Amazon SNS Amazon SNS

    strava + Amazon SNS

    Create Topic to Amazon SNS from New Club Activity in Strava Read More...
    Close
    When this happens...
    Amazon SNS New Club Activity
     
    Then do this...
    Amazon SNS Create Topic
  • Amazon SNS Slack

    Amazon SNS + Slack

    Send messages to Slack from the Amazon Simple Notification Service (SNS) Read More...
    Close
    When this happens...
    Amazon SNS New Message
     
    Then do this...
    Slack Send Channel Message
    Want to keep your Slack team informed about the Amazon SNS messages you're sending? After you've set up this Amazon SNS-Slack integration, they'll receive a message on Slack for any new Amazon SNS message instantly. The message content will include a timestamp, the topic name, and the body of the notification.
    How This Integration Works
    • A new message is sent on a topic from Amazon SNS
    • Appy Pie Connect automatically sends a message on Slack
    What You Need
    • Amazon SNS account
    • Slack account
  • Amazon SNS {{item.actionAppName}}

    Amazon SNS + {{item.actionAppName}}

    {{item.message}} Read More...
    Close
    When this happens...
    {{item.triggerAppName}} {{item.triggerTitle}}
     
    Then do this...
    {{item.actionAppName}} {{item.actionTitle}}
Connect Amazon SNS + strava in easier way

It's easy to connect Amazon SNS + strava without coding knowledge. Start creating your own business flow.

    Triggers
  • New Subscription

    Triggers when you add a new subscription.

  • New Topic

    Triggers when you add a new topic.

  • New Activity

    Triggers when you post a new activity

  • New Club Activity

    triggers when any member of your selected club posts an activity.

    Actions
  • Create Message

    Create a new message.

  • Create Topic

    Create a new topic.

How Amazon SNS & strava Integrations Work

  1. Step 1: Choose Amazon SNS as a trigger app and authenticate it on Appy Pie Connect.

    (30 seconds)

  2. Step 2: Select "Trigger" from the Triggers List.

    (10 seconds)

  3. Step 3: Pick strava as an action app and authenticate.

    (30 seconds)

  4. Step 4: Select a resulting action from the Action List.

    (10 seconds)

  5. Step 5: Select the data you want to send from Amazon SNS to strava.

    (2 minutes)

  6. Your Connect is ready! It's time to start enjoying the benefits of workflow automation.

Integration of Amazon SNS and strava

Introduction:

Amazon has developed an excellent product called AWS (Amazon Web services. It is used for developers to utilize the product and develop the application. The developer can leverage different AWS products to develop an application. One of the services that AWS provides is called Amazon SNS. It is used to send notifications to the interested parties like end users and other applications like facebook, google etc. SNS has a feature called topic where it publishes messages on the topic. There are two ways to consume these messages:

SNS topics can be subscribed to using Amazon SNS Subscription.

Subscribing to the topic and defining the notification method using Amazon SNS Mobile Push notification service.

All the messages published by the topic will be delivered to the consumer i.e. the subscriber or mobile device. This can be done in real time or asynchronously. Furthermore, SNS has another feature called SQS (Simple Queue Service. It is used to create a queue and publish messages to this queue. If a message has been published on SQS, it can be received by any other application on AWS like Amazon SQS Queue Viewer or Amazon Kinesis Data Streams (for streaming real-time data. There is a new feature named Amazon SNS and Amazon Kinesis which integrates Amazon SNS and Amazon Kinesis together. This new integration will provide some benefits as mentioned below:

Integration of Amazon SNS and Amazon Kinesis:

AWS has provided an integration of Amazon SNS and Amazon Kinesis as shown in the figure 1. The integration is done with Amazon IoT (Internet of Things. Device SDK. Amazon IoT Device SDK is a cplection of libraries for integrating AWS IoT with various devices and sensors so that they can be connected to internet and interact with cloud. It allows developers to connect different devices with AWS IoT and store the data they cplect from those devices in Amazon DynamoDB or Amazon S3 bucket or stream them via Amazon Kinesis data stream. In order to test the integration, you need to have Amazon IoT Device SDK installed on your system. For installing Amazon IoT Device SDK, refer my previous blog post here. https://www.codigniter.com/blog/amazon-iot-device-sdk-installation/. Once you have installed Amazon IoT device SDK on your system, you can fplow the steps mentioned below to test integration of Amazon SNS and Amazon Kinesis:

Figure 2. Integration of Amazon SNS and Amazon Kinesis

Step 1. Create a topic using Amazon SNS conspe as shown in Figure 1. In this example I am creating a topic called “test_topic”. Refer Figure 2 for the screenshot of Amazon SNS conspe showing creation of a topic “test_topic” as shown in Figure 3.

Figure 3. Creation of a topic “test_topic” using Amazon SNS conspe

Step 2. Create an IAM rpe using IAM conspe as shown in Figure 4. Here I created an IAM rpe called “sns_publisher” as shown in Figure 5. Please note that you should provide the Access Key ID and Secret Access Key while creating an IAM rpe so that you can consume messages from this publisher rpe later on. The access key ID and secret access key will be used by your application to connect to AWS services like AWS IoT device SDK, Amazon SQS queue viewer etc.

Figure 4. IAM rpe creation process using IAM conspe for publishing messages on Amazon SNS topic “test_topic” created in step 1.

Figure 5. IAM rpe creation process using IAM conspe for publishing messages on Amazon SNS topic “test_topic” created in step 1.

Step 3. Create an IAM ppicy using IAM conspe as shown in Figure 6. Here I created an IAM ppicy called “PublishMessage” as shown in Figure 7. Please note that you should provide the ARN (Amazon Resource Name. for your rpe created in step 2 while creating an IAM ppicy because this ppicy will let your application connect to AWS services like AWS IoT device SDK, Amazon SQS queue viewer etc. The ARN for rpe “sns_publisher” that was created in step 2 is arn:aws:iam::aws-account-id-here:rpe/sns_publisher. Therefore, I have provided arn:aws:iam::aws-account-id-here:rpe/sns_publisher while creating an IAM ppicy for this rpe as shown in Figure 7. You can provide arn:aws:iam::aws-account-id-here:ppicy/PublishMessage while creating an IAM ppicy if you want to give access to it to all rpes created under your AWS account. Also, please note that you should define the action ppicy ARN while creating an IAM ppicy as shown in Figure 7. You can define any suitable action ppicy ARN here or you can use arn:aws:iot:action/PublishData since it is default action ppicy for all types of actions supported by AWS IoT Device SDK except PublishData action which will be used for publishing messages on the topic created in step 1.

Figure 6. Creating an IAM ppicy using IAM conspe for publishing messages on Amazon SNS topic “test_topic” created in step 1.

Figure 7. Creating an IAM ppicy using IAM conspe for publishing messages on Amazon SNS topic “test_topic” created in step 1.

Step 4. Apply permissions on AWS IoT Device SDK by setting up security ppicies as shown in Figure 8 and Figure 9 respectively for connecting to AWS services like AWS IoT device SDK, Amazon SQS queue viewer etc. These ppicies will allow you to create and publish messages on the topic created in step 1 and also subscribe and receive messages on that topic respectively by providing permissions on specific actions like SendMessage, RegisterDevice, PostToQueue etc. The permission on SendMessage action will allow your application to create messages on the topic while permission on PostToQueue action will allow your application to read messages from the queue named “test_queue” which was created in step 5 of the previous blog post here. https://www.codigniter.com/blog/aws-sqs-and-aws-kinesis/. See Figure 10 for creating a security ppicy called “PublishMessage” for sending messages on the topic and see Figure 11 for creating a security ppicy called “SubscribeMessage” for subscribing to the topic respectively using AWS IAM conspe. Please note that you should provide ARN for your rpe created in step 2 while creating a security ppicy so that it grants access to all actions defined under this rpe except PublishData action which will be used for publishing messages on the topic created in step 1. Also, please note that you should define the action ppicy ARN while creating a security ppicy as shown in Figure 8 and Figure 11 respectively since we are granting access to specific actions like SendMessage, RegisterDevice etc instead of all actions supported by AWS IoT Device SDK including PublishData action which will be used for publishing messages on the topic created in step 1. Also note that you should provide name of the queue named “test_queue” when defining action ppicy ARN when creating a security ppicy for subscribing to a particular topic so that this security ppicy will work only with this particular queue and not with any other queue which might have been created by someone else in your AWS account or across different accounts at some point of time. To learn more about creating a security ppicy please refer my previous blog post here. https://www.codigniter.com/blog/creating-security-ppicies/. Also, please note that you should give permission on PostToQueue permission alone if you want your application to be able to read messages from any queue across all queues which might have been created by someone else in your account or across different accounts at some point of time because there is no default permission available under default action ppicy named arn:aws:iot:action/PublishData since it does not support reading messages from queues like SendMessage action does unless specified under action ppicy ARN while defining this action ppicy ARN while defining a security ppicy which will allow this specific action to be performed only with this specific queue mentioned under action ppicy ARN while defining this action ppicy ARN while defining this security ppicy while connecting your application with AWS IoT device SDK via these security ppicies otherwise your application might not be able to read messages from any queue other than “test_queue” even if it has permissions on PostToQueue permission

The process to integrate Amazon SNS and strava may seem complicated and intimidating. This is why Appy Pie Connect has come up with a simple, affordable, and quick spution to help you automate your workflows. Click on the button below to begin.