AWS securityhub documentation change
Summary
Removed 'AWS' prefix from CloudFormation references in cross-account role configuration and deployment instructions
Security assessment
Terminology standardization without security impact. Changes relate to service naming conventions rather than security controls or vulnerability mitigation.
Diff
diff --git a/securityhub/latest/partnerguide/integration-use-cases.md b/securityhub/latest/partnerguide/integration-use-cases.md index fee4ef6bc..2000085e9 100644 --- a//securityhub/latest/partnerguide/integration-use-cases.md +++ b//securityhub/latest/partnerguide/integration-use-cases.md @@ -76 +76 @@ Enabling a partner product to send findings to the customer in Security Hub with - 3. The customer configures the cross-account role either manually or using AWS CloudFormation. For information on cross-account roles, see [Providing access to AWS accounts owned by third parties](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html) in the _IAM User Guide_. + 3. The customer configures the cross-account role either manually or using CloudFormation. For information on cross-account roles, see [Providing access to AWS accounts owned by third parties](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html) in the _IAM User Guide_. @@ -129 +129 @@ The customer enables the partner product to send findings from the customer's ac - 1. The customer deploys the partner product into their AWS account manually using AWS CloudFormation, or another deployment tool. + 1. The customer deploys the partner product into their AWS account manually using CloudFormation, or another deployment tool.