AWS eks documentation change
Summary
Corrected URL for Docker's default seccomp profile.
Security assessment
The change fixes a broken link to Docker's seccomp profile. While seccomp relates to security, this is a routine documentation maintenance update. No new security information is added, and there's no evidence of a patched vulnerability.
Diff
diff --git a/eks/latest/best-practices/runtime-security.md b/eks/latest/best-practices/runtime-security.md index 717c2d30b..d93b7fd12 100644 --- a//eks/latest/best-practices/runtime-security.md +++ b//eks/latest/best-practices/runtime-security.md @@ -29 +29 @@ With secure computing (seccomp) you can prevent a containerized application from -Seccomp works by intercepting syscalls and only allowing those that have been allowlisted to pass through. Docker has a [default](https://github.com/moby/moby/blob/master/profiles/seccomp/default.json) seccomp profile which is suitable for a majority of general purpose workloads, and other container runtimes like containerd provide comparable defaults. You can configure your container or Pod to use the container runtime’s default seccomp profile by adding the following to the `securityContext` section of the Pod spec: +Seccomp works by intercepting syscalls and only allowing those that have been allowlisted to pass through. Docker has a [default](https://github.com/moby/profiles/blob/main/seccomp/default.json) seccomp profile which is suitable for a majority of general purpose workloads, and other container runtimes like containerd provide comparable defaults. You can configure your container or Pod to use the container runtime’s default seccomp profile by adding the following to the `securityContext` section of the Pod spec: