1 Answer
- Newest
- Most votes
- Most comments
0
Hi check these steps to resolve issue Hope it helps You:
IAM Role Permissions: The Firehose delivery stream needs appropriate permissions to access the VPC endpoint and communicate with the HEC endpoint.
VPC Endpoint Policy: The VPC endpoint might have restrictions on inbound traffic, which could prevent Firehose from accessing the Splunk endpoint.
Potential Causes:
- IAM Policy Issues: Firehose might not have the necessary permissions to access the VPC endpoint or perform actions required for HEC communication.
- VPC Endpoint Configuration: The VPC endpoint might not be correctly configured to allow Firehose access.
- Network Connectivity: There might be network issues preventing Firehose from reaching the Splunk endpoint, even within the VPC.
Review IAM Policy for Firehose
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"firehose:PutRecord",
"firehose:PutRecordBatch",
"ec2:DescribeVpcEndpoints",
"ec2:DescribeNetworkInterfaces"
],
"Resource": "*"
}
]
}
Follow the links for more:
- IAM Policies: https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html
- VPC Endpoints: https://docs.aws.amazon.com/vpc/latest/userguide/vpc-endpoints.html
- Firehose: https://docs.aws.amazon.com/firehose/latest/dev/controlling-access.html
- https://docs.splunk.com/Documentation/AddOns/released/Firehose/ConfigureFirehose
Relevant content
- asked 6 months ago
- asked 4 months ago
- asked 3 years ago
Hi Garre, appreciate your response and input!
I can confirm there are no inbound/outbound restrictions for the VPC endpoint based on the security group settings. I did, however, revisit the policy requirements and Lambda assist function noted here: https://docs.aws.amazon.com/firehose/latest/dev/vpc.html. I'm not sure if the Lambda function is still required(?) but have it enabled anyway.
Currently, the IAM policy for Firehose is the default one from when the stream was created and rather long. Is the IAM policy example you provided intended to replace that policy for use with any private VPC endpoint that is configured for Firehose or does a vpce ID need to be specified? If a specific vpce ID needs to be defined, I'm not sure how that would bind to a HEC endpoint since it has no associated arn.
In your scenario, the Lambda function for data transformation is likely not required since you're sending data directly to Splunk using HEC. You can safely disable it if it's not being used.
Review Firehose Logs:
Examine the Firehose delivery stream logs for error messages. They might provide clues about the issue. You can access logs through the Firehose console or CloudWatch.
HEC Token and Configuration: Double-check the HEC token and other configuration settings within Splunk to ensure they are correct.