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

CloudTrial to ElasticSearch #16

Open
johnakash opened this issue Nov 6, 2017 · 1 comment
Open

CloudTrial to ElasticSearch #16

johnakash opened this issue Nov 6, 2017 · 1 comment

Comments

@johnakash
Copy link

Hi Team,

We having nearly 20 AWS accounts and we centralised CloudTrail logs to a single management account. We have a custom build ElasticSearch (5.6) in the EC2 in the same account.

Now we are trying to push all CloudTrail data from S3 bucket to ES (with put object as event trigger for lambda) using a lambda function. When using this we are facing some challenges while pushing the data to ES.

While going through lambda logs it is identified that some event response data (in json) is not maintaining proper structures. We are using python codes in lambda functions

Could you please help us to find a way to put all the CloudTrail events to ElasticSearch with out any failure.

@pacohope
Copy link

I realise this is a year-old question. But if the goal is getting CloudTrail into ElasticSearch, this Lambda function is probably not the way you want to do it. The documentation on CloudTrail talks about how you get CloudTrail going to CloudWatch Logs. Then, CloudWatch Logs can stream directly to ElasticSearch. You don't have to send the CloudTrial to S3 (unless you want to) and you don't have to use Lambda.

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

2 participants