I have a google managed domain, and a lambda based api in aws api gateway. I want to create a sub domain that points to api gateway.
I created an ACM Certificate using aws certificate manager. This included creating CNAME credentials, which were imported into my google domain. AWS performed the handshake and validate the credentials.
I then created a custom domain in aws api gateway. I named it the same as the acm certificate's domain, api.coopstools.com, and attached it to the acm certificate. I then added the base path mapping to the API I created in lambda.
(as a side note, I can hit and use the API using the default url that is provided when I staged the API, so I know it's up and running)
I did this all more than 24 hours ago (knowing that it sometimes takes a while).
I've tried hitting the endpoint to no avail, just receiving a "Could not resolve host: ..." message.
The dig result shows that the core domain has authority, but none of the subdomain show up.
Am I missing a piece in here? Or, are there any specific pieces of information needed to help me?
Thanks for any help,
P.S. I apologize for not giving more specific details as I still haven't figured out some of the security settings, and don't want to over expose anything.
EDIT: The issue was fixed thanks to @Joseph. All I had to due was the take the Target Domain Name from the custom domain in api gateway, and use it to create a new CNAME entry in the Custom Resource Records of Google Domains (the same place I put the original CNAME for creating the ACM certificate). It took about a minute and a half for everything to update.