AWS config documentation change
Summary
Multiple instances of 'AWS CloudFormation' replaced with 'CloudFormation' in changelog entries
Security assessment
Changes are branding/naming convention updates without altering security context. IAM policy updates mentioned are existing security documentation but the edits themselves don't modify security content.
Diff
diff --git a/config/latest/developerguide/DocumentHistory.md b/config/latest/developerguide/DocumentHistory.md index 35b04372b..ca1a1d884 100644 --- a//config/latest/developerguide/DocumentHistory.md +++ b//config/latest/developerguide/DocumentHistory.md @@ -57 +57 @@ AWS Config supports new conformance pack| With this release, AWS Config supports -Security IAM updates| The `AWSConfigServiceRolePolicy` and `AWS_ConfigRole` policies now grants additional permissions for AWS Amplify, AWS AppSync, Amazon Bedrock, AWS CloudTrail, AWS CloudFormation, AWS CodeArtifact, AWS CodePipeline, Amazon Connect, AWS Deadline Cloud, Amazon EC2, AWS Entity Resolution, AWS IoT SiteWise, Amazon IVS, AWS Lambda, Amazon EventBridge, Amazon Quick Suite, Amazon Redshift, Amazon Redshift Serverless, AWS Identity and Access Management Roles Anywhere, Amazon SageMaker, AWS Secrets Manager, Amazon Security Lake, AWS Service Catalog, AWS Shield, Amazon EC2 Systems Manager, and AWS WAFV2. For more information, see [AWS managed policies for AWS Config](https://docs.aws.amazon.com/config/latest/developerguide/security-iam-awsmanpol.html).| October 1, 2025 +Security IAM updates| The `AWSConfigServiceRolePolicy` and `AWS_ConfigRole` policies now grants additional permissions for AWS Amplify, AWS AppSync, Amazon Bedrock, AWS CloudTrail, CloudFormation, AWS CodeArtifact, AWS CodePipeline, Amazon Connect, AWS Deadline Cloud, Amazon EC2, AWS Entity Resolution, AWS IoT SiteWise, Amazon IVS, AWS Lambda, Amazon EventBridge, Amazon Quick Suite, Amazon Redshift, Amazon Redshift Serverless, AWS Identity and Access Management Roles Anywhere, Amazon SageMaker, AWS Secrets Manager, Amazon Security Lake, AWS Service Catalog, AWS Shield, Amazon EC2 Systems Manager, and AWS WAFV2. For more information, see [AWS managed policies for AWS Config](https://docs.aws.amazon.com/config/latest/developerguide/security-iam-awsmanpol.html).| October 1, 2025 @@ -124 +124 @@ Security IAM updates| The `AWSConfigServiceRolePolicy` policy now grants additio -AWS Config supports new resource types| With this release, you can use AWS Config to record configuration changes to new AWS Backup, AWS Billing and Cost Management, AWS CloudFormation, Amazon CloudFront, AWS Entity Resolution, AWS IoT, AWS Private Certificate Authority, Amazon Relational Database Service, and Amazon S3 resource types. For more information, see [Supported resource types](https://docs.aws.amazon.com/config/latest/developerguide/resource-config-reference.html#amazonbedrock).| July 15, 2025 +AWS Config supports new resource types| With this release, you can use AWS Config to record configuration changes to new AWS Backup, AWS Billing and Cost Management, CloudFormation, Amazon CloudFront, AWS Entity Resolution, AWS IoT, AWS Private Certificate Authority, Amazon Relational Database Service, and Amazon S3 resource types. For more information, see [Supported resource types](https://docs.aws.amazon.com/config/latest/developerguide/resource-config-reference.html#amazonbedrock).| July 15, 2025 @@ -1539 +1539 @@ Documentation update | AWS Config limits are available in this developer guide. -Documentation update | Third-party resources that are managed (that is, created/updated/deleted) through AWS CloudFormation registry are automatically tracked in AWS Config as configuration items. For more information, see [Recording Configurations with AWS Config for Third-Party Resources using the AWS CLI](./customresources.html). | March 30, 2020 +Documentation update | Third-party resources that are managed (that is, created/updated/deleted) through CloudFormation registry are automatically tracked in AWS Config as configuration items. For more information, see [Recording Configurations with AWS Config for Third-Party Resources using the AWS CLI](./customresources.html). | March 30, 2020 @@ -1859 +1859 @@ New API operation | You can use the [GetDiscoveredResourceCounts](https://docs.a -AWS Config supports the AWS CloudFormation stack resource type and one new managed rule | With this release, you can use AWS Config to record configuration changes to your AWS CloudFormation stacks. For more information, see [Supported Resource Types for AWS Config](./resource-config-reference.html). This release supports the following managed rule: +AWS Config supports the CloudFormation stack resource type and one new managed rule | With this release, you can use AWS Config to record configuration changes to your CloudFormation stacks. For more information, see [Supported Resource Types for AWS Config](./resource-config-reference.html). This release supports the following managed rule: @@ -1893 +1893 @@ New and updated content | This release adds support for AWS Config Rules in the -New and updated content | This release adds AWS CloudFormation templates for AWS Config managed rules. You can use the templates to create managed rules for your account. For more information, see [Creating AWS Config Managed Rules With AWS CloudFormation Templates](./aws-config-managed-rules-cloudformation-templates.html). | February 16, 2017 +New and updated content | This release adds CloudFormation templates for AWS Config managed rules. You can use the templates to create managed rules for your account. For more information, see [Creating AWS Config Managed Rules With AWS CloudFormation Templates](./aws-config-managed-rules-cloudformation-templates.html). | February 16, 2017