Your team is publishing research results and needs to make large amounts of data available to other researchers within the professional community and the public at minimum cost. How should you host the data?
A.
Use a Cloud Storage bucket and enable ג€Requester Pays.ג€
B.
Use a Cloud Storage bucket and provide Signed URLs for the data files.
C.
Use a Cloud Storage bucket and set up a Cloud Interconnect connection to allow access to the data.
D.
Host the data on-premises, and set up a Cloud Interconnect connection to allow access to the data.
Enabling "Requester Pays" on a Cloud Storage bucket allows you to shift the cost of accessing the data to the requester. This means that the individuals or organizations accessing the data will be responsible for the cost of data transfer and operations, rather than your organization incurring the expenses.
With this approach, you can make the data publicly accessible in the Cloud Storage bucket while ensuring that the cost of data access is covered by the requesters. This can help reduce your organization's expenses in hosting and serving the data.
Option B (providing Signed URLs) would require you to generate and manage unique URLs for each requester, which might not be practical for making the data available to a wide audience.
A. Enabling Requester Pays is useful, for example, if you have a lot of data you want to make available to users, but you don't want to be charged for their access to that data.
https://cloud.google.com/storage/docs/requester-pays
The requester pays works on Projects Inside your GCP Env. in that the requester will pay for request not the primary project from where the request is made. This is not Public as per Google Documentation I believe.
Requester Pays" is a feature specifically designed for this scenario. It allows you to make your data publicly accessible while shifting the cost of data access (storage, retrieval) to the users who are downloading the data. This minimizes costs for your team while still making the data readily available to the research community and public.
Requester Pays is a feature of Cloud Storage that allows you to transfer the cost of data egress to your users. This means that users who download your data will be charged for the egress traffic, not you.
Cloud Storage Bucket: Host your data in a Google Cloud Storage bucket, which provides scalable and reliable storage.
Signed URLs: Create and provide signed URLs to users. Signed URLs grant temporary access to specific objects in your Cloud Storage bucket without the need for users to have Google Cloud accounts or pay for egress costs. This approach allows you to maintain control over who accesses your data while minimizing costs for your users.
Option B is a better choice for sharing data with a wider public audience while keeping costs low and ensuring accessibility without requiring users to pay for egress fees.
The answer is A
Enabling Requester Pays is useful, for example, if you have a lot of data you want to make available to users, but you don't want to be charged for their access to that data.
https://cloud.google.com/storage/docs/requester-pays
In reading through Google docs on Signed URLs there is no mention of cost minimization.
https://cloud.google.com/storage/docs/access-control/signed-urls
I just don't see how it's practical to ask everyone to have a google account to bill against. A might be what they're looking for, but I'm just seeing it as a practical solution.
If you want to make them pay... do so through an app, then provide them a signed url for the download. It's more complex to implement, but it actually works.
It's B. Signed URL's are available to the public, and you control who has access. Requester pays - With Requester Pays enabled on your bucket, you can require requesters to include a billing project in their requests, thus billing the requester's project
Requestor pays is not for the public
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
cookieMr
Highly Voted 10 months, 3 weeks agoprachisri
8 months, 3 weeks agojvg637
Highly Voted 2 years, 3 months agopspandher
1 year, 7 months agoVenRam
2 years, 3 months agoShivGupt
Most Recent 2 months, 2 weeks agochai_gpt
5 months, 4 weeks ago__rajan__
6 months, 2 weeks agoRK_MANOJ
6 months, 3 weeks agomdsarfraz69
7 months, 1 week agoAtmatap
1 year agoMHx1
1 year, 1 month agoskybd3hel
1 year, 1 month agoalfantastic
1 year, 3 months agosomeshsehgal
1 year, 4 months agovicjean
1 year, 4 months agoucsdmiami2020
1 year, 4 months agojellybiscuit
1 year, 6 months agoDan_W
1 year, 6 months agobrainysaki
1 year, 7 months ago