Before you begin, you’ll need:
s3:GetObjectpermissions for the required S3 bucket
File names in ascending alphanumeric order. This is important because the S3 fetcher’s offset is determined by the name of the last file fetched. We recommend using standard AWS naming conventions to determine the file name ordering and to avoid log duplication.
Send your logs to an S3 bucket
Logz.io fetches your S3 access logs from a separate S3 bucket. S3 access logs are not enabled S3 by default, so you’ll need to set this up.
For help with this, see Amazon S3 Server Access Logging from AWS.
Add the S3 bucket information
To use the S3 fetcher, fill out the S3 bucket information on the S3 access logs log shipping page. You must be logged in to Logz.io.
Check Logz.io for your logs
Give your logs some time to get from your system to ours, and then open Kibana.
If you still don’t see your logs, see log shipping troubleshooting.