Logentries Docs

Find comprehensive guides and documentation to help you start and continue to work with Logentries.

    

Search results for "{{ search.query }}"

No results found for "{{search.query}}". 
View All Results

S3 Archiving from Logentries

Logentries S3 Archiving allows Logentries customers to utilize the inexpensive and massive storage capabilities of Amazon Web Services’ S3 Archiving features. S3 Archiving sends your Logentries Logs to an AWS S3 Archive, (a bucket of your choice) for storing your log entries received in your Logentries account as a backup.

This S3 Archiving functionality will occur once a day and store the entire day’s logs received the day before.

Benefits

  • Inexpensive and expansive storage of your Logentries Data
  • Longer retention beyond your Logentries plan.
  • Saves you money because these are not stored on Logentries within your retention plan.
  • Users may potentially analyze these logs in a manner in which Logentries doesn’t provide at the moment.

REQUIREMENTS: The Logentries Client must have or create an S3 Bucket. The user must also have S3 permissions set on the specific S3 Bucket (Detailed Below)

S3 Archiving makes it possible for the logs that you forward to Logentries to also be archived on AWS S3.

Setting Up S3 Archiving

For this, you simply need to provide list and upload permissions to an S3 bucket on your AWS account. If you do not have an AWS account and wish to archive your Logentries logs onto S3, you can simply signup to AWS.

Create an S3 bucket on AWS account where you wish to archive your Logentries data.
You can find your bucket names under S3 in the “All Buckets” view of your AWS console.

The “user” that you need to give permissions to is archive@logentries.com, you can also use the canonical ID a9c2e4259cad99e03b67c7450d6cc9c0d4f3243363c80ca73f6b5152ff293bb0. This “user” requires list, view, and upload permissions. See the image to the below for details. The user will not be available to choose from the drop down, you will need to type in the account manually. If archive@logentries.com does not work for you in the verification process please contact support@logentries.com who will manually add the your bucket to the service.

The user here should be a9c2e4259cad99e03b67c7450d6cc9c0d4f3243363c80ca73f6b5152ff293bb0. After entering this correctly, AWS may shorten this user name to “archive” (as shown below)

NOTE If you are in the Frankfurt AWS region you will not be able to use archive@logentries.com as a grantee. Instead use the following canonical ID a9c2e4259cad99e03b67c7450d6cc9c0d4f3243363c80ca73f6b5152ff293bb0.

Getting your S3 Archive Bucket name On AWS S3 Archive Page.

To enable archiving to an S3 bucket, (after creating the S3 bucket in AWS as detailed above).

Login to your Logentries Account. Go to your Account Settings.Then navigate to the Logentries Account Setting page and the “Archiving” Tab:

Click Enabled Checkbox.

Enter the precise name of your S3 Bucket you created on your AWS account to store your Logentries Archives.

Click Save and the Logetnries will ‘Validate’ your settings. If everything is validated correctly, you will see “Validation Complete” in your Logentries UI.

S3 Archiving is now set up and will run at a given time in the future to back up your Logentries’ logs to this S3 Archive.

Note: Archiving will not begin immediately. You should see logs in your S3 Archive usually 24 hours after set up. This S3 archive will store logs going forward but not retrospectively, so logs received by Logentries from time of set up will be archived but previous logs will not.

S3 Archiving from Logentries