External-dns: Where to provide AWS KEY ID and ACCESS KEY?

[dondreytaylor]

It's unclear where to provide the AWS key ID and access key after creating it for external-dns. The documentation only shows you how to specify the IAM role name and account number within the external-dns deployment, but doesn't show where to specify the credentials.

Here is the documentation I'm following to setup Route 53 access for external dns.
https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/aws.md

[mleklund]

I am not 100% sure about AWS_ACCESS_KEY_ID, and AWS_SECRET_ACCESS_KEY but I know that AWS_SHARED_CREDENTIALS_FILE works where you can feed it the path to a creds file in normal ini format:

[default]
aws_access_key_id = XXXXX
aws_secret_access_key =XXXXX

I suspect you could also feed it and AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY as ENV variables and it would work. This is not well documented and _I THINK_ is based upon those ENVs being used by the upstream AWS library they are using.

I found the AWS_SHARED_CREDENTIALS_FILE by snooping bitnami's helm file.

Hope this helps.

[seanmalloy]

/triage support

[seanmalloy]

/kind documentation

[dondreytaylor]

Thanks @mleklund, appreciate the help! Just tried setting _AWS_ACCESS_KEY_ID_ and _AWS_SECRET_ACCESS_KEY_ as ENV variables on the ec2 worker node that external-dns was deployed to and it worked perfectly. Supplying the variables within a file referenced by the environment variable AWS_SHARED_CREDENTIALS_FILE also worked.

[mleklund]

Probably would be worthwhile to add documentation for this. I may add a pull request if time permits.

[seanmalloy]

This should be documented somewhere for end users.

/reopen
/remove-triage support
/help

[k8s-ci-robot]

@seanmalloy: Reopened this issue.

In response to this:

This should be documented somewhere for end users.

/reopen
/remove-triage support
/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[seanmalloy]

My understanding is that we still need someone to update the documentation.

/remove-lifecycle stale