I am using an ESXi host with only IPV6, IPV4 is not configured. It looks like vertical does not have the Amazon S3 IPV6 endpoints implemented since the vertical init commands finishes up with error
Allowing outgoing connections on port 443 to connect to S3 servers
Failed to connect to the bucket vertical: gaierror(-2, ‘Name or service not known’)
I think boto handles IPv6 quite fine, the issue may be how the authorization header is contructed. In this case it looks the region is incorrectly parsed from the url. AWS defines endpoint naming scheme here:
AWS_DEFAULT_REGION is available only in boto3, but not boto.
I think it is just boto failed to parse the region name when ‘eu-central-1’ goes with ‘dualstack’. Endpoints for other regions seem to work fine, like s3.dualstack.us-west-1.amazonaws.com.
I might be able to modify boto to fix the parsing issue. Please stay tuned.
Can you try this build: http://acrosync.com/esxi/vertical (sha256: 52012c7f4680d75df25f77f10800d5f2952120580786c28f1395e4e6f2210680).
I don’t have an IPv6 only esxi to test, but it worked fine on an IPv4 esxi with s3://s3.dualstack.eu-central-1.amazonaws.com/duplicacy-eu as the storage url.