feat(client-accessanalyzer): We are launching a new analyzer type, internal access analyzer. The new analyzer will generate internal access findings, which help customers understand who within their AWS organization or AWS Account has access to their critical AWS resources.

Author: awstools

clients/client-accessanalyzer/README.md

@@ -6,30 +6,7 @@
 
 AWS SDK for JavaScript AccessAnalyzer Client for Node.js, Browser and React Native.
 
-<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>
 
 ## Installing
 

clients/client-accessanalyzer/src/AccessAnalyzer.ts

@@ -788,30 +788,7 @@ export interface AccessAnalyzer {
 }
 
 /**
- * <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>
  * @public
  */
 export class AccessAnalyzer extends AccessAnalyzerClient implements AccessAnalyzer {}

clients/client-accessanalyzer/src/AccessAnalyzerClient.ts

@@ -415,30 +415,7 @@ export type AccessAnalyzerClientResolvedConfigType = __SmithyResolvedConfigurati
 export interface AccessAnalyzerClientResolvedConfig extends AccessAnalyzerClientResolvedConfigType {}
 
 /**
- * <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>
  * @public
  */
 export class AccessAnalyzerClient extends __Client<

clients/client-accessanalyzer/src/commands/ApplyArchiveRuleCommand.ts

@@ -28,8 +28,7 @@ export interface ApplyArchiveRuleCommandInput extends ApplyArchiveRuleRequest {}
 export interface ApplyArchiveRuleCommandOutput extends __MetadataBearer {}
 
 /**
- * <p>Retroactively applies the archive rule to existing findings that meet the archive rule
- *          criteria.</p>
+ * <p>Retroactively applies the archive rule to existing findings that meet the archive rule criteria.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

clients/client-accessanalyzer/src/commands/CheckNoNewAccessCommand.ts

@@ -32,12 +32,7 @@ export interface CheckNoNewAccessCommandInput extends CheckNoNewAccessRequest {}
 export interface CheckNoNewAccessCommandOutput extends CheckNoNewAccessResponse, __MetadataBearer {}
 
 /**
- * <p>Checks whether new access is allowed for an updated policy when compared to the existing
- *          policy.</p>
- *          <p>You can find examples for reference policies and learn how to set up and run a custom
- *          policy check for new access in the <a href="https://github.com/aws-samples/iam-access-analyzer-custom-policy-check-samples">IAM Access Analyzer custom policy checks samples</a> repository on GitHub. The reference
- *          policies in this repository are meant to be passed to the
- *             <code>existingPolicyDocument</code> request parameter.</p>
+ * <p>Checks whether new access is allowed for an updated policy when compared to the existing policy.</p> <p>You can find examples for reference policies and learn how to set up and run a custom policy check for new access in the <a href="https://github.com/aws-samples/iam-access-analyzer-custom-policy-check-samples">IAM Access Analyzer custom policy checks samples</a> repository on GitHub. The reference policies in this repository are meant to be passed to the <code>existingPolicyDocument</code> request parameter.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

clients/client-accessanalyzer/src/commands/CheckNoPublicAccessCommand.ts

@@ -32,8 +32,7 @@ export interface CheckNoPublicAccessCommandInput extends CheckNoPublicAccessRequ
 export interface CheckNoPublicAccessCommandOutput extends CheckNoPublicAccessResponse, __MetadataBearer {}
 
 /**
- * <p>Checks whether a resource policy can grant public access to the specified resource
- *          type.</p>
+ * <p>Checks whether a resource policy can grant public access to the specified resource type.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

clients/client-accessanalyzer/src/commands/CreateAccessPreviewCommand.ts

@@ -28,8 +28,7 @@ export interface CreateAccessPreviewCommandInput extends CreateAccessPreviewRequ
 export interface CreateAccessPreviewCommandOutput extends CreateAccessPreviewResponse, __MetadataBearer {}
 
 /**
- * <p>Creates an access preview that allows you to preview IAM Access Analyzer findings for your
- *          resource before deploying resource permissions.</p>
+ * <p>Creates an access preview that allows you to preview IAM Access Analyzer findings for your resource before deploying resource permissions.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

clients/client-accessanalyzer/src/commands/CreateAnalyzerCommand.ts

@@ -79,6 +79,23 @@ export interface CreateAnalyzerCommandOutput extends CreateAnalyzerResponse, __M
  *         ],
  *       },
  *     },
+ *     internalAccess: { // InternalAccessConfiguration
+ *       analysisRule: { // InternalAccessAnalysisRule
+ *         inclusions: [ // InternalAccessAnalysisRuleCriteriaList
+ *           { // InternalAccessAnalysisRuleCriteria
+ *             accountIds: [
+ *               "STRING_VALUE",
+ *             ],
+ *             resourceTypes: [ // ResourceTypeList
+ *               "STRING_VALUE",
+ *             ],
+ *             resourceArns: [ // ResourceArnsList
+ *               "STRING_VALUE",
+ *             ],
+ *           },
+ *         ],
+ *       },
+ *     },
  *   },
  * };
  * const command = new CreateAnalyzerCommand(input);

clients/client-accessanalyzer/src/commands/CreateArchiveRuleCommand.ts

@@ -28,9 +28,7 @@ export interface CreateArchiveRuleCommandInput extends CreateArchiveRuleRequest
 export interface CreateArchiveRuleCommandOutput extends __MetadataBearer {}
 
 /**
- * <p>Creates an archive rule for the specified analyzer. Archive rules automatically archive
- *          new findings that meet the criteria you define when you create the rule.</p>
- *          <p>To learn about filter keys that you can use to create an archive rule, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-reference-filter-keys.html">IAM Access Analyzer filter keys</a> in the <b>IAM User Guide</b>.</p>
+ * <p>Creates an archive rule for the specified analyzer. Archive rules automatically archive new findings that meet the criteria you define when you create the rule.</p> <p>To learn about filter keys that you can use to create an archive rule, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-reference-filter-keys.html">IAM Access Analyzer filter keys</a> in the <b>IAM User Guide</b>.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

clients/client-accessanalyzer/src/commands/DeleteAnalyzerCommand.ts

@@ -28,9 +28,7 @@ export interface DeleteAnalyzerCommandInput extends DeleteAnalyzerRequest {}
 export interface DeleteAnalyzerCommandOutput extends __MetadataBearer {}
 
 /**
- * <p>Deletes the specified analyzer. When you delete an analyzer, IAM Access Analyzer is disabled
- *          for the account or organization in the current or specific Region. All findings that were
- *          generated by the analyzer are deleted. You cannot undo this action.</p>
+ * <p>Deletes the specified analyzer. When you delete an analyzer, IAM Access Analyzer is disabled for the account or organization in the current or specific Region. All findings that were generated by the analyzer are deleted. You cannot undo this action.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript