Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

URL creation for custom domains on AWS CloudFront #9781

Closed
cyberduck opened this issue Dec 8, 2016 · 1 comment
Closed

URL creation for custom domains on AWS CloudFront #9781

cyberduck opened this issue Dec 8, 2016 · 1 comment

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Dec 8, 2016

5963342 created the issue

  1. we uploaded files to S3 to a bucket name "shared.jovo.to"
    The https URL for a file (created by Cyberduck) then is something like
    https://shared.jovo.to.s3.amazonaws.com/my-file.jpg

  2. now we want to use our own domain (shared.jovo.to), so we CNAME shared.jovo.to to shared.jovo.to.s3.amazonaws.com. and put http://shared.jovo.to into the Setting "Web URL"
    The http URL now is
    http://shared.jovo.to/my-file.jpg (fine!)
    but the https URL is
    https://shared.jovo.to.s3.amazonaws.com/my-file.jpg
    which kind of works, but gives a security warning, because serving files from S3 with own SSL certificate is not possible and so the domain and the default AES S3 certificate do not match.
    Nothing much Cyberduck can do about this.

  3. we put a Cloudfront distribution in front of the bucket change the CNAME to point to our CloudFront distribution and upload our certificate in CloudFront. Now the HTTPS URL if the file really should be
    https://shared.jovo.to/my-file.jpg (which works fine and shows the correct certificate) but Cyberduck still gives:
    https://shared.jovo.to.s3.amazonaws.com/my-file.jpg (making substitutions to the URL given in "Web URL")

Problem: There is no way of overriding the WebURL for HTTPS
Expected: Cyberduck should use the exact URL given in Web URL and not make substitutions, even for https.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 8, 2016

5963342 commented

I realize this may actually be a duplicate of #9650

Loading

@cyberduck cyberduck closed this Dec 12, 2016
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant