On Sat, 7 Mar 2020 at 13:54, Nikolaus Rath <nikol...@rath.org> wrote: [...]
> > I'm not sure the bucket is locked down; later versions appear to read > files > > from the bucket fine (but then fail with object format mismatches). > > S3QL switched from using v3 authentication to using v4 authentication > for Amazon S3 at some point. Maybe AWS no longer supports v3? > I verified the credentials with both the aws tool and s3fs. I also tried creating brand new credentials, and they behave in precisely the same way. So I'm confident it's not a credential problem. s3fs was very unhappy about mounting a bucket with dots in the name. I know s3ql used to have this problem, but I thought it'd been fixed. If I rename my bucket, will s3ql still mount it, or are there internal references to the bucket name in the metadata? -- You received this message because you are subscribed to the Google Groups "s3ql" group. To unsubscribe from this group and stop receiving emails from it, send an email to s3ql+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/s3ql/CALgV52j%3DxH5Kxx9AHk9Dw8cpmbw%3DZ3R04ie%2B2VO3ZRaO-Y-dLQ%40mail.gmail.com.
