containers-roadmap | public roadmap for AWS container services | AWS library

Disclaimer, I don't have personal experience with eBPF on AWS ECS, however I have some experience with eBPF requirements since I maintain a loader library.

In general to use eBPF you need:

• A linux kernel which is compiled with BPF support and the BPF features you want to use.
• Having the the CAP_SYS_ADMIN capability on kernel versions lower than 5.8 or the CAP_BPF capability on kernel versions 5.8 and above (CAP_SYS_ADMIN will still work, but gives you much more than just BPF access).
• Depending on which tools you want to use you might need extra capabilities like CAP_PERFMON to use perf features(uprobe, kprobe, tracepoint) (or CAP_SYS_ADMIN on kernel versions below 5.8)

Using eBPF within a container should not be an issue since containers share the same kernel with the host(containers are just isolated processes on the host).

But since eBPF allows you to probe the kernel this obviously breaks the isolation of the container, and giving CAP_SYS_ADMIN to a container also basically gives it full root access, so security is a challenge(unless you are just using it in development, in which case you can just make your container privileged). That is the reason you won't see eBPF enabled on shared hardware(if things are configured properly).