AWS Config
AWS Config control plane — config rules, configuration recorders, and delivery channels, with recorder start/stop and compliance / evaluation-status reads. State is stored as metadata; MiniStack does not evaluate rules against live resource configuration.
Quick start
import boto3
cfg = boto3.client("config", endpoint_url="http://localhost:4566",
region_name="us-east-1",
aws_access_key_id="test", aws_secret_access_key="test")
cfg.put_configuration_recorder(
ConfigurationRecorder={"name": "default", "roleARN": "arn:aws:iam::000000000000:role/config"})
cfg.put_config_rule(ConfigRule={"ConfigRuleName": "s3-versioning",
"Source": {"Owner": "AWS", "SourceIdentifier": "S3_BUCKET_VERSIONING_ENABLED"}})
print([r["ConfigRuleName"] for r in cfg.describe_config_rules()["ConfigRules"]])
Supported operations
14 operations exposed by this service as of MiniStack 1.4.21. Extracted directly from the handler dispatch in the source module.
DeleteConfigRule
DescribeComplianceByConfigRule
DescribeConfigRuleEvaluationStatus
DescribeConfigRules
DescribeConfigurationRecorders
DescribeConfigurationRecorderStatus
DescribeDeliveryChannels
DescribeDeliveryChannelStatus
GetComplianceDetailsByConfigRule
PutConfigRule
PutConfigurationRecorder
PutDeliveryChannel
StartConfigurationRecorder
StopConfigurationRecorder
CloudFormation
No CloudFormation resource types map to this service yet. Resources can still be created via the SDK or CLI.
Known limitations
- Compliance and evaluation reads are inert — DescribeComplianceByConfigRule returns INSUFFICIENT_DATA and no rule is ever evaluated against live resource configuration.
Source
ministack/services/config.py
Read the source to verify the ops list above — dispatch tables and handler functions are the ground truth.