Examples of various configurations to illustrate how to define configurations to deploy to ECS with FireLens logging configuration, using FluentBit, via Compose-X.
All the examples in this repository are used as tests for end-to-end testing when working on new features and version of ECS Compose-X
- Declare FireLens with cloudwatch plugin
- Declare FireLens with firehose plugin
- Replace awslogs with FireLens cloudwatch plugin
The following examples take things a step further and will use Compose-X Files Composer as a sidecar that will load up the configuration for FireLens to include and use in final deployment.
A lot of examples available today, which are remarkable btw, in the amazon-ecs-firelens-examples GIT repository, all involve adding a configuration file to the container when you want to use advanced configurations in AWS Fargate.
On EC2 deployments, you can pull the configuration from S3. Which is great, if it never changes.
With the x-logging.FireLens extension, I really wanted to have something that would give users the agility to change configuration quickly, dynamically, and without having to worry about where in AWS the configuration is stored.
And so, the current implementation allows to deploy to any ECS compute target (EC2, Fargate, ECS Anywhere) and never have to make any changes.