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

Allow reading payload parameters from secret / parameter store

Open
#5 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
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
aws, python
Domain
cloud, security

Research direction

No files or tests are named in the issue. Start by locating the Lambda payload handling and AWS configuration, then trace how values are sent to the HTTP endpoint. Done means payload values using both specified forms are resolved from the corresponding AWS store before the request is made, without exposing the secrets in the payload.

Written by the indexing model from the issue text.

Description

enhancement lambda-http-check

In case of authorization headers needing to be sent to HTTP(s) endpoint - they should be stored in secret store, rather than passed unencrypted as payload to lambda function. Suggestion is that if any value in payload is in following forms

  • aws:smps("path")
  • aws:sm("store.key")

They should be replaced with actual secret value from AWS System Manager Parameter Store (first form), or AWS Secrets Manager (2nd form).

Dominant language
Python
Stars
33
Forks
16
PR merge metrics
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 base2Services/aws-lambda-http-check

All issues in base2Services/aws-lambda-http-check

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.