Store sample SQLite file in a new location

[shntnu]

https://github.com/cytomining/pipeline-examples/blob/main/0.download.sh

aws s3 cp s3://imaging-platform/projects/2018_05_30_ResistanceMechanisms_Kapoor/workspace/backend/2020_07_02_Batch8/218360/218360.sqlite data/218360.sqlite
is in Intelligent Tiering mode. We should move this to a new location that will not get (eventually) glaciered

[bethac07]

(and is also public)

[shntnu]

It seems to be public already unless you did this just now @bethac07

[bethac07]

I did it just now. I did not notice if that banner was there when I did it though.

…

On Thu, Apr 14, 2022 at 9:46 AM Shantanu Singh ***@***.***> wrote: [image: image] <https://user-images.githubusercontent.com/1210428/163403968-ae5742d9-40b9-4577-a983-c7160119dfdb.png> It seems to be public already unless you did this just now @bethac07 <https://github.com/bethac07> — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABTI725DPA3LFKZAFDUUCD3VFAOSXANCNFSM5L7JV77Q> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Beth Cimini, PhD Senior Group Leader & CZI Imaging Scientist Imaging Platform, Broad Institute 415 Main St Room 5011 Cambridge, MA 02142 Current office number- (617) 714-8189 Pronouns - She/her/hers I will sometimes send or respond to emails outside of my local office hours, but I never expect responses outside of your local office hours.

[bethac07]

Hmmm, still getting this error though after I have removed my aws credentials -

wm57d-d6c: bcimini$ aws s3 cp s3://imaging-platform/projects/2018_05_30_ResistanceMechanisms_Kapoor/workspace/backend/2020_07_02_Batch8/218360/218360.sqlite /Users/bcimini/Desktop/test/218360.sqlite
fatal error: An error occurred (403) when calling the HeadObject operation: Forbidden

[bethac07]

🤔

I added read to the "Object ACL" (was previously only in the "Object" column), still same 403 forbidden error.

(I ruled out just a typo in my string by re-getting the s3uri right from the web console.)

[bethac07]

🤔

Ruled out the "and not blocked by Public Access settings" part of the clause in your screenshot

[bethac07]

Ah; I had before just put in garbage credentials, when I put in good credentials that just can't access this account (a brand new set that I made in one of the new otherwise still unused AWS accounts for my lab, I can download fine. So this user just doesn't have any good credentials in there, probably.

[shntnu]

Ah; I had before just put in garbage credentials, when I put in good credentials that just can't access this account (a brand new set that I made in one of the new otherwise still unused AWS accounts for my lab, I can download fine. So this user just doesn't have any good credentials in there, probably.

This is fixed in #5

[shntnu]

• figure out where this example data should live