Hello Cyberduck Community,
Wanted to check here first before submitting a ticket. Has anyone run into issues adding a "Default Hostname" property to the S3 (Credentials from Instance Metadata) profile?
For some reason, when I specify a default hostname property in the profile and create a bookmark from it, I can't connect to the s3 server/hostname specified. In the Cyberduck logs, I can see Cyberduck is trying to connect to the s3.amazon.com
address NOT the one specified in the profile and bookmark.
I've verified the policy attached to the ec2 role works by running some aws cli commands against it.
Here's where I believe it's a Cyberduck issue, if I don't add the Default Hostname property in the ec2 metadata profile and create a bookmark using it. The server defaults to s3.amazon.com
, which doesn't work obviously. If I change the bookmark's server to the desired s3 hostname I want, it connects successfully. This seems to be the work-around, but not what I'm after.
I would greatly appreciate any thoughts or insight into adding a Default Hostname in the ec2 metadata profile. Please let me know if there is any further information I can provide!
Cyberduck Version 7.9.1 (34974)
Windows Server 2019 Datacenter 10.0.17763 Build 17763
Thank you in advance,