Ensure Glue jobs have encryption for S3 data targets
Glue ETL jobs writing to S3 should enable encryption at rest for target data to protect sensitive information.
Security Impact
Unencrypted output data in S3 is vulnerable to unauthorized access if bucket permissions are misconfigured.
How to Remediate
Configure job security settings to enable S3 encryption for data written by Glue jobs. Use SSE-S3 or SSE-KMS.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all AWS Glue resources across your AWS accounts every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for PCI-DSS, HIPAA, SOC 2 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-glue-3
- Service
- AWS Glue
- Category
- Encryption
- Severity
- HIGH
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated AWS Glue Checks
View all checksEnsure Glue Data Catalog encryption at rest is enabled
Ensure Glue connection passwords are encrypted
Ensure Glue jobs have CloudWatch log encryption enabled
Ensure Glue jobs are configured with job bookmarks
Ensure Glue Data Catalog resource policies restrict access appropriately