Other Articles
- EC2 Volume – Enable EBS Encryption
- EC2 Volume – Enable EBS Volume Backup
- EFS – Enable EFS Storage Backup
- EC2 Instance – Enable Deletion Protection
- EC2 Instance – Monitor CPU Utilization
- ECS Service – Monitor CPU Utilization
- ECS Service – Monitor Memory Utilization
- EC2 VPC – Ensure Flow Logs are Enabled
- S3 Bucket – Block S3 Bucket Public Access
- S3 Bucket – Enable S3 Bucket Versioning
- S3 Bucket – Enable S3 Bucket Encryption
- RDS DB Instance – Enable Auto Minor Version Upgrade
- RDS DB Instance – Block Public Access
- RDS DB Instance – Monitor Free Storage Space
- RDS DB Instance – Monitor CPU Utilization
- RDS DB Instance – Encryption of Storage
- RDS DB Instance – Enable Deletion Protection
- SQS Queue – Monitor Message Age
- DynamoDB Table – Enable Table Encryption
- DynamoDB Table – Enable Table Point In Time Recovery
- DynamoDB Table – Enable Table Deletion Protection
- DynamoDB Table – Monitor Table Read Capacity
- DynamoDB Table – Monitor Table Write Capacity
- DynamoDB Table – Monitor Table Latency
- Enable User MFA
- Enforce Key Rotation
- Enforce Active Key Limit
- Disable Unused User Credentials
- Enforce Group Permission
- Enable CloudTrail
- Enable AWS Security Hub
- Enforce Password Length
- Prohibit Password Reuse
- Purge Expired Certificates
- Check Root Access Keys Existence
- Enable Root MFA
- Establish Support Role
- Enable Key Rotation
- Encrypt CloudTrail Logs
- Enable GuardDuty
SQS Queue – Monitor Message Visibility
This check ensures that the visibility timeout for Amazon SQS queues is properly configured. A correct visibility timeout prevents messages from being processed multiple times and helps ensure reliable message handling.
Check Details
- Resource: SQS Queue
- Check: Monitor SQS message visibility timeout
- Risk: Messages may be processed multiple times or lost due to incorrect timeout configuration
Remediation via AWS Console
-
Log in to the AWS Management Console and open the
Amazon SQS console.
-
Click Queues and select the required SQS queue.
- Click Edit.
-
Under Details, set the
Default visibility timeout to a value between
30 and 300 seconds.
- Click Save.
Remediation via AWS CLI
-
Log in to the AWS Management Console and click the
CloudShell icon (
>_) in the top-right corner.
-
Set the visibility timeout for the SQS queue:
aws sqs set-queue-attributes \ --queue-url <queue-url> \ --attributes VisibilityTimeout=30
Replace <queue-url> with the actual SQS queue URL.