From 0913a6ca57248f9332cbac151c06f65516e94026 Mon Sep 17 00:00:00 2001 From: Wesley Pettit Date: Mon, 19 Dec 2022 21:41:45 -0800 Subject: [PATCH] core dump tutorial: add sanity check idea for Fargate EFS setup Signed-off-by: Wesley Pettit --- troubleshooting/tutorials/remote-core-dump/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/troubleshooting/tutorials/remote-core-dump/README.md b/troubleshooting/tutorials/remote-core-dump/README.md index 6228a5662..88a9842e0 100644 --- a/troubleshooting/tutorials/remote-core-dump/README.md +++ b/troubleshooting/tutorials/remote-core-dump/README.md @@ -196,6 +196,8 @@ Then, you can define the volume in the task definition to be your EFS filesystem }], ``` +As a sanity check that you setup the EFS filesystem correctly on the Fargate task, create a file in the EFS filesystem. For example, `touch my-efs-id.txt`. Then, when you later setup your Fargate task, you can use ECS Exec to check that you can see the file in the cores directory: `ls /cores`. + #### Set initProcessEnabled and enable SYS_PTRACE capability The flag `initProcessEnabled` ensures that when Fluent Bit crashes or is killed, orphaned processes will be cleaned up gracefully. This is primarily important if you are enabling ECS Exec, as it ensures the embedded SSM Agent and shell session are cleaned up gracefully if/when you terminate Fluent Bit.