kanisterio/kanister

[BUG] kando push command fails requiring region to be us-east-1

Open

#3,613 opened on Aug 21, 2025

 (3 comments) (0 reactions) (0 assignees)Go (178 forks)auto 404
acceptedbughelp wanted

Repository metrics

Stars
 (883 stars)
PR merge metrics
 (PR metrics pending)

Description

Describe the bug I am using kanctl for creating a profile pointing to a s3 bucket. created in the eu-west-1 region, so I try to execute:

kanctl create profile s3compliant --access-key XXXXXXXX --secret-key YYYYYY --endpoint s3.amazonaws.com --region eu-west-1 --namespace backup --bucket bucket-eu-west-1

I get as output:

secret 's3-secret-85hvy0' created
Failed the 'Validate bucket region specified in profile' check.. ❌
validation failed, deleting secret 's3-secret-85hvy0'
secret 's3-secret-85hvy0' deleted
Error: profile validation failed: failed to get bucket-eu-west-1: GetBucketLocation: AuthorizationHeaderMalformed: The authorization header is malformed; the region 'eu-west-1' is wrong; expecting 'us-east-1'
	status code: 400, request id: GC3FAMRKRQ6CGEGC, host id: UOX3mNXWRn4sW8QTHdp9i8ZWzrhraDhlqd8MumHXdNfZzZLF2r9kDiNGzfvvNFyYR++DUhTCKhaOgIqGcHOE05hRRyz3zvF/iWaGytP+dho=

If I run

kanctl create profile s3compliant --access-key XXXXXXXXXXXXXX --secret-key YYYYYYYYYYY --endpoint s3.amazonaws.com --region us-east-1 --namespace backup --bucket bucket-us-east-1

I get:

secret 's3-secret-8fhwvt' created
profile 's3-profile-x6459' created

and the profile is correctly created.

Similar issues occurs with kando. It seems neither kando nor kanctl support regions different from us-east-1.

I am using kanister-tools version 0.114.0.

Contributor guide