Fix the SNS configuration for deploy_cloudtrail_cloudformations

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
aws, python
Domain
cloud, devops

Research direction

Start by locating the deploy_cloudtrail_cloudformations entry point and its SNS configuration, then reproduce the reported InvalidClientTokenId error with AWS. Trace how the tool currently writes to STDOUT and identify the disabled SNS path. Done means the tool emits the output through both SNS and STDOUT without the reported configuration error.

Written by the indexing model from the issue text.

Description

Currently SNS is disabled because it causes errors

"Code":"InvalidClientTokenId",
"Message":"No account found for the given parameters",
"Type":"Sender"

Troubleshoot this with AWS and update the tool to emit its output through SNS in addition to STDOUT

Dominant language
Python
Stars
44
Forks
16
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 mozilla/security

All issues in mozilla/security

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.