Update splunk inputs.conf in ECS container instance when task is updated

johannliebert — Fri, 03 Aug 2018 05:55:56 GMT

Hi,

I am using AWS ECS for hosting some of my microservices with splunk installed in my AMI.
I have mapped all my logs from docker containers to the EC2 instance.
Splunk then picks up these logs from EC2 instance.

The problem is, I also need release version number of my microservice to be indexed but it is
configured one time in the inputs.conf when a launch configuration is created from user data.

So, when a new version of my micro service is released, the task definition (docker image) is updated
but the version number in inputs.conf remains old.

Is there any way to solve this problem ?

Re: Update splunk inputs.conf in ECS container instance when task is updated

coccyx — Fri, 03 Aug 2018 15:48:49 GMT

This is I think out of scope for this forum. This is a broader configuration management question of how do you take something out of your CI/CD pipeline and trigger Splunk configuration changes. There are a number of ways to accomplish this, with Puppet, Chef or SaltStack being probably the more popular.

topic Update splunk inputs.conf in ECS container instance when task is updated in Getting Data In

Update splunk inputs.conf in ECS container instance when task is updated

Re: Update splunk inputs.conf in ECS container instance when task is updated