We include URLs for browse/thumbnail images, product files, and log files, but they will return 403 - Access Denied errors when end-user buckets are not public.
The S3 bucket and prefix are provided in the job response, and for product files, the S3 bucket and Key is also specified, so users with private buckets should still know where the products are and how to access them.
Clients like Vertex, however, will need to handle 403 - Access Denied errors when accessing these URLs.
We could, alternatively, copy browse images/thumbnails/logs to the HyP3 content bucket in the get-files step and provide those URLs in the jobs response, but then we'd report different locations for files, which could be confusing, or more importantly, expiration times of these files may not match the reported expiration time.
So I'm inclined to leave this as open with a 'wontfix` label to document this behavior for users.
We include URLs for browse/thumbnail images, product files, and log files, but they will return 403 - Access Denied errors when end-user buckets are not public.
The S3 bucket and prefix are provided in the job response, and for product files, the S3 bucket and Key is also specified, so users with private buckets should still know where the products are and how to access them.
Clients like Vertex, however, will need to handle 403 - Access Denied errors when accessing these URLs.
We could, alternatively, copy browse images/thumbnails/logs to the HyP3 content bucket in the
get-filesstep and provide those URLs in the jobs response, but then we'd report different locations for files, which could be confusing, or more importantly, expiration times of these files may not match the reported expiration time.So I'm inclined to leave this as open with a 'wontfix` label to document this behavior for users.