-
Notifications
You must be signed in to change notification settings - Fork 24
object storage 4.4 CORS
- Description
- Tracking
- Related Features
- Related Issues
- Analysis
- Use Cases
- Assumptions and Questions
- Elements
- Interactions
- Abstractions
- Milestones
- Risks
- References
(Adapted from AWS CORS Dev Guide) Cross-origin resource sharing (CORS) defines a way for client web applications that are loaded in one domain to interact with resources in a different domain. With CORS support in S3, you can build rich client-side web applications with S3 and selectively allow cross-origin access to your S3 resources.
We wish to support the S3 CORS feature in Eucalyptus. We expect it to be fully compatible with the AWS CORS feature.
The Eucalyptus web console can use this as well as any user-created browser-based application that is subject to CORS constraints.
- Aug 2016: Initial template
- Sep 2016: First draft, in progress
The Management Console will be adding support for CRUD operations on a bucket's CORS configuration, to be implemented by GUI-2735 JIRA (eucalyptus.atlassian.net).
EUCA-12174 JIRA (eucalyptus.atlassian.net)
TBD
Assumptions and open questions around requirements for the feature.
Assumptions:
Open questions:
A set of CORS Rules that define which other domains can access which resources in a given bucket in what ways
A definition of a set of origins that can access certain resources in a given bucket in certain ways
An HTTP request to an S3 endpoint to perform CRUD operations on a CORS Configuration
An HTTP request to find out if an access attempt to an S3 resource in a different domain would succeed
An HTTP request to access an S3 resource in a different domain from the requesting origin.
See EUCA-12715 JIRA (eucalyptus.atlassian.net) for details.
Areas currently identified as risks:
AWS returns CORS headers in responses for any S3 request, whether it's relevant to that request or not. That covers a lot of touch points in Eucalyptus code, if we want to be fully compatible.