-
Notifications
You must be signed in to change notification settings - Fork 16
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
Create and document the access to S3 storage for testnet and mainnet #6
Comments
Access key of any user who has access to our AWS S3 buckets is required. Bucket name is |
@khorolets Do you believe the README on this repo is a bad place to put this documentation or why do you ask? |
I'm asking because the info about the required credentials is already in the README. Do you want me to add bucket names and regions to README? |
There should be a section that describes how to use the data ("raw-mode" and also provide a reference to near-lake-framework). Given that we can setup S3 in a way that the users will pay for their read usage, let's make sure we provide clear instructions on how to get it working (ideally, let's have |
We haven't done any test regarding the "user will pay for their read usage" yet. And I doubt we can do it before the 1.0 milestone. Though I can add the section that describes how to use the data with NEAR Lake Framework. How about we extract the quoted part of your comment to a separate issue for the 1.0 milestone? |
Let's just have a section with a link to the framework.
Ok, please, extract it into a separate issue |
We should make sure we have a sane separation of concerns.
Let's start with private access to S3 storage, but make sure we can change it later to public read access later (I assume so, but I want to be explicit)
The text was updated successfully, but these errors were encountered: