Deploying an OVF or OVA template from a URL using Amazon S3 Pre-Signed URLs fails with the Error - "URL is not well formed or unsupported"
search cancel

Deploying an OVF or OVA template from a URL using Amazon S3 Pre-Signed URLs fails with the Error - "URL is not well formed or unsupported"

book

Article ID: 436815

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

When trying to deploy a OVA/OVF from a URL using pre-signed URLs it is failing with the Error -  "URL is not well formed or unsupported" 

Amazon S3 Pre-Signed URLs use a suffix of ?X* after the .ova/.ovf file extension for example 

https://s3.amazonaws.com/test-s3-bucket/2026/Appliance.ova?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIA3SGQVQG7FGA6KKA6%2F20221104%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20221104T140227Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=host&X-Amz-Signature=b228dbec8c1008c80c162e1210e4503dceead1e4d4751b4d9787314fd6da4d55

Environment

vCenter Server 8.x

vCenter Server 7.x

 

Cause

URLs that contain an HTTP query parameters are not supported.

Resolution

Amazon Pre-Signed URLs are not supported when deploying OVA/OVF from URLs. The file extension must be in .ova/.ovf format.

Additional Information

 https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3v-release-notes.html