From 296d5b2ca2d5b3907df25d34303db4b9c34b9472 Mon Sep 17 00:00:00 2001 From: Katie Horne Date: Wed, 27 Oct 2021 10:45:30 -0500 Subject: [PATCH 1/2] Update Route 53 doc --- guides/tls-certificates/route53.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/guides/tls-certificates/route53.md b/guides/tls-certificates/route53.md index a650ef7e6..5fd684800 100644 --- a/guides/tls-certificates/route53.md +++ b/guides/tls-certificates/route53.md @@ -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/) @@ -98,7 +98,13 @@ To make sure that your `clusterIssuer` can change your DNS settings, 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. +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=" +``` ## Step 4: Create the ACME Issuer From 877f07db1c4ab1383a94b76a5475e52edfbd77cd Mon Sep 17 00:00:00 2001 From: Katie Horne Date: Wed, 27 Oct 2021 10:46:32 -0500 Subject: [PATCH 2/2] fix typo --- guides/tls-certificates/route53.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/tls-certificates/route53.md b/guides/tls-certificates/route53.md index 5fd684800..e13c4c7c0 100644 --- a/guides/tls-certificates/route53.md +++ b/guides/tls-certificates/route53.md @@ -97,7 +97,7 @@ 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 +`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