Security News
tea.xyz Spam Plagues npm and RubyGems Package Registries
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
aws-secrets-manager-actions2
Advanced tools
Readme
This GitHub Action helps you define your secrets that stored in AWS Secrets Manager to environment values.
steps:
- name: Store ENV from AWS SecretManager
uses: say8425/aws-secrets-manager-actions@v1
with:
AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
AWS_DEFAULT_REGION: ${{ secrets.AWS_DEFAULT_REGION }}
SECRET_NAME: ${{ secrets.SECRET_NAME }}
OUTPUT_PATH: '.env' # optional
EXPORT_TO_ENV: true
Add your AWS IAM keys and you secret name that you want to use from your AWS Secrets Manager secrets list. Then your secrets will be defined environment values.
You need AWS IAM user that has proper policy to access AWS Secrets Manager.
If you have it, then add this IAM user keys at AWS_ACCESS_KEY_ID
, AWS_SECRET_ACCESS_KEY
and region AWS_DEFAULT_REGION
.
But we greatly recommend to store these keys at GitHub Secrets.
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "VisualEditor0",
"Effect": "Allow",
"Action": "secretsmanager:GetSecretValue",
"Resource": "*"
}
]
}
If you need policy example, then feel free to use this above policy. And you can get more information at AWS User Guide.
Add you want to use secret name from your AWS Secrets Manager secrets list. You can use only one secret name.
Your secrets will be environment values.
And these environment values are masked with ***
. So never be revealed.
Most of the secrets are can be parsed.
But some case, parsing can be failed, like invalid json.
In this case, this unparsed raw sting will be stored in asm_secret
env key.
You can export these environment variables to file with OUTPUT_PATH
input parameter.
When you define OUTPUT_PATH
, then action create a file named as you defined.
And environments will be exported into this file.
If you only want to write the secrets to a file, and not export them to the environment, set EXPORT_TO_ENV: false
in the action inputs. Otherwise, you must set EXPORT_TO_ENV: true
.
Your Contributions are always welcome! Feel free to check issues or Pull Requests
This project is MIT licensed.
FAQs
GitHub Actions for AWS Secrets Manager
The npm package aws-secrets-manager-actions2 receives a total of 4 weekly downloads. As such, aws-secrets-manager-actions2 popularity was classified as not popular.
We found that aws-secrets-manager-actions2 demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
Security News
As cyber threats become more autonomous, AI-powered defenses are crucial for businesses to stay ahead of attackers who can exploit software vulnerabilities at scale.
Security News
UnitedHealth Group disclosed that the ransomware attack on Change Healthcare compromised protected health information for millions in the U.S., with estimated costs to the company expected to reach $1 billion.