How To Enforce Compliance Using AWS Config (2 Min) | S3 Bucket Compliance Config Rule

Описание: In this tutorial, you'll learn how to enforce compliance on S3 Buckets using AWS Config Rules.
—
Facebook:   / gokcedbsql  
—
Video Transcript:
—
Hi guys, this is Abhi from Gokcedb. In this video, you're going to learn how to enforce compliance on S3 buckets using AWS config. Let's start by navigating to the S3 service. 

Here you can see I have eight buckets. Let's navigate to the AWS config service then click on settings. Here, click on edit and make sure the recorder is set to on when you do the status will change to taking inventory. 

I've also restricted the resource types to record to S3 buckets and configured config buckets for the delivery method. Next, click on rules then hit add a role. Search for S3 and select the S3 bucket encryption enable row. 

This rule checks whether the server-side encryption is enabled on your bucket or not. Click next then select AWS buckets as the resource type then click next again. Review your rule settings then hit add a rule. 

Go inside your row then from the actions drop-down, select re-evaluate to force evaluate. This rule gives it a few minutes then refresh the page to see the results. Looks like all eight buckets are non-compliant. 

Let's head back to the S3 service and enable server-side encryption for one of our buckets. In the properties tab, enable default server-side encryption then come back to the AWS config console. I'm going to reevaluate this rule again and then refresh the page. 

As expected this time bucket one is showing as a complaint. Note, you can also monitor your compliance status from the config dashboard. Finally, if you wanted to set up automatic remediation, go back to your row and select manage remediation from the actions drop-down. 

Here, you can set up appropriate remediation action based on your requirement. There you have it. Make sure you like, subscribe, and turn on the notification bell. 

Until next time.