estore S3bucket backup to aws as disaster recovery very slow compared to azure

In recent days, we have been testing disaster recovery in a cloud environment.

In our on-premises environment, we prepared and executed backups of two test machines to an Azure Blob storage, as well as a backup to an AWS S3 bucket.

We then prepared two labs:

the first lab on Azure, with a Veeam 13 machine performing the restore of the data from the Blob storage to a different subscription from the one hosting the Veeam VM;
the second lab, where a Veeam 13 machine was created in an AWS subscription to restore the data from the S3 bucket to another AWS subscription.

We noticed a significant difference in data restore times between Azure and AWS:

on Azure, a VM of approximately 50 GB was restored in about 8 minutes;
on AWS, restoring the same machine required approximately 86 minutes.

The most noticeable gap lies in two tasks that are present on AWS but not on Azure: the snapshot creation task and the VM importing task.

In both cases, we followed the recommendations and guidelines provided in the Veeam KB articles, including creating a proxy in the same region as the storage.

Could you help us understand whether we are doing something wrong? Is this due to a configuration issue, or are restore performances actually so different because of technical reasons?

Thank you very much.