Skip to content

Commit cc267b3

Browse files
tungbqMarinaburkhardt
authored andcommitted
🐛 updating DynamoDB
1 parent 846e5a6 commit cc267b3

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ The Infrastructure folder contains the terraform code to deploy the AWS resource
4949
- 2 CodeDeploy Applications
5050
- 1 CodePipeline pipeline
5151
- 2 S3 Buckets (1 used by CodePipeline to store the artifacts and another one used to store assets accessible from within the application)
52-
- 1 Dynamodb table (used by the application)
52+
- 1 DynamoDB table (used by the application)
5353
- 1 SNS topic for notifications
5454

5555
## Infrastructure Architecture
@@ -167,18 +167,18 @@ The application folder structure is separeted in components, views and services,
167167
### Client considerations due to demo proposals
168168
1) The assets used by the client application are going to be requested from the S3 bucket created with this code. Please add 3 images to the created S3 bucket.
169169

170-
2) The Dynamodb structure used by the client application is the following one:
170+
2) The DynamoDB structure used by the client application is the following one:
171171

172172
```shell
173173
- id: N (HASH)
174174
- path: S
175175
- title: S
176176
```
177-
Feel free to change the structure as needed. But in order to have full demo experience, please add 3 Dynamodb Items with the specified structure from above. Below is an example.
177+
Feel free to change the structure as needed. But in order to have full demo experience, please add 3 DynamoDB Items with the specified structure from above. Below is an example.
178178

179179
*Note: The path attribute correspondes to the S3 Object URL of each added asset from the previous step.*
180180

181-
Example of a Dynamodb Item:
181+
Example of a DynamoDB Item:
182182

183183
```json
184184
{
@@ -202,7 +202,7 @@ Swagger was also implemented in order to document the APIs. The Swagger endpoint
202202

203203
The server exposes 3 endpoints:
204204
- /status: serves as a dummy endpoint to know if the server is up and running. This one is used as the health check endpoint by the AWS ECS resources
205-
- /api/getAllProducts: main endpoint, which returns all the Items from an AWS Dynamodb table
205+
- /api/getAllProducts: main endpoint, which returns all the Items from an AWS DynamoDB table
206206
- /api/docs: the Swagger enpoint for the API documentation
207207

208208
## Cleanup

0 commit comments

Comments
 (0)