Skip to content

chore: added secret creation command to Route 53 doc #691

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Oct 29, 2021
Merged

chore: added secret creation command to Route 53 doc #691

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
296d5b2
Update Route 53 doc
Oct 27, 2021
877f07d
fix typo
Oct 27, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 9 additions & 3 deletions guides/tls-certificates/route53.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ You must have:
You should also:

- Be a cluster admin
- Have access to your DNS provider.
- Have access to your DNS provider
- Have an AWS account so that you can access
[Route 53](https://aws.amazon.com/route53/) and
[IAM](https://aws.amazon.com/iam/)
Expand Down Expand Up @@ -97,8 +97,14 @@ To make sure that your `clusterIssuer` can change your DNS settings,
[create the required IAM role](https://cert-manager.io/docs/configuration/acme/dns01/route53/#set-up-an-iam-role)

When you create the secret for cert-manager, referenced below as
`route53-credentials` be sure it is in the cert-manager namespace since it's
used by the cert-manager pod to perform DNS configuration changes.
`route53-credentials`, be sure it is in the cert-manager namespace since it's
used by the cert-manager pod to perform DNS configuration changes:

```console
kubectl --namespace cert-manager \
create secret generic route53-credentials \
--from-literal="secret-access-key=<YOUR-AWS-SECRET-ACCESS-KEY>"
```

## Step 4: Create the ACME Issuer

Expand Down