AWS Config: 75 new managed rules
AWS Config added 75 new managed rules for security, durability and operations — a notable expansion for rule‑based compliance and automated drift detection in AWS environments. The update gives cloud teams more out‑of‑the‑box checks to integrate into governance pipelines. (x.com)
AWS published the managed-rules update in its March 18–19, 2026 product roundups and third‑party aggregators captured the change on March 18, 2026. (mwpro.co.uk) New entries target specific services and controls across encryption, TLS, resource configuration and tagging, with coverage added for ACM, API Gateway, SageMaker, EC2, AppIntegrations and App Mesh. (dev.classmethod.jp) Sample rule identifiers published in the update include ACM_CERTIFICATE_TRANSPARENT_LOGGING_ENABLED, APIGATEWAY_DOMAIN_NAME_TLS_CHECK, EC2_LAUNCHTEMPLATE_EBS_ENCRYPTED and SAGEMAKER_DATA_QUALITY_JOB_ENCRYPT_IN_TRANSIT. (dev.classmethod.jp) AWS continues to recommend packaging managed rules into Conformance Packs for multi‑account deployment and policy-as-code rollouts, a deployment pattern highlighted in prior AWS Config rule releases. (aws.amazon.com) The AWS Config developer guide’s managed‑rules index now lists the new rule entries with descriptions and supported resource types for each rule. (docs.aws.amazon.com) Documentation indicates these managed rules support both change‑triggered and periodic evaluation modes and are customizable to fit existing governance pipelines and automated drift detection workflows. (docs.aws.amazon.com) The March update follows a pattern of incremental expansions in 2025 (for example, a November 2025 batch that added 42 rules), signaling a continued broadening of AWS Config’s out‑of‑the‑box coverage across AWS services. (aws.amazon.com)
