Configure Amazon S3 Log Collector
The Alert Logic Amazon S3 log collector is designed to collect Amazon Simple Storage Service (S3) logs delivered to an Amazon S3 bucket. You can find S3 logs collected with keyword search in the Alert Logic console Get Started with Search page.
You can configure an instance of the Alert Logic Amazon S3 log collector to collect one of the following application log types:
- Elastic Load Balancing:
- Application Load Balancer
- Classic Load Balancer
- Network Load Balancer
- Amazon Redshift:
- User Activity
- Amazon S3 Audit
- Amazon VPC Flow Logs
You must complete the following to successfully configure your Amazon S3 log collector:
- Set up an SNS topic and IAM role in your AWS account
- Set up S3 notifications in your AWS account
- Configure collection in the Alert Logic console
You can use the same setup in AWS for configuring another instance of the Amazon S3 log collector or the AWS Network Firewall log collector. If you have already completed the setup in AWS and want to reuse it, you can skip to Configure collection in the Alert Logic console.
In the AWS account that hosts your S3 buckets, you must set up an Amazon Simple Notification Service (SNS) topic where AWS publishes S3 notifications. You must also set up an IAM role to grant Alert Logic access to your S3 buckets.
Use an AWS CloudFormation template that Alert Logic provides to set up the SNS topic and IAM role, or you can set them up manually.
Set up an SNS topic and IAM role with a CloudFormation template
Alert Logic recommends that you deploy the Alert Logic CloudFormation template to set up the SNS topic and IAM role.
To set up an SNS topic and IAM role with a CloudFormation template:
- Click the following link, and ensure you select the same region as your S3 bucket. Note this region identifier (for example, us-east-2 for Ohio), which you need when you configure the collector in the Alert Logic console.
- Under Parameters, in the External ID field, enter your Alert Logic Account ID.
- In the Stack Name and AlertLogicAWSAccountId fields, leave the default values.
- Select the I acknowledge that AWS CloudFormation might create IAM resources with custom names check box.
- Click Create stack to deploy the stack.
- View the stack output to retrieve the IAM Role ARN, SNS Topic ARN, and External ID, which you need when you configure the collector in the Alert Logic console.
Set up an SNS topic and IAM Role manually
If you are unable to use CloudFormation in your AWS account, you can use the following procedures instead to set up the SNS topic and IAM role manually.
Set up an SNS topic for S3 notifications manually
In the AWS account that Alert Logic protects, you must create an Amazon SNS topic to which Amazon S3 can publish notifications. The SNS topic must be in the same region as your S3 bucket.
You must also configure the SNS topic access policy to allow S3 to publish notifications to the topic and grant Alert Logic permission to receive and process S3 notifications, specifically object created events.
To set up an SNS topic for S3 notifications manually:
- Sign in to the Amazon SNS console.
- In the left navigation pane, choose Topics.
- Choose to create a Standard topic.
- In the Details section, enter a descriptive Name for the topic (for example, my-sns-topic).
- Click this link to download the S3 SNS access policy document (JSON file). Keep the link open so you can edit the example as described next.
- In the Access policy section, use the downloaded example to configure the SNS topic access policy to allow S3 to publish notifications to the topic and grant Alert Logic permission to subscribe to updates.
The example allows the publishing of S3 notifications from S3 bucket "my-bucket" in AWS account 123456789101 to an SNS topic with ARN arn:aws:sns:us-east-2: 123456789101:my-sns-topic. It also grants Alert Logic permission to subscribe to the SNS topic. Edit the example as follows:
- Replace values for the SNS topic ARN in lines 15 and 32.
- Replace the AWS account in line 18.
- Replace the S3 bucket name in line 21.
- Add the statements to your SNS access policy.
- Replace values for the SNS topic ARN in lines 15 and 32.
- Scroll to the end of the form and choose Create topic.
Set up an IAM role in AWS for your S3 buckets manually
Alert Logic uses AWS IAM role-based authentication to enable access to your S3 buckets. Before you configure your S3 collector in the Alert Logic console, you must first create an IAM role with the necessary permissions that Alert Logic can use to retrieve objects from S3.
To create an IAM role for your S3 buckets manually:
- In the AWS console, navigate to the IAM service.
- Under Roles, click Create Role.
- Select Another AWS Account.
- In the Account ID field, enter 230378978437.
- Under Options, select Require external ID, and enter an external ID of your choosing. Make note of it. You will need the value when you configure the collection in the Alert Logic console.
- Click this link to download the S3 IAM policy document (JSON file). Keep the link open so you can copy and paste the information in the next step.
- Under Permissions, click Create policy, and then paste the JSON policy.
- In the Review Policy section, type a descriptive Policy name (for example, AlertLogicS3AccessPolicy).
- Return to your Role creation page, and then click the policy you created.
- Type a Role name, and then click Create Role.
- Note the Role ARN value, which you will need when you configure the collection in the Alert Logic console.
The next step is to send Amazon S3 notifications to the Amazon SNS topic you set up.
To set up S3 notifications:
- Log in to AWS and navigate to the Amazon S3 service console.
- Select the S3 bucket that collects the logs you want Alert Logic to process.
- In the Properties tab, under Advanced settings, click the Events tile.
- Click Add notification.
- In the Name field, type a descriptive name for this event.
- Select the All object create events check box.
- (Optional) To limit the objects that Alert Logic receives notifications about, add the prefix in the Prefix field. Use this option if, for example, you store your logs in a particular folder.
- Leave the Suffix field blank.
- Click the Send to drop-down box, and then select SNS topic.
- Select the SNS topic created in the previous procedure, and then click Save.
A message notifies you whether the event was created successfully, and if not, provides troubleshooting tips.
After you set up the SNS topic, IAM role for your S3 buckets, and S3 event notifications in AWS, you must complete the log collection configuration process in the Alert Logic console. This configuration is an account-level integration, which means you can configure more than one instance of Amazon S3 log collection. This capability is useful when more than one instance of the application exists.
To access the Application Registry page, click the menu icon (). Click Configure, and then click Application Registry.
To add a new application collection:
- In the Application Registry, click the AWS tile, and then click Amazon S3.
- In the Application Name field, enter a name for this Amazon S3 log collection instance.
- Under Collection Method and Policy, in the Application Log Type field, select the type of logs to collect from the S3 bucket.
- In the Role ARN field, enter the ARN for the IAM role granting access to your S3 bucket that you noted earlier.
- In the External ID field, enter the value in the External ID field that you noted earlier.
- In the S3 Bucket Name field, enter the name of the S3 bucket from which to collect logs.
- (Optional) If you want Alert Logic to collect logs from a particular folder in your S3 bucket, in the S3 Object Key Prefix field enter the prefix that identifies the folder, followed by a slash (for example, "logs/"). Leave this field blank if you want Alert Logic to collect all objects in the bucket.
- In the SNS Topic ARN field, enter the ARN of the SNS topic created earlier that receives S3 notifications (for example, arn:aws:sns:us-east-2: 123456789101:my-sns-topic).
- In the SNS Topic Region field, select the AWS region where S3 sends notifications when data is stored in S3.
- Click ADD. Wait a few minutes for the application to create and appear in your application list. Do not click ADD again.
The Health console also indicates whether the application collector is healthy or unhealthy. For more information, see Health.