Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/dmjio/s3-signer
:cloud: Presigned S3 URLs for Haskell
https://github.com/dmjio/s3-signer
ajax aws aws-s3 haskell hmac s3-signer
Last synced: about 2 months ago
JSON representation
:cloud: Presigned S3 URLs for Haskell
- Host: GitHub
- URL: https://github.com/dmjio/s3-signer
- Owner: dmjio
- License: bsd-2-clause
- Created: 2014-06-09T12:18:15.000Z (over 10 years ago)
- Default Branch: master
- Last Pushed: 2023-06-01T22:51:56.000Z (over 1 year ago)
- Last Synced: 2024-10-28T14:19:39.866Z (2 months ago)
- Topics: ajax, aws, aws-s3, haskell, hmac, s3-signer
- Language: Haskell
- Homepage: http://hackage.haskell.org/package/s3-signer
- Size: 53.7 KB
- Stars: 24
- Watchers: 5
- Forks: 10
- Open Issues: 8
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
s3-signer
======
[](https://hackage.haskell.org/package/s3-signer)
[](https://travis-ci.org/dmjio/s3-signer)
s3-signer is intended to be an aid in building secure cloud-based services with
AWS. This library generates cryptographically secure URLs that
expire at a user-defined interval. These URLs can be used to offload
the process of uploading and downloading large files, freeing your
webserver to focus on other things.
### Features
- Minimal depedencies
- Web framework agnostic
- Reduces web server load
- Simple API
- Ideal for AJAX direct-to-s3 upload scenarios
### Documentation
[S3 Query String Request Authentication](http://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAuthentication.html#RESTAuthenticationQueryStringAuth)
### Implementation
> AWS Specification
```shell
Signature = URL-Encode( Base64( HMAC-SHA1( YourSecretAccessKeyID,UTF-8-Encoding-Of( StringToSign ) ) ) );
```
> Haskell Implementation
```haskell
module Network.S3.Sign ( sign ) where
import Crypto.Hash.SHA1 (hash)
import Crypto.MAC.HMAC (hmac)
import qualified Data.ByteString.Base64 as B64
import Data.ByteString.UTF8 (ByteString)
import Network.HTTP.Types.URI (urlEncode)
-- | HMAC-SHA1 Encrypted Signature
sign :: ByteString -> ByteString -> ByteString
sign secretKey url = urlEncode True . B64.encode $ hmac hash 64 secretKey url
```
### Use Case
```haskell
{-# LANGUAGE OverloadedStrings #-}
module Main where
import Network.S3
main :: IO ()
main = print =<< generateS3URL credentials request
where
credentials = S3Keys "" ""
request = S3Request S3GET "application/zip" "bucket-name" "file-name.extension" 3 -- 3 secs until expired
```
### Result
```haskell
S3URL {
signedRequest =
"https://bucket-name.s3.amazonaws.com/file-name.extension?AWSAccessKeyId=&Expires=1402346638&Signature=1XraY%2Bhp117I5CTKNKPc6%2BiihRA%3D"
}
```
### Snap integration - Downloads
```haskell
-- Quick and dirty example
type FileID = ByteString
makeS3URL :: FileID -> IO S3URL
makeS3URL fileId = generateS3URL credentials request
where
credentials = S3Keys "" ""
request = S3Request S3GET "application/zip" "bucket-name" (fileId <> ".zip") 3
downloadFile :: Handler App (AuthManager App) ()
downloadFile = method POST $ currentUserId >>= maybe the404 handleDownload
where handleDownload uid = do
Just fileId <- getParam "fileId"
-- Ensure file being requested belongs to user else 403...
S3URL url <- liftIO $ makeS3URL fileId
redirect' url 302
```
### Direct to S3 AJAX Uploads
- Configure S3 Bucket CORS Policy settings
- [CORS Docs](http://docs.aws.amazon.com/AmazonS3/latest/dev/cors.html#how-do-i-enable-cors)
```xml
https://my-url-goes-here.com
PUT
*
```
- Retrieve PUT Request URL via AJAX
```haskell
type FileID = ByteString
makeS3URL :: FileID -> IO S3URL
makeS3URL fileId = generateS3URL credentials request
where
credentials = S3Keys "" ""
request = S3Request S3PUT "application/zip" "bucket-name" (fileId <> ".zip") 3
getUploadURL :: Handler App (AuthManager App) ()
getUploadURL = method POST $ currentUserId >>= maybe the404 handleDownload
where handleDownload _ = do
Just fileId <- getParam "fileId"
writeJSON =<< Data.Text.Encoding.decodeUtf8 <$> liftIO (makeS3URL fileId)
```
- Embed FileReader blob data to request
- Send upload request
```javascript
var xhr = new XMLHttpRequest();
xhr.open('PUT', url /* S3-URL generated from server */);
xhr.setRequestHeader('Content-Type', 'application/zip'); /* whatever http-content-type makes sense */
xhr.setRequestHeader('x-amz-acl', 'public-read');
/* upload completion check */
xhr.onreadystatechange = function(e) {
if (this.readyState === 4 && this.status === 200)
console.log('upload complete');
};
/* Amazon gives you progress information on AJAX Uploads */
xhr.upload.addEventListener("progress", function(evt) {
if (evt.lengthComputable) {
var v = (evt.loaded / evt.total) * 100,
val = Math.round(v) + '%',
console.log('Completed: ' + val);
}
}, false);
/* error handling */
xhr.upload.addEventListener("error", function(evt) {
console.log("There has been an error :(");
}, false);
/* Commence upload */
xhr.send(file); // file here is a blob from the file reader API
```
### File Reader Info
[How to read file data from the browser](https://developer.mozilla.org/en-US/docs/Web/API/FileReader)
### Troubleshoooting
- Why do I keep getting 403 forbidden when I attempt to upload or download from a pre-signed URL?
* Ask yourself the following:
- Are my keys specified correctly?
- Did I configure the CORS settings on my bucket properly?
- Still trouble? [Make an issue](https://github.com/dmjio/s3-signer/issues)
- Why are my URLs expiring faster than the specified time?
* Ask yourself the following:
- Is my server's clock synchronized with AWS? [See wiki for NTP info](https://github.com/dmjio/s3-signer/wiki/If-URLs-expire-too-quickly)
### FAQ
- Why didn't you use HMAC-SHA256?
* It's 30% slower, and for all intents and purposes no more secure
than HMAC-SHA1 (no known vulnerabilities exist for it, to my knowledge). Plain
SHA1 is a different story. Collisions can be found, but there is
no known way to apply those to HMAC-SHA1.
* For the curious [SHA-1 is broken](https://www.schneier.com/blog/archives/2005/02/sha1_broken.html)
* For the paranoid (Schneier quote from same article above)
* [Relevant SO Post](http://stackoverflow.com/questions/3334524/hmac-security-is-the-security-of-the-hmac-based-on-sha-1-affected-by-the-colli)
> This attack builds on previous attacks on SHA-0 and SHA-1, and is
> a major, major cryptanalytic result. It pretty much puts a bullet
> into SHA-1 as a hash function for digital signatures (although it
> **doesn't** **affect** applications such as **HMAC** where collisions aren't important).