Cross-account Hosted Zone for v3.0

I am trying to create a cluster with pre-existing hosted zone, but in a different account. The hosted zone is public and the IAM role attached to the EC2 machine which I am using to start a PC has route53:Get* permissions on all resources (*). Since Route53 does not support resource-based policy, there is nothing like whitelisting the account ID in R53 Hosted Zone.
Does v3.0 support cross-account public hosted zone? and If yes, what changes have to be made in order to get this to work.
The cluster creation command fails with the following error -

```
[ssm-user@ip-10-xx-xx-xx ~]$ pcluster create-cluster --cluster-name parallel-cluster-01 --cluster-configuration cluster-config.yaml
{
"configurationValidationErrors": [
{
"level": "ERROR",
"type": "HostedZoneValidator",
"message": "User: arn:aws:sts::xx12345566755:assumed-role/pcluster-ec2-role-dev-01/i-0449063137xxxxxx is not authorized to access this resource"
}
],
"message": "Invalid cluster configuration."
}
```

cluster-config.yaml
```
Region: us-east-1
Image:
Os: alinux2
HeadNode:
InstanceType: t2.micro
Networking:
SubnetId: subnet-xxxx1111
Ssh:
KeyName: my-keypair
Scheduling:
Scheduler: slurm
SlurmSettings:
ScaledownIdletime: 10
Dns:
HostedZoneId: xx12345
SlurmQueues:
- Name: def-q
ComputeResources:
- Name: t2micro
InstanceType: t2.micro
MinCount: 0
MaxCount: 2
Networking:
SubnetIds:
- subnet-xxxx1111
- Name: spot-q
ComputeResources:
- Name: t2micro
InstanceType: t2.micro
MinCount: 0
MaxCount: 2
Networking:
SubnetIds:
- subnet-xxxx1111
```