Currently, fusera assumes that URLs for object incorporate authorization (signedURLs). Significant new data will be open access, and will be sitting in requester pays buckets. In that scenario, fusera must present the user's credentials to S3/GCS to so that charges can be assigned to the user, and not to the SDDP production account.
Currently, fusera assumes that URLs for object incorporate authorization (signedURLs). Significant new data will be open access, and will be sitting in requester pays buckets. In that scenario, fusera must present the user's credentials to S3/GCS to so that charges can be assigned to the user, and not to the SDDP production account.