AWS SNS Slack Subscriber
A library that creates a slack subscriber to your aws sns topic.
Remarks
The project is written by Laimonas Sutkus and is owned by iDenfy. This is an open source library intended to be used by anyone. iDenfy aims to share its knowledge and educate market for better and more secure IT infrastructure.
Related technology
This project utilizes the following technology:
- AWS (Amazon Web Services).
- AWS CDK (Amazon Web Services Cloud Development Kit).
- AWS Lambda.
- AWS Sns.
- Slack.
Install
The project is built and uploaded to PyPi. Install it by using pip.
pip install aws_sns_slack_subscriber
Or directly install it through source.
./build.sh -ic
Description
When you have SNS Topics, you may subscribe to them with various ways. For example, email subscription will send an email to a desired email address when a notification is pushed to a SNS Topic. Most of the time email subscription is not ideal as it may clutter your email box. Hence, there are other ways to subscribe to a SNS Topic. We think the most convenient way to subscribe to SNS Topic is a Lambda Function integration which sends callbacks to your specified Slack channel. This library project is about that. It creates a "Slack subscription" with a help of Lambda.
Examples
Create sns slack subscriber as any other lambda function:
from aws_sns_slack_subscriber.slack_subscriber import SlackSubscriber
lambda_function_slack_subscirber = SlackSubscriber(...)
Release history
2.2.0
Force update 1.60.0 and add upper bound of 2.0.0.
2.1.0
URL and AWS CDK updates.
1.1.1
Completely refactor functionality. Add an explicit pipeline handler. Rewrite everything on python.
1.1.1
Add js file to manifest.
1.1.0
Add ability to specify slack channel.
1.0.0
Initial commit.
Metadata
Release files for aws-sns-slack-subscriber 2.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| aws_sns_slack_subscriber-2.2.0.tar.gz | 5.1 kB | Without provenance | Details for aws_sns_slack_subscriber-2.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aws_sns_slack_subscriber-2.2.0-py3-none-any.whl | Python 3 | none | any | Details for aws_sns_slack_subscriber-2.2.0-py3-none-any.whl |
Total release size: 26.3 kB
Release files / aws_sns_slack_subscriber-2.2.0.tar.gz
| Download URL | aws_sns_slack_subscriber-2.2.0.tar.gz |
|---|---|
| Size | 5.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d4a06269d5fb00f49da9c92db882529ecce47caa765257070bb07a425077d011
|
|
BLAKE2b-256 checksum How to use checksums |
77a48195da732880ac6f45e4665e7eef861868d78b7b3cc1739fe0530a0d808e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.6.0 requests-toolbelt/0.9.1 tqdm/4.48.2 CPython/3.6.9
|
Release files / aws_sns_slack_subscriber-2.2.0-py3-none-any.whl
| Download URL | aws_sns_slack_subscriber-2.2.0-py3-none-any.whl |
|---|---|
| Size | 21.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bfbd3f114f35fd02ee91dd0f86523a42904405642f2932d38559ac6d188c96d3
|
|
BLAKE2b-256 checksum How to use checksums |
3d62a0c990e087d34df882c18ed70ef28e07e3f5402d10a6597a562db49490e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.6.0 requests-toolbelt/0.9.1 tqdm/4.48.2 CPython/3.6.9
|
Security for aws-sns-slack-subscriber 2.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.