S3 custom domain and collectstatic about django-s3-storage HOT 3 CLOSED

On Fri, 17 Feb 2017 at 20:42, Dionyz Lazar ***@***.***> wrote: I have a cdn.domain.com that points to a s3 bucket with the same name. In my settings for this app I've added: AWS_S3_CALLING_FORMAT_STATIC = 'boto.s3.connection.VHostCallingFormat' AWS_S3_HOST_STATIC = 'cdn.domain.com' and URLs that are generated by {% static %} now work properly. I still have one problem though - when I run collectstatic command I get: <Error> <Code>InvalidRequest</Code> <Message> The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256. </Message> <RequestId>FCA19FC7046E571A</RequestId> <HostId>...</HostId> </Error> If I remove AWS_S3_CALLING_FORMAT_STATIC and AWS_S3_HOST_STATIC settings then collectstatic runs fine and I can see files being uploaded to S3. Am I missing some other setting here? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#44>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAJFCBNkinLCnYAOs6CyNEw_UH2xfVsuks5rdgZAgaJpZM4MEucU> .

On Sat, 18 Feb 2017 at 00:26, Dionyz Lazar ***@***.***> wrote: Different kind of error pops up: <Error> <Code>AuthorizationHeaderMalformed</Code> <Message>The authorization header is malformed; the region 'cdn' is wrong; expecting 'eu-central-1'</Message> <Region>eu-central-1</Region> <RequestId>EB5E328FFBC0D2DD</RequestId> <HostId>...</HostId> </Error> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#44 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAJFCFggp7NtbmLhkRdaHJJ7Sz7SoZcoks5rdjqygaJpZM4MEucU> .