AWS codepipeline documentation change
Summary
Updated parameter names (VPCId→VpcId, SecurityGroups→SecurityGroupIds) and cross-account action guidance
Security assessment
Documentation corrections and clarifications about security group/VPC configuration, but no new security features or issue fixes.
Diff
diff --git a/codepipeline/latest/userguide/action-reference-Commands.md index 9e0dbeb2c..4b9cd2d1e 100644 --- a/codepipeline/latest/userguide/action-reference-Commands.md +++ b/codepipeline/latest/userguide/action-reference-Commands.md @@ -64 +64 @@ Because the isolated build environment is used at the account level, an instance - * The commands action is supported for cross-account or cross-Region actions. + * The commands action is supported for cross-account actions. To add a cross-account commands action, add `actionRoleArn` from your target account in the action declaration. @@ -170 +170 @@ The supported format for files is the same as for CodeBuild file patterns. For e -**VPCId** +**VpcId** @@ -184 +184 @@ The subnets for the VPC. This field is needed when your commands need to connect -**SecurityGroups** +**SecurityGroupIds** @@ -189 +189 @@ Required: No -The security groups for the VPC for your cluster. These are part of the same VPC that is attached to your cluster. You can also provide security groups that aren't already attached to your cluster and specify them here without adding to the **Networking** for your cluster. +The security groups for the VPC. This field is needed when your commands need to connect to resources in a VPC.