This is because you are trying to request a certificate for the elasticbeanstalk.com domain. You will not be able to get a certificate for this domain because you do not own it :). You also cannot set https for the standard domain bean blocks that they give you.
You must use ACM to obtain a certificate for your custom domain, which you plan to do for the CNAME record.
Example:
If you must own, tell the domain amyneville.com . You can create a certificate through ACM for this domain.
If you use your own domain, you do NOT need to get a certificate for the elasticbeanstalk.com domain.
A couple more things:
You cannot create a CNAME record on TLD ( amyneville.com ). You can create a CNAME record for www.amyneville.com . Therefore, if you want to use the CNAME approach, you will need to create a non-www redirect to www. .
But better than CNAME would use record A and point it to the elastic beanstalk resource that was configured. So the load balancer that was created for you uses the A record.
Last but not least, you cannot apply the ACM certificate through the elastic beanstalk console. Instead, you have to use AWS CLI tools. Here's a link on how to do this: fooobar.com/questions/556348 / ...
Kirill Fuchs
source share