You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(client-accessanalyzer): IAM Access Analyzer now continuously monitors IAM roles and users in your AWS account or organization to generate findings for unused access. Additionally, IAM Access Analyzer now provides custom policy checks to validate that IAM policies adhere to your security standards ahead of deployments.
Copy file name to clipboardExpand all lines: clients/client-accessanalyzer/README.md
+56-9Lines changed: 56 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -6,15 +6,30 @@
6
6
7
7
AWS SDK for JavaScript AccessAnalyzer Client for Node.js, Browser and React Native.
8
8
9
-
<p>Identity and Access Management Access Analyzer helps identify potential resource-access risks by enabling you to
10
-
identify any policies that grant access to an external principal. It does this by using
11
-
logic-based reasoning to analyze resource-based policies in your Amazon Web Services environment. An
12
-
external principal can be another Amazon Web Services account, a root user, an IAM user or role, a
13
-
federated user, an Amazon Web Services service, or an anonymous user. You can also use IAM Access Analyzer to
14
-
preview and validate public and cross-account access to your resources before deploying
15
-
permissions changes. This guide describes the Identity and Access Management Access Analyzer operations that you can
16
-
call programmatically. For general information about IAM Access Analyzer, see <ahref="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>
17
-
<p>To start using IAM Access Analyzer, you first need to create an analyzer.</p>
9
+
<p>Identity and Access Management Access Analyzer helps you to set, verify, and refine your IAM policies by providing
10
+
a suite of capabilities. Its features include findings for external and unused access,
11
+
basic and custom policy checks for validating policies, and policy generation to generate
12
+
fine-grained policies. To start using IAM Access Analyzer to identify external or unused access,
13
+
you first need to create an analyzer.</p>
14
+
<p>
15
+
<b>External access analyzers</b> help identify potential risks
16
+
of accessing resources by enabling you to identify any resource policies that grant access
17
+
to an external principal. It does this by using logic-based reasoning to analyze
18
+
resource-based policies in your Amazon Web Services environment. An external principal can be another
19
+
Amazon Web Services account, a root user, an IAM user or role, a federated user, an Amazon Web Services service, or an
20
+
anonymous user. You can also use IAM Access Analyzer to preview public and cross-account access
21
+
to your resources before deploying permissions changes.</p>
22
+
<p>
23
+
<b>Unused access analyzers</b> help identify potential
24
+
identity access risks by enabling you to identify unused IAM roles, unused access keys,
25
+
unused console passwords, and IAM principals with unused service and action-level
26
+
permissions.</p>
27
+
<p>Beyond findings, IAM Access Analyzer provides basic and custom policy checks to validate IAM
28
+
policies before deploying permissions changes. You can use policy generation to refine
29
+
permissions by attaching a policy generated using access activity logged in CloudTrail logs. </p>
30
+
<p>This guide describes the IAM Access Analyzer operations that you can call programmatically.
31
+
For general information about IAM Access Analyzer, see <ahref="https://docs.aws.amazon.com/IAM/latest/UserGuide/what-is-access-analyzer.html">Identity and Access Management Access Analyzer</a> in the
32
+
<b>IAM User Guide</b>.</p>
18
33
19
34
## Installing
20
35
@@ -226,6 +241,22 @@ CancelPolicyGeneration
226
241
227
242
[Command API Reference](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/client/accessanalyzer/command/CancelPolicyGenerationCommand/) / [Input](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-accessanalyzer/Interface/CancelPolicyGenerationCommandInput/) / [Output](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-accessanalyzer/Interface/CancelPolicyGenerationCommandOutput/)
228
243
244
+
</details>
245
+
<details>
246
+
<summary>
247
+
CheckAccessNotGranted
248
+
</summary>
249
+
250
+
[Command API Reference](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/client/accessanalyzer/command/CheckAccessNotGrantedCommand/) / [Input](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-accessanalyzer/Interface/CheckAccessNotGrantedCommandInput/) / [Output](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-accessanalyzer/Interface/CheckAccessNotGrantedCommandOutput/)
251
+
252
+
</details>
253
+
<details>
254
+
<summary>
255
+
CheckNoNewAccess
256
+
</summary>
257
+
258
+
[Command API Reference](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/client/accessanalyzer/command/CheckNoNewAccessCommand/) / [Input](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-accessanalyzer/Interface/CheckNoNewAccessCommandInput/) / [Output](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-accessanalyzer/Interface/CheckNoNewAccessCommandOutput/)
259
+
229
260
</details>
230
261
<details>
231
262
<summary>
@@ -306,6 +337,14 @@ GetFinding
306
337
307
338
[Command API Reference](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/client/accessanalyzer/command/GetFindingCommand/) / [Input](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-accessanalyzer/Interface/GetFindingCommandInput/) / [Output](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-accessanalyzer/Interface/GetFindingCommandOutput/)
308
339
340
+
</details>
341
+
<details>
342
+
<summary>
343
+
GetFindingV2
344
+
</summary>
345
+
346
+
[Command API Reference](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/client/accessanalyzer/command/GetFindingV2Command/) / [Input](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-accessanalyzer/Interface/GetFindingV2CommandInput/) / [Output](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-accessanalyzer/Interface/GetFindingV2CommandOutput/)
347
+
309
348
</details>
310
349
<details>
311
350
<summary>
@@ -362,6 +401,14 @@ ListFindings
362
401
363
402
[Command API Reference](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/client/accessanalyzer/command/ListFindingsCommand/) / [Input](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-accessanalyzer/Interface/ListFindingsCommandInput/) / [Output](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-accessanalyzer/Interface/ListFindingsCommandOutput/)
364
403
404
+
</details>
405
+
<details>
406
+
<summary>
407
+
ListFindingsV2
408
+
</summary>
409
+
410
+
[Command API Reference](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/client/accessanalyzer/command/ListFindingsV2Command/) / [Input](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-accessanalyzer/Interface/ListFindingsV2CommandInput/) / [Output](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-aws-sdk-client-accessanalyzer/Interface/ListFindingsV2CommandOutput/)
* <p>Identity and Access Management Access Analyzer helps identify potential resource-access risks by enabling you to
596
-
* identify any policies that grant access to an external principal. It does this by using
597
-
* logic-based reasoning to analyze resource-based policies in your Amazon Web Services environment. An
598
-
* external principal can be another Amazon Web Services account, a root user, an IAM user or role, a
599
-
* federated user, an Amazon Web Services service, or an anonymous user. You can also use IAM Access Analyzer to
600
-
* preview and validate public and cross-account access to your resources before deploying
601
-
* permissions changes. This guide describes the Identity and Access Management Access Analyzer operations that you can
602
-
* 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>
603
-
* <p>To start using IAM Access Analyzer, you first need to create an analyzer.</p>
678
+
* <p>Identity and Access Management Access Analyzer helps you to set, verify, and refine your IAM policies by providing
679
+
* a suite of capabilities. Its features include findings for external and unused access,
680
+
* basic and custom policy checks for validating policies, and policy generation to generate
681
+
* fine-grained policies. To start using IAM Access Analyzer to identify external or unused access,
682
+
* you first need to create an analyzer.</p>
683
+
* <p>
684
+
* <b>External access analyzers</b> help identify potential risks
685
+
* of accessing resources by enabling you to identify any resource policies that grant access
686
+
* to an external principal. It does this by using logic-based reasoning to analyze
687
+
* resource-based policies in your Amazon Web Services environment. An external principal can be another
688
+
* Amazon Web Services account, a root user, an IAM user or role, a federated user, an Amazon Web Services service, or an
689
+
* anonymous user. You can also use IAM Access Analyzer to preview public and cross-account access
690
+
* to your resources before deploying permissions changes.</p>
691
+
* <p>
692
+
* <b>Unused access analyzers</b> help identify potential
693
+
* identity access risks by enabling you to identify unused IAM roles, unused access keys,
694
+
* unused console passwords, and IAM principals with unused service and action-level
695
+
* permissions.</p>
696
+
* <p>Beyond findings, IAM Access Analyzer provides basic and custom policy checks to validate IAM
697
+
* policies before deploying permissions changes. You can use policy generation to refine
698
+
* permissions by attaching a policy generated using access activity logged in CloudTrail logs. </p>
699
+
* <p>This guide describes the IAM Access Analyzer operations that you can call programmatically.
700
+
* 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
0 commit comments