comment
authorJoey Hess <joeyh@joeyh.name>
Mon, 6 Feb 2023 17:05:27 +0000 (13:05 -0400)
committerJoey Hess <joeyh@joeyh.name>
Mon, 6 Feb 2023 17:05:27 +0000 (13:05 -0400)
doc/bugs/S3_remote_errors_with_garage_endpoint/comment_8_d8cdf46fb8de877ea167d14a055813e0._comment [new file with mode: 0644]

diff --git a/doc/bugs/S3_remote_errors_with_garage_endpoint/comment_8_d8cdf46fb8de877ea167d14a055813e0._comment b/doc/bugs/S3_remote_errors_with_garage_endpoint/comment_8_d8cdf46fb8de877ea167d14a055813e0._comment
new file mode 100644 (file)
index 0000000..ec62c54
--- /dev/null
@@ -0,0 +1,17 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 8"""
+ date="2023-02-06T16:51:58Z"
+ content="""
+> It's working, because presumably AWS accept 's3.amazon.com' as a region setting for the scope in their cloud.
+
+I doubt it; that's not what aws sends to it.
+
+Just to be clear, comment #5 is me fully understanding the problem
+and escalating the issue to the relevant library. Further speculation
+would probably muddy the water.
+
+Thanks for clarifying that "scope" is internal jargon of garage though.
+Also it's good to know that `AWS_DEFAULT_REGION` is a commonly used
+environment variable for it.
+"""]]