After upgrading the Splunk Add-on for AWS from version 7.11.0 to 8.1.0, AWS data ingestion stops.
The following error is observed in the internal logs using the below SPL:
SPL:
index=_internal sourcetype=aws:*:log Error
Error Message:
botocore.exceptions.SSLError: SSL validation failed for https://sts.us-west-2.amazonaws.com/ [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:1161)
Confirm that the environment uses self-signed certificates or a private CA for outbound connectivity to AWS endpoints.
In version 7.11.0, appending the self-signed certificate to the app-level cacert.pem files was sufficient to resolve SSL errors.
However, version 8.1.0 relies on Splunk's Python globally, requiring the certificate to be present in additional Splunk core-level directories.
To resolve the issue follow the below steps:
cat /path/to/your_ca_cert.pem >> $SPLUNK_HOME/etc/apps/Splunk_TA_aws/lib/botocore/cacert.pem
cat /path/to/your_ca_cert.pem >> $SPLUNK_HOME/etc/apps/Splunk_TA_aws/lib/certifi/cacert.pem
cat /path/to/your_ca_cert.pem >> $SPLUNK_HOME/lib/python3.9/site-packages/certifi/cacert.pem
cat /path/to/your_ca_cert.pem >> $SPLUNK_HOME/etc/auth/cacert.pem
Note: Replace /path/to/your_ca_cert.pem with the actual path to the certificate file.
$SPLUNK_HOME/bin/splunk restart
Splunk document - Reference
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
01-Oct-2026
|
Initial Release |