No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Did you create `<http://app.dev.example.com|app.dev.example.com>`?

It says "targetDomain string

    The domain used to serve the content. A Route53 hosted zone must exist for this domain."

`<http://example.com|example.com>` won't do it. But there's no extra cost to creating an extra CNAME record in route53

Yes I have <http://example.com|example.com> in the account that I am using , I thought I could  go with multi account strategy like create dev account and add <http://dev.example.com|dev.example.com> to there 

But I am not sure how they check route53 zone

To test this idea , I tried to create resource with  <http://app.example.com|app.example.com> , but still no luck 

You can put <http://dev.example.com|dev.example.com> in another account if you want to.
If you are creating <http://app.example.com|app.example.com>, you need to create the DNS record first. The rule is in the docs:
"A Route53 hosted zone must exist for this domain"

So if you don't have <http://app.example.com|app.example.com> in Route53, then you can't create the website.

Yep there is , hosted zone. I ran it to deploy for <http://example.com|example.com>. That works.  :)

Because my hosted zone is for <http://example.com|example.com>

But when I try to create another app for <http://app.example.com|app.example.com> , it looks up for route53 zone named for <http://app.example.com|app.example.com> rather than <http://example.com|example.com> (in my opinion)

My fear is when I create <http://dev.example.com|dev.example.com> in dev account, then when I create <http://app.dev.example.com|app.dev.example.com> it will look up hosted zone with whole domain again :)

A zone can have any number of records in it. Create more records in the existing zone. A records if you're pointing at an IP address, or CNAME records if you're pointing at another DNS record.

Zones aren't DNS entries, Records are. The docs say you cannot have a Website at <http://app.dev.example.com|app.dev.example.com> until you have a route53 Record for that name in a route53 Zone.

Alright!

So your suggestion is first I should create record then website with this component.

I guess, I will need to skip domainTarget option and update A record with webSiteUrl of bucket.

Am I understanding you correct?

UPDATE :

I created <http://dev.example.com|dev.example.com> ,by following <https://theburningmonk.com/2021/05/how-to-manage-route53-hosted-zones-in-a-multi-account-environment/>

When I run <http://app.dev.example.com|app.dev.example.com> with Website component, it’s just working :partying_face:

Thanks <@U012UJTT55M> for suggestions!