-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathtest
More file actions
356 lines (230 loc) · 4.75 KB
/
Copy pathtest
File metadata and controls
356 lines (230 loc) · 4.75 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
## 1. Build your Lambda package
From the project root:
```bash
chmod +x build.sh
./build.sh
```
You should see:
```text
Building DocumentParser Lambda...
Installing Python dependencies...
Copying Lambda source...
Build complete.
```
## 2. Format Terraform
```bash
terraform fmt
```
## 3. Check the infrastructure
```bash
terraform plan
```
Look through it and make sure there are no unexpected changes.
## 4. Deploy
```bash
terraform apply
```
Type:
```text
yes
```
## 5. Get your testing values
Now:
```bash
terraform output
```
You'll see:
```text
upload_url = "https://..."
bucket_name = "..."
queue_url = "https://..."
dlq_url = "https://..."
parser_log_group = "/aws/lambda/..."
upload_log_group = "/aws/lambda/..."
error_handler_log_group = "/aws/lambda/..."
```
Now put them into variables:
```bash
export API_URL=$(terraform output -raw upload_url)
export BUCKET=$(terraform output -raw bucket_name)
export QUEUE_URL=$(terraform output -raw queue_url)
export DLQ_URL=$(terraform output -raw dlq_url)
```
Check:
```bash
echo $API_URL
echo $BUCKET
echo $QUEUE_URL
echo $DLQ_URL
```
# 6. Prepare a test PDF
Create/use a real PDF called:
```text
urgent.pdf
```
Make sure the PDF contains:
```text
URGENT
This is a test invoice.
```
# 7. Open CloudWatch logs
Open **two terminals**.
### Terminal 1 — UploadProcessor
```bash
aws logs tail "$(terraform output -raw upload_log_group)" --follow
```
### Terminal 2 — DocumentParser
```bash
aws logs tail "$(terraform output -raw parser_log_group)" --follow
```
Leave both running.
# 8. Upload the PDF through API Gateway
Open a **third terminal**.
Encode the PDF:
```bash
BASE64=$(base64 -w 0 urgent.pdf)
```
Then:
```bash
curl -X POST "$API_URL" \
-H "Content-Type: application/pdf" \
-d "$BASE64"
```
Watch Terminal 1.
You should see something like:
```text
UPLOAD_SUCCESS: abc123....bin
```
# 9. Check S3
Run:
```bash
aws s3 ls "s3://$BUCKET/"
```
You should see your uploaded file.
You can also open:
**AWS Console → S3 → your bucket**
and see the object.
# 10. Check SQS
Run:
```bash
aws sqs get-queue-attributes \
--queue-url "$QUEUE_URL" \
--attribute-names ApproximateNumberOfMessages
```
Don't worry if it says `0`.
Your Lambda may have already picked the message up.
Instead, watch **Terminal 2**.
You should see:
```text
PROCESSING_STARTED: ...
SQS_MESSAGE_ID: ...
Found keywords: [...]
DOCUMENT_PROCESSED: ...
```
# 11. Check your email
Because your PDF contains `urgent`, your `DocumentParser` currently publishes to SNS **whenever it finds any of your keywords**.
So you should receive the SNS email.
Check your inbox.
# 12. Verify the complete chain
At this point you've tested:
```text
curl
↓
API Gateway
↓
UploadProcessor Lambda
↓
S3
↓
S3 Event
↓
SQS
↓
DocumentParser Lambda
↓
PDF extraction
↓
Keyword detection
↓
SNS
↓
Email
```
That's your **happy-path test**.
# 13. Now test failure / DLQ
After the happy path works, test your failure handling.
Temporarily put this inside `DocumentParser`:
```python
raise Exception("TEST_DLQ")
```
Then rebuild and deploy:
```bash
./build.sh
terraform apply
```
Upload another PDF:
```bash
BASE64=$(base64 -w 0 urgent.pdf)
curl -X POST "$API_URL" \
-H "Content-Type: application/pdf" \
-d "$BASE64"
```
Watch the parser logs:
```bash
aws logs tail "$(terraform output -raw parser_log_group)" --follow
```
You should see failures.
Because your queue has:
```hcl
maxReceiveCount = 3
```
the message should eventually move to the DLQ.
Check:
```bash
aws sqs get-queue-attributes \
--queue-url "$DLQ_URL" \
--attribute-names ApproximateNumberOfMessages
```
Then watch your error handler:
```bash
aws logs tail "$(terraform output -raw error_handler_log_group)" --follow
```
You should see:
```text
DLQ_DOCUMENT_RECEIVED
DLQ_ALERT_SENT
```
And your SNS email should arrive.
## So your entire testing routine is:
```bash
./build.sh
terraform fmt
terraform plan
terraform apply
terraform output
export API_URL=$(terraform output -raw upload_url)
export BUCKET=$(terraform output -raw bucket_name)
export QUEUE_URL=$(terraform output -raw queue_url)
export DLQ_URL=$(terraform output -raw dlq_url)
```
Then:
**Terminal 1**
```bash
aws logs tail "$(terraform output -raw upload_log_group)" --follow
```
**Terminal 2**
```bash
aws logs tail "$(terraform output -raw parser_log_group)" --follow
```
**Terminal 3**
```bash
BASE64=$(base64 -w 0 urgent.pdf)
curl -X POST "$API_URL" \
-H "Content-Type: application/pdf" \
-d "$BASE64"
```
Then inspect:
**S3 → SQS → Parser logs → SNS email**
Once that works, deliberately break the parser and test:
**Lambda failure → SQS retry → DLQ → ErrorHandler → SNS email.**
That's the exact testing workflow I'd use for your project.