Overview
This guide walks you through configuring Meter’s SIEM integration to export intrusion detection events to your AWS Kinesis stream. Once configured, Meter will continuously stream security events from your network to your chosen SIEM platform for analysis, alerting, and compliance.Prerequisites
Before configuring the integration in Dashboard, you must:- Have an AWS account with permissions to create IAM roles, policies, and Kinesis streams
- Create an AWS Kinesis Data Stream in your AWS account
- Configure IAM roles and trust policies (see Terraform configuration examples)
- Have Dashboard access with SIEM integration write permissions
- Screenshot callout: Verify you have the proper permissions by checking Settings > Organization > Integrations is accessible
Use cases
- Integrate Meter network security events with Splunk, Sumo Logic, or other SIEM platforms
- Stream events to AWS Security Lake for centralized security data management
- Process events with custom AWS Lambda functions for automated incident response
- Archive security events to S3 via Kinesis Firehose for long-term retention
Setup
Gather required information
Before starting, collect the following from your AWS account:- AWS Kinesis ARN: The ARN of your Kinesis Data Stream (format:
arn:aws:kinesis:region:account-id:stream/stream-name
) - Role ARN: The ARN of the IAM role Meter will assume to write to your stream (format:
arn:aws:iam::account-id:role/role-name
) - External ID: A unique secret string you generated for secure role assumption (recommended: 64+ character random string)
How-to
Navigate to SIEM integration settings
- Log in to Meter Dashboard at https://dashboard.meter.com
- Click Settings in the left navigation menu
- Select Organization from the Settings submenu
- Click the Integrations tab
- Click the Services sub-tab
Configure the integration
- In the Services section, locate the SIEM integration card
- Click the Configure button on the SIEM card
- A drawer will open titled “Configure SIEM”
-
Fill in the required fields:
AWS Kinesis ARN
- Paste the full ARN of your Kinesis Data Stream
- Example:
arn:aws:kinesis:us-east-1:123456789012:stream/meter-siem-events
- Paste the ARN of the IAM role in your AWS account
- This role must trust Meter’s service role and have permissions to write to the Kinesis stream
- Example:
arn:aws:iam::123456789012:role/MeterSIEMIntegrationRole
- Paste the external ID you generated and configured in the IAM role’s trust policy
- This secret prevents the confused deputy security problem
- Example:
9167190a4095f18bb33c84d75f9596366ee0cd392332e72f130f66da38c320d3
- Click Save to create the integration
Verify integration status
- After saving, you’ll return to the Services page
- The SIEM integration card now displays:
- A Configuration button (replaces the Configure button)
- An integration status badge showing the current state
-
Integration status indicators:
- Active (green checkmark): Events are being successfully delivered
- Unauthorized (red X): Authentication failed - verify your Role ARN, External ID, and IAM trust policy
- Unknown (gray): Initial state before first event delivery attempt
- Hover over the status badge to see the last status update time
Send a test event
- Click the Configuration button to open the integration details
- In the configuration drawer, locate the Send test event button
- Click Send test event
- A test IDS detection event will be immediately sent to your Kinesis stream
- A success notification will appear if the test event was delivered
- If the test fails, an error notification will display with details about the failure (e.g., “Unauthorized - check your Role ARN and External ID”)
- Verify the test event arrived in your Kinesis stream:
- Use the AWS Kinesis Console to view recent records
- Or check your downstream SIEM platform for a test event with
type: "TYPE_TEST"
Delete the integration
- From the configuration drawer, click the Delete button at the bottom
- A confirmation dialog will appear: “Are you sure you want to delete this SIEM integration?”
- Click Delete to confirm removal
- The integration will be immediately deleted and event delivery will stop
- You can create a new integration at any time by clicking Configure again
Configuration options
Field | Required | Description | Example |
---|---|---|---|
AWS Kinesis ARN | Yes | The full ARN of your Kinesis Data Stream | arn:aws:kinesis:us-east-1:123456789012:stream/meter-siem |
Role ARN | Yes | The IAM role ARN that Meter will assume | arn:aws:iam::123456789012:role/MeterSIEMRole |
External ID | Yes | Secret string for secure role assumption | 9167190a... (64+ chars) |
Best practices
Monitoring
- Check status regularly: Monitor the integration status badge in Dashboard to detect delivery failures quickly
- Set up alerts: Configure CloudWatch alarms on your Kinesis stream’s
IncomingRecords
metric to alert if event flow stops - Test after changes: Always send a test event after modifying IAM policies, Kinesis stream configurations, or rotating credentials
Operational
- Document your configuration: Keep a record of your AWS Kinesis ARN, Role ARN, and when the External ID was last rotated
- Plan for downtime: If you need to delete and recreate the integration, events generated during the gap will not be backfilled
- Validate downstream: After initial setup, verify events are reaching your SIEM platform and being parsed correctly
Troubleshooting
Integration status shows “Unauthorized”
Cause: Meter cannot assume the IAM role you specified. Solutions:- Verify the Role ARN is correct and the role exists in your AWS account
- Check the IAM role’s trust policy allows Meter’s service role ARN to assume it
- Confirm the External ID in Dashboard exactly matches the one in the IAM trust policy (no extra spaces or characters)
- Ensure the IAM role has permissions to write to the Kinesis stream (see Terraform examples)
Test event succeeds but no events appear in my SIEM
Cause: Events are reaching Kinesis but not being consumed by your downstream system. Solutions:- Verify your Kinesis consumer (Lambda, Firehose, etc.) is running and has permissions to read from the stream
- Check CloudWatch Logs for your consumer for parsing errors
- Confirm your SIEM platform is configured to ingest from the correct Kinesis stream
- Review the event schema in the technical overview to ensure your parser handles CloudEvents format
Integration status never updates from “Unknown”
Cause: No IDS events have been generated yet, or the integration was just created. Solutions:- Wait for network activity to trigger IDS detections (this can take minutes to hours depending on traffic)
- Click Send test event to immediately trigger a status update
- Verify your network has IDS features enabled (contact Meter support if unsure)
Related resources
- SIEM integration technical overview
- Terraform configuration examples
- AWS IAM roles documentation
- AWS Kinesis Data Streams documentation