openapi: 3.1.0 info: title: Amazon Web Services accessanalyzer 2012 09 25 Virtualclusters API description:

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.

External access analyzers 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.

Unused access analyzers 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.

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.

This guide describes the IAM Access Analyzer operations that you can call programmatically. For general information about IAM Access Analyzer, see Identity and Access Management Access Analyzer in the IAM User Guide.

tags: - name: Virtualclusters paths: /virtualclusters/{virtualClusterId}/jobruns/{jobRunId}: GET: summary: Amazon Web Services Describejobrun description: Displays detailed information about a job run. A job run is a unit of work, such as a Spark jar, PySpark script, or SparkSQL query, that you submit to Amazon EMR on EKS. operationId: amazonWebServicesDescribeJobRun tags: - Virtualclusters /virtualclusters/{virtualClusterId}/endpoints: GET: summary: Amazon Web Services Listmanagedendpoints description: Lists managed endpoints based on a set of parameters. A managed endpoint is a gateway that connects Amazon EMR Studio to Amazon EMR on EKS so that Amazon EMR Studio can communicate with your virtual cluster. operationId: amazonWebServicesListManagedEndpoints tags: - Virtualclusters /virtualclusters: GET: summary: Amazon Web Services Listvirtualclusters description: Lists information about the specified virtual cluster. Virtual cluster is a managed entity on Amazon EMR on EKS. You can create, describe, list and delete virtual clusters. They do not consume any additional resource in your system. A single virtual cluster maps to a single Kubernetes namespace. Given this relationship, you can model virtual clusters the same way you model Kubernetes namespaces to meet your requirements. operationId: amazonWebServicesListVirtualClusters tags: - Virtualclusters /virtualclusters/{virtualClusterId}/endpoints/{endpointId}: GET: summary: Amazon Web Services Describemanagedendpoint description: Displays detailed information about a managed endpoint. A managed endpoint is a gateway that connects Amazon EMR Studio to Amazon EMR on EKS so that Amazon EMR Studio can communicate with your virtual cluster. operationId: amazonWebServicesDescribeManagedEndpoint tags: - Virtualclusters /virtualclusters/{virtualClusterId}: GET: summary: Amazon Web Services Describevirtualcluster description: Displays detailed information about a specified virtual cluster. Virtual cluster is a managed entity on Amazon EMR on EKS. You can create, describe, list and delete virtual clusters. They do not consume any additional resource in your system. A single virtual cluster maps to a single Kubernetes namespace. Given this relationship, you can model virtual clusters the same way you model Kubernetes namespaces to meet your requirements. operationId: amazonWebServicesDescribeVirtualCluster tags: - Virtualclusters /virtualclusters/{virtualClusterId}/endpoints/{endpointId}/credentials: POST: summary: Amazon Web Services Getmanagedendpointsessioncredentials description: 'Generate a session token to connect to a managed endpoint. ' operationId: amazonWebServicesGetManagedEndpointSessionCredentials tags: - Virtualclusters /virtualclusters/{virtualClusterId}/jobruns: POST: summary: Amazon Web Services Startjobrun description: Starts a job run. A job run is a unit of work, such as a Spark jar, PySpark script, or SparkSQL query, that you submit to Amazon EMR on EKS. operationId: amazonWebServicesStartJobRun tags: - Virtualclusters