WinSCP doesn't follow S3 bucket naming convention

Advertisement

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
41,490
Location:
Prague, Czechia

Re: WinSCP doesn't follow S3 bucket naming convention

I get "The specified bucket is not valid" from the AWS when I try that.

Please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.

Reply with quote

martin
Site Admin
martin avatar

Re: WinSCP doesn't follow S3 bucket naming convention

Sorry, I do not understand what should the log show. To me it looks like you are using WinSCP to access existing bucket IGR-DataLake-FAT. What's wrong about that? Am I missing something?

Reply with quote

mminihold

Yes. Correct. The bucket IGR-DataLake-FAT is and can be accessed with WinSCP without error. And that's the problem. IGR-DataLake-FAT isn't a valid bucket name! Bucket names can only be lower case and have to follow some rules. It's even worse. The bucket was created with WinSCP which brakes the naming rules and the compatibility. See Amazon S3 bucket naming requirements https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html for correct naming.

Reply with quote

Advertisement

martin
Site Admin
martin avatar

As I wrote before, when I try to create IGR-DataLake-FAT in WinSCP, I get "The specified bucket is not valid" response from AWS.

I've asked you for a log file showing how you can create such bucket in WinSCP.

Reply with quote

Advertisement

You can post new topics in this forum