Cloud Workload Protection for Storage fails to scan S3 bucket

book

Article ID: 225529

calendar_today

Updated On:

Products

Cloud Workload Protection for Storage

Issue/Introduction

Cloud Workload Protection for Storage was failing to scan S3 buckets.  The following errors were found in the spe-s3-protection-controller-service.log.

2021-09-02 23:12:07,722 [pool-13-thread-1] ERROR SqsPollerTask:217 - Encountered exception in SQS poller run. Exception Message: 
2021-09-02 23:12:07,722 [pool-13-thread-1] ERROR SqsPollerTask:220 - Exception Stack Trace: 
com.amazonaws.SdkClientException: Unable to execute HTTP request: Connect to sqs.us-west-2.amazonaws.com:443 [sqs.us-west-2.amazonaws.com/XX.XXX.XXX.XXX] failed: connect timed out
 at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleRetryableException(AmazonHttpClient.java:1175)
 at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1121)
 at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:770)
 at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:744)
 at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:726)
 at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:686)
 at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:668)
 at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:532)
 at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:512)
 at com.amazonaws.services.sqs.AmazonSQSClient.doInvoke(AmazonSQSClient.java:2207)
 at com.amazonaws.services.sqs.AmazonSQSClient.invoke(AmazonSQSClient.java:2174)
 at com.amazonaws.services.sqs.AmazonSQSClient.invoke(AmazonSQSClient.java:2163)
 at com.amazonaws.services.sqs.AmazonSQSClient.executeReceiveMessage(AmazonSQSClient.java:1607)
 at com.amazonaws.services.sqs.AmazonSQSClient.receiveMessage(AmazonSQSClient.java:1578)
 at com.symantec.spe.nrts.SqsPollerTask.run(SqsPollerTask.java:177)
 at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
 at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
 at java.lang.Thread.run(Unknown Source)

Resolution

The AWS Auto Scaling Groups settings where changed to the following.

Desired Capacity 0

Minimum Capacity 0

Maximum Capacity 0

 

This allowed the instance to spin down. After this completed, the settings where changed back to the previous settings.   

Setting Capacity Limits AWS