blocks|key|2893528|text|与这里相关的不是域根。它是位于您输入的级别下的的子域。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2893529|2893530|如果输入auth.example.com，则需要example.com+|unordered-list-item|CODE|2893531|的A记录如果输入auth.qa.example.com，则需要qa.example.com+|2893532|的A记录|2893533|如果输入foo.bar.qa.example.com，则需要D14的A记录|2893534|2893535|entityMap^0|9|1|N|4|0|0|0|Z|4|G|O|B|0|0|19|8|J|V|E|0|0|4|0|0|11|4|M|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|J]|$9|14|A|15|B|J]]|D|@]|E|$]]|$1|K|3|L|5|I|7|16|8|@$9|17|A|18|B|C]|$9|19|A|1A|B|J]|$9|1B|A|1C|B|J]]|D|@]|E|$]]|$1|M|3|N|5|6|7|1D|8|@$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|O|3|P|5|I|7|1G|8|@$9|1H|A|1I|B|C]|$9|1J|A|1K|B|J]]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|1L|8|@]|D|@]|E|$]]|$1|R|3|-4|5|6|7|1M|8|@]|D|@]|E|$]]]|S|$]]

It isn't the domain root that is relevant here. It's the subdomain that sits at the level below the one you enter.

<ul>
<li>If you enter <code>auth.example.com</code>, you need an A record for
<code>example.com</code> </li>
<li>If you enter <code>auth.qa.example.com</code>, you need an A record
for <code>qa.example.com</code> </li>
<li>If you enter <code>foo.bar.qa.example.com</code> you need
an A record for <code>bar.qa.example.com</code></li>
</ul>

blocks|key|155559|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|155560|您拥有的Web域。其根目录在DNS中必须具有有效A记录。|blockquote|155561|155562|155563|简而言之，如果您的域是example.com，那么在继续之前，需要为网站实际配置根目录--+example.com。A记录的特定值与Cognito无关，因为这将取决于您选择如何设置站点...但是Cognito需要它出现在那里。|offset|length|style|CODE|155564|entityMap^0|0|0|0|0|B|B|1A|B|0^^$0|@$1|2|3|-4|4|5|6|N|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|O|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|P|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|Q|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|R|7|@$H|S|I|T|J|K]|$H|U|I|V|J|K]]|8|@]|9|$]]|$1|L|3|-4|4|5|6|W|7|@]|8|@]|9|$]]]|M|$]]

<blockquote>
 A web domain that you own. Its root must have a valid A record in DNS. 
</blockquote>

In simplified terms, if your domain is <code>example.com</code> then the root -- <code>example.com</code> -- needs to actually be configured for a web site before you continue. The specific value of the A record is not relevant to Cognito, since that would depend on how you choose to set up the site... but Cognito requires it to be there.

blocks|key|158124|text|似乎尝试使用带有太多点的子域会导致此错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|158125|这是可行的：|158126|auth.example.com|158127|这不会：|158128|dev.auth.example.com|158129|此外，如果您删除并重新添加相同的域名，这似乎会导致错误。更改到不同的域是可行的。|158130|我向#awswishlist+https://awswishlist.com/添加了一个修复此问题的请求|offset|length|158131|entityMap|0|LINK|mutability|MUTABLE|url|https://awswishlist.com/^0|0|0|0|0|0|0|F|O|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Z|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|10|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|11|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|12|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|13|8|@]|9|@$N|14|O|15|1|16]]|A|$]]|$1|P|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W]]]]

It seems that trying to use a subdomain with too many dots causes this error. 

This works:

auth.example.com

This does not:

dev.auth.example.com

Also if you remove and re-add the same domain name this seems to cause an error. Changing to a different domain works.

I added a request to fix this to the #awswishlist <a href="https://awswishlist.com/" rel="nofollow noreferrer">https://awswishlist.com/</a>

blocks|key|155653|text|为了处理子域，我用IP+127.0.0.1创建了一个记录，它正在工作。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|155654|我想添加auth.dev.${domain_name}.com作为一个自定义域名，但我没有指向dev.${domain_name}.com的任何网站，所以为dev.${domain_name}.com创建了一个记录，并指向127.0.0.1+ip地址。|155655|Reference|155656|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/holy-order-of-the-lambda-cube/CognitoOauth2S3Website/issues/1^0|C|9|0|4|R|1B|M|33|9|0|0|9|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|11|8|@]|D|@$9|12|A|13|1|14]]|E|$]]|$1|J|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]]]

To deal with subdomains, I have created A record with IP <code>127.0.0.1</code> and it's working.
I wanted to add <code>auth.dev.${domain_name}.com</code> as a custom domain in cognito but I don't have pointing to any website for <code>dev.${domain_name}.com</code> so created A record for dev.${domain_name}.com and pointed to <code>127.0.0.1</code> ip address.
<a href="https://github.com/holy-order-of-the-lambda-cube/CognitoOauth2S3Website/issues/1" rel="nofollow noreferrer">Reference</a>

blocks|key|2064104|text|流行的答案正确地回答了这个问题。但在更高的层次上，还有更多的东西要做。在配置依赖中有一个循环：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2064105|2064106|+Cognito需要auth.example.com+A记录，这需要example.com+A记录。Cognito记录需要一个网站来指向，该网站需要example.com。|blockquote|offset|length|style|CODE|2064107|2064108|2064109|为了打破这个循环，|2064110|2064111|创建一个新的路由53区域auth.example.com，以便独立于网站的example.com区域使用。这打破了依赖循环。|ordered-list-item|2064112|创建了一个指向占位符IP地址(如127.0.0.1+)的auth.example.com+A记录。|2064113|现在您可以为每个环境的Cognito自定义域创建A记录，如dev.auth.example.com、stage.auth.example.com或prod.auth.example.com。|2064114|2064115|下面的Terraform示例将这一切结合在一起，创建了一个Cognito自定义域prod.auth.example.com|2064116|#+Pre-existing+hosted+zone+created+by+Route53+Registrar
data+"aws_route53_zone"+"main"+{
++name+=+"example.com"
}

#+Create+a+new+Route+53+zone+auth.example.com
#
#+Actually,+Route+53+zone+creation+belongs+in+a+separate+Terraform
#+module+where+it+can+be+shared+by+multiple+environments.

resource+"aws_route53_zone"+"auth"+{
++name+=+"auth.example.com"
}

resource+"aws_route53_record"+"auth-ns"+{
++zone_id+=+data.aws_route53_zone.main.zone_id
++name++++=+"auth.example.com"
++type++++=+"NS"
++ttl+++++=+"30"
++records+=+aws_route53_zone.auth.name_servers
}+As+it+is+now,
#+`terraform+destroy`+will+destroy+zone+auth.example.com,+leaving+the+other+environments+in+the+lurch.

#+Only+the+name+servers+in+the+auth.example.com+zone+NS+record+know+where
#+to+find+auth.example.com.+Add+NS+record+in+example.com+pointing+to+the
#+auth.example.com+zone+name+servers.+Now+auth.example.com+can
#+be+found+through+example.com.
resource+"aws_route53_record"+"auth-a"+{
++zone_id+=+aws_route53_zone.auth.zone_id
++name++++=+"auth.example.com"
++type++++=+"A"
++ttl+++++=+300
++records+=+["127.0.0.1"]++#+Placeholder+that+is+never+used
}

#+Route+53+zone+auth.example.com+setup+done

module+"acm"+{
++source+=+"terraform-aws-modules/acm/aws"

++domain_name+++++++++++++++=+"prod.auth.example.com"
++zone_id+++++++++++++++++++=+aws_route53_zone.auth.zone_id
++subject_alternative_names+=+[]
++wait_for_validation+++++++=+true
}

resource+"aws_cognito_user_pool"+"this"+{
++name+=+"prod-cognito"
}

resource+"aws_cognito_user_pool_domain"+"this"+{
++depends_on++++++=+[aws_route53_record.auth-a]
++domain++++++++++=+"prod.auth.example.com"
++certificate_arn+=+module.acm.this_acm_certificate_arn
++user_pool_id++++=+aws_cognito_user_pool.this.id
}

resource+"aws_route53_record"+"subdomain-a"+{
++zone_id+=+aws_route53_zone.auth.zone_id
++name++++=+"prod.auth.example.com"
++type++++=+"A"
++alias+{
++++evaluate_target_health+=+false
++++name+++++++++++++++++++=+aws_cognito_user_pool_domain.this.cloudfront_distribution_arn
++++#+Every+CloudFront+distribution's+zone+ID+is+Z2FDTNDATAQYW2
++++zone_id+=+"Z2FDTNDATAQYW2"
++}
}|code-block|syntax|javascript|2064117|还有一些工作要做:您还需要使用aws_cognito_user_pool_client创建应用程序客户端。我省略了这一点，因为应用程序客户端与自定义域无关。|2064118|更新：我发现我可以通过为每个环境创建一个托管区域来更好地隔离环境，比如dev-auth.example.com，stage-auth.example.com和auth.example.com。没有必要为这些下面的子域而烦恼。|BOLD|2064119|entityMap^0|0|0|A|G|Y|B|22|B|0|0|0|0|0|C|G|11|B|0|G|9|S|G|0|T|K|1E|M|21|L|0|0|14|L|0|0|F|S|0|0|3|Z|K|1K|M|27|G|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1C|8|@$F|1D|G|1E|H|I]|$F|1F|G|1G|H|I]|$F|1H|G|1I|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1L|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|1N|8|@$F|1O|G|1P|H|I]|$F|1Q|G|1R|H|I]]|9|@]|A|$]]|$1|R|3|S|5|Q|7|1S|8|@$F|1T|G|1U|H|I]|$F|1V|G|1W|H|I]]|9|@]|A|$]]|$1|T|3|U|5|Q|7|1X|8|@$F|1Y|G|1Z|H|I]|$F|20|G|21|H|I]|$F|22|G|23|H|I]]|9|@]|A|$]]|$1|V|3|-4|5|6|7|24|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|25|8|@$F|26|G|27|H|I]]|9|@]|A|$]]|$1|Y|3|Z|5|10|7|28|8|@]|9|@]|A|$11|12]]|$1|13|3|14|5|6|7|29|8|@$F|2A|G|2B|H|I]]|9|@]|A|$]]|$1|15|3|16|5|6|7|2C|8|@$F|2D|G|2E|H|17]|$F|2F|G|2G|H|I]|$F|2H|G|2I|H|I]|$F|2J|G|2K|H|I]]|9|@]|A|$]]|$1|18|3|-4|5|6|7|2L|8|@]|9|@]|A|$]]]|19|$]]

The popular answer correctly answers the question. But at a higher level there's still more to it. There is a cycle in the configuration dependencies:
<blockquote>
Cognito requires the <code>auth.example.com</code> A record, which requires the <code>example.com</code> A record. The <code>example.com</code> A record needs a website to point to, and the website needs Cognito.
</blockquote>
To break this cycle,
<ol>
<li>Create a new Route 53 zone <code>auth.example.com</code> for Cognito to use independently from the website's <code>example.com</code> zone. This breaks the dependency cycle.</li>
<li>Create an <code>auth.example.com</code> A record pointing to a placeholder IP address like <code>127.0.0.1</code>. This will never actually be used.</li>
<li>Now you can create an A record like <code>dev.auth.example.com</code>, <code>stage.auth.example.com</code> or <code>prod.auth.example.com</code> for each environment's Cognito custom domain.</li>
</ol>
The following Terraform example puts this all together, creating a Cognito custom
domain <code>prod.auth.example.com</code>:
<pre><code># Pre-existing hosted zone created by Route53 Registrar
data &quot;aws_route53_zone&quot; &quot;main&quot; {
 name = &quot;example.com&quot;
}

# Create a new Route 53 zone auth.example.com
#
# Actually, Route 53 zone creation belongs in a separate Terraform
# module where it can be shared by multiple environments.

resource &quot;aws_route53_zone&quot; &quot;auth&quot; {
 name = &quot;auth.example.com&quot;
}

resource &quot;aws_route53_record&quot; &quot;auth-ns&quot; {
 zone_id = data.aws_route53_zone.main.zone_id
 name = &quot;auth.example.com&quot;
 type = &quot;NS&quot;
 ttl = &quot;30&quot;
 records = aws_route53_zone.auth.name_servers
} As it is now,
# `terraform destroy` will destroy zone auth.example.com, leaving the other environments in the lurch.

# Only the name servers in the auth.example.com zone NS record know where
# to find auth.example.com. Add NS record in example.com pointing to the
# auth.example.com zone name servers. Now auth.example.com can
# be found through example.com.
resource &quot;aws_route53_record&quot; &quot;auth-a&quot; {
 zone_id = aws_route53_zone.auth.zone_id
 name = &quot;auth.example.com&quot;
 type = &quot;A&quot;
 ttl = 300
 records = [&quot;127.0.0.1&quot;] # Placeholder that is never used
}

# Route 53 zone auth.example.com setup done

module &quot;acm&quot; {
 source = &quot;terraform-aws-modules/acm/aws&quot;

 domain_name = &quot;prod.auth.example.com&quot;
 zone_id = aws_route53_zone.auth.zone_id
 subject_alternative_names = []
 wait_for_validation = true
}

resource &quot;aws_cognito_user_pool&quot; &quot;this&quot; {
 name = &quot;prod-cognito&quot;
}

resource &quot;aws_cognito_user_pool_domain&quot; &quot;this&quot; {
 depends_on = [aws_route53_record.auth-a]
 domain = &quot;prod.auth.example.com&quot;
 certificate_arn = module.acm.this_acm_certificate_arn
 user_pool_id = aws_cognito_user_pool.this.id
}

resource &quot;aws_route53_record&quot; &quot;subdomain-a&quot; {
 zone_id = aws_route53_zone.auth.zone_id
 name = &quot;prod.auth.example.com&quot;
 type = &quot;A&quot;
 alias {
 evaluate_target_health = false
 name = aws_cognito_user_pool_domain.this.cloudfront_distribution_arn
 # Every CloudFront distribution's zone ID is Z2FDTNDATAQYW2
 zone_id = &quot;Z2FDTNDATAQYW2&quot;
 }
}
</code></pre>
A bit of work remains: you also need to create application client(s) using <code>aws_cognito_user_pool_client</code>. I left this out because app clients are unrelated to the custom domain.
Update: I have since found I can get better isolation between
environments by creating a hosted zone for each environment, like
<code>dev-auth.example.com</code>, <code>stage-auth.example.com</code> and
<code>auth.example.com</code>. There is no need to bother with further sub-subdomains
below these.

blocks|key|2064054|text|我用的是|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2064055|2064056|+authdev.mycompany.com|blockquote|2064057|2064058|2064059|并且必须在根域中创建A记录(使用弹性ip)，根域是|2064060|2064061|+mycompany.com.|2064062|2064063|2064064|​|2064065|📷|atomic|offset|length|2064066|2064067|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/d86aa586cf5ed18e3dd5503a1c99b24d.jpeg|imageAlt^0|0|0|0|0|0|0|0|0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|16|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|17|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1A|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|K|3|L|5|E|7|1C|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1F|8|@]|9|@]|A|$]]|$1|Q|3|R|5|S|7|1G|8|@]|9|@$T|1H|U|1I|1|1J]]|A|$]]|$1|V|3|P|5|6|7|1K|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13|14|-4]]]]

I was using 

<blockquote>
 authdev.mycompany.com
</blockquote>

and had to create an A record(using the elastic ip) in the root domain which is 

<blockquote>
 mycompany.com.
</blockquote>

<a href="https://i.stack.imgur.com/CeYct.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/CeYct.jpg" alt="enter image description here"></a>

blocks|key|2893732|text|我知道您正在使用Cognito托管UI进行身份验证，并且您需要一个自定义域。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2893733|当您为cognito创建自定义域时，它将返回一个Alias目标(指向cloudfront分发版)。|2893734|然后，根据您使用的是Route53还是DNS配置，执行以下步骤：|2893735|DNS配置|offset|length|style|BOLD|2893736|2893737|让您的DNS服务提供商将上一步中的别名目标添加为您的用户池自定义域的别名。|ordered-list-item|2893738|您的DNS提供商还需要为您的自定义域设置子域。|2893739|2893740|Route53|2893741|2893742|登录到路由53控制台。系统可能会提示您输入您的亚马逊网络服务credentials.|2893743|2893744|2893745|如果您在53路中没有托管区域，请设置一个。否则，请跳过此步骤。|2893746|2893747|-+a.+Choose+Create+Hosted+Zone.
-+b.+Choose+your+custom+domain+from+the+Domain+Name+list.
-+c.+For+Comment,+type+an+optional+comment+about+the+hosted+zone.
-+d.+Choose+Create.|code-block|syntax|javascript|2893748|2893749|在托管区域页面上，选择托管区域的名称。|2893750|2893751|2893752|选择Create+Record+Set。|2893753|2893754|2893755|为别名选项选择是。|2893756|2893757|2893758|在别名目标中键入您在上一步中记下的别名目标名称。|2893759|2893760|2893761|选择Create。|2893762|2893763|2893764|使用别名目标在路由53中添加子域。|2893765|2893766|-+a.+On+the+Hosted+Zones+page,+choose+the+name+of+your+hosted+zone.
-+b.+Choose+Create+Record+Set+and+enter+the+following+values:+
++++-+i.+For+Name,+type+your+preferred+subdomain+name.+For+example,+if+the+subdomain+you’re+attempting+to+create+is+auth.example.com,+type+auth.
++++-+ii.+For+Type,+choose+A+-+IPv4+address.
++++-+iii.+Select+Yes+for+the+Alias+option.
++++-+iv.+Type+the+alias+target+name+that+you+noted+in+a+previous+step+in+Alias+Target.|2893767|-+c.+Choose+Create.|2893768|参考：https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pools-add-custom-domain.html|2893769|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pools-add-custom-domain.html^0|0|0|0|0|5|0|0|0|0|0|0|7|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|3|2R|0|0^^$0|@$1|2|3|4|5|6|7|29|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|2A|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|2B|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|2C|8|@$H|2D|I|2E|J|K]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|2F|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|2G|8|@]|9|@]|A|$]]|$1|P|3|Q|5|O|7|2H|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|2I|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|2J|8|@$H|2K|I|2L|J|K]]|9|@]|A|$]]|$1|U|3|-4|5|6|7|2M|8|@]|9|@]|A|$]]|$1|V|3|W|5|O|7|2N|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|2O|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|2P|8|@]|9|@]|A|$]]|$1|Z|3|10|5|O|7|2Q|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|2R|8|@]|9|@]|A|$]]|$1|12|3|13|5|14|7|2S|8|@]|9|@]|A|$15|16]]|$1|17|3|-4|5|6|7|2T|8|@]|9|@]|A|$]]|$1|18|3|19|5|O|7|2U|8|@]|9|@]|A|$]]|$1|1A|3|-4|5|6|7|2V|8|@]|9|@]|A|$]]|$1|1B|3|-4|5|6|7|2W|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|O|7|2X|8|@]|9|@]|A|$]]|$1|1E|3|-4|5|6|7|2Y|8|@]|9|@]|A|$]]|$1|1F|3|-4|5|6|7|2Z|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|O|7|30|8|@]|9|@]|A|$]]|$1|1I|3|-4|5|6|7|31|8|@]|9|@]|A|$]]|$1|1J|3|-4|5|6|7|32|8|@]|9|@]|A|$]]|$1|1K|3|1L|5|O|7|33|8|@]|9|@]|A|$]]|$1|1M|3|-4|5|6|7|34|8|@]|9|@]|A|$]]|$1|1N|3|-4|5|6|7|35|8|@]|9|@]|A|$]]|$1|1O|3|1P|5|O|7|36|8|@]|9|@]|A|$]]|$1|1Q|3|-4|5|6|7|37|8|@]|9|@]|A|$]]|$1|1R|3|-4|5|6|7|38|8|@]|9|@]|A|$]]|$1|1S|3|1T|5|O|7|39|8|@]|9|@]|A|$]]|$1|1U|3|-4|5|6|7|3A|8|@]|9|@]|A|$]]|$1|1V|3|1W|5|14|7|3B|8|@]|9|@]|A|$15|16]]|$1|1X|3|1Y|5|14|7|3C|8|@]|9|@]|A|$15|16]]|$1|1Z|3|20|5|6|7|3D|8|@]|9|@$H|3E|I|3F|1|3G]]|A|$]]|$1|21|3|-4|5|6|7|3H|8|@]|9|@]|A|$]]]|22|$23|$5|24|25|26|A|$27|28]]]]

I understand that you're using Cognito Hosted UI for authentication and you need a custom domain.
When you create a custom domain for cognito, it will return an Alias target (which points to a cloudfront distribution).
Then take the following steps depending if you're using Route53 or DNS configuration:
DNS configuration
<ol>
<li>have your DNS service provider add the alias target from the previous step as an alias for your user pool custom domain.</li>
<li>Your DNS provider will also need to set up the subdomain for your custom domain.</li>
</ol>
Route53
<ol>
<li>Sign in to the Route 53 console. You might be prompted for your AWS credentials.
</li>
<li>If you don't have a hosted zone in Route 53, set one up. Otherwise, skip this step.
<ul>
<li>a. Choose Create Hosted Zone.</li>
<li>b. Choose your custom domain from the Domain Name list.</li>
<li>c. For Comment, type an optional comment about the hosted zone.</li>
<li>d. Choose Create.</li>
</ul>
</li>
<li>On the Hosted Zones page, choose the name of your hosted zone.
</li>
<li>Choose Create Record Set.
</li>
<li>Select Yes for the Alias option.
</li>
<li>Type the alias target name that you noted in a previous step into Alias Target.
</li>
<li>Choose Create.
</li>
<li>Add a subdomain in Route 53 by using the alias target.
<ul>
<li>a. On the Hosted Zones page, choose the name of your hosted zone.</li>
<li>b. Choose Create Record Set and enter the following values:
<ul>
<li>i. For Name, type your preferred subdomain name. For example, if the subdomain you’re attempting to create is auth.example.com, type auth.</li>
<li>ii. For Type, choose A - IPv4 address.</li>
<li>iii. Select Yes for the Alias option.</li>
<li>iv. Type the alias target name that you noted in a previous step in Alias Target.</li>
</ul>
</li>
<li>c. Choose Create.</li>
</ul>
</li>
</ol>
Reference: <a href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pools-add-custom-domain.html" rel="nofollow noreferrer">https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pools-add-custom-domain.html</a>

I am trying to assign an own domain name to a user pool for Cognito and facing an issue that it seems that an A Record is required. 

In my case i have registered wildcard on my internet domain and am trying to follow the steps as mentioned in <a href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pools-add-custom-domain.html" rel="noreferrer">https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pools-add-custom-domain.html</a>

Now i can create an A Record but have no clue where this A Record should point to. Any hints or tips are welcome :) It would be nice if this can be done without using CloudFront.

I tried CNAME's etc but as stated an A Record is required.

Cognito own domain name required A Record

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在尝试将自己的域名分配给Cognito的用户池，但遇到了一个问题，似乎需要A记录。在我的例子中，我已经在我的Internet域上注册了通配符，并且正在尝试按照中提到的步骤进行操作现在我可以创建一个A记录，但是不知道这个A记录应该指向哪里。欢迎任何提示或技巧:)如果不使用CloudFront就能做到这一点，那就太好了。我试过CNAME的etc，但如上所述，A记录是必需的。

问需要Cognito自己的域名A记录
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问需要Cognito自己的域名A记录EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问需要Cognito自己的域名A记录
EN