AWS lookout-for-equipment documentation change
Summary
Simplified explanations of IAM policy elements (Resource, Condition), removed redundant details about policy evaluation logic, updated terminology from 'AWS' to 'Amazon Web Services', and consolidated content about temporary credentials/ABAC.
Security assessment
Changes are editorial improvements and terminology updates rather than security fixes. The removal of details about policy evaluation logic (AND/OR conditions) and placeholder variables reduces specificity but doesn't introduce or mitigate vulnerabilities. The temporary credentials section still emphasizes best practices without adding new security guidance.
Diff
diff --git a/lookout-for-equipment/latest/ug/security_iam_service-with-iam.md b/lookout-for-equipment/latest/ug/security_iam_service-with-iam.md index 1d32813c0..0ce6370a8 100644 --- a//lookout-for-equipment/latest/ug/security_iam_service-with-iam.md +++ b//lookout-for-equipment/latest/ug/security_iam_service-with-iam.md @@ -19 +19 @@ Identity-based policies are JSON permissions policy documents that you can attac -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. You can't specify the principal in an identity-based policy because it applies to the user or role to which it is attached. To learn about all of the elements that you can use in a JSON policy, see [IAM JSON policy elements reference](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements.html) 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](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements.html) in the _IAM User Guide_. @@ -23 +23 @@ With IAM identity-based policies, you can specify allowed or denied actions and -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_. +Administrators can use Amazon Web Services JSON policies to specify who has access to what. That is, which _principal_ can perform _actions_ on what _resources_ , and under what _conditions_. @@ -48,3 +48 @@ Administrators can use AWS JSON policies to specify who has access to what. That -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)](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference-arns.html). 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. +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)](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference-arns.html). For actions that don't support resource-level permissions, use a wildcard (*) to indicate that the statement applies to all resources. @@ -70 +68 @@ Some Lookout for Equipment actions, such as those for creating resources, cannot -To see a list of Lookout for Equipment resource types and their ARNs, see [Resources Defined by Amazon Lookout for Equipment](https://docs.aws.amazon.com/service-authorization/latest/reference/reference.html) in the _Service Authorization Reference_. To learn with which actions you can specify the ARN of each resource, see [Actions defined by Amazon Lookout for Equipment](https://docs.aws.amazon.com/service-authorization/latest/reference/reference.html). For more information about the format of ARNs, see [Amazon Resource Names (ARNs) and AWS Service Namespaces](https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html). +To see a list of Lookout for Equipment resource types and their ARNs, see [Resources Defined by Amazon Lookout for Equipment](https://docs.aws.amazon.com/service-authorization/latest/reference/reference.html) in the _Service Authorization Reference_. To learn with which actions you can specify the ARN of each resource, see [Actions defined by Amazon Lookout for Equipment](https://docs.aws.amazon.com/service-authorization/latest/reference/reference.html). For more information about the format of ARNs, see [Amazon Resource Names (ARNs) and Amazon Web Services Service Namespaces](https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html). @@ -76,7 +74 @@ Administrators can use AWS JSON policies to specify who has access to what. That -The `Condition` element (or `Condition` _block_) lets you specify conditions in which a statement is in effect. The `Condition` element is optional. You can create conditional expressions that use [condition operators](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition_operators.html), such as equals or less than, to match the condition in the policy with values in the request. - -If you specify multiple `Condition` elements in a statement, or multiple keys in a single `Condition` element, AWS evaluates them using a logical `AND` operation. If you specify multiple values for a single condition key, AWS evaluates the condition using a logical `OR` operation. All of the conditions must be met before the statement's permissions are granted. - -You can also use placeholder variables when you specify conditions. For example, you can grant an IAM user permission to access a resource only if it is tagged with their IAM user name. For more information, see [IAM policy elements: variables and tags](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_variables.html) in the _IAM User Guide_. - -AWS supports global condition keys and service-specific condition keys. To see all AWS global condition keys, see [AWS global condition context keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html) in the _IAM User Guide_. +The `Condition` element specifies when statements execute based on defined criteria. You can create conditional expressions that use [condition operators](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition_operators.html), 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](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html) in the _IAM User Guide_. @@ -119,3 +111 @@ The ID field in the ACL is the AWS account canonical user ID. To learn how to vi -Attribute-based access control (ABAC) is an authorization strategy that defines permissions based on attributes. In AWS, these attributes are called _tags_. You can attach tags to IAM entities (users or roles) and to many AWS resources. Tagging entities and resources is the first step of ABAC. Then you design ABAC policies to allow operations when the principal's tag matches the tag on the resource that they are trying to access. - -ABAC is helpful in environments that are growing rapidly and helps with situations where policy management becomes cumbersome. +Attribute-based access control (ABAC) is an authorization strategy that defines permissions based on attributes called tags. You can attach tags to IAM entities and AWS resources, then design ABAC policies to allow operations when the principal's tag matches the tag on the resource. @@ -131,5 +121 @@ For more information about ABAC, see [Define permissions with ABAC authorization -Some AWS services don't work when you sign in using temporary credentials. For additional information, including which AWS services work with temporary credentials, see [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) in the _IAM User Guide_. - -You are using temporary credentials if you sign in to the AWS Management Console using any method except a user name and password. For example, when you access AWS using your company's single sign-on (SSO) link, that process automatically creates temporary credentials. You also automatically create temporary credentials when you sign in to the console as a user and then switch roles. For more information about switching roles, see [Switch from a user to an IAM role (console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-console.html) in the _IAM User Guide_. - -You can manually create temporary credentials using the AWS CLI or AWS API. You can then use those temporary credentials to access AWS. AWS recommends that you dynamically generate temporary credentials instead of using long-term access keys. For more information, see [Temporary security credentials in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp.html). +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](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp.html) and [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) in the _IAM User Guide_. @@ -139 +125 @@ You can manually create temporary credentials using the AWS CLI or AWS API. You -When you use an IAM user or role to perform actions in AWS, you are considered a principal. When you use some services, you might perform an action that then initiates another action in a different service. FAS uses the permissions of the principal calling an AWS service, combined with the requesting AWS service to make requests to downstream services. FAS requests are only made when a service receives a request that requires interactions with other AWS services or resources to complete. In this case, you must have permissions to perform both actions. For policy details when making FAS requests, see [Forward access sessions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_forward_access_sessions.html). +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](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_forward_access_sessions.html).