How to Move AWS ALB Access Logs to Glacier

Select Language:

If you want to move your ALB (Application Load Balancer) access logs from S3 to Glacier, setting up a lifecycle policy is the way to go. The first step is to make sure your lifecycle configuration is correctly set up with the right prefix that matches where your logs are stored.

When creating your S3 lifecycle policy, you need to specify a prefix that matches the folder path where your ALB logs reside. Usually, these logs are stored under a path starting with “AWSLogs/” followed by your account ID.

Your lifecycle rule should include a few key parts:
– The correct prefix, like “AWSLogs/” or the specific folder where your logs are kept.
– A transition action that moves the logs to Glacier, which is specified as the “GLACIER” storage class.
– A timing setting, either a certain number of days after the logs are created or a specific date, to decide when the transition will happen.

For example, you might create a rule that says all logs with a prefix like “AWSLogs/” will be moved to Glacier after 30 days. If your bucket has versioning enabled, you can also add rules for moving non-current versions of your logs.

Make sure to turn on the “Status” for the rule by setting it to “Enabled” so that the policy works. Once you set up everything correctly, S3 will automatically start moving your logs—both existing ones and new ones—according to the timeline you’ve chosen.

This way, your logs won’t take up unnecessary space and will be stored cost-effectively in Glacier.