Skip to content
This repository has been archived by the owner on Nov 18, 2024. It is now read-only.

scaleway: S3 issue #122

Open
revolunet opened this issue Oct 11, 2024 · 2 comments
Open

scaleway: S3 issue #122

revolunet opened this issue Oct 11, 2024 · 2 comments

Comments

@revolunet
Copy link

revolunet commented Oct 11, 2024

When runing bin/terraform-init.sh scaleway i get the following error

caused by: Post "https://sts.PAR.amazonaws.com/": dial tcp: lookup sts.PAR.amazonaws.com on 127.0.0.11:53: no such host

Looks like the S3 endpoint defined in backend.conf is not used 🤔

I'm following the cluster-auto documenttation

@p-bizouard
Copy link
Contributor

I did not used the Scaleway backend for a while as our prod is on OVH. I cannot help you on this :(

@lunika
Copy link
Member

lunika commented Oct 14, 2024

The s3 backend conf is used only to share the state. Not for application usage.

Can you provide a complete message stack ?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants