AWS guardduty documentation change
Summary
Updated references from 'AWS CloudFormation' to 'CloudFormation' for consistency
Security assessment
Change only modifies product name references without altering security context or functionality
Diff
diff --git a/guardduty/latest/ug/guardduty-feature-object-api-changes-march2023.md b/guardduty/latest/ug/guardduty-feature-object-api-changes-march2023.md index 77447399f..abc032ba9 100644 --- a//guardduty/latest/ug/guardduty-feature-object-api-changes-march2023.md +++ b//guardduty/latest/ug/guardduty-feature-object-api-changes-march2023.md @@ -59 +59 @@ GuardDuty has deprecated the use of data sources that are associated with the pr - * If you manage GuardDuty configurations through APIs, SDKs, or AWS CloudFormation template, and want to enable potential new GuardDuty features, you will need to modify your code and template, respectively. For more information, see the updated APIs in the _[Amazon GuardDuty API Reference](https://docs.aws.amazon.com/guardduty/latest/APIReference/API_Operations.html)_. + * If you manage GuardDuty configurations through APIs, SDKs, or CloudFormation template, and want to enable potential new GuardDuty features, you will need to modify your code and template, respectively. For more information, see the updated APIs in the _[Amazon GuardDuty API Reference](https://docs.aws.amazon.com/guardduty/latest/APIReference/API_Operations.html)_. @@ -61 +61 @@ GuardDuty has deprecated the use of data sources that are associated with the pr - * For GuardDuty features configured prior to this upgrade, you can continue using the APIs, SDKs, or AWS CloudFormation template. However, we recommend that you switch to using `feature` object. + * For GuardDuty features configured prior to this upgrade, you can continue using the APIs, SDKs, or CloudFormation template. However, we recommend that you switch to using `feature` object.