├── IAM ├── assume-role-api-gateway.json └── dynamo-full-user-comments-api-sam.json ├── LICENSE ├── README.md ├── bash └── apigateway-dynamodb │ ├── apigateway-dynamo.yaml │ ├── build-package-deploy-dynamo-data-api.sh │ ├── common-variables.sh │ ├── create-role.sh │ └── delete-stack.sh └── images ├── building-scalable-serverless-microservice-rest-data-api-video.png └── implementing-serverless-microservices-architecture-patterns-video.png /IAM/assume-role-api-gateway.json: -------------------------------------------------------------------------------- 1 | { 2 | "Version": "2012-10-17", 3 | "Statement": [ 4 | { 5 | "Sid": "", 6 | "Effect": "Allow", 7 | "Principal": { 8 | "Service": "apigateway.amazonaws.com" 9 | }, 10 | "Action": "sts:AssumeRole" 11 | } 12 | ] 13 | } -------------------------------------------------------------------------------- /IAM/dynamo-full-user-comments-api-sam.json: -------------------------------------------------------------------------------- 1 | { 2 | "Version": "2012-10-17", 3 | "Statement": [ 4 | { 5 | "Sid": "Stmt1422032676021", 6 | "Effect": "Allow", 7 | "Action": [ 8 | "dynamodb:DeleteItem", 9 | "dynamodb:DescribeTable", 10 | "dynamodb:GetItem", 11 | "dynamodb:PutItem", 12 | "dynamodb:Query", 13 | "dynamodb:Scan", 14 | "dynamodb:UpdateItem" 15 | ], 16 | "Resource": [ 17 | "arn:aws:dynamodb:eu-west-1:000000000000:table/user-comments-api-sam" 18 | ] 19 | }, 20 | { 21 | "Effect": "Allow", 22 | "Action": "dynamodb:ListTables", 23 | "Resource": "*", 24 | "Condition": {} 25 | } 26 | ] 27 | } -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "[]" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright [yyyy] [name of copyright owner] 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | Copyright (c) 2017-2018 Starwolf Ltd and Richard Freeman. All Rights Reserved. 2 | 3 | Licensed under the Apache License, Version 2.0 (the "License"). 4 | You may not use this file except in compliance with the License. 5 | A copy of the License is located at http://www.apache.org/licenses/LICENSE-2.0 or in the "license" file accompanying this file. This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. 6 | 7 | # Serverless and Lambdaless Scalable CRUD Data API with AWS API Gateway and DynamoDB 8 | 9 | The full details are part of my [Serverless and Lambdaless Scalable CRUD Data API with AWS API Gateway and DynamoDB blog post on Hacknoon](https://hackernoon.com/serverless-and-lambdaless-scalable-crud-data-api-with-aws-api-gateway-and-dynamodb-626161008bb2). 10 | 11 | We are moving away from the large and complex monolithic architectures that are hard to scale to Microservices architectures. For example, you could have a loosely coupled fleet of microservices each with an API for each data source, integrating with a clustered NoSQL database, such as Cassandra. Adopting Microservices architecture typically means that you need a DevOps team that, for example, setup, monitor and maintain the continuous integration / continuous deployment (CI/CD) pipelines, [Kubernetes](https://kubernetes.io/) container-orchestration platform and monitoring systems. Things are looking better recently as AWS has announced [Amazon Elastic Container Service for Kubernetes (EKS)](https://aws.amazon.com/eks/) and [AWS Fargate](https://aws.amazon.com/fargate/) that help with Kubernetes, but there is still a lot of integration that needs to be built by developers and containers configuration to think about. 12 | 13 | Back in 2014, AWS launch Lambda functions which act as integration glue between services where you only need to write the business logic code to respond to inbound events. These events could be an GET request from API Gateway, new records added to a Kinesis Streams or an object put into S3. Using Lambda has been very popular as they are stateless, have built in event source integration and you only pay per 100ms of execution time. So rather than use a fleet of Microservices running on containers, you can build a highly scalable Serverless stack integrating API Gateway, Lambda and DynamoDB. There are many tutorials on this including my first [video course](https://www.packtpub.com/application-development/building-scalable-serverless-microservice-rest-data-api-video). 14 | 15 | In this repo, I loose the Lambda altogether and have API Gateway directly invoke DynamoDB, to create a full suite of create, read, update, and delete (CRUD) operations. Other posts I've read only cover how to partially do this manually in the AWS console and not in code using [Swagger](https://swagger.io/) and [SAM](https://github.com/awslabs/serverless-application-model), which is what I will show you here. Using Swagger and SAM to deploy the infrastructure and API is realistically what you absolutely want to do to release it to a production environment for minimising human error, repeatability and scalability. 16 | 17 | ## Shell Scripts and Deployment 18 | I'm only describing a subset that you need to get this code and config deployed and tested, for the full details and discussions see my [Serverless and Lambdaless Scalable CRUD Data API with AWS API Gateway and DynamoDB blog post](https://hackernoon.com/serverless-and-lambdaless-scalable-crud-data-api-with-aws-api-gateway-and-dynamodb-626161008bb2). 19 | 20 | ### Setup 21 | 22 | You need to setup AWS CLI and add you profile in `common-variables.sh` and will also need to change the AWS accountId (current set to 000000000000). The AWS accountId is also used in some IAM policies in the IAM folder. In addition the region will have to be changed. To replace your accountId (assume your AWS accountId is 111111111111) you can do it manually or run: 23 | ``` 24 | find ./ -type f -exec sed -i '' -e 's/000000000000/111111111111/' {} \; 25 | ``` 26 | I've done this so you can more easily support multiple AWS Account in a CI pipeline. 27 | 28 | ### List of scripts: 29 | * Execute `./build-package-deploy-dynamo-data-api.sh` - creates the policies, roles, API Gateway methods and DynamoDB 30 | * `apigateway-dynamo.yaml` - SAM template used to creates DynamoDB config and CRUD API methods. 31 | * `assume-role-api-gateway.json` - the API Gateway assume role 32 | * `dynamo-full-user-comments-api-sam.json` - Policy API Gateway uses to access DynamoDB 33 | * Execute `./delete-stack.sh` - deletes the serverless CloudFormation stack 34 | 35 | ### Deployment 36 | ``` 37 | $ aws cloudformation deploy --template-file $template.yaml --stack-name $template --capabilities CAPABILITY_IAM --region $region --profile $profile 38 | ``` 39 | 40 | ## Testing the API 41 | 42 | Logon to the AWS console > API Gateway or you can also use browser plugins like postman for this. 43 | 44 | ### Testing the PUT Method or Create 45 | 46 | As you have no data in DynamoDB yet, let's start by adding some. 47 | 1. Open the [API Gateway](https://console.aws.amazon.com/apigateway/) 48 | 2. On the navigation pane, choose apigateway-dynamo and Resources 49 | 3. In Resources Click on Put 50 | 4. Under /visits - PUT - Method Execution click on Test 51 | 5. In "Request Body" enter the following JSON 52 | 53 | ``` 54 | {"PageId": "444", 55 | "EventCount": 1, 56 | "Message": "happy"} 57 | ``` 58 | 59 | 6. Scroll down and click on the Test button. 60 | 61 | You will see on the right (or under on mobile devices) Status: 200 which means the call was successful and see a response body. You will also see full API logs, which are useful for testing and debugging. These are also stored in CloudWatch logs, which is the first place you need to look at if you start getting 4XX or 5XX errors. 62 | 63 | ### Testing the GET method 64 | 65 | Now that you have a record in DynamoDB, let's retrieve it using a PageId = 444 query. 66 | 1. In resources Click on Put 67 | 2. Under /visits/{PageId} - GET - Method Execution click on Test 68 | 3. In Path for {PageId} enter 444 OR in Query Strings for {PageId} enter PageId=444 69 | 4. Click on the Test button. 70 | 71 | You should get a status: 200 and also see the following Response Body which is what we expect 72 | ``` 73 | { 74 | "comments": [ 75 | { 76 | "PageId": "444", 77 | "Message": "happy", 78 | "EventCount": "1" 79 | } 80 | ] 81 | } 82 | ``` 83 | 84 | ### Testing the POST Method 85 | With the PUT method, you saw that the `EventCount` value remains constant no matter how many times you call it. Now let's test the POST method that increments a counter by the specified value each time it is called. 86 | 87 | 1. In Resources Click on Post 88 | 2. Under /visits - POST - Method Execution click on Test 89 | 2. In "Request Body" enter the following JSON 90 | ``` 91 | {"PageId": "444", 92 | "EventCount": 1, 93 | "Message": "happy"} 94 | ``` 95 | You should get a status: 200 and also see the following Response Body 96 | ``` 97 | "comments": [ 98 | { 99 | "PageId": "444", 100 | "Message": "happy", 101 | "EventCount": "2" 102 | } 103 | ] 104 | } 105 | ``` 106 | 107 | Run it several times and you will see EventCount increment, you can also increment it by more than 1 if you modify the request JSON body EventCount value. Why does this POST method return the current value? It's down to the config `"ReturnValues\": \"ALL_NEW\"` as I wanted to show you the effects of the POST without having to go to the DynamoDB console! 108 | 109 | ### Testing the DELETE Method 110 | 111 | Now that you have a lot of data, maybe you need to delete some records. 112 | 113 | 1. In resources Click on Delete 114 | 2. Under /visits/{PageId} - DELETE - Method Execution click on Test 115 | 3. In Path for {PageId} enter 444 OR in Query Strings for {PageId} enter PageId=444 116 | 4. Click on the Test button. 117 | 118 | You should get a status: 200 and also see the a Response Body of the deleted record, I used the `"ReturnValues\": \"ALL_OLD\"`. 119 | 120 | To double check you can have a look at the DynamoDB in the AWS Console 121 | 1. Open the [DynamoDB Console](https://console.aws.amazon.com/dynamodb) 122 | 2. Under the navigation click on Tables 123 | 3. Under name click on `user-comments-api-sam` 124 | 4. On the tab click on Items 125 | 126 | You should see the record is no longer there, you can also use the Query drop down to check. 127 | 128 | ## Clean up 129 | 130 | To delete the stack simply run `./delete-stack.sh` here are the contents of the shell script: 131 | ``` 132 | $ aws cloudformation delete-stack --stack-name $template --region $region --profile $profile 133 | ``` 134 | 135 | Additional discussions on [Serverless and Lambdaless Scalable CRUD Data API with AWS API Gateway and DynamoDB blog post on Hacknoon](https://hackernoon.com/serverless-and-lambdaless-scalable-crud-data-api-with-aws-api-gateway-and-dynamodb-626161008bb2). 136 | 137 | Not everything can be done with this Lambdaless approach but Serverless computing can be used in most scenarios. If you want to find out more on Serverless microservices and have more complex use cases, please have a look at my video courses and so support me in writing more blog posts. 138 | 139 | Additional implemented Serverless pattern architecture, source code, shell scripts, config and walkthroughs are provided with my video courses: 140 | 141 | |For beginners and intermediates, the [full Serverless Data API](https://www.packtpub.com/application-development/building-scalable-serverless-microservice-rest-data-api-video?utm_source=github) code, configuration and a detailed walk through |For intermediate or advanced users, I cover the implementation of [15+ serverless microservice patterns](https://www.packtpub.com/application-development/implementing-serverless-microservices-architecture-patterns-video?utm_source=github) with original content, code, configuration and detailed walk through | 142 | |:----------|:-------------| 143 | | [![Building a Scalable Serverless Microservice REST Data API Video Course](images/building-scalable-serverless-microservice-rest-data-api-video.png "Building a Scalable Serverless Microservice REST Data API Video Course")](https://www.packtpub.com/application-development/building-scalable-serverless-microservice-rest-data-api-video)| [![Implementing Serverless Microservices Architecture Patterns Video Course](./images/implementing-serverless-microservices-architecture-patterns-video.png "Implementing Serverless Microservices Architecture Patterns Video Course")](https://www.packtpub.com/application-development/implementing-serverless-microservices-architecture-patterns-video) | 144 | 145 | Feel free to connect with me on [LinkedIn](https://www.linkedin.com/in/drfreeman/) or message me on [Medium](https://medium.com/@rfreeman) for comments. -------------------------------------------------------------------------------- /bash/apigateway-dynamodb/apigateway-dynamo.yaml: -------------------------------------------------------------------------------- 1 | AWSTemplateFormatVersion: '2010-09-09' 2 | Transform: AWS::Serverless-2016-10-31 3 | Description: Serverless Data API configured using Swagger specified inline 4 | 5 | Parameters: 6 | Table: {Default: user-comments-api-sam, Type: String} 7 | AccountId: {Default: 000000000000, Type: String} 8 | RoleName: {Default: api-gateway-dynamo-full-user-comments, Type: String} 9 | 10 | Resources: 11 | DynamoDBTable: 12 | Type: AWS::DynamoDB::Table 13 | Properties: 14 | TableName: !Ref Table 15 | SSESpecification: 16 | SSEEnabled: True 17 | AttributeDefinitions: 18 | - AttributeName: PageId 19 | AttributeType: S 20 | KeySchema: 21 | - AttributeName: PageId 22 | KeyType: HASH 23 | ProvisionedThroughput: 24 | ReadCapacityUnits: 1 25 | WriteCapacityUnits: 1 26 | MyApi: 27 | Type: AWS::Serverless::Api 28 | Properties: 29 | StageName: Prod 30 | DefinitionBody: 31 | swagger: 2.0 32 | info: 33 | title: 34 | Ref: AWS::StackName 35 | paths: 36 | "/visits/{PageId}": 37 | get: 38 | consumes: 39 | - "application/json" 40 | produces: 41 | - "application/json" 42 | responses: 43 | "200": 44 | description: "200 response" 45 | schema: 46 | $ref: "#/definitions/Empty" 47 | x-amazon-apigateway-integration: 48 | httpMethod: POST 49 | type: AWS 50 | uri: { "Fn::Sub": "arn:aws:apigateway:${AWS::Region}:dynamodb:action/Query" } 51 | credentials: { "Fn::Sub": "arn:aws:iam::${AccountId}:role/${RoleName}" } 52 | requestTemplates: 53 | application/json: { 'Fn::Sub': "{ \n\ 54 | \t\"TableName\": \"${Table}\",\n\ 55 | \t\"KeyConditionExpression\": \"PageId = :v1\",\n\ 56 | \t\"ExpressionAttributeValues\": {\n\ 57 | \t\t\":v1\": { \n\ 58 | \t\t\t\"S\": \"$input.params('PageId')\"\n\ 59 | \t\t}\n\ 60 | \t}\n}"} 61 | responses: 62 | default: 63 | statusCode: "200" 64 | responseTemplates: 65 | application/json: "#set($inputRoot = $input.path('$'))\n\ 66 | {\n\ 67 | \t\"comments\": [\n\ 68 | \t\t#foreach($elem in $inputRoot.Items) {\n\ 69 | \t\t\t\"PageId\": \"$elem.PageId.S\",\n\ 70 | \t\t\t\"Message\": \"$elem.Message.S\",\n\ 71 | \t\t\t\"EventCount\": \"$elem.EventCount.N\"\n\ 72 | \t\t}#if($foreach.hasNext),#end\n\ 73 | \t#end\n\ 74 | \t]\n}" 75 | 76 | delete: 77 | consumes: 78 | - "application/json" 79 | produces: 80 | - "application/json" 81 | parameters: 82 | - name: "PageId" 83 | in: "path" 84 | required: true 85 | type: "string" 86 | responses: 87 | "200": 88 | description: "200 response" 89 | schema: 90 | $ref: "#/definitions/Empty" 91 | x-amazon-apigateway-integration: 92 | credentials: { "Fn::Sub": "arn:aws:iam::${AccountId}:role/${RoleName}" } 93 | uri: { "Fn::Sub": "arn:aws:apigateway:${AWS::Region}:dynamodb:action/DeleteItem" } 94 | requestTemplates: 95 | application/json: { 'Fn::Sub': "{ \n\ 96 | \t\"TableName\": \"${Table}\",\n\ 97 | \t\"Key\": {\n\ 98 | \t\t\"PageId\": {\n 99 | \t\t\t\"S\": \"$input.params('PageId')\"\n\ 100 | \t\t}\n\ 101 | \t},\n\ 102 | \t\"ConditionExpression\": \"attribute_not_exists(Replies)\",\n\ 103 | \t\"ReturnValues\": \"ALL_OLD\"\n}" } 104 | responses: 105 | default: 106 | statusCode: "200" 107 | passthroughBehavior: "when_no_match" 108 | httpMethod: "POST" 109 | type: "aws" 110 | 111 | "/visits": 112 | put: 113 | consumes: 114 | - "application/json" 115 | produces: 116 | - "application/json" 117 | responses: 118 | "200": 119 | description: "200 response" 120 | schema: 121 | $ref: "#/definitions/Empty" 122 | x-amazon-apigateway-integration: 123 | httpMethod: POST 124 | type: AWS 125 | uri: { "Fn::Sub": "arn:aws:apigateway:${AWS::Region}:dynamodb:action/PutItem" } 126 | credentials: { "Fn::Sub": "arn:aws:iam::${AccountId}:role/${RoleName}" } 127 | requestTemplates: 128 | application/json: { 'Fn::Sub': "{ \n\ 129 | \t\"TableName\": \"${Table}\",\n\ 130 | \t\"Item\": {\n\ 131 | \t\t\"PageId\": {\n\ 132 | \t\t\t\"S\": \"$input.path('$.PageId')\"\n\ 133 | \t\t},\n\ 134 | \t\t\"EventCount\": {\n\ 135 | \t\t\t\"N\": \"$input.path('$.EventCount')\"\n\ 136 | \t\t},\n\ 137 | \t\t\"Message\": {\n\ 138 | \t\t\t\"S\": \"$input.path('$.Message')\"\n\ 139 | \t\t}\n 140 | \t}\n}" } 141 | responses: 142 | default: 143 | statusCode: "200" 144 | post: 145 | consumes: 146 | - "application/json" 147 | produces: 148 | - "application/json" 149 | responses: 150 | "200": 151 | description: "200 response" 152 | schema: 153 | $ref: "#/definitions/Empty" 154 | x-amazon-apigateway-integration: 155 | httpMethod: POST 156 | type: AWS 157 | uri: { "Fn::Sub": "arn:aws:apigateway:${AWS::Region}:dynamodb:action/UpdateItem" } 158 | credentials: { "Fn::Sub": "arn:aws:iam::${AccountId}:role/${RoleName}" } 159 | requestTemplates: 160 | application/json: { 'Fn::Sub': "{\n\t\"TableName\": \"${Table}\",\n\ 161 | \t\"Key\":{\n 162 | \t\t\"PageId\": {\n 163 | \t\t\t\"S\": \"$input.path('$.PageId')\"\n\ 164 | \t\t}\n\ 165 | \t},\n\ 166 | \t\"ExpressionAttributeValues\": {\n\ 167 | \t\t\":event_count\": {\n\ 168 | \t\t\t\"N\": \"$input.path('$.EventCount')\"},\n\ 169 | \t\t\":message\": {\n\ 170 | \t\t\t\"S\": \"$input.path('$.Message')\"}\n\ 171 | \t},\n\ 172 | \t\"UpdateExpression\": \"ADD EventCount :event_count SET Message = :message\",\n\ \t\"ReturnValues\": \"ALL_NEW\"\n}"} 173 | responses: 174 | default: 175 | statusCode: "200" 176 | definitions: 177 | Empty: 178 | type: "object" 179 | title: "Empty Schema" 180 | -------------------------------------------------------------------------------- /bash/apigateway-dynamodb/build-package-deploy-dynamo-data-api.sh: -------------------------------------------------------------------------------- 1 | #!/usr/bin/env bash 2 | # Copyright (c) 2017-2018 Starwolf Ltd and Richard Freeman. All Rights Reserved. 3 | # Licensed under the Apache License, Version 2.0 4 | 5 | #Variables 6 | . ./common-variables.sh 7 | 8 | #Create the roles needed by API Gateway 9 | ./create-role.sh 10 | 11 | #Deploy your Serverless Stack using SAM + Cloudformation 12 | aws cloudformation deploy --template-file $template.yaml --stack-name $template --capabilities CAPABILITY_IAM --region $region --profile $profile 13 | -------------------------------------------------------------------------------- /bash/apigateway-dynamodb/common-variables.sh: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | # Copyright (c) 2017-2018 Starwolf Ltd and Richard Freeman. All Rights Reserved. 3 | # Licensed under the Apache License, Version 2.0 4 | 5 | export profile="demo" 6 | export region="eu-west-1" 7 | export aws_account_id="000000000000" 8 | export template="apigateway-dynamo" 9 | 10 | -------------------------------------------------------------------------------- /bash/apigateway-dynamodb/create-role.sh: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | # Copyright (c) 2017-2018 Starwolf Ltd and Richard Freeman. All Rights Reserved. 3 | # Licensed under the Apache License, Version 2.0 4 | 5 | #This Script creates an API Gateway role and attaches the 2 required policies 6 | 7 | #Settings 8 | . ./common-variables.sh 9 | 10 | #Setup API Gateway Role 11 | role_name=api-gateway-dynamo-full-user-comments 12 | aws iam create-role --role-name ${role_name} \ 13 | --assume-role-policy-document file://../../IAM/assume-role-api-gateway.json --profile $profile 14 | 15 | #Add Policy for API Gateway to write to logs 16 | role_policy_arn="arn:aws:iam::aws:policy/service-role/AmazonAPIGatewayPushToCloudWatchLogs" 17 | aws iam attach-role-policy \ 18 | --role-name "${role_name}" \ 19 | --policy-arn "${role_policy_arn}" --profile ${profile} 20 | 21 | #Create DynamoDB Policy 22 | policy_name="dynamo-full-user-comments-api-sam" 23 | aws iam create-policy --policy-name ${policy_name} --policy-document file://../../IAM/${policy_name}.json --profile ${profile} 24 | 25 | #Attach Policy for API Gateway to access DynamoDB 26 | role_policy_arn="arn:aws:iam::${aws_account_id}:policy/${policy_name}" 27 | aws iam attach-role-policy \ 28 | --role-name "${role_name}" \ 29 | --policy-arn "${role_policy_arn}" --profile ${profile} 30 | -------------------------------------------------------------------------------- /bash/apigateway-dynamodb/delete-stack.sh: -------------------------------------------------------------------------------- 1 | #!/usr/bin/env bash 2 | # Copyright (c) 2017-2018 Starwolf Ltd and Richard Freeman. All Rights Reserved. 3 | # Licensed under the Apache License, Version 2.0 4 | 5 | . ./common-variables.sh 6 | 7 | aws cloudformation delete-stack --stack-name $template --region $region --profile $profile 8 | -------------------------------------------------------------------------------- /images/building-scalable-serverless-microservice-rest-data-api-video.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/astarwolf/serverless-lambdaless-apigateway-dynamodb/3cfdefd3917e43ee6b732c491ecb69831af1ffb0/images/building-scalable-serverless-microservice-rest-data-api-video.png -------------------------------------------------------------------------------- /images/implementing-serverless-microservices-architecture-patterns-video.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/astarwolf/serverless-lambdaless-apigateway-dynamodb/3cfdefd3917e43ee6b732c491ecb69831af1ffb0/images/implementing-serverless-microservices-architecture-patterns-video.png --------------------------------------------------------------------------------