-
Notifications
You must be signed in to change notification settings - Fork 13
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
S3 file upload cloud formation setup #35
Comments
I'm setting up the S3 as part of the API. |
The S3 is setup for int and test bundled with the API. The permissions from the API is:
^ This is the bit that has that logic. @jamesdools and @pietrop , we might want to consider what the life-cycle (expire in 1 year or half a year...) of items in the bucket should be. I have it currently commented out - but once we figure out the subdirectory names (e.g. audio, original, preview etc.) we can uncomment + implement the lifecycle policy. |
@emettely can you add some more details on how this works? I get there's something added to the cloud formation to give the EC2 instance for the API serve the capability to access the bucket(?) Do we know more about how do you then access (add or get files from the S3 bucket) from within the express server inside the API? (do we use the AWS Node SDK?) Also I see the link goes straight into master, was there a PR for this? And is this still in progress ready for review or done? |
narrowing down this card to be only covering first part of acceptance criteria to do with
moving the rest to a separate card bbc/digital-paper-edit-api#4 |
To review this (draft)
|
Context
We want to upload directly to S3 from the client using the signed URL.
Acceptance Criteria
-Make sure upload of files are only done through signed URLs, retrieved from the API-
(moved to a different ticket)
Some useful references
The text was updated successfully, but these errors were encountered: