Changed DynamoDB rangeKey & relative settings && update README.MD about binary support && Added file buffer size console log to know binary file buffer is coming well

Author: TylerShin

README.md

@@ -51,6 +51,15 @@ just run
 npm run deploy:prod
 ```
 
+**IMPORTANT**
+
+![Set API Gateway](https://m7ix47c297.execute-api.us-east-1.amazonaws.com/prod/getImage?id=2017-06-11T03:22:10.250Z&filename=a11ebe37-312f-4178-b43a-517fe801340e&width=800)
+
+You should set lambda-image-manager's API Gateway's binary support option.
+
+At API Gateway setting page, set binary option allow header to "image/*".
+Then, **Deploy** API Gateway once again in console dashboard.
+
 ## Running the tests
 
 WIP

serverless.yml

@@ -54,12 +54,12 @@ resources:
         AttributeDefinitions:
           - AttributeName: fileId
             AttributeType: S
-          - AttributeName: version
+          - AttributeName: id
             AttributeType: S
         KeySchema:
           - AttributeName: fileId
             KeyType: HASH
-          - AttributeName: version
+          - AttributeName: id
             KeyType: RANGE
         ProvisionedThroughput:
           ReadCapacityUnits: 5

src/db/model/imageMeta.ts

@@ -7,11 +7,11 @@ const imageMetaSchema = new Schema({
     type: String,
     hashKey: true,
   },
-  version: {
+  id: {
     type: String,
     rangeKey: true,
   },
-  id: {
+  version: {
     type: String,
   },
   fileName: {

src/handlers/uploadImage/index.ts

@@ -4,6 +4,7 @@ import FilenameMaker from "../../helpers/filenameMaker";
 const handler: AWSLambda.ProxyHandler = async (event, context, _callback) => {
   const buffer = new Buffer(event.body as string, "base64");
   const fileSize = buffer.byteLength;
+  console.log(fileSize, "=== file buffer size");
 
   // Size validation
   if (fileSize > process.env.MAX_SIZE_LIMIT) {