You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to use a custom s3 endpoint endpoints.s3.
It should work since v0.69.12
When I'm right the backend-config should something like: -backend-config='endpoints={s3="https://s3-nbg1.foo.bar"}'
╷
│ Error: Missing close bracket on index
│
│ on -backend-config="endpoints=map[s3:https://s3-nbg1.foo.bar]" line 1:
│ (source code not available)
│
│ The index operator must end with a closing bracket ("]").
╵
Steps To Reproduce
When I run terragrunt init I get the described error.
@Scarbous , to be honest, I haven't needed to setup a custom s3 endpoint for OpenTofu/Terraform backends, and I don't have experience tackling this kind of configuration. Are you interested in doing some more investigation here, and proposing a solution for your bug?
qhga
added a commit
to qhga/terragrunt
that referenced
this issue
Apr 29, 2025
@yhakbar Today I discovered terragrunt and immediately ran into the same problem.
Since this tool could be really useful for my current project, I troubleshooted a bit and the solution should be as follows:
# The value for the enpoint map has to be formatted correctly
-backend-config="endpoints=map[s3:https://object.storage.eu01.mycloud.mep]"# Input has to be valid json
-backend-config=endpoints='{"s3": "https://object.storage.eu01.mycloud.mep"}'
When manually adjusting this value in the generated command, the custom S3 endpoint works.
I took some time to create a WIP PR #4225 that works, but it still requires proper logging in case the json encoding fails.
Describe the bug
I want to use a custom s3 endpoint
endpoints.s3
.It should work since v0.69.12
When I'm right the backend-config should something like:
-backend-config='endpoints={s3="https://s3-nbg1.foo.bar"}'
Steps To Reproduce
When I run
terragrunt init
I get the described error.Expected behavior
It uses my custom s3 endpoint
Nice to haves
Versions
Additional context
The text was updated successfully, but these errors were encountered: