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
+33Lines changed: 33 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -393,6 +393,39 @@ services:
393
393
AWS_LAMBDA_LOG_FORMAT: JSON
394
394
```
395
395
396
+
### Check the updated values
397
+
398
+
Run the following command:
399
+
400
+
```shell
401
+
docker compose up --abort-on-container-exit
402
+
```
403
+
404
+
> [!NOTE]
405
+
> On this execution you'll be able to confirm two of the values are working.
406
+
> Find the Lambda `REPORT` log and you'll now see `Memory Size: 128 MB Max Memory Used: 128 MB` instead of the previous `Memory Size: 3008 MB Max Memory Used: 3008 MB`.
407
+
> Find the `Hello world!` log and you'll see it has now switched to a JSON structured log rather than just text.
408
+
409
+
### Check the timeout
410
+
411
+
Update `docker-compose.yaml`:
412
+
413
+
```yaml
414
+
AWS_LAMBDA_FUNCTION_TIMEOUT: 0
415
+
```
416
+
417
+
Run the following command:
418
+
419
+
```shell
420
+
docker compose up --abort-on-container-exit
421
+
```
422
+
423
+
> [!NOTE]
424
+
> On this execution you'll see that the `curl` container received `Task timed out after 0.00 seconds`.
425
+
> Find the Lambda `REPORT` again and you'll see `Init Duration: 0.00 ms Duration: 0.00 ms Billed Duration: 0 ms`.
426
+
>
427
+
> **Be sure to set `AWS_LAMBDA_FUNCTION_TIMEOUT` back to `3` now.**
428
+
396
429
### Create the events subdirectory
397
430
398
431
Create the events subdirectory in the root (keep events outside the code folder):
0 commit comments