Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

custom message in the SNS

Open
#6 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, github-actions, shell
Domain
cloud, devops

Research direction

Review how the commit file inside app.tgz is uploaded to S3 and how the SNS payload is assembled. Compare that flow with triggering a CodeDeploy deployment through an API call carrying the commit ID. Done means the deployment alert can relate the deploy-id to the commit-id, including in Slack notifications.

Written by the indexing model from the issue text.

Description

I am currently storing the commit ID in a file named (commit) within the file that is updated to the S3. Is there a way to read the file so that it can be used within the SNS payload and I could I relate the deploy-id with the commit-id when sending alerts for example via slack.

Currently the alerts look like this:

[test] - Deployment d-705FE8ZY4 app-title : i-0d910a1c70be24407 Succeeded
ApplicationStop: Succeeded
DownloadBundle: Succeeded
BeforeInstall: Succeeded
Install: Succeeded
AfterInstall: Succeeded
ApplicationStart: Succeeded
ValidateService: Succeeded

But I haven't found how to use/read the commit file that is within the app.tgz so that I could use is as the title, or wondering if instead of triggering automatically the pipeline by updating the file in S3, is there a way to trigger the deploy via an API call in where I could there add a custom payload (pass the commit Id) and use it?

Dominant language
Shell
Stars
151
Forks
214
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws-samples/aws-codedeploy-github-actions-deployment

All issues in aws-samples/aws-codedeploy-github-actions-deployment

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.