Cannot access S3 bucket when I connect to vpce and using URL Style = 1

Advertisement

kseeeew
Guest

Cannot access S3 bucket when I connect to vpce and using URL Style = 1

I try setup batch script but cannot access to s3 bucket
open s3://Axxxxxxx:xxxxxxxxx@vpce-xxxxxx-xxxxxxx.s3.ap-southeast-1.vpce.amazonaws.com/ -certificate=""12:34:66:66:66:66:66:66:99:3f:75:3d:66:6b:fe:25:76:66:8d:44:88:38:0c:a7:9e:e7:7a:8f:05:76:19:85"" -rawsettings S3UrlStyle=1
cd /video-call-sit/%cdate%/audio-record/
But found this error
/
transfer        binary    
D:\Batch\S3\videocall\sit
Error changing directory to '/video-call-sit/20260724/audio-record/'.
The specified bucket does not exist

Extra Details: BucketName: video-call-sit.vpce-xxxxxxxx-xxxxxx.s3.ap-southeast-1.vpce.amazonaws.com, RequestId: xxxxxxxxxxxxx, HostId: xxxxxxxxxxxxxxxxxxxxxxxxxxxx/hbL0G5Yd0+qCGYmsfsg=

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
43,017
Location:
Prague, Czechia

Re: Cannot access S3 bucket when I connect to vpce and using URL Style = 1

Can you connect from WinSCP GUI? If you can, please post session log both from GUI and the script.
If not, please post log from aws commandline showing a successful connection (and WinSCP script log).

Reply with quote

kseeeew
Guest

Re: Cannot access S3 bucket when I connect to vpce and using URL Style = 1

After I try swap -rawsettings S3UrlStyle=1 before -certificate=""12:34:66:66:66:66:66:66:99:3f:75:3d:66:6b:fe:25:76:66:8d:44:88:38:0c:a7:9e:e7:7a:8f:05:76:19:85"" It's working. I can manage files on S3 bucket now. Thanks

open s3://AKIAXXXXXXXXXXXXX:SECRETKEY@vpce-0dc3564fffda19bb6-ds1wt9rx.s3.ap-southeast-1.vpce.amazonaws.com/ -rawsettings S3UrlStyle=1 -certificate=""12:34:66:66:66:66:66:66:99:3f:75:3d:66:6b:fe:25:76:66:8d:44:88:38:0c:a7:9e:e7:7a:8f:05:76:19:85""

Reply with quote

martin
Site Admin
martin avatar
Joined:
Posts:
43,017
Location:
Prague, Czechia

Re: Cannot access S3 bucket when I connect to vpce and using URL Style = 1

The order shouldn't matter in general. But, if you have the open command in an actual script file (not on WinSCP commandline in a batch file), the problem might be the double double-quotes. It should be just:
-certificate="12:34:66:66:66:66:66:66:..."
The command is probably broken after the double double-quote. The script might work even with brokent -certificate, if the certificate is cached already (from GUI) and if you are not isolating the script from the GUI configuration (what you should do to make the script portable).

Reply with quote

Advertisement

You can post new topics in this forum