How Amazon Inspector works with IAM - Amazon Inspector

How Amazon Inspector works with IAM

Before you use IAM to manage access to Amazon Inspector, you should understand what IAM features are available to use with Amazon Inspector. To get a high-level view of how Amazon Inspector and other AWS services work with IAM, see AWS Services That Work with IAM in the IAM User Guide.

Amazon Inspector identity-based policies

With IAM identity-based policies, you can specify allowed or denied actions and resources as well as the conditions under which actions are allowed or denied. Amazon Inspector supports specific actions, resources, and condition keys. To learn about all of the elements that you use in a JSON policy, see IAM JSON Policy Elements Reference in the IAM User Guide.

Actions

Administrators can use AWS JSON policies to specify who has access to what. That is, which principal can perform actions on what resources, and under what conditions.

The Action element of a JSON policy describes the actions that you can use to allow or deny access in a policy. Policy actions usually have the same name as the associated AWS API operation. There are some exceptions, such as permission-only actions that don't have a matching API operation. There are also some operations that require multiple actions in a policy. These additional actions are called dependent actions.

Include actions in a policy to grant permissions to perform the associated operation.

Policy actions in Amazon Inspector use the following prefix before the action: inspector:. For example, the inspector:ListFindings permission allows the user permissions to perform the Amazon Inspector ListFindings operation. Policy statements must include either an Action or NotAction element. Amazon Inspector defines its own set of actions that describe tasks that you can perform with this service.

To specify multiple actions in a single statement, separate them with commas as follows:

"Action": [ "inspector:action1", "inspector:action2"

You can specify multiple actions using wildcards (*). For example, to specify all actions that begin with the word Describe, include the following action:

"Action": "inspector:Describe*"

To see a list of Amazon Inspector actions, see Actions Defined by Amazon Inspector in the IAM User Guide.

Resources

Administrators can use AWS JSON policies to specify who has access to what. That is, which principal can perform actions on what resources, and under what conditions.

The Resource JSON policy element specifies the object or objects to which the action applies. Statements must include either a Resource or a NotResource element. As a best practice, specify a resource using its Amazon Resource Name (ARN). You can do this for actions that support a specific resource type, known as resource-level permissions.

For actions that don't support resource-level permissions, such as listing operations, use a wildcard (*) to indicate that the statement applies to all resources.

"Resource": "*"

Amazon Inspector does not support specifying a resource ARN in the Resource element of an IAM policy statement. To allow access to Amazon Inspector, specify "Resource": "*" in your policy.

Condition keys

Amazon Inspector does not provide any service-specific condition keys, but it does support using some global condition keys. To see all AWS global condition keys, see AWS global condition context keys in the IAM User Guide.

Managed policies for Amazon Inspector

Amazon Inspector provides the following AWS managed policies, which you can attach to IAM users in your account.

  • AmazonInspectorFullAccess – Provides full access to Amazon Inspector.

  • AmazonInspectorReadOnlyAccess – Provides read-only access to Amazon Inspector.

Examples

To view examples of Amazon Inspector identity-based policies, see Amazon Inspector identity-based policy examples.

Amazon Inspector resource-based policies (not supported)

Amazon Inspector does not support resource-based policies.

Authorization based on Amazon Inspector tags (not supported)

Amazon Inspector does not support tagging resources or controlling access based on tags

Amazon Inspector IAM roles

An IAM role is an entity within your AWS account that has specific permissions.

Using temporary credentials with Amazon Inspector

You can use temporary credentials to sign in with federation, to assume an IAM role, or to assume a cross-account role. You obtain temporary security credentials by calling AWS STS API operations such as AssumeRole or GetFederationToken.

Amazon Inspector supports using temporary credentials.

Service-linked roles

Service-linked roles allow AWS services to access resources in other services to complete an action on your behalf. Service-linked roles appear in your IAM account and are owned by the service. An IAM administrator can view but not edit the permissions for service-linked roles.

Amazon Inspector supports service-linked roles. For details about creating or managing Amazon Inspector service-linked roles, see Using service-linked roles for Amazon Inspector.

Service roles

This feature allows a service to assume a service role on your behalf. This role allows the service to access resources in other services to complete an action on your behalf. Service roles appear in your IAM account and are owned by the account. This means that an IAM administrator can change the permissions for this role. However, doing so might break the functionality of the service.

Amazon Inspector supports service roles.