Closed nfilip21 closed 1 day ago
We have been seeing similar errors as reported. Appreciate help here:
07-17-2024 06:03:09.545 +0000 ERROR AwsCredentials [143795 CMUploadReplicatedBucketThread] - Failed to execute runSync() for transaction with uri=https://sts.amazonaws.com http_code=400
07-17-2024 06:03:10.832 +0000 ERROR AwsCredentials [143795 CMUploadReplicatedBucketThread] - Failed to execute runSync() for transaction with uri=https://sts.amazonaws.com http_code=400
07-17-2024 06:03:13.120 +0000 ERROR AwsCredentials [143795 CMUploadReplicatedBucketThread] - Failed to execute runSync() for transaction with uri=https://sts.amazonaws.com http_code=400
07-17-2024 06:03:17.398 +0000 ERROR AwsCredentials [143795 CMUploadReplicatedBucketThread] - Failed to execute runSync() for transaction with uri=https://sts.amazonaws.com http_code=400
07-17-2024 06:03:25.683 +0000 ERROR AwsCredentials [143795 CMUploadReplicatedBucketThread] - Failed to execute runSync() for transaction with uri=https://sts.amazonaws.com http_code=400
07-17-2024 06:03:41.973 +0000 ERROR AwsCredentials [143795 CMUploadReplicatedBucketThread] - Failed to execute runSync() for transaction with uri=https://sts.amazonaws.com http_code=400
07-17-2024 06:04:14.255 +0000 ERROR AwsCredentials [143795 CMUploadReplicatedBucketThread] - Failed to execute runSync() for transaction with uri=https://sts.amazonaws.com http_code=400
07-17-2024 06:05:14.537 +0000 ERROR AwsCredentials [143795 CMUploadReplicatedBucketThread] - Failed to execute runSync() for transaction with uri=https://sts.amazonaws.com http_code=400
07-17-2024 06:06:14.820 +0000 ERROR AwsCredentials [143795 CMUploadReplicatedBucketThread] - Failed to execute runSync() for transaction with uri=https://sts.amazonaws.com http_code=400
07-17-2024 06:07:15.099 +0000 ERROR AwsCredentials [143795 CMUploadReplicatedBucketThread] - Failed to execute runSync() for transaction with uri=https://sts.amazonaws.com http_code=400
07-17-2024 06:08:06.263 +0000 ERROR AwsCredentials [568873 FilesystemOpExecutorWorker-0] - Failed to execute runSync() for transaction with uri=https://sts.amazonaws.com http_code=400
07-17-2024 06:08:07.551 +0000 ERROR AwsCredentials [568873 FilesystemOpExecutorWorker-0] - Failed to execute runSync() for transaction with uri=https://sts.amazonaws.com http_code=400
07-17-2024 06:08:09.830 +0000 ERROR AwsCredentials [568873 FilesystemOpExecutorWorker-0] - Failed to execute runSync() for transaction with uri=https://sts.amazonaws.com http_code=400
07-17-2024 06:08:14.112 +0000 ERROR AwsCredentials [568873 FilesystemOpExecutorWorker-0] - Failed to execute runSync() for transaction with uri=https://sts.amazonaws.com http_code=400
07-17-2024 06:08:22.396 +0000 ERROR AwsCredentials [568873 FilesystemOpExecutorWorker-0] - Failed to execute runSync() for transaction with uri=https://sts.amazonaws.com http_code=400
07-17-2024 06:08:38.702 +0000 ERROR AwsCredentials [568873 FilesystemOpExecutorWorker-0] - Failed to execute runSync() for transaction with uri=https://sts.amazonaws.com http_code=400
07-17-2024 06:09:10.986 +0000 ERROR AwsCredentials [568873 FilesystemOpExecutorWorker-0] - Failed to execute runSync() for transaction with uri=https://sts.amazonaws.com http_code=400
07-17-2024 06:10:11.274 +0000 ERROR AwsCredentials [568873 FilesystemOpExecutorWorker-0] - Failed to execute runSync() for transaction with uri=https://sts.amazonaws.com http_code=400
07-17-2024 06:11:11.554 +0000 ERROR AwsCredentials [568873 FilesystemOpExecutorWorker-0] - Failed to execute runSync() for transaction with uri=https://sts.amazonaws.com http_code=400
07-17-2024 06:12:11.834 +0000 ERROR AwsCredentials [568873 FilesystemOpExecutorWorker-0] - Failed to execute runSync() for transaction with uri=https://sts.amazonaws.com http_code=400
07-17-2024 06:12:11.848 +0000 ERROR S3Client [568873 FilesystemOpExecutorWorker-0] - command=head transactionId=0x7f0a3a71e000 rTxnId=0x7f0a2c7f5f10 status=completed success=N uri=https://
upcoming splunk enterprise release should fix this issue.
Hi @nfilip21 , the fix for AWS IRSA JWT token expiring has been fixed in splunk 9.3.2. Please try it and let us know if you are running into further issues.
Hi, now is everything working as aspected.
Please select the type of request
Bug
Tell us more
Describe the request
CloudTrail can be used to confirm that the token has expired.
Expected behavior
Splunk setup on K8S
Splunk Setup
K8s environment
Proposed changes(optional)
K8s collector data(optional)
Additional context(optional)