feat(Storage): S3 bucket instead of EC2 storage for images and thumbnails #17
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nathanagez
force-pushed
the
feat/strapi/s3-image-storage
branch
from
198e1a4
to
eaafe6e
Compare
mezzLMC
added a commit
that referenced
this pull request
Dec 11, 2023
…ails (#17) * feat(s3): default plugin config + no credentials patch --------- Co-authored-by: Nathan Agez <nathan.agez@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
strapi-provider-upload-aws-s3 lets us use an S3 bucket as storage for our various images, instead of using the storage system of the machine hosting the server.
the problem was that it required a user's full credentials (access key + secret Key) to work.
A patch was therefore applied so that it would use these values when they were supplied, or let aws-sdk use system authentication when no credentials were supplied.