Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:
-
Story Points:1
-
Epic Link:
-
Sprint:Fall 3: Oct 12 - Oct 23, Fall 4 Oct 26 - Nov 6, Fall 5 Nov 9 - Nov 20, Fall 6 Nov 30 - Dec 11, Fall 7 Dec 14 - Dec 23
Description
We would like to increase our use of S3 buckets to provide data to IGB client application via HTTP.
However, some people might be tempted to download the entire contents of a bucket using this same mechanism, which would be costly.
Let's investigate: Is there a way that we could restrict HTTP requests to IGB only for an S3 bucket?
For example, could we create some kind of filtering function or setting that would "greenlight" requests that meet some criteria, such as: the application making the request is IGB.
Attachments
Issue Links
Activity
| Field | Original Value | New Value |
|---|---|---|
| Epic Link | IGBF-2323 [ 18477 ] |
| Description |
We would like to use S3 buckets to provide data to IGB via HTTP calls.
However, some people might be tempted to download the entire contents of a bucket using this same mechanism, which would be costly. Let's investigate: Is there a way that we could restrict HTTP requests to IGB only for an S3 bucket. For example, could we create some kind of filtering function or setting that would "greenlight" requests that meet our criteria, e.g., the application making the request is IGB or an application running on a BioViz host? |
|
| Story Points | 1 | |
| Sprint | Fall 3: Oct 12 - Oct 23 [ 106 ] | |
| Labels | Advanced | |
| Assignee | Ann Loraine [ aloraine ] |
| Summary | Investigate: How can we ignore all HTTP requests to S3 to IGB only? | Investigate: How to restrict HTTP requests |
| Description |
We would like to use S3 buckets to provide data to IGB via HTTP calls.
However, some people might be tempted to download the entire contents of a bucket using this same mechanism, which would be costly. Let's investigate: Is there a way that we could restrict HTTP requests to IGB only for an S3 bucket. For example, could we create some kind of filtering function or setting that would "greenlight" requests that meet our criteria, e.g., the application making the request is IGB or an application running on a BioViz host? |
We would like to increase our use of S3 buckets to provide data to IGB client application via HTTP.
However, some people might be tempted to download the entire contents of a bucket using this same mechanism, which would be costly. Let's investigate: Is there a way that we could restrict HTTP requests to IGB only for an S3 bucket? For example, could we create some kind of filtering function or setting that would "greenlight" requests that meet some criteria, such as: the application making the request is IGB. |
| Assignee | Chirag Chandrahas Shetty [ chirag24 ] |
| Assignee | Chirag Chandrahas Shetty [ chirag24 ] | Ann Loraine [ aloraine ] |
| Assignee | Ann Loraine [ aloraine ] | Chirag Chandrahas Shetty [ chirag24 ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Sprint | Fall 3: Oct 12 - Oct 23 [ 106 ] | Fall 3: Oct 12 - Oct 23, Fall 4 Oct 26 - Nov 6 [ 106, 107 ] |
| Rank | Ranked higher |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Chirag Chandrahas Shetty [ chirag24 ] | Ann Loraine [ aloraine ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
| Assignee | Ann Loraine [ aloraine ] | Chirag Chandrahas Shetty [ chirag24 ] |
| Assignee | Chirag Chandrahas Shetty [ chirag24 ] | Ann Loraine [ aloraine ] |
| Assignee | Ann Loraine [ aloraine ] | Chirag Chandrahas Shetty [ chirag24 ] |
| Sprint | Fall 3: Oct 12 - Oct 23, Fall 4 Oct 26 - Nov 6 [ 106, 107 ] | Fall 3: Oct 12 - Oct 23, Fall 4 Oct 26 - Nov 6, Fall 5 Nov 9 - Nov 20 [ 106, 107, 108 ] |
| Rank | Ranked higher |
| Attachment | screenshot-1.png [ 14941 ] |
| Sprint | Fall 3: Oct 12 - Oct 23, Fall 4 Oct 26 - Nov 6, Fall 5 Nov 9 - Nov 20 [ 106, 107, 108 ] | Fall 3: Oct 12 - Oct 23, Fall 4 Oct 26 - Nov 6, Fall 5 Nov 9 - Nov 20, Fall 6 Nov 23 - Dec 4 [ 106, 107, 108, 109 ] |
| Rank | Ranked higher |
| Sprint | Fall 3: Oct 12 - Oct 23, Fall 4 Oct 26 - Nov 6, Fall 5 Nov 9 - Nov 20, Fall 6 Nov 30 - Dec 11 [ 106, 107, 108, 109 ] | Fall 3: Oct 12 - Oct 23, Fall 4 Oct 26 - Nov 6, Fall 5 Nov 9 - Nov 20, Fall 6 Nov 30 - Dec 11, Fall 7 Dec 14 - Dec 23 [ 106, 107, 108, 109, 110 ] |
| Rank | Ranked higher |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Chirag Chandrahas Shetty [ chirag24 ] | Ann Loraine [ aloraine ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | Ready for Pull Request [ 10304 ] |
| Status | Ready for Pull Request [ 10304 ] | Pull Request Submitted [ 10101 ] |
| Status | Pull Request Submitted [ 10101 ] | Reviewing Pull Request [ 10303 ] |
| Status | Reviewing Pull Request [ 10303 ] | Merged Needs Testing [ 10002 ] |
| Status | Merged Needs Testing [ 10002 ] | Post-merge Testing In Progress [ 10003 ] |
| Resolution | Done [ 10000 ] | |
| Status | Post-merge Testing In Progress [ 10003 ] | Closed [ 6 ] |
| Assignee | Ann Loraine [ aloraine ] | Chirag Chandrahas Shetty [ chirag24 ] |
| Resolution | Done [ 10000 ] | |
| Status | Closed [ 6 ] | To-Do [ 10305 ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | Needs 1st Level Review [ 10005 ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | Needs 1st Level Review [ 10005 ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | Ready for Pull Request [ 10304 ] |
| Status | Ready for Pull Request [ 10304 ] | Pull Request Submitted [ 10101 ] |
| Status | Pull Request Submitted [ 10101 ] | Reviewing Pull Request [ 10303 ] |
| Status | Reviewing Pull Request [ 10303 ] | Merged Needs Testing [ 10002 ] |
| Status | Merged Needs Testing [ 10002 ] | Post-merge Testing In Progress [ 10003 ] |
| Resolution | Done [ 10000 ] | |
| Status | Post-merge Testing In Progress [ 10003 ] | Closed [ 6 ] |