You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,7 @@ The Infrastructure folder contains the terraform code to deploy the AWS resource
49
49
- 2 CodeDeploy Applications
50
50
- 1 CodePipeline pipeline
51
51
- 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)
53
53
- 1 SNS topic for notifications
54
54
55
55
## Infrastructure Architecture
@@ -167,18 +167,18 @@ The application folder structure is separeted in components, views and services,
167
167
### Client considerations due to demo proposals
168
168
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.
169
169
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:
171
171
172
172
```shell
173
173
- id: N (HASH)
174
174
- path: S
175
175
- title: S
176
176
```
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.
178
178
179
179
*Note: The path attribute correspondes to the S3 Object URL of each added asset from the previous step.*
180
180
181
-
Example of a Dynamodb Item:
181
+
Example of a DynamoDB Item:
182
182
183
183
```json
184
184
{
@@ -202,7 +202,7 @@ Swagger was also implemented in order to document the APIs. The Swagger endpoint
202
202
203
203
The server exposes 3 endpoints:
204
204
- /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
206
206
- /api/docs: the Swagger enpoint for the API documentation
0 commit comments