Bucket that breaks DNS rules - Workaround
Posted: Tue Dec 11, 2012 7:51 am
You may experiment connection issue with US buckets that do not conform AWS S3 DNS rules (i.e. bucket name with uppercase). Rules are defined in link below:
http://docs.amazonwebservices.com/Amazo ... tions.html
It's due to virtual host addressing, bucket is accessed through (1) http://bucketname.s3.amazonaws.com and not through (2) http://s3.amazonaws.com/bucketname then DNS rules applies and you may get issues in S3Anywhere and other software if you do not conform rules.
However, it may be too late for you, your bucket is already created and you don't want to move/rename it. Since 1.9.6, S3Anywhere provides a new option to allow #2 addressing and then get rid of DNS rules.
To apply: Edit->Advanced->Expert/Specific S3 settings->Virtual Host->Disable->Back->Save.
http://docs.amazonwebservices.com/Amazo ... tions.html
It's due to virtual host addressing, bucket is accessed through (1) http://bucketname.s3.amazonaws.com and not through (2) http://s3.amazonaws.com/bucketname then DNS rules applies and you may get issues in S3Anywhere and other software if you do not conform rules.
However, it may be too late for you, your bucket is already created and you don't want to move/rename it. Since 1.9.6, S3Anywhere provides a new option to allow #2 addressing and then get rid of DNS rules.
To apply: Edit->Advanced->Expert/Specific S3 settings->Virtual Host->Disable->Back->Save.
- Virtual Host option
- virtualhost.png (23.37 KiB) Viewed 15789 times