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

The parameter Origin does not refer to a valid S3 bucket #3068

Closed
cyberduck opened this issue Mar 17, 2009 · 4 comments
Closed

The parameter Origin does not refer to a valid S3 bucket #3068

cyberduck opened this issue Mar 17, 2009 · 4 comments
Assignees
Labels
bug fixed s3 version:3.1.1
Milestone

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Mar 17, 2009

@dkocher created the issue

I might have missed something, but I can't figure out how to setup an Amazon CloudFront distribution (I have a AWS account with S3 and Cloudfront enabled)
When I try to set the check box, the Where field stays at Unknown, pressing "apply" shows an error: The parameter Origin does not refer to a valid S3 bucket.
The transcript is:

Date: Wed, 18 Feb 2009 10:59:04 GMT[\r][\n]
Cneonction: close[\r][\n]
Server: CloudFront[\r][\n]
[\r][\n]
[\r][\n]
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 17, 2009

@dkocher commented

This issue occurs only when creating a new distribution. Updating an existing distribution works as expected. The issue seems to be that the Origin parameter is expected to be <bucketname>.s3.amazonaws.com but we only send <bucketname> for the parameter.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 17, 2009

@dkocher commented

The documentation in the CloudFront developer guide is clear about this:

''When you create the distribution, you specify the origin server bucket's name using this format:
.s3.amazonaws.com. Do not use the Amazon S3 path style for specifying the bucket,
which is s3.amazonaws.com/. If the bucket has a CNAME alias, you must specify the
bucket name and not the CNAME alias.''

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 17, 2009

@dkocher commented

In 70f4ab2. bedspread

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 18, 2009

@dkocher commented

The nightly build is now available.

@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.
Labels
bug fixed s3 version:3.1.1
Projects
None yet
Development

No branches or pull requests

2 participants