CloudFront deployment issue when domain is tied to a deleted or locked AWS account

Hello.

If you have access to the AWS account that contains the CloudFront to which the domain is linked, you can move it using an API or similar, but in your case, this is not possible because the AWS account is already closed.
Therefore, I think the only way to deal with this is to contact AWS support as described in the following document.
https://repost.aws/knowledge-center/resolve-cnamealreadyexists-error

If you don't have access to the account that contains the source distribution or you can't deactivate the source distribution, then contact AWS Support.

If it's been less than 90 days since the account containing the CloudFront distribution with the name you want to use elsewhere, and assuming it's an account you owned, you can ask AWS Support to reopen the account, then you can log on, detach any TLS certificates associated with the CloudFront distribution, and delete the distribution. Finally, close the account again. Note, however, that AWS will resume billing you for the contents of the account when it's reopened, so depending on its contents, there might be a cost impact.

As a general rule to avoid issues like this, you should delete unneeded resources in your account before closing it, particularly resources that involve claims in global namespaces, such as DNS names associated with CloudFront distributions, names of S3 buckets, and so on. Otherwise, the names will remain claimed after the account is closed, until AWS starts removing all resources 90 days after the account was closed.