AWS cli medium security documentation change
Summary
Removed 'V1' as valid value for registry policy scope, now only allows 'V2'
Security assessment
Removing support for V1 policy scope likely indicates deprecation of less secure version. This change enforces more secure V2 policies by removing older option, addressing potential security weaknesses in registry policy implementation.
Diff
diff --git a/cli/latest/reference/ecr/get-account-setting.md b/cli/latest/reference/ecr/get-account-setting.md index 139e5a7cb..4d274d5fa 100644 --- a//cli/latest/reference/ecr/get-account-setting.md +++ b//cli/latest/reference/ecr/get-account-setting.md @@ -15 +15 @@ - * [AWS CLI 2.34.38 Command Reference](../../index.html) » + * [AWS CLI 2.34.40 Command Reference](../../index.html) » @@ -230 +230 @@ value -> (string) -> The setting value for the setting name. Valid value for basic scan type: `AWS_NATIVE` . Valid values for registry policy scope: `V1` or `V2` . Valid values for blob mounting: `ENABLED` or `DISABLED` . +> The setting value for the setting name. Valid value for basic scan type: `AWS_NATIVE` . Valid values for registry policy scope: `V2` . Valid values for blob mounting: `ENABLED` or `DISABLED` . @@ -249 +249 @@ value -> (string) - * [AWS CLI 2.34.38 Command Reference](../../index.html) » + * [AWS CLI 2.34.40 Command Reference](../../index.html) »