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
- Amazon Verified Permissions now supports policy store aliases and named policies and policy templates

- Amazon WorkSpaces Personal now supports unique DNS names for PrivateLink

- AWS announces general availability of Smithy-Java client framework

- (Updated) Microsoft 365 Copilot: User-day export for Copilot dashboard metrics in public preview [MC1222978]
![(Updated) Microsoft 365 Copilot: User-day export for Copilot dashboard metrics in public preview [MC1222978] 5 gift 1420830 1920](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)




![(Updated) Microsoft 365 Copilot: User-day export for Copilot dashboard metrics in public preview [MC1222978] 5 gift 1420830 1920](https://mwpro.co.uk/wp-content/uploads/2025/06/gift-1420830_1920-150x150.webp)
