Benchmark: EMR
Description
This section contains recommendations for configuring EMR resources.
Usage
Install the mod:
mkdir dashboardscd dashboardspowerpipe mod initpowerpipe mod install github.com/turbot/steampipe-mod-aws-complianceStart the Powerpipe server:
steampipe service startpowerpipe serverOpen http://localhost:9033 in your browser and select EMR.
Run this benchmark in your terminal:
powerpipe benchmark run aws_compliance.benchmark.all_controls_emrSnapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_compliance.benchmark.all_controls_emr --shareControls
- EMR account public access should be blocked
- EMR clusters encryption at rest should be enabled
- EMR clusters client side encryption (CSE CMK) enabled with CMK
- EMR clusters server side encryption (SSE KMS) enabled with KMS
- EMR clusters encryption in transit should be enabled
- EMR cluster Kerberos should be enabled
- EMR cluster local disks should be encrypted with CMK
- EMR clusters local disk encryption should be enabled
- EMR cluster master nodes should not have public IP addresses
- EMR clusters should have security configuration enabled
- Amazon EMR security configurations should be encrypted at rest
- Amazon EMR security configurations should be encrypted in transit