@aws-sdk/client-accessanalyzer 3.828.0 → 3.831.0

package/dist-types/commands/UpdateAnalyzerCommand.d.ts

@@ -54,6 +54,23 @@ declare const UpdateAnalyzerCommand_base: {
  *         ],
  *       },
  *     },
+ *     internalAccess: { // InternalAccessConfiguration
+ *       analysisRule: { // InternalAccessAnalysisRule
+ *         inclusions: [ // InternalAccessAnalysisRuleCriteriaList
+ *           { // InternalAccessAnalysisRuleCriteria
+ *             accountIds: [
+ *               "STRING_VALUE",
+ *             ],
+ *             resourceTypes: [ // ResourceTypeList
+ *               "STRING_VALUE",
+ *             ],
+ *             resourceArns: [ // ResourceArnsList
+ *               "STRING_VALUE",
+ *             ],
+ *           },
+ *         ],
+ *       },
+ *     },
  *   },
  * };
  * const command = new UpdateAnalyzerCommand(input);
@@ -77,6 +94,23 @@ declare const UpdateAnalyzerCommand_base: {
  * //         ],
  * //       },
  * //     },
+ * //     internalAccess: { // InternalAccessConfiguration
+ * //       analysisRule: { // InternalAccessAnalysisRule
+ * //         inclusions: [ // InternalAccessAnalysisRuleCriteriaList
+ * //           { // InternalAccessAnalysisRuleCriteria
+ * //             accountIds: [
+ * //               "STRING_VALUE",
+ * //             ],
+ * //             resourceTypes: [ // ResourceTypeList
+ * //               "STRING_VALUE",
+ * //             ],
+ * //             resourceArns: [ // ResourceArnsList
+ * //               "STRING_VALUE",
+ * //             ],
+ * //           },
+ * //         ],
+ * //       },
+ * //     },
  * //   },
  * // };
  *

package/dist-types/commands/ValidatePolicyCommand.d.ts

@@ -27,9 +27,7 @@ declare const ValidatePolicyCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Requests the validation of a policy and returns a list of findings. The findings help
- *          you identify issues and provide actionable recommendations to resolve the issue and enable
- *          you to author functional policies that meet security best practices. </p>
+ * <p>Requests the validation of a policy and returns a list of findings. The findings help you identify issues and provide actionable recommendations to resolve the issue and enable you to author functional policies that meet security best practices. </p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/endpoint/EndpointParameters.d.ts

@@ -3,9 +3,9 @@ import { Endpoint, EndpointParameters as __EndpointParameters, EndpointV2, Provi
  * @public
  */
 export interface ClientInputEndpointParameters {
-    region?: string | Provider<string>;
-    useDualstackEndpoint?: boolean | Provider<boolean>;
-    useFipsEndpoint?: boolean | Provider<boolean>;
+    region?: string | undefined | Provider<string | undefined>;
+    useDualstackEndpoint?: boolean | undefined | Provider<boolean | undefined>;
+    useFipsEndpoint?: boolean | undefined | Provider<boolean | undefined>;
     endpoint?: string | Provider<string> | Endpoint | Provider<Endpoint> | EndpointV2 | Provider<EndpointV2>;
 }
 export type ClientResolvedEndpointParameters = ClientInputEndpointParameters & {
@@ -31,8 +31,8 @@ export declare const commonParams: {
     };
 };
 export interface EndpointParameters extends __EndpointParameters {
-    Region?: string;
-    UseDualStack?: boolean;
-    UseFIPS?: boolean;
-    Endpoint?: string;
+    Region?: string | undefined;
+    UseDualStack?: boolean | undefined;
+    UseFIPS?: boolean | undefined;
+    Endpoint?: string | undefined;
 }

package/dist-types/index.d.ts

@@ -1,28 +1,5 @@
 /**
- * <p>Identity and Access Management Access Analyzer helps you to set, verify, and refine your IAM policies by providing
- *          a suite of capabilities. Its features include findings for external and unused access,
- *          basic and custom policy checks for validating policies, and policy generation to generate
- *          fine-grained policies. To start using IAM Access Analyzer to identify external or unused access,
- *          you first need to create an analyzer.</p>
- *          <p>
- *             <b>External access analyzers</b> help identify potential risks
- *          of accessing resources by enabling you to identify any resource policies that grant access
- *          to an external principal. It does this by using logic-based reasoning to analyze
- *          resource-based policies in your Amazon Web Services environment. An external principal can be another
- *          Amazon Web Services account, a root user, an IAM user or role, a federated user, an Amazon Web Services service, or an
- *          anonymous user. You can also use IAM Access Analyzer to preview public and cross-account access
- *          to your resources before deploying permissions changes.</p>
- *          <p>
- *             <b>Unused access analyzers</b> help identify potential
- *          identity access risks by enabling you to identify unused IAM roles, unused access keys,
- *          unused console passwords, and IAM principals with unused service and action-level
- *          permissions.</p>
- *          <p>Beyond findings, IAM Access Analyzer provides basic and custom policy checks to validate IAM
- *          policies before deploying permissions changes. You can use policy generation to refine
- *          permissions by attaching a policy generated using access activity logged in CloudTrail logs. </p>
- *          <p>This guide describes the IAM Access Analyzer operations that you can call programmatically.
- *          For general information about IAM Access Analyzer, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/what-is-access-analyzer.html">Identity and Access Management Access Analyzer</a> in the
- *             <b>IAM User Guide</b>.</p>
+ * <p>Identity and Access Management Access Analyzer helps you to set, verify, and refine your IAM policies by providing a suite of capabilities. Its features include findings for external and unused access, basic and custom policy checks for validating policies, and policy generation to generate fine-grained policies. To start using IAM Access Analyzer to identify external or unused access, you first need to create an analyzer.</p> <p> <b>External access analyzers</b> help identify potential risks of accessing resources by enabling you to identify any resource policies that grant access to an external principal. It does this by using logic-based reasoning to analyze resource-based policies in your Amazon Web Services environment. An external principal can be another Amazon Web Services account, a root user, an IAM user or role, a federated user, an Amazon Web Services service, or an anonymous user. You can also use IAM Access Analyzer to preview public and cross-account access to your resources before deploying permissions changes.</p> <p> <b>Unused access analyzers</b> help identify potential identity access risks by enabling you to identify unused IAM roles, unused access keys, unused console passwords, and IAM principals with unused service and action-level permissions.</p> <p>Beyond findings, IAM Access Analyzer provides basic and custom policy checks to validate IAM policies before deploying permissions changes. You can use policy generation to refine permissions by attaching a policy generated using access activity logged in CloudTrail logs. </p> <p>This guide describes the IAM Access Analyzer operations that you can call programmatically. For general information about IAM Access Analyzer, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/what-is-access-analyzer.html">Identity and Access Management Access Analyzer</a> in the <b>IAM User Guide</b>.</p>
  *
  * @packageDocumentation
  */