You need to do these steps below in all domains that you will need a certificate and you need to do in the region that you created the resources and in North Virginia region (US-EAST-1) : To use an ACM certificate with Amazon CloudFront, you must request or import the certificate in the US East (N. Virginia) region. ACM certificates in this region that are associated with a CloudFront distribution are distributed to all the geographic locations configured for that distribution.
To request an ACM public certificate (console)
1) Sign into the AWS Management Console and open the ACM console https://console.aws.amazon.com/acm/home
2) Choose Request a certificate.
3) On the Request a certificate page, choose Request a public certificate and Request a certificate to continue.
4) On the Add domain names page, type your domain name. You can use a fully qualified domain name (FQDN), such as www.example.com, or a bare or apex domain name such as example.com. You can also use an asterisk (*) as a wild card in the leftmost position to protect several site names in the same domain. For example, *.example.com protects corp.example.com, and images.example.com. The wild card name will appear in the Subject field and the Subject Alternative Name extension of the ACM certificate.
Note: When you request a wild card certificate, the asterisk (*) must be in the leftmost position of the domain name and can protect only one subdomain level. For example, *.example.com can protect login.example.com, and test.example.com, but it cannot protect test.login.example.com. Also note that *.example.com protects only the subdomains of example.com, it does not protect the bare or apex domain (example.com). To protect both, see the next step.
5)To add another name, choose Add another name to this certificate and type the name in the text box. This is useful for protecting both a bare or apex domain (such as example.com) and its subdomains such as *.example.com).
When you finish adding names, choose Next.
6) On the Select validation method page, choose either DNS validation or Email validation, depending on your needs. If you are able to edit your DNS configuration, we recommend that you use DNS domain validation rather than email validation. DNS validation has multiple benefits over email validation.
Before ACM issues a certificate, it validates that you own or control the domain names in your certificate request. You can use either email validation or DNS validation. If you choose email validation, ACM sends validation email to three contact addresses registered in the WHOIS database and to five common system administration addresses for each domain name. You or an authorized representative must reply to one of these email messages. For more information, see Using Email to Validate Domain Ownership. If you use DNS validation, you simply add a CNAME record provided by ACM to your DNS configuration. For more information about DNS validation, see Using DNS to Validate Domain Ownership.
7) On the Add tags page, you can optionally tag your certificate. Tags are key/value pairs that serve as metadata for identifying and organizing AWS resources. For a list of ACM tag parameters and for instructions on how to add tags to certificates after creation, see Tagging AWS Certificate Manager Certificates.
8) When you finish adding tags, choose Review.
9) If the Review page contains correct information about your request, choose Confirm and request. A confirmation page shows that your request is being processed and that certificate domains are being validated. Certificates awaiting validation are in the Pending validation state. After choosing a validation method, choose Next.