From 5e285de8b096a07a353e071ee90ff799dacaf8a0 Mon Sep 17 00:00:00 2001 From: Zinovii Dmytriv Date: Wed, 5 Jul 2023 19:52:33 +0300 Subject: [PATCH] Fixed broken links in READMEs (https://github.com/cloudposse/terraform-aws-components/pull/749) --- src/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/README.md b/src/README.md index 0c54054..82d3527 100644 --- a/src/README.md +++ b/src/README.md @@ -2,7 +2,7 @@ This component is responsible for requesting an ACM certificate for a domain and adding a CNAME record to the DNS zone to complete certificate validation. -The ACM component is to manage an unlimited number of certificates, predominantly for vanity domains. While the [dns-primary](/reference-architecture/components/dns-primary) component has the ability to generate ACM certificates, it is very opinionated and can only manage one zone. In reality, companies have many branded domains associated with a load balancer, so we need to be able to generate more complicated certificates. +The ACM component is to manage an unlimited number of certificates, predominantly for vanity domains. While the [dns-primary](/components/library/aws/dns-primary) component has the ability to generate ACM certificates, it is very opinionated and can only manage one zone. In reality, companies have many branded domains associated with a load balancer, so we need to be able to generate more complicated certificates. We have, as a convenience, the ability to create an ACM certificate as part of creating a DNS zone, whether primary or delegated. That convenience is limited to creating `example.com` and `*.example.com` when creating a zone for `example.com`. For example, Acme has delegated `acct.acme.com` and in addition to `*.acct.acme.com` needed an ACM certificate for `*.usw2.acct.acme.com`, so we use the ACM component to provision that, rather than extend the DNS primary or delegated components to take a list of additional certificates. Both are different views on the Single Responsibility Principle.