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

Create and document the access to S3 storage for testnet and mainnet #6

Closed
frol opened this issue Feb 9, 2022 · 6 comments · Fixed by #25
Closed

Create and document the access to S3 storage for testnet and mainnet #6

frol opened this issue Feb 9, 2022 · 6 comments · Fixed by #25
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@frol
Copy link
Contributor

frol commented Feb 9, 2022

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)

@frol frol added the enhancement New feature or request label Feb 9, 2022
@frol frol added this to the MVP Release milestone Feb 9, 2022
@khorolets khorolets self-assigned this Feb 13, 2022
@khorolets
Copy link
Member

Access key of any user who has access to our AWS S3 buckets is required.

Bucket name is near-lake-testnet for testnet. The same naming concept will be used for mainnet. Where do you suggest to document this?

@frol
Copy link
Contributor Author

frol commented Feb 14, 2022

@khorolets Do you believe the README on this repo is a bad place to put this documentation or why do you ask?

@khorolets
Copy link
Member

@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?

@frol
Copy link
Contributor Author

frol commented Feb 15, 2022

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 curl commands showing how to download some specific block with all the shards)

@khorolets
Copy link
Member

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 curl commands showing how to download some specific block with all the shards)

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?

@frol
Copy link
Contributor Author

frol commented Feb 17, 2022

Though I can add the section that describes how to use the data with NEAR Lake Framework.

Let's just have a section with a link to the framework.

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.
How about we extract the quoted part of your comment to a separate issue for the 1.0 milestone?

Ok, please, extract it into a separate issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants