Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuration of SC4S hosted on ECS/Fargate #2424

Open
krish-flutter opened this issue Apr 25, 2024 · 0 comments
Open

Configuration of SC4S hosted on ECS/Fargate #2424

krish-flutter opened this issue Apr 25, 2024 · 0 comments

Comments

@krish-flutter
Copy link

What is the sc4s version ?
Latest version

Is there a pcap available?
N/A

What the vendor name?
N/A

What's the product name?
N/A

** Feature Request description: **
Support to run SC4S on ECS/Fargate deployment/configuration

** Should it support TCP or UDP?**
N/A

** Do you want to have it for local usage or prepare a github PR? **
Github PR will be great as it would be officially supported by splunk, but happy to start with local usage
We have an overarching principle to lean on native aws serverless services and in this case we are trying to leverage aws-ecs & aws-fargate.

Can you kindly confirm/support this configuration mechanism? I.e. deploy/run the sc4s containers (docker based) orchestrated by aws-ecs with fargate-launchtype please? Currently we are facing errors while sc4s is trying to start.

Error Log

2024-04-23T15:46:41.207+02:00 starting syslog-ng
[2024-04-23T13:46:43.079546] Failed to grab disk-buffer dirlock; filename='/var/lib/syslog-ng/syslog-ng-disk-buffer.dirlock', error='Bad file descriptor (9)'
[2024-04-23T13:46:43.079546] Error initializing message pipeline; plugin_name='http', location='root generator dest_hec:5:5'
Handling exit 1 and restarting

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant