New Training: Deploy AWS Config Compliance Rules with AWS Tools for PowerShell

In this 6-video skill, CBT Nuggets trainer Trevor Sullivan explores how the AWS Tools for PowerShell can be used to deploy AWS Config governance rules across one or many AWS accounts and regions. Gain an understanding of how to automate AWS Config with PowerShell. Watch this new AWS training.

Watch the full course: AWS Cloud Automation

This training includes:

• 6 videos

• 55 minutes of training

You’ll learn these topics in this skill:

• Introduction to AWS Config Service and AWS Tools for PowerShell SDK

• Create Remote Development Environment with Amazon EC2 and Visual Studio Code

• Configure AWS IAM Role for AWS Config Automation

• Write AWS Config Rule with Write-CFGConfigRule PowerShell Command

• Retrieve Compliance Details for AWS Config Rules with PowerShell

• Replicate AWS Config Configuration Recorders and Rules Across Regions

Using PowerShell To List Resources In AWS Config

By using AWS Tools for PowerShell, you can easily create, manage, and deploy governance rules in your AWS environments. AWS Tools for PowerShell include multiple -s for PowerShell for working with the AWS Config through the AWS SDK. Read the documentation page for AWS Config with AWS Tools for PowerShell to see all the -s available.

One cmdlet that should be emphasized immediately is the Get-CFGAggregateComplianceByConfigRuleList command. With this -, you can quickly enumerate an existing list of compliant and non-compliant rules. This is an easy, programmatic way to list existing configurations within your environment.

This cmdlet includes nine additional flags:

• Filters_AccountId

• Filters_AwsRegion

• Filters_ComplianceType

• Filters_ConfigRuleName

• ConfigurationAggregatorName

• Limit

• NextToken

• Select

• NoAutoIteration

Note that the ConfigurationAggregatorName flag is required. The other 8 are optional. Like the rest of the AWS Tools for PowerShell -s, this tool also has access to common credential and regional flags as well.

Read the documentation page for this cmdlet for more information.