S3 Testing and adjustments #1386
Merged
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
suprjinx
reviewed
Aug 15, 2024
suprjinx
reviewed
Aug 15, 2024
|
After testing once again the whole flow with proper values for the URIs and AWS params, everything seems to work fine even when omitting the path style. I am a bit confused as to why it wasn't quite working before. 🤔 |
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.
PR to add documentation for AWS logging.
After testing with the right values for each environment variable required by both the backend and AWS S3, it turns out we don't need to make any changes. I added a guide with the variables and example values.
Changelog
SetUsePathStyleproperty to false in order to get AWS S3 to track correctly (otherwise the resource cannot be found)