aws-config-rules | sample Custom Rules for AWS Config | Configuration Management library

by awslabs Python Version: Current License: CC0-1.0

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | aws-config-rules Summary

aws-config-rules is a Python library typically used in Devops, Configuration Management applications. aws-config-rules has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. However aws-config-rules build file is not available. You can download it from GitHub.

AWS Community repository of custom Config rules. Contributions welcome. Instructions for leveraging these rules are below.

Support

Quality

Security

License

Reuse

Support

aws-config-rules has a medium active ecosystem.

It has 1449 star(s) with 814 fork(s). There are 123 watchers for this library.

It had no major release in the last 6 months.

There are 62 open issues and 93 have been closed. On average issues are closed in 59 days. There are 42 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of aws-config-rules is current.

Quality

aws-config-rules has 0 bugs and 0 code smells.

Security

aws-config-rules has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

aws-config-rules code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

aws-config-rules is licensed under the CC0-1.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

aws-config-rules releases are not available. You will need to build from source code and install.

aws-config-rules has no build file. You will be need to create the build yourself to build the component from source.

Installation instructions, examples and code snippets are available.

aws-config-rules saves you 20504 person hours of effort in developing the same functionality from scratch.

It has 49017 lines of code, 3469 functions and 218 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed aws-config-rules and discovered the below as its top functions. This is intended to give you an instant insight into aws-config-rules implemented functionality, and help decide if they suit your requirements.

Evaluate a change .
Returns a mapping of cluster names to cluster ids
Evaluate a scheduled compliance .
Check if a service is open .
Cleanup old evaluation results .
Check if statements are allowed .
Evaluate the compliance condition .
Evaluate an AMI
Determine if statements include full starred star
Helper function to get the name of an ASG .

Get all kandi verified functions for this library.

aws-config-rules Key Features

No Key Features are available at this moment for aws-config-rules.

aws-config-rules Examples and Code Snippets

No Code Snippets are available at this moment for aws-config-rules.

Community Discussions

Trending Discussions on aws-config-rules

Can't deploy a config rule through the CDK

AWS Config - Resource discovery stuck on "Your resources are being discovered"

QUESTION

Can't deploy a config rule through the CDK

Asked 2021-Sep-29 at 04:56

I'm working on applying config rules in my organisation by leveraging Python CDK for AWS. In my setup I have a list of managed config rules from here. This list is in the stack that would be further deployed through a stackset. I've got a problem with some config rules from the conformance pack. For some reason cloudformation is not accepting SourceIdentifier: AWS_CONFIG_PROCESS_CHECK

...

ANSWER

Answered 2021-Sep-28 at 14:52

You are creating a new rule with an identifier that is the same as an existing AWS-owned ManagedRule.

To import an existing rule instead of creating a new one, use ManagedRule.fromConfigRuleName:

Source https://stackoverflow.com/questions/69346541

QUESTION

AWS Config - Resource discovery stuck on "Your resources are being discovered"

Asked 2021-May-19 at 11:52

My company has 2 AWS accounts. On the first (lets call it playground), I have full administrative permissions. On the second (lets call it production) I have limited IAM permissions

I enabled AWS Config (using the terraform file on the appendix) on both accounts.

On the playground it runs smoothly, everything is fine.
One the production, it fails. More specifically, it fails to detect the account's resources with the message "Your resources are being discovered" as shown in the screenshot below.

I initially suspected this could be an IAM role permission issue.

e.g running

aws configservice list-discovered-resources --resource-type AWS::EC2::SecurityGroup --profile playground gives me a list of the SecurityGroups discovered by the AWS Config on the playground (pretty much what I see on the console dashboard).

On the other hand:

aws configservice list-discovered-resources --resource-type AWS::EC2::SecurityGroup --profile production returns a null list (there are security groups though. Same results with other types such as AWS::EC2::Instance)

...

ANSWER

Answered 2021-May-19 at 11:52

This was likely a AWS terraform provider bug.

The service linked role AWSServiceRoleForConfig does not get activated automatically the first time you apply the terraform plan. You need to manually add it to AWS config. Then it works fine.

EDIT

The solution could be another than the aforementioned (or a combination of both). I also noticed that AWS Config get stuck on "resources are being discovered" when there are no rules/conformance packs deployed. If you deploy a single rule it discovers resources (?!)

Source https://stackoverflow.com/questions/67483448

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install aws-config-rules

You can download it from GitHub.
You can use aws-config-rules like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: