Conflicting aws credentials environment keys and missing documentation on dynamodb

[YannickTeKulve]

Hi

I wanted to try digger but running in a few issues:

• The enviroment variables to use for dynamodb credentials are the same as s3 backend. We use a local minio so those are not the same for us.
• Missing documentation on what is needed for dynamodb.

[motatoes]

Hi @YannickTeKulve thanks for trying out digger!

The enviroment variables to use for dynamodb credentials are the same as s3 backend. We use a local minio so those are not the same for us.

So you wish to support a separate state backend such as minio and in this case you have a separate set of keys like MINIO_ACCESS_KEY and MINIO_SECRET_KEY is it correct?

Missing documentation on what is needed for dynamodb.

I assume you mean the DynamoDB table which is created by digger for locks. Digger creates this dynamoDB table called DiggerDynamoDBLockTable implicitly on the first run if it does not exist.
We can fill in the documentation for you, you would like to know the IAM policy needed for dynamoDB access using these keys.

Let me know if it is what you meant!

[YannickTeKulve]

Minio: terraform s3 backend can used for minio but uses AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env (it's not logical, but it does work this way).
Dynamodb: yes, but I think documentation on how to get started on your own environment is lacking overall.

[motatoes]

I have added some documentation on the required access for DynamoDB here: https://diggerhq.gitbook.io/digger-docs/cloud-providers/aws

let me know if anything I missed!

[motatoes]

I'll get back to you RE Minio shortly

[motatoes]

Hey @YannickTeKulve we will support -backend-config option for terraform in #16 and you can use this to set it up with minio similar to this article

will this resolve your issue of dealing with multiple keys?

[YannickTeKulve]

Yes I think it would