Skip to content

Commit

Permalink
core dump tutorial: add sanity check idea for Fargate EFS setup
Browse files Browse the repository at this point in the history
Signed-off-by: Wesley Pettit <[email protected]>
  • Loading branch information
PettitWesley committed Jan 4, 2023
1 parent 3f7d2c3 commit 0913a6c
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions troubleshooting/tutorials/remote-core-dump/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down

0 comments on commit 0913a6c

Please sign in to comment.