AWS securityhub documentation change
Summary
Updated CloudFormation references by removing 'AWS' prefix in integration configuration guidance
Security assessment
Documentation style update for consistent CloudFormation naming. No security-related content added or modified beyond terminology alignment.
Diff
diff --git a/securityhub/latest/partnerguide/manifest-use-case-marketing.md b/securityhub/latest/partnerguide/manifest-use-case-marketing.md index 709f82732..ff24a59bb 100644 --- a//securityhub/latest/partnerguide/manifest-use-case-marketing.md +++ b//securityhub/latest/partnerguide/manifest-use-case-marketing.md @@ -40 +40 @@ Provide two customer use cases for your work with Security Hub. These can be pri - * How do you help customers bootstrap Security Hub? For example, have you helped customers use professional services, a Terraform module, or an AWS CloudFormation template? + * How do you help customers bootstrap Security Hub? For example, have you helped customers use professional services, a Terraform module, or an CloudFormation template? @@ -89 +89 @@ Describe how a customer will configure your integration with Security Hub. -At a minimum, you must use AWS CloudFormation templates or a similar infrastructure such as code templates. Some partners have provided a user interface to support one-click integration. +At a minimum, you must use CloudFormation templates or a similar infrastructure such as code templates. Some partners have provided a user interface to support one-click integration.