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

That is surprising.  When you say you got a valid resource ID - do you mean you got back an ARN or equivalent?  If you use `aws` CLI to query for that - does it not exist?

sooo i just went to answer this question for you, but i’m not able to reproduce this problem… on my test domain… even tho it was reproducing reliably a few times yesterday on my main domain - really confusing. let me do a little more investigation

ok - soooo this works totally fine on my test domain - same pulumi script, but here’s what happens on my main domain:

the resource name is just HOSTEDZONEID_domainname_TXT

so removing that resource from the pulumi script &amp; then running update causes the resource to be created

on both test &amp; real domains, it reports success

it’s shown in `aws route53 list-resource-record-sets` for both

BUT for the test domain, it also shows up in the aws console

meanwhile, for the test domain, `dig` on the nameserver produces the right record

i can manually add the record in the aws console &amp; then it shows up &amp; dig reports the right result

`aws route53 list-resource-record-sets` does not show a duplicate record

seems like something is funky on the aws side … just for my main domain ¯\_(ツ)_/¯

…. and just tried it one more time and it worked correctly

anyway, this is not really blocking/hurting me in any way now - but it was surprising/confusing

i’m paranoid about checking DNS records anyway - so maybe no action necessary other than remember i said this so that later when somebody else has a similar problem a pattern may start to emerge :slightly_smiling_face: sorry for the distraction