S3Drive - Getting same error for 2 different functionalities.

Hey I'm trying to connect my aws s3 using accesskey and secretkey but I'm getting an error "the specified bucket does not exist". Thing is I'm getting same error message for creating a new bucket too. I have setted custom region as "ap-south-1". Please guide me to fix this issue. Thanks in advance. PFA.

Hi, Are you 100% sure that your bucket name is correct? If your bucket exists, but in a different region then you would get: "Bad state: Response has no Location header for redirect" If your access key was incorrect then you would get: "The AWS Access Key Id you provided does not exist in our records". If your secret was incorrect then you would get: "The request signature we calculated does not match the signature you provided. Check your key and signing method.". Can you double check your bucket name? == If you've tried to create a new bucket then any error would've been displayed in the red bottom bar, but if bucket creation suceeeded, then the newly created name would end up in the "Bucket name" field, so you can connect straight away. Note: Any preexisting error displayed under the endpoint field won't be cleared even if bucket creation is successful, which may give false impression that bucket creation fails. When you create a new bucket can you check if your bucket name is prefilled automatically or whether you get some error at the bottom bar?

Tom

Hi, Are you 100% sure that your bucket name is correct? If your bucket exists, but in a different region then you would get: "Bad state: Response has no Location header for redirect" If your access key was incorrect then you would get: "The AWS Access Key Id you provided does not exist in our records". If your secret was incorrect then you would get: "The request signature we calculated does not match the signature you provided. Check your key and signing method.". Can you double check your bucket name? == If you've tried to create a new bucket then any error would've been displayed in the red bottom bar, but if bucket creation suceeeded, then the newly created name would end up in the "Bucket name" field, so you can connect straight away. Note: Any preexisting error displayed under the endpoint field won't be cleared even if bucket creation is successful, which may give false impression that bucket creation fails. When you create a new bucket can you check if your bucket name is prefilled automatically or whether you get some error at the bottom bar?

Thanks for the clarification, cleared the existing bucket name field and creating a new bucket worked. So it always take existing bucket name field as default even if we have text inside the create bucket input field. (edited)

Hi, that's not really what we're finding. Given the: oldbucket in the bucket field, and then, clicking + to Create new bucket and newbucket in the form, upon clicking Create, the newbucket gets created and filled inside the bucket name (thus replacing the oldbucket with newbucket)