Closed kevin-lindsay-1 closed 2 years ago
As previously mentioned, I have a fairly simple workaround, that being setting a subdomain and setting an ALIAS manually.
For example:
service FQDN: api.api.mydomain.com
then, in Route 53, set apex (no name) to an A Alias record to api.api.mydomain.com
.
Less than ideal, but it appears to work just fine.
This issue has not received any attention in 1 year. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.
Now, technically I understand that this isn't a bug, as both of these parameters,
domainZone
anddomainName
are required, however I'm running into a particular issue where I can't assign an A record to the root of a zone.For example, let's say I have a hosted zone for:
api.mydomain.com
In that zone, I have other APIs,
user.api.mydomain.com
,product.api.mydomain.com
, etc.Since the
@
domain doesn't work in route 53, and this parameter always appends the zone,.api.mydomain.com
, when I provideAWS::NoValue
, it accepts it, but still appends.api.mydomain.com
, whereas it should appendapi.mydomain.com
.I've tried a few workarounds on this issue, but can't seem to find anything that will solve this (other than making a distinction between
api.mydomain.com
and another zone ofapis.mydomain.com
).Example:
outputs:
Should (likely) be:
Reproduction Steps
Error Log
Environment
Other
This is :bug: Bug Report