@aws-sdk/client-iam 3.1039.0 → 3.1041.0

package/README.md

@@ -11,6 +11,57 @@ AWS SDK for JavaScript IAM Client for Node.js, Browser and React Native.
 access to Amazon Web Services services. With IAM, you can centrally manage users, security credentials
 such as access keys, and permissions that control which Amazon Web Services resources users and
 applications can access. For more information about IAM, see <a href="http://aws.amazon.com/iam/">Identity and Access Management (IAM)</a> and the <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/">Identity and Access Management User Guide</a>.</p>
+<p>
+<b>Programmatic access to IAM</b>
+</p>
+<p>We recommend that you use the Amazon Web Services SDKs to make programmatic API calls to IAM. The Amazon Web Services
+SDKs consist of libraries and sample code for various programming languages and platforms
+(for example, Java, Ruby, .NET, iOS, and Android). The SDKs provide a convenient way to
+create programmatic access to IAM and Amazon Web Services. For example, the SDKs take care of tasks such as
+cryptographically signing requests, managing errors, and retrying requests automatically.
+For more information, see <a href="http://aws.amazon.com/tools/">Tools to build on
+Amazon Web Services</a>.</p>
+<p>Alternatively, you can also use the IAM Query API to make direct calls to the IAM
+service. For more information about calling the IAM Query API, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/IAM_UsingQueryAPI.html">Making query
+requests</a> in the <i>Identity and Access Management User Guide</i>. IAM supports GET and
+POST requests for all actions. That is, the API does not require you to use GET for some
+actions and POST for others. However, GET requests are subject to the limitation size of a
+URL. Therefore, for operations that require larger sizes, use a POST request.</p>
+<p>
+<b>Signing requests</b>
+</p>
+<p>Requests must be signed using an access key ID and a secret access key. We strongly
+recommend that you do not use your Amazon Web Services account access key ID and secret access key for
+everyday work with IAM. You can use the access key ID and secret access key for an
+IAM user or you can use the Security Token Service to generate temporary security credentials and use
+those to sign requests.</p>
+<p>To sign requests, we recommend that you use <a href="https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html">Signature Version 4</a>. If you have an
+existing application that uses Signature Version 2, you do not have to update it to use
+Signature Version 4. However, some operations now require Signature Version 4. The
+documentation for operations that require version 4 indicate this requirement.</p>
+<p>
+<b>Additional resources</b>
+</p>
+<ul>
+<li>
+<p>
+<a href="https://docs.aws.amazon.com/general/latest/gr/aws-security-credentials.html">Amazon Web Services
+security credentials</a>. This topic provides general information about the types of
+credentials used for accessing Amazon Web Services.</p>
+</li>
+<li>
+<p>
+<a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/IAMBestPractices.html">IAM best
+practices</a>. This topic presents a list of suggestions for using the IAM service
+to help secure your Amazon Web Services resources.</p>
+</li>
+<li>
+<p>
+<a href="https://docs.aws.amazon.com/general/latest/gr/signing_aws_api_requests.html">Signing
+Amazon Web Services API requests</a>. This set of topics walk you through the process of signing a
+request using an access key ID and secret access key.</p>
+</li>
+</ul>
 
 ## Installing
 

package/dist-types/IAM.d.ts

@@ -1539,6 +1539,57 @@ export interface IAM {
  *       access to Amazon Web Services services. With IAM, you can centrally manage users, security credentials
  *       such as access keys, and permissions that control which Amazon Web Services resources users and
  *       applications can access. For more information about IAM, see <a href="http://aws.amazon.com/iam/">Identity and Access Management (IAM)</a> and the <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/">Identity and Access Management User Guide</a>.</p>
+ *          <p>
+ *             <b>Programmatic access to IAM</b>
+ *          </p>
+ *          <p>We recommend that you use the Amazon Web Services SDKs to make programmatic API calls to IAM. The Amazon Web Services
+ *       SDKs consist of libraries and sample code for various programming languages and platforms
+ *       (for example, Java, Ruby, .NET, iOS, and Android). The SDKs provide a convenient way to
+ *       create programmatic access to IAM and Amazon Web Services. For example, the SDKs take care of tasks such as
+ *       cryptographically signing requests, managing errors, and retrying requests automatically.
+ *       For more information, see <a href="http://aws.amazon.com/tools/">Tools to build on
+ *         Amazon Web Services</a>.</p>
+ *          <p>Alternatively, you can also use the IAM Query API to make direct calls to the IAM
+ *       service. For more information about calling the IAM Query API, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/IAM_UsingQueryAPI.html">Making query
+ *         requests</a> in the <i>Identity and Access Management User Guide</i>. IAM supports GET and
+ *       POST requests for all actions. That is, the API does not require you to use GET for some
+ *       actions and POST for others. However, GET requests are subject to the limitation size of a
+ *       URL. Therefore, for operations that require larger sizes, use a POST request.</p>
+ *          <p>
+ *             <b>Signing requests</b>
+ *          </p>
+ *          <p>Requests must be signed using an access key ID and a secret access key. We strongly
+ *       recommend that you do not use your Amazon Web Services account access key ID and secret access key for
+ *       everyday work with IAM. You can use the access key ID and secret access key for an
+ *       IAM user or you can use the Security Token Service to generate temporary security credentials and use
+ *       those to sign requests.</p>
+ *          <p>To sign requests, we recommend that you use <a href="https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html">Signature Version 4</a>. If you have an
+ *       existing application that uses Signature Version 2, you do not have to update it to use
+ *       Signature Version 4. However, some operations now require Signature Version 4. The
+ *       documentation for operations that require version 4 indicate this requirement.</p>
+ *          <p>
+ *             <b>Additional resources</b>
+ *          </p>
+ *          <ul>
+ *             <li>
+ *                <p>
+ *                   <a href="https://docs.aws.amazon.com/general/latest/gr/aws-security-credentials.html">Amazon Web Services
+ *           security credentials</a>. This topic provides general information about the types of
+ *           credentials used for accessing Amazon Web Services.</p>
+ *             </li>
+ *             <li>
+ *                <p>
+ *                   <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/IAMBestPractices.html">IAM best
+ *           practices</a>. This topic presents a list of suggestions for using the IAM service
+ *           to help secure your Amazon Web Services resources.</p>
+ *             </li>
+ *             <li>
+ *                <p>
+ *                   <a href="https://docs.aws.amazon.com/general/latest/gr/signing_aws_api_requests.html">Signing
+ *           Amazon Web Services API requests</a>. This set of topics walk you through the process of signing a
+ *           request using an access key ID and secret access key.</p>
+ *             </li>
+ *          </ul>
  * @public
  */
 export declare class IAM extends IAMClient implements IAM {

package/dist-types/IAMClient.d.ts

@@ -350,6 +350,57 @@ export interface IAMClientResolvedConfig extends IAMClientResolvedConfigType {
  *       access to Amazon Web Services services. With IAM, you can centrally manage users, security credentials
  *       such as access keys, and permissions that control which Amazon Web Services resources users and
  *       applications can access. For more information about IAM, see <a href="http://aws.amazon.com/iam/">Identity and Access Management (IAM)</a> and the <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/">Identity and Access Management User Guide</a>.</p>
+ *          <p>
+ *             <b>Programmatic access to IAM</b>
+ *          </p>
+ *          <p>We recommend that you use the Amazon Web Services SDKs to make programmatic API calls to IAM. The Amazon Web Services
+ *       SDKs consist of libraries and sample code for various programming languages and platforms
+ *       (for example, Java, Ruby, .NET, iOS, and Android). The SDKs provide a convenient way to
+ *       create programmatic access to IAM and Amazon Web Services. For example, the SDKs take care of tasks such as
+ *       cryptographically signing requests, managing errors, and retrying requests automatically.
+ *       For more information, see <a href="http://aws.amazon.com/tools/">Tools to build on
+ *         Amazon Web Services</a>.</p>
+ *          <p>Alternatively, you can also use the IAM Query API to make direct calls to the IAM
+ *       service. For more information about calling the IAM Query API, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/IAM_UsingQueryAPI.html">Making query
+ *         requests</a> in the <i>Identity and Access Management User Guide</i>. IAM supports GET and
+ *       POST requests for all actions. That is, the API does not require you to use GET for some
+ *       actions and POST for others. However, GET requests are subject to the limitation size of a
+ *       URL. Therefore, for operations that require larger sizes, use a POST request.</p>
+ *          <p>
+ *             <b>Signing requests</b>
+ *          </p>
+ *          <p>Requests must be signed using an access key ID and a secret access key. We strongly
+ *       recommend that you do not use your Amazon Web Services account access key ID and secret access key for
+ *       everyday work with IAM. You can use the access key ID and secret access key for an
+ *       IAM user or you can use the Security Token Service to generate temporary security credentials and use
+ *       those to sign requests.</p>
+ *          <p>To sign requests, we recommend that you use <a href="https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html">Signature Version 4</a>. If you have an
+ *       existing application that uses Signature Version 2, you do not have to update it to use
+ *       Signature Version 4. However, some operations now require Signature Version 4. The
+ *       documentation for operations that require version 4 indicate this requirement.</p>
+ *          <p>
+ *             <b>Additional resources</b>
+ *          </p>
+ *          <ul>
+ *             <li>
+ *                <p>
+ *                   <a href="https://docs.aws.amazon.com/general/latest/gr/aws-security-credentials.html">Amazon Web Services
+ *           security credentials</a>. This topic provides general information about the types of
+ *           credentials used for accessing Amazon Web Services.</p>
+ *             </li>
+ *             <li>
+ *                <p>
+ *                   <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/IAMBestPractices.html">IAM best
+ *           practices</a>. This topic presents a list of suggestions for using the IAM service
+ *           to help secure your Amazon Web Services resources.</p>
+ *             </li>
+ *             <li>
+ *                <p>
+ *                   <a href="https://docs.aws.amazon.com/general/latest/gr/signing_aws_api_requests.html">Signing
+ *           Amazon Web Services API requests</a>. This set of topics walk you through the process of signing a
+ *           request using an access key ID and secret access key.</p>
+ *             </li>
+ *          </ul>
  * @public
  */
 export declare class IAMClient extends __Client<__HttpHandlerOptions, ServiceInputTypes, ServiceOutputTypes, IAMClientResolvedConfig> {

package/dist-types/index.d.ts

@@ -4,6 +4,57 @@
  *       access to Amazon Web Services services. With IAM, you can centrally manage users, security credentials
  *       such as access keys, and permissions that control which Amazon Web Services resources users and
  *       applications can access. For more information about IAM, see <a href="http://aws.amazon.com/iam/">Identity and Access Management (IAM)</a> and the <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/">Identity and Access Management User Guide</a>.</p>
+ *          <p>
+ *             <b>Programmatic access to IAM</b>
+ *          </p>
+ *          <p>We recommend that you use the Amazon Web Services SDKs to make programmatic API calls to IAM. The Amazon Web Services
+ *       SDKs consist of libraries and sample code for various programming languages and platforms
+ *       (for example, Java, Ruby, .NET, iOS, and Android). The SDKs provide a convenient way to
+ *       create programmatic access to IAM and Amazon Web Services. For example, the SDKs take care of tasks such as
+ *       cryptographically signing requests, managing errors, and retrying requests automatically.
+ *       For more information, see <a href="http://aws.amazon.com/tools/">Tools to build on
+ *         Amazon Web Services</a>.</p>
+ *          <p>Alternatively, you can also use the IAM Query API to make direct calls to the IAM
+ *       service. For more information about calling the IAM Query API, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/IAM_UsingQueryAPI.html">Making query
+ *         requests</a> in the <i>Identity and Access Management User Guide</i>. IAM supports GET and
+ *       POST requests for all actions. That is, the API does not require you to use GET for some
+ *       actions and POST for others. However, GET requests are subject to the limitation size of a
+ *       URL. Therefore, for operations that require larger sizes, use a POST request.</p>
+ *          <p>
+ *             <b>Signing requests</b>
+ *          </p>
+ *          <p>Requests must be signed using an access key ID and a secret access key. We strongly
+ *       recommend that you do not use your Amazon Web Services account access key ID and secret access key for
+ *       everyday work with IAM. You can use the access key ID and secret access key for an
+ *       IAM user or you can use the Security Token Service to generate temporary security credentials and use
+ *       those to sign requests.</p>
+ *          <p>To sign requests, we recommend that you use <a href="https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html">Signature Version 4</a>. If you have an
+ *       existing application that uses Signature Version 2, you do not have to update it to use
+ *       Signature Version 4. However, some operations now require Signature Version 4. The
+ *       documentation for operations that require version 4 indicate this requirement.</p>
+ *          <p>
+ *             <b>Additional resources</b>
+ *          </p>
+ *          <ul>
+ *             <li>
+ *                <p>
+ *                   <a href="https://docs.aws.amazon.com/general/latest/gr/aws-security-credentials.html">Amazon Web Services
+ *           security credentials</a>. This topic provides general information about the types of
+ *           credentials used for accessing Amazon Web Services.</p>
+ *             </li>
+ *             <li>
+ *                <p>
+ *                   <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/IAMBestPractices.html">IAM best
+ *           practices</a>. This topic presents a list of suggestions for using the IAM service
+ *           to help secure your Amazon Web Services resources.</p>
+ *             </li>
+ *             <li>
+ *                <p>
+ *                   <a href="https://docs.aws.amazon.com/general/latest/gr/signing_aws_api_requests.html">Signing
+ *           Amazon Web Services API requests</a>. This set of topics walk you through the process of signing a
+ *           request using an access key ID and secret access key.</p>
+ *             </li>
+ *          </ul>
  *
  * @packageDocumentation
  */

package/dist-types/models/models_0.d.ts

@@ -1002,6 +1002,11 @@ export interface CreateOpenIDConnectProviderRequest {
      *          <p>For more information about obtaining the OIDC provider thumbprint, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/identity-providers-oidc-obtain-thumbprint.html">Obtaining the
      *                 thumbprint for an OpenID Connect provider</a> in the <i>IAM user
      *                 Guide</i>.</p>
+     *          <note>
+     *             <p>If your OIDC provider's discovery endpoint and JWKS endpoint
+     *                 (<code>jwks_uri</code>) use different certificates or hosts, include the
+     *                 thumbprints for both endpoints in this list.</p>
+     *          </note>
      * @public
      */
     ThumbprintList?: string[] | undefined;

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@aws-sdk/client-iam",
   "description": "AWS SDK for JavaScript Iam Client for Node.js, Browser and React Native",
-  "version": "3.1039.0",
+  "version": "3.1041.0",
   "scripts": {
     "build": "concurrently 'yarn:build:types' 'yarn:build:es' && yarn build:cjs",
     "build:cjs": "node ../../scripts/compilation/inline client-iam",
@@ -27,17 +27,17 @@
   "dependencies": {
     "@aws-crypto/sha256-browser": "5.2.0",
     "@aws-crypto/sha256-js": "5.2.0",
-    "@aws-sdk/core": "^3.974.7",
-    "@aws-sdk/credential-provider-node": "^3.972.38",
+    "@aws-sdk/core": "^3.974.8",
+    "@aws-sdk/credential-provider-node": "^3.972.39",
     "@aws-sdk/middleware-host-header": "^3.972.10",
     "@aws-sdk/middleware-logger": "^3.972.10",
     "@aws-sdk/middleware-recursion-detection": "^3.972.11",
-    "@aws-sdk/middleware-user-agent": "^3.972.37",
+    "@aws-sdk/middleware-user-agent": "^3.972.38",
     "@aws-sdk/region-config-resolver": "^3.972.13",
     "@aws-sdk/types": "^3.973.8",
     "@aws-sdk/util-endpoints": "^3.996.8",
     "@aws-sdk/util-user-agent-browser": "^3.972.10",
-    "@aws-sdk/util-user-agent-node": "^3.973.23",
+    "@aws-sdk/util-user-agent-node": "^3.973.24",
     "@smithy/config-resolver": "^4.4.17",
     "@smithy/core": "^3.23.17",
     "@smithy/fetch-http-handler": "^5.3.17",