How AWS Continuum works with IAM

Before you use IAM to manage access to AWS Continuum, learn what IAM features are available to use with AWS Continuum.

IAM feature	AWS Continuum support
Identity-based policies	Yes
Resource-based policies	Yes
Policy actions	Yes
Policy resources	Yes
Policy condition keys	Yes
ACLs	No
ABAC (tags in policies)	Partial
Temporary credentials	Yes
Principal permissions	Yes
Service roles	Yes
Service-linked roles	Yes

To get a high-level view of how AWS Continuum and other AWS services work with most IAM features, see AWS services that work with IAM in the IAM User Guide.

Identity-based policies for AWS Continuum

Supports identity-based policies: Yes

Identity-based policies are JSON permissions policy documents that you can attach to an identity, such as an IAM user, group of users, or role. These policies control what actions users and roles can perform, on which resources, and under what conditions. To learn how to create an identity-based policy, see Define custom IAM permissions with customer managed policies in the IAM User Guide.

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. To learn about all of the elements that you can use in a JSON policy, see IAM JSON policy elements reference in the IAM User Guide.

Identity-based policy examples for AWS Continuum

To view examples of AWS Continuum identity-based policies, see Identity-based policy examples for AWS Continuum.

Resource-based policies within AWS Continuum

Supports resource-based policies: Yes

Resource-based policies are JSON policy documents that you attach to a resource. Examples of resource-based policies are IAM role trust policies and Amazon S3 bucket policies. In services that support resource-based policies, service administrators can use them to control access to a specific resource. For the resource where the policy is attached, the policy defines what actions a specified principal can perform on that resource and under what conditions. You must specify a principal in a resource-based policy. Principals can include accounts, users, roles, federated users, or AWS services.

To enable cross-account access, you can specify an entire account or IAM entities in another account as the principal in a resource-based policy. For more information, see Cross account resource access in IAM in the IAM User Guide.

AWS Continuum supports resource-based policies for collectors. A collector resource policy controls access to the inventory that the collector gathers. You must use a resource policy to grant access to a principal outside the collector's AWS account. The resource policy does not associate the collector with an environment. Create that association separately and provide a collector data-access role.

You manage a collector resource policy with GetResourcePolicy and PutResourcePolicy. For instructions on setting up a resource policy and an example policy, see Authorizing an environment to use collector data.

Policy resources for AWS Continuum

Supports policy resources: Yes

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. As a best practice, specify a resource using its Amazon Resource Name (ARN). For actions that don't support resource-level permissions, use a wildcard (*) to indicate that the statement applies to all resources.

"Resource": "*"

For information about scoping policies to a collector, an environment, and a data-access role, see Authorizing an environment to use collector data. For information about specifying resources in a policy, see IAM JSON policy elements: Resource in the IAM User Guide.

To view examples of AWS Continuum identity-based policies, see Identity-based policy examples for AWS Continuum.

Policy condition keys for AWS Continuum

Supports service-specific policy condition keys: Yes

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 Condition element specifies when statements execute based on defined criteria. You can create conditional expressions that use condition operators, such as equals or less than, to match the condition in the policy with values in the request. To see all AWS global condition keys, see AWS global condition context keys in the IAM User Guide.

For information about conditions in collector authorization policies, see Authorizing an environment to use collector data. For information about conditions in a policy, see IAM JSON policy elements: Condition in the IAM User Guide.

To view examples of AWS Continuum identity-based policies, see Identity-based policy examples for AWS Continuum.

Using temporary credentials with AWS Continuum

Supports temporary credentials: Yes

Temporary credentials provide short-term access to AWS resources and are automatically created when you use federation or switch roles. AWS recommends that you dynamically generate temporary credentials instead of using long-term access keys. For more information, see Temporary security credentials in IAM and AWS services that work with IAM in the IAM User Guide.

Cross-service principal permissions for AWS Continuum

Supports forward access sessions (FAS): Yes

Forward access sessions (FAS) use the permissions of the principal calling an AWS service, combined with the requesting AWS service to make requests to downstream services. For policy details when making FAS requests, see Forward access sessions.

Service roles for AWS Continuum

Supports service roles: Yes

A service role is an IAM role that a service assumes to perform actions on your behalf. An IAM administrator can create, modify, and delete a service role from within IAM. For more information, see Create a role to delegate permissions to an AWS service in the IAM User Guide.

Warning

Changing the permissions for a service role might break AWS Continuum functionality. Edit service roles only when AWS Continuum provides guidance to do so.

Service-linked roles for AWS Continuum

Supports service-linked roles: Yes

A service-linked role is a type of service role that is linked to an AWS service. The service can assume the role to perform an action on your behalf. Service-linked roles appear in your AWS account and are owned by the service. An IAM administrator can view, but not edit the permissions for service-linked roles.

For details about creating or managing service-linked roles, see AWS services that work with IAM.