Update generated code (#1042)

* update generated code

* Update src/Service/Lambda/CHANGELOG.md

Co-authored-by: Jérémy Derussé <[email protected]>

Author: async-aws-bot

CHANGELOG.md

@@ -4,6 +4,7 @@
 
 ### Added
 
+- AWS enhancement: Documentation updates for AWS Security Token Service.
 
 ## 1.10.0
 

src/Sts/Exception/InvalidIdentityTokenException.php

@@ -6,8 +6,8 @@
 use Symfony\Contracts\HttpClient\ResponseInterface;
 
 /**
- * The web identity token that was passed could not be validated by AWS. Get a new identity token from the identity
- * provider and then retry the request.
+ * The web identity token that was passed could not be validated by Amazon Web Services. Get a new identity token from
+ * the identity provider and then retry the request.
  */
 final class InvalidIdentityTokenException extends ClientException
 {

src/Sts/Exception/PackedPolicyTooLargeException.php

@@ -7,9 +7,10 @@
 
 /**
  * The request was rejected because the total packed size of the session policies and session tags combined was too
- * large. An AWS conversion compresses the session policy document, session policy ARNs, and session tags into a packed
- * binary format that has a separate limit. The error message indicates by percentage how close the policies and tags
- * are to the upper size limit. For more information, see Passing Session Tags in STS in the *IAM User Guide*.
+ * large. An Amazon Web Services conversion compresses the session policy document, session policy ARNs, and session
+ * tags into a packed binary format that has a separate limit. The error message indicates by percentage how close the
+ * policies and tags are to the upper size limit. For more information, see Passing Session Tags in STS in the *IAM User
+ * Guide*.
  * You could receive this error even though you meet other defined session policy and session tag limits. For more
  * information, see IAM and STS Entity Character Limits in the *IAM User Guide*.
  *

src/Sts/Exception/RegionDisabledException.php

@@ -8,7 +8,7 @@
 /**
  * STS is not activated in the requested region for the account that is being asked to generate credentials. The account
  * administrator must use the IAM console to activate STS in that region. For more information, see Activating and
- * Deactivating AWS STS in an AWS Region in the *IAM User Guide*.
+ * Deactivating Amazon Web Services STS in an Amazon Web Services Region in the *IAM User Guide*.
  *
  * @see https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_enable-regions.html
  */

src/Sts/Input/AssumeRoleRequest.php

@@ -60,7 +60,7 @@ final class AssumeRoleRequest extends Input
 
     /**
      * A list of session tags that you want to pass. Each session tag consists of a key name and an associated value. For
-     * more information about session tags, see Tagging AWS STS Sessions in the *IAM User Guide*.
+     * more information about session tags, see Tagging STS Sessions in the *IAM User Guide*.
      *
      * @see https://docs.aws.amazon.com/IAM/latest/UserGuide/id_session-tags.html
      *
@@ -86,7 +86,7 @@ final class AssumeRoleRequest extends Input
      * up to trust everyone in an account. Therefore, the administrator of the trusting account might send an external ID to
      * the administrator of the trusted account. That way, only someone with the ID can assume the role, rather than
      * everyone in the account. For more information about the external ID, see How to Use an External ID When Granting
-     * Access to Your AWS Resources to a Third Party in the *IAM User Guide*.
+     * Access to Your Amazon Web Services Resources to a Third Party in the *IAM User Guide*.
      *
      * @see https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-user_externalid.html
      *

src/Sts/Result/AssumeRoleResponse.php

@@ -8,8 +8,8 @@
 use AsyncAws\Core\Sts\ValueObject\Credentials;
 
 /**
- * Contains the response to a successful AssumeRole request, including temporary AWS credentials that can be used to
- * make AWS requests.
+ * Contains the response to a successful AssumeRole request, including temporary Amazon Web Services credentials that
+ * can be used to make Amazon Web Services requests.
  */
 class AssumeRoleResponse extends Result
 {

src/Sts/Result/AssumeRoleWithWebIdentityResponse.php

@@ -8,8 +8,8 @@
 use AsyncAws\Core\Sts\ValueObject\Credentials;
 
 /**
- * Contains the response to a successful AssumeRoleWithWebIdentity request, including temporary AWS credentials that can
- * be used to make AWS requests.
+ * Contains the response to a successful AssumeRoleWithWebIdentity request, including temporary Amazon Web Services
+ * credentials that can be used to make Amazon Web Services requests.
  */
 class AssumeRoleWithWebIdentityResponse extends Result
 {

src/Sts/Result/GetCallerIdentityResponse.php

@@ -21,12 +21,12 @@ class GetCallerIdentityResponse extends Result
     private $userId;
 
     /**
-     * The AWS account ID number of the account that owns or contains the calling entity.
+     * The Amazon Web Services account ID number of the account that owns or contains the calling entity.
      */
     private $account;
 
     /**
-     * The AWS ARN associated with the calling entity.
+     * The Amazon Web Services ARN associated with the calling entity.
      */
     private $arn;
 

src/Sts/StsClient.php

@@ -25,11 +25,11 @@
 class StsClient extends AbstractApi
 {
     /**
-     * Returns a set of temporary security credentials that you can use to access AWS resources that you might not normally
-     * have access to. These temporary credentials consist of an access key ID, a secret access key, and a security token.
-     * Typically, you use `AssumeRole` within your account or for cross-account access. For a comparison of `AssumeRole`
-     * with other API operations that produce temporary credentials, see Requesting Temporary Security Credentials and
-     * Comparing the AWS STS API operations in the *IAM User Guide*.
+     * Returns a set of temporary security credentials that you can use to access Amazon Web Services resources that you
+     * might not normally have access to. These temporary credentials consist of an access key ID, a secret access key, and
+     * a security token. Typically, you use `AssumeRole` within your account or for cross-account access. For a comparison
+     * of `AssumeRole` with other API operations that produce temporary credentials, see Requesting Temporary Security
+     * Credentials and Comparing the STS API operations in the *IAM User Guide*.
      *
      * @see https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html
      * @see https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_request.html#stsapi_comparison

src/Sts/ValueObject/AssumedRoleUser.php

@@ -12,7 +12,7 @@ final class AssumedRoleUser
 {
     /**
      * A unique identifier that contains the role ID and the role session name of the role that is being assumed. The role
-     * ID is generated by AWS when the role is created.
+     * ID is generated by Amazon Web Services when the role is created.
      */
     private $assumedRoleId;