Amazon Elastic Container Services (Amazon ECS) now allows you to run Firelens containers as a non-root user, by specifying a User ID in your Task Definition.
Specifying a non-root user with a specific user ID reduces the potential attack footprint by users who may gain access to such software, a security best practice and a compliance requirement by some industries and security services such as the AWS Security Hub. With this release, Amazon ECS allows you to specify a user ID in the “user” field of your Firelens containerDefinition element of your Task Definition, instead of only allowing “user”: “0” (root user).
The new capability is supported in all AWS Regions. See the documentation for using Firelens for more details on how to set up your Firelens container to run as non-root.
Categories: marketing:marchitecture/serverless,general:products/aws-govcloud-us,general:products/amazon-ecs,marketing:marchitecture/containers
Source: Amazon Web Services
Latest Posts
- AWS SAM CLI adds Finch support, expanding local development tool options for serverless applications
- AWS Step Functions now supports Diagnose with Amazon Q
- (Updated) Entra ID: Upcoming changes to support passkey profiles in the authentication methods policy (preview) [MC1097225]
- Amazon Kinesis Data Streams announces new Fault Injection Service (FIS) actions for API errors
![Dynamics 365 Customer Insights – Data – Filter rows from source data for better processing [MC1173012]](https://mwpro.co.uk/wp-content/uploads/2025/06/door-1587863_1920-96x96.webp "Dynamics 365 Customer Insights – Data – Filter rows from source data for better processing [MC1173012] 6")
