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

Add guidelines to list S3 public bucket folder / file structure #4

Open
karenng-civicsoftware opened this issue May 21, 2019 · 4 comments
Assignees

Comments

@karenng-civicsoftware
Copy link
Collaborator

karenng-civicsoftware commented May 21, 2019

There has been a request to find ways to list the directory structure of S3 files.

Right now we are unable to list the content of our public hacko-data-archive S3 bucket with the AWS CLI, most possibly due to permission issues
Reference from stack overflow here
@DingoEatingFuzz Is it possible for us to change the permission of the files & folders in that public S3 bucket? If permission is not the problem, how can we enable this?

[resolution] Karen will write a platform request to ask for a REST API to check what files are availabe in the S3 bucket

@karenng-civicsoftware karenng-civicsoftware added enhancement New feature or request help wanted Extra attention is needed labels May 21, 2019
@karenng-civicsoftware karenng-civicsoftware changed the title add guidelines to access S3 public bucket add guidelines to list S3 public bucket folder / file structure May 21, 2019
@karenng-civicsoftware karenng-civicsoftware changed the title add guidelines to list S3 public bucket folder / file structure Add guidelines to list S3 public bucket folder / file structure May 21, 2019
@DingoEatingFuzz
Copy link

I responded to this in the sagemaker PR: hackoregon/hackoregon-aws-infrastructure#61 (comment)

@karenng-civicsoftware
Copy link
Collaborator Author

@DingoEatingFuzz being able to list the data files will allow better collaboration between the different teams. The desired workflow is to do

$ aws s3 ls s3://hacko-data-archive

An error occurred (AccessDenied) when calling the ListObjectsV2 operation: Access Denied

I do not think this will be computationally intensive operation. Why wouldn't you want to allow access?

@DingoEatingFuzz
Copy link

It is not computationally intensive, and I don't mind if data scientists are given access tokens to use with the aws cli tool, the issue is around security.

Even though the S3 bucket is public, you'd have to know the URL you want in order to download anything. If I make the ListObjects operation available to the public, then anyone could crawl through the bucket and clone the whole thing.

I would like to eventually open this up, but not before doing an audit and making sure there is truly nothing in there that we would want exposed.

@karenng-civicsoftware karenng-civicsoftware self-assigned this Jun 15, 2019
@karenng-civicsoftware
Copy link
Collaborator Author

karenng-civicsoftware commented Jun 15, 2019

resolution: @karenng-civicsoftware will gather a list of emails of the data scientists needing AWS accounts to list the files on the S3 buckets. Then share it with Michael to create the accounts.

@karenng-civicsoftware karenng-civicsoftware removed enhancement New feature or request help wanted Extra attention is needed labels Jul 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants