deno_aws_sign_v4's Introduction

deno_aws_sign_v4

Generates AWS Signature V4 for AWS low-level REST APIs.

Example

The below example will generate signed headers based on the region and credentials in following ENV variables:

AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY
AWS_SESSION_TOKEN
AWS_REGION

import { AWSSignerV4 } from "https://deno.land/x/[email protected]/mod.ts";

const signer = new AWSSignerV4();
const body = new TextEncoder().encode("Hello World!");
const request = new Request("https://test-bucket.s3.amazonaws.com/test", {
  method: "PUT",
  headers: { "content-length": body.length.toString() },
  body,
});
const req = await signer.sign("s3", request);

const response = await fetch(req);

You can also explicitly specify credentials and a region when constructing a new AWSSignerV4:

const signer = new AWSSignerV4("us-east-1", {
  awsAccessKeyId: "accesskey";
  awsSecretKey: "secretkey";
  sessionToken: "sessiontoken";
});

Related projects

The module is licenced under GPL-3.0. For more see the LICENCE file.

This module is forked from @silver-xu's work in [https://github.com/silver-xu/deno-aws-sign-v4]. Many thanks to them. This fork has some large feature improvements and bug fixes, and has tests.

deno_aws_sign_v4's People

Contributors

Stargazers

Watchers

deno_aws_sign_v4's Issues

Important : dead domain

The domain denopkg.com which is used for the hmac function is for sale, so the code is no longer working,

More logs:
export {hmac} from "https://denopkg.com/chiefbiiko/[email protected]/mod.ts";

at https://deno.land/x/[email protected]/deps.ts:1:10

Issues when running in deno deploy

I am getting this error when running deploying to deploy (not present when running locally in deployctl) probably because of the fetch rewrite of 1.9.1:

❗️    TypeError: This property is not implemented.
    at Request.get cache (deno:op_crates/fetch/23_request.js:343:13)
    at AWSSignerV4.sign (https://deno.land/x/[email protected]/mod.ts:86:28)
    at S3Bucket._doRequest (https://deno.land/x/[email protected]/src/bucket.ts:26:50)
    at S3Bucket.getObject (https://deno.land/x/[email protected]/src/bucket.ts:152:32)
    at unknownHandler (https://raw.githubusercontent.com/denosaurs/crux.land/9069446ebf0b9fe1ab17f61e72d595a4e31a64f0/main.ts:40:35)
    at https://raw.githubusercontent.com/denosaurs/crux.land/9069446ebf0b9fe1ab17f61e72d595a4e31a64f0/util/router.ts:7:24
    at https://raw.githubusercontent.com/denosaurs/crux.land/9069446ebf0b9fe1ab17f61e72d595a4e31a64f0/main.ts:82:7
    at innerInvokeEventListeners (deno:op_crates/web/02_event.js:750:27)
    at invokeEventListeners (deno:op_crates/web/02_event.js:785:5)
    at dispatch (deno:op_crates/web/02_event.js:660:11)

This could technically also be an issue with s3.