AWS desk
Event date
Published
Last materially updated
No material update since publication
Reviewed by
Avinash Srinivasan, Founder and Lead Engineer
AWS
AWS Batch on Amazon EKS
MG-01

AWS Batch on Amazon EKS Security Context Settings (November 2026): What Startups Need to Know

Our recommendation: Adopt the added job definition settings when your AWS Batch jobs on Amazon EKS need explicit Linux capabilities, seccomp profiles or pod-wide security settings.

Affected: The release covers AWS Batch job definitions for Amazon EKS, including jobs on clusters that enforce the Kubernetes Pod Security Standards restricted profile.

What did the vendor release?

On 13 November 2026, AWS announced additional Kubernetes security context settings in AWS Batch job definitions for Amazon EKS. These include Linux capabilities, seccomp profiles and pod-level settings.

The RegisterJobDefinition API lets you set capabilities and seccompProfile in a container's securityContext, or define pod-wide settings such as fsGroup through securityContext in podProperties. Container-level settings override pod-level defaults.

You can configure the settings through the AWS Management Console, AWS CLI, AWS SDKs or AWS CloudFormation. AWS supports the additions in all AWS Regions where AWS Batch is available.

Which startups are affected?

This release concerns AWS Batch job definitions for Amazon EKS. For clusters enforcing the Kubernetes Pod Security Standards restricted profile, AWS says Batch jobs can now run with only the privileges and system calls they require.

Our recommendation: Prioritise a review if your team runs AWS Batch jobs on EKS and needs to express these security settings in its job definitions. Identify the jobs, their container requirements and any intended pod-wide defaults. Assign a reviewer who can explain why each proposed setting is needed.

Adopt it or keep the existing approach?

Our recommendation: Adopt the added fields when you have a specific security requirement to express. Start with one representative job and record the intended capabilities, seccomp profile and pod-wide settings before changing its definition. Keep the review focused on the privileges and system calls that job needs.

Our recommendation: Keep your existing approach if you have no identified requirement for these fields. Do not schedule a broad migration solely because the settings are available. Revisit that decision when reviewing your job definitions or cluster security requirements.

Our recommendation: Treat container overrides as an explicit review item. Compare each container's settings with the pod defaults, and document any intentional difference. Agree on the expected job result and the evidence the reviewer needs before approving wider use.

What to check before enabling it?

  • Our recommendation: Confirm scope. List the AWS Batch jobs that run on EKS and choose a representative job for the first review. Record whether its cluster enforces the restricted profile.
  • Our recommendation: Check placement. Put proposed capabilities and seccompProfile settings in the intended container's securityContext. Review securityContext in podProperties for pod-wide settings such as fsGroup, then check any container overrides.
  • Our recommendation: Test the intended restrictions. Run the selected job with the proposed definition in a test environment. Check the job's expected result and investigate any failure before extending the change to other jobs.
  • Our recommendation: Review the configuration method. Use the console, CLI, SDK or CloudFormation workflow your team intends to maintain. Keep the reviewed values and their justification together so another engineer can understand the decision.
  • Our recommendation: Set a rollout decision. Record the owner, validation result and conditions for broader adoption. Keep a copy of the existing configuration for comparison, and pause expansion if the selected job does not meet the agreed checks.

Sources

  1. AWS Batch on Amazon EKS adds Linux capabilities, seccomp, and pod-level settings (Amazon Web Services, 13 Nov 2026). Primary source.