AWS Security ChangesHomeSearch

AWS cli documentation change

Service: cli · 2025-04-11 · Documentation low

File: cli/latest/topic/config-vars.md

Summary

Updated CLI version references from 1.38.26 to 1.38.32, added navigation link for 'AWS CLI Configuration Variables', fixed typo in 'Table Of Contents', standardized punctuation (straight quotes to curly quotes), and updated dash formatting in option flags

Security assessment

Changes are primarily formatting updates, typo fixes, and version number increments. No explicit security vulnerabilities or new security features documented. References to security-related configurations (e.g., ca_bundle, external_id) were only modified for punctuation consistency.

Diff

diff --git a/cli/latest/topic/config-vars.md b/cli/latest/topic/config-vars.md
index d5125c003..31aa89af1 100644
--- a//cli/latest/topic/config-vars.md
+++ b//cli/latest/topic/config-vars.md
@@ -15 +15 @@
-  * [AWS CLI 1.38.26 Command Reference](../index.html) »
+  * [AWS CLI 1.38.32 Command Reference](../index.html) »
@@ -16,0 +17 @@
+  * [AWS CLI Configuration Variables]()
@@ -27 +28 @@
-### [Table Of Contents](../index.html)
+### [Table of Contents](../index.html)
@@ -97 +98 @@ The AWS CLI config file, which defaults to `~/.aws/config` has the following for
-The `default` section refers to the configuration values for the default profile. You can create profiles, which represent logical groups of configuration. Profiles that aren't the default profile are specified by creating a section titled "profile profilename":
+The `default` section refers to the configuration values for the default profile. You can create profiles, which represent logical groups of configuration. Profiles that aren’t the default profile are specified by creating a section titled “profile profilename”:
@@ -126,3 +127,3 @@ Variable | Option | Config Entry | Environment Variable | Description
-profile | \--profile | N/A | AWS_PROFILE | Default profile name  
-region | \--region | region | AWS_DEFAULT_REGION | Default AWS Region  
-output | \--output | output | AWS_DEFAULT_OUTPUT | Default output style  
+profile | –profile | N/A | AWS_PROFILE | Default profile name  
+region | –region | region | AWS_DEFAULT_REGION | Default AWS Region  
+output | –output | output | AWS_DEFAULT_OUTPUT | Default output style  
@@ -131 +132 @@ cli_follow_urlparam | N/A | cli_follow_urlparam | N/A | Fetch URL url parameters
-ca_bundle | \--ca-bundle | ca_bundle | AWS_CA_BUNDLE | CA Certificate Bundle  
+ca_bundle | –ca-bundle | ca_bundle | AWS_CA_BUNDLE | CA Certificate Bundle  
@@ -161 +162 @@ The valid values of the `output` configuration variable are:
-`parameter_validation` controls whether parameter validation should occur when serializing requests. The default is True. You can disable parameter validation for performance reasons. Otherwise, it's recommended to leave parameter validation enabled.
+`parameter_validation` controls whether parameter validation should occur when serializing requests. The default is True. You can disable parameter validation for performance reasons. Otherwise, it’s recommended to leave parameter validation enabled.
@@ -163 +164 @@ The valid values of the `output` configuration variable are:
-The `max_attempts` and `retry_mode` are explained in the "Retry Configuration" section below.
+The `max_attempts` and `retry_mode` are explained in the “Retry Configuration” section below.
@@ -233 +234 @@ You can specify the following configuration values for configuring an IAM role i
-  * `external_id` \- A unique identifier that is used by third parties to assume a role in their customers' accounts. This maps to the `ExternalId` parameter in the `AssumeRole` operation. This is an optional parameter.
+  * `external_id` \- A unique identifier that is used by third parties to assume a role in their customers’ accounts. This maps to the `ExternalId` parameter in the `AssumeRole` operation. This is an optional parameter.
@@ -311 +312 @@ The following describes a method of sourcing credentials from an external proces
-If you have a method of sourcing credentials that isn't built in to the AWS CLI, you can integrate it by using `credential_process` in the config file. The AWS CLI will call that command exactly as given and then read json data from stdout. The process must write credentials to stdout in the following format:
+If you have a method of sourcing credentials that isn’t built in to the AWS CLI, you can integrate it by using `credential_process` in the config file. The AWS CLI will call that command exactly as given and then read json data from stdout. The process must write credentials to stdout in the following format:
@@ -362 +363 @@ Example configuration:
-By setting an API version for a service, it ensures that the interface for that service's commands is representative of the specified API version.
+By setting an API version for a service, it ensures that the interface for that service’s commands is representative of the specified API version.
@@ -364 +365 @@ By setting an API version for a service, it ensures that the interface for that
-In the example configuration, the `ec2` CLI commands will be representative of Amazon EC2's `2015-03-01` API version and the `cloudfront` CLI commands will be representative of Amazon CloudFront's `2015-09-17` API version.
+In the example configuration, the `ec2` CLI commands will be representative of Amazon EC2’s `2015-03-01` API version and the `cloudfront` CLI commands will be representative of Amazon CloudFront’s `2015-09-17` API version.
@@ -439 +440 @@ If you have data stored in AWS that uses a particular encoding, you should make
-  * [AWS CLI 1.38.26 Command Reference](../index.html) »
+  * [AWS CLI 1.38.32 Command Reference](../index.html) »
@@ -440,0 +442 @@ If you have data stored in AWS that uses a particular encoding, you should make
+  * [AWS CLI Configuration Variables]()