You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AWS Budget actions does not support triggering a change in the ACL of an S3 bucket (the way to change the status of a bucket from public to private). Explore the option of setting up a simple lambda that subscribes to AWS Budget events to do the thing. Useful resources
Though still a nice to have feature, I do not see it as a priority for the near future considering that #44 enables users to request access to the backend by simply raising a PR.
A short documentation section for self-granting access to DVC assets can be found in the README.
One option we did not consider enough is to setup a Cloudfront distribution to enable HTTP based access, and use some rate-based rules to limit the number of requests, for example, per IP.
Resources
Troubleshooting access denied errors via Cloudfront (link)
In order for everyone to be able to access DVC assets and appeareces snapshots, allow public access
on the bucketsomehowA few things to consider
Is S3 throttling a possible solution to avoid incurring into big costs buts still allowing public access?AWS Bugdet actions seem to be way to go for implementing a security shutdown of the bucket access if traffic increases too much hereAWS Budget actions does not support triggering a change in the ACL of an S3 bucket (the way to change the status of a bucket from public to private). Explore the option of setting up a simple lambda that subscribes to AWS Budget events to do the thing. Useful resources
The text was updated successfully, but these errors were encountered: