Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow AWS keys to be optional #1

Open
NickLarsenNZ opened this issue Jun 11, 2021 · 0 comments
Open

Allow AWS keys to be optional #1

NickLarsenNZ opened this issue Jun 11, 2021 · 0 comments

Comments

@NickLarsenNZ
Copy link

I'm using a github action to assume a role, so my credentials/session key are already set.
It would be nice to not have to supply them again.

Eg:

    - name: Assume AWS Role
      uses: aws-actions/configure-aws-credentials@v1
      with:
        aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
        aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
        aws-region: us-east-1
        role-to-assume: arn:aws:iam::XXXXXXXXXXXXX:role/example-role
        role-duration-seconds: 1200

    - name: Upsert DNS Record
      uses: Roosterfish/aws-route53-record-set-action@master
      with:
        # No need to set the access key
        # aws_access_key_id: ${{ secrets.AWS_ACCESS_KEY_ID }}
        # aws_secret_access_key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
        aws_route53_hosted_zone_id: Z9876312478623
        aws_route53_rr_action: "CREATE"
        aws_route53_rr_name: "your-fqdn.example.com"
        aws_route53_rr_type: "A"
        aws_route53_rr_ttl: "300"
        aws_route53_rr_value: "1.2.3.4"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant