Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spike: Long-term solution for cloud storage extension dataset #248

Closed
Shmuma opened this issue Mar 13, 2024 · 0 comments
Closed

Spike: Long-term solution for cloud storage extension dataset #248

Shmuma opened this issue Mar 13, 2024 · 0 comments
Labels
shelved:yes Closed because this ticket is very unlikely to get implemented task

Comments

@Shmuma
Copy link
Contributor

Shmuma commented Mar 13, 2024

Around beginning of March, Y8M dataset we used for cloud storage extension notebook was closed.
Created a ticket for dataset provider: aws-samples/data-lake-as-code#28
And ticket for replacing the dataset: #247

But we need long-term solution for such situations.
It is risky to put some data on public dataset, as it could be used for "payment attack" when data is requested and AWS bills grow infinitely.

Possible solutions we discussed with @redcatbear and @tkilias:

  • as AWS s3 doesn't support rate limiting out of the box, we can consider switching to another cloud provider supported by cloud-storage extension
  • api gateway with rate limiter could potentially be used (if it can mimic s3 protocol)
  • s3 requestor pays option (might require support in cloud-storage provider)
  • monitor aws bills and disable access in case of suspicious activity

Those options require deeper investigation.

@Shmuma Shmuma added the task label Mar 13, 2024
@redcatbear redcatbear added the shelved:yes Closed because this ticket is very unlikely to get implemented label Sep 27, 2024
@redcatbear redcatbear closed this as not planned Won't fix, can't repro, duplicate, stale Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
shelved:yes Closed because this ticket is very unlikely to get implemented task
Projects
None yet
Development

No branches or pull requests

2 participants