Director Fails to Install Due to Incompatibility with Signed URLS

Products

• Operations Manager

Issue/Introduction

Different variations of S3 Blobstore (Openstack, ECS) may not be compatible with signed_urls which can cause issues when deploying/apply changes.

Signed URLs are generated URLs with access permissions encoded into it for a specific bucket and object that is valid only for a certain time period

https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-presigned-url.html

Symptoms:
When installing the Director, customer's may run into an issue where the director will ask "s3" for a signed url, receive a blank host in return, and then send that blank url to the agent. 
 

Task 103 | 18:34:24 | Compiling packages: golang-1-linux/e07fa80a3e9eb2c0beae3cad38ac914ffa7d56695458b672fa6ee126f2026145 (00:01:44)
L Error: Action Failed get_task: Task fc9355d0-####-####-####-5ff8db431e69 result: Compiling package golang-1-linux: Fetching package golang-1-linux: Fetching package blob : Excuting GET request: Get https:///pcf-bosh-blob/51f46630-####-####-####-cb3d4c499aa2: http: no Host in request URL

Environment

Product Version: 2.9

Resolution

The solution to this issue is to simply disable signed URLs in the Director tile and apply changes. The default value for a new foundation is set to ON.