https://github.com/forter/guarddutybeat
An elasticbeat for consuming AWS GuardDuty Events
https://github.com/forter/guarddutybeat
aws beats elasticbeats go golang guardduty
Last synced: 5 months ago
JSON representation
An elasticbeat for consuming AWS GuardDuty Events
- Host: GitHub
- URL: https://github.com/forter/guarddutybeat
- Owner: forter
- License: other
- Archived: true
- Created: 2019-05-26T05:19:44.000Z (about 7 years ago)
- Default Branch: master
- Last Pushed: 2023-03-21T19:20:44.000Z (about 3 years ago)
- Last Synced: 2025-09-15T06:47:17.330Z (9 months ago)
- Topics: aws, beats, elasticbeats, go, golang, guardduty
- Language: Go
- Size: 45.5 MB
- Stars: 0
- Watchers: 4
- Forks: 3
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE.txt
Awesome Lists containing this project
README
# Guarddutybeat
Welcome to Guarddutybeat.
Ensure that this folder is at the following location:
`${GOPATH}/src/github.com/forter/guarddutybeat`
## Getting Started with Guarddutybeat
### Requirements
* [Golang](https://golang.org/dl/) 1.7
### Init Project
To get running with Guarddutybeat and also install the
dependencies, run the following command:
```
make setup
```
It will create a clean git history for each major step. Note that you can always rewrite the history if you wish before pushing your changes.
To push Guarddutybeat in the git repository, run the following commands:
```
git remote set-url origin https://github.com/forter/guarddutybeat
git push origin master
```
For further development, check out the [beat developer guide](https://www.elastic.co/guide/en/beats/libbeat/current/new-beat.html).
### Build
To build the binary for Guarddutybeat run the command below. This will generate a binary
in the same directory with the name guarddutybeat.
```
make
```
### Run
To run Guarddutybeat with debugging output enabled, run:
```
./guarddutybeat -c guarddutybeat.yml -e -d "*"
```
### Test
To test Guarddutybeat, run the following command:
```
make testsuite
```
alternatively:
```
make unit-tests
make system-tests
make integration-tests
make coverage-report
```
The test coverage is reported in the folder `./build/coverage/`
### Update
Each beat has a template for the mapping in elasticsearch and a documentation for the fields
which is automatically generated based on `fields.yml` by running the following command.
```
make update
```
### Cleanup
To clean Guarddutybeat source code, run the following command:
```
make fmt
```
To clean up the build directory and generated artifacts, run:
```
make clean
```
### Clone
To clone Guarddutybeat from the git repository, run the following commands:
```
mkdir -p ${GOPATH}/src/github.com/forter/guarddutybeat
git clone https://github.com/forter/guarddutybeat ${GOPATH}/src/github.com/forter/guarddutybeat
```
For further development, check out the [beat developer guide](https://www.elastic.co/guide/en/beats/libbeat/current/new-beat.html).
## Packaging
The beat frameworks provides tools to crosscompile and package your beat for different platforms. This requires [docker](https://www.docker.com/) and vendoring as described above. To build packages of your beat, run the following command:
```
make release
```
This will fetch and create all images required for the build process. The whole process to finish can take several minutes.