S3 config does not do anything

[FrederikNygaardSvendsen]

Please see https://discourse.getcockpit.com/t/issues-with-s3-cloudstorage-addon-in-docker/1545 for details

[FrederikNygaardSvendsen]

For reference, this is the content of the post:

Hi

We are Proof Of Concepting, whether or not we want to use Cockpit as our CMS. Im running CockPit in Docker, where i extend agentejo/cockpit and add the addon files and the config.yaml

But when i upload an asset, it doesnt upload to S3. I can see that the iam user’s accesskey is never used, so it looks like its not even attempting to upload it? Any ideas?

IAM Policy:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": [
                "s3:*"
            ],
            "Resource": [
                "arn:aws:s3:::BUCKETNAME/*",
                "arn:aws:s3:::BUCKETNAME"
            ]
        }
    ]
}

config.yaml:

cloudstorage:
    assets:
        type: s3
        key: ACCESS-KEY
        secret: SECRET-ACCESS-KEY
        region: eu-west-1
        bucket: BUCKETNAME

Dockerfile:

FROM agentejo/cockpit

ARG CONFIG_FILE

COPY CloudStorage-master-52afa0f5389c5bc75e961ae60fd17ad78f5ed58c/ /var/www/html/addons/CloudStorage/

COPY ${CONFIG_FILE} /var/www/html/config/config.yaml

Everything looks correct inside the built docker image

The folder CloudStorage-master-52afa0f5389c5bc75e961ae60fd17ad78f5ed58c contains the content of the master branch (commit: 52afa0f) from CloudStorage, which is copied into the image as instructed - as is the config.yaml.

Please help, as this is a show stopper for us 😦

Kind Regards
Frederik

[eLoyyyyy]

the original discourse conversation is already solved. Can you share us the solution?