-
Notifications
You must be signed in to change notification settings - Fork 42
Description
This is not an issue. Please pardon me as I do not know where to put this
So I am implementing Github OpenID connect to retrieve secrets from AWS secretsmanager instead AWS user that uses AWS credentials. I do not want to store any secrets using Github secret. It also look like OpenID Connect is Git action's preferred method of authentication into AWS. So I went for it with terraform aws_iam_openid_connect_provider
resource as seen https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_openid_connect_provider
Here is my workflow after deploying the AWS role
jobs:
trigger-build:
runs-on: ubuntu-latest
steps:
- name: Configure AWS Credentials
uses: aws-actions/configure-aws-credentials@v1
with:
aws-region: us-east-1
role-to-assume: arn:aws:iam::{aws_account_id}:role/AWSRole
audience: sts.amazonaws.com
- name: Read secrets from AWS Secrets Manager into environment variables
uses: bitovi/github-actions-aws-secrets-manager@v2.0.0
with:
secrets: |
my_secret
parse-json: true
- name: Trigger Pipeline
env:
CIRCLE_BRANCH: ${{ github.head_ref }}
TOKEN: ${my_secret}
My concern/question (and please forgive my naivety) is that: is it possible for an attacker to copy this entire code and use it in a different git action jobs to access my secrets `my_secret'? I don't seems to find additional protection for this chunk of code