AWS IoT FleetWise will no longer be open to new customers as of April 30, 2026. Existing AWS IoT FleetWise customers can continue using the service. The [Guidance for Connected Mobility on AWS](https://aws.amazon.com/solutions/guidance/connected-mobility-on-aws/) provides guidance on how to develop and deploy modular services for connected mobility solutions that can be used to achieve equivalent capabilities as AWS IoT FleetWise.

# Identity and Access Management for AWS IoT FleetWise
<a name="security-iam"></a>





AWS Identity and Access Management (IAM) is an AWS service that helps an administrator securely control access to AWS resources. IAM administrators control who can be *authenticated* (signed in) and *authorized* (have permissions) to use AWS IoT FleetWise resources. IAM is an AWS service that you can use with no additional charge.

**Topics**
+ [Audience](#security_iam_audience)
+ [Authenticating with identities](#security_iam_authentication)
+ [Managing access using policies](#security_iam_access-manage)
+ [How AWS IoT FleetWise works with IAM](security_iam_service-with-iam.md)
+ [Identity-based policy examples for AWS IoT FleetWise](security_iam_id-based-policy-examples.md)
+ [Troubleshooting AWS IoT FleetWise identity and access](security_iam_troubleshoot.md)
+ [AWS IoT FleetWise API actions and resources reference](api-permissions-reference.md)

## Audience
<a name="security_iam_audience"></a>

How you use AWS Identity and Access Management (IAM) differs based on your role:
+ **Service user** - request permissions from your administrator if you cannot access features (see [Troubleshooting AWS IoT FleetWise identity and access](security_iam_troubleshoot.md))
+ **Service administrator** - determine user access and submit permission requests (see [How AWS IoT FleetWise works with IAM](security_iam_service-with-iam.md))
+ **IAM administrator** - write policies to manage access (see [Identity-based policy examples for AWS IoT FleetWise](security_iam_id-based-policy-examples.md))

## Authenticating with identities
<a name="security_iam_authentication"></a>

Authentication is how you sign in to AWS using your identity credentials. You must be authenticated as the AWS account root user, an IAM user, or by assuming an IAM role.

You can sign in as a federated identity using credentials from an identity source like AWS IAM Identity Center (IAM Identity Center), single sign-on authentication, or Google/Facebook credentials. For more information about signing in, see [How to sign in to your AWS account](https://docs.aws.amazon.com/signin/latest/userguide/how-to-sign-in.html) in the *AWS Sign-In User Guide*.

For programmatic access, AWS provides an SDK and CLI to cryptographically sign requests. For more information, see [AWS Signature Version 4 for API requests](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv.html) in the *IAM User Guide*.

### AWS account root user
<a name="security_iam_authentication-rootuser"></a>

 When you create an AWS account, you begin with one sign-in identity called the AWS account *root user* that has complete access to all AWS services and resources. We strongly recommend that you don't use the root user for everyday tasks. For tasks that require root user credentials, see [Tasks that require root user credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html#root-user-tasks) in the *IAM User Guide*. 

### Federated identity
<a name="security_iam_authentication-federated"></a>

As a best practice, require human users to use federation with an identity provider to access AWS services using temporary credentials.

A *federated identity* is a user from your enterprise directory, web identity provider, or Directory Service that accesses AWS services using credentials from an identity source. Federated identities assume roles that provide temporary credentials.

For centralized access management, we recommend AWS IAM Identity Center. For more information, see [What is IAM Identity Center?](https://docs.aws.amazon.com/singlesignon/latest/userguide/what-is.html) in the *AWS IAM Identity Center User Guide*.

### IAM users and groups
<a name="security_iam_authentication-iamuser"></a>

An *[IAM user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users.html)* is an identity with specific permissions for a single person or application. We recommend using temporary credentials instead of IAM users with long-term credentials. For more information, see [Require human users to use federation with an identity provider to access AWS using temporary credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#bp-users-federation-idp) in the *IAM User Guide*.

An [https://docs.aws.amazon.com/IAM/latest/UserGuide/id_groups.html](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_groups.html) specifies a collection of IAM users and makes permissions easier to manage for large sets of users. For more information, see [Use cases for IAM users](https://docs.aws.amazon.com/IAM/latest/UserGuide/gs-identities-iam-users.html) in the *IAM User Guide*.

### IAM roles
<a name="security_iam_authentication-iamrole"></a>

An *[IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html)* is an identity with specific permissions that provides temporary credentials. You can assume a role by [switching from a user to an IAM role (console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-console.html) or by calling an AWS CLI or AWS API operation. For more information, see [Methods to assume a role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_manage-assume.html) in the *IAM User Guide*.

IAM roles are useful for federated user access, temporary IAM user permissions, cross-account access, cross-service access, and applications running on Amazon EC2. For more information, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*.

## Managing access using policies
<a name="security_iam_access-manage"></a>

You control access in AWS by creating policies and attaching them to AWS identities or resources. A policy defines permissions when associated with an identity or resource. AWS evaluates these policies when a principal makes a request. Most policies are stored in AWS as JSON documents. For more information about JSON policy documents, see [Overview of JSON policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#access_policies-json) in the *IAM User Guide*.

Using policies, administrators specify who has access to what by defining which **principal** can perform **actions** on what **resources**, and under what **conditions**.

By default, users and roles have no permissions. An IAM administrator creates IAM policies and adds them to roles, which users can then assume. IAM policies define permissions regardless of the method used to perform the operation.

### Identity-based policies
<a name="security_iam_access-manage-id-based-policies"></a>

Identity-based policies are JSON permissions policy documents that you attach to an identity (user, group, or role). These policies control what actions identities 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](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) in the *IAM User Guide*.

Identity-based policies can be *inline policies* (embedded directly into a single identity) or *managed policies* (standalone policies attached to multiple identities). To learn how to choose between managed and inline policies, see [Choose between managed policies and inline policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-choosing-managed-or-inline.html) in the *IAM User Guide*.

### Resource-based policies
<a name="security_iam_access-manage-resource-based-policies"></a>

Resource-based policies are JSON policy documents that you attach to a resource. Examples include 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. You must [specify a principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html) in a resource-based policy.

Resource-based policies are inline policies that are located in that service. You can't use AWS managed policies from IAM in a resource-based policy.

### Other policy types
<a name="security_iam_access-manage-other-policies"></a>

AWS supports additional policy types that can set the maximum permissions granted by more common policy types:
+ **Permissions boundaries** – Set the maximum permissions that an identity-based policy can grant to an IAM entity. For more information, see [Permissions boundaries for IAM entities](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html) in the *IAM User Guide*.
+ **Service control policies (SCPs)** – Specify the maximum permissions for an organization or organizational unit in AWS Organizations. For more information, see [Service control policies](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html) in the *AWS Organizations User Guide*.
+ **Resource control policies (RCPs)** – Set the maximum available permissions for resources in your accounts. For more information, see [Resource control policies (RCPs)](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_rcps.html) in the *AWS Organizations User Guide*.
+ **Session policies** – Advanced policies passed as a parameter when creating a temporary session for a role or federated user. For more information, see [Session policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session) in the *IAM User Guide*.

### Multiple policy types
<a name="security_iam_access-manage-multiple-policies"></a>

When multiple types of policies apply to a request, the resulting permissions are more complicated to understand. To learn how AWS determines whether to allow a request when multiple policy types are involved, see [Policy evaluation logic](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_evaluation-logic.html) in the *IAM User Guide*.

# How AWS IoT FleetWise works with IAM
<a name="security_iam_service-with-iam"></a>

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






**IAM features you can use with AWS IoT FleetWise**  

| IAM feature | AWS IoT FleetWise support | 
| --- | --- | 
|  [Identity-based policies](#security_iam_service-with-iam-id-based-policies)  |   Yes  | 
|  [Resource-based policies](#security_iam_service-with-iam-resource-based-policies)  |   No   | 
|  [Policy actions](#security_iam_service-with-iam-id-based-policies-actions)  |   Yes  | 
|  [Policy resources](#security_iam_service-with-iam-id-based-policies-resources)  |   Yes  | 
|  [Policy condition keys](#security_iam_service-with-iam-id-based-policies-conditionkeys)  |   Yes  | 
|  [ACLs](#security_iam_service-with-iam-acls)  |   No   | 
|  [ABAC (tags in policies)](#security_iam_service-with-iam-tags)  |   Partial  | 
|  [Temporary credentials](#security_iam_service-with-iam-roles-tempcreds)  |   Yes  | 
|  [Principal permissions](#security_iam_service-with-iam-principal-permissions)  |   Yes  | 
|  [Service roles](#security_iam_service-with-iam-roles-service)  |   No   | 
|  [Service-linked roles](#security_iam_service-with-iam-roles-service-linked)  |   No   | 

To get a high-level view of how AWS IoT FleetWise and other AWS services work with most IAM features, 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*.

## Identity-based policies for AWS IoT FleetWise
<a name="security_iam_service-with-iam-id-based-policies"></a>

**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](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.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*.

### Identity-based policy examples for AWS IoT FleetWise
<a name="security_iam_service-with-iam-id-based-policies-examples"></a>



To view examples of AWS IoT FleetWise identity-based policies, see [Identity-based policy examples for AWS IoT FleetWise](security_iam_id-based-policy-examples.md).

## Resource-based policies within AWS IoT FleetWise
<a name="security_iam_service-with-iam-resource-based-policies"></a>

**Supports resource-based policies:** No 

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](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html) 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](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*.

## Policy actions for AWS IoT FleetWise
<a name="security_iam_service-with-iam-id-based-policies-actions"></a>

**Supports policy actions:** 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 `Action` element of a JSON policy describes the actions that you can use to allow or deny access in a policy. Include actions in a policy to grant permissions to perform the associated operation.



To see a list of AWS IoT FleetWise actions, see [Actions Defined by AWS IoT FleetWise ](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awskeymanagementservice.html#awskeymanagementservice-actions-as-permissions) in the *Service Authorization Reference*.

Policy actions in AWS IoT FleetWise use the following prefix before the action:

```
iotfleetwise
```

To specify multiple actions in a single statement, separate them with commas.

```
"Action": [
      "iotfleetwise:action1",
      "iotfleetwise:action2"
]
```





You can specify multiple actions using wildcards (\$1). For example, to specify all actions that begin with the word `List`, include the following action:

```
"Action": "iotfleetwise:List*"
```

To view examples of AWS IoT FleetWise identity-based policies, see [Identity-based policy examples for AWS IoT FleetWise](security_iam_id-based-policy-examples.md).

## Policy resources for AWS IoT FleetWise
<a name="security_iam_service-with-iam-id-based-policies-resources"></a>

**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)](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference-arns.html). For actions that don't support resource-level permissions, use a wildcard (\$1) to indicate that the statement applies to all resources.

```
"Resource": "*"
```

To see a list of AWS IoT FleetWise resource types and their ARNs, see [Resources Defined by AWS IoT FleetWise ](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awskeymanagementservice.html#awskeymanagementservice-resources-for-iam-policies) in the *Service Authorization Reference*. To learn with which actions you can specify the ARN of each resource, see [Actions Defined by AWS IoT FleetWise ](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awskeymanagementservice.html#awskeymanagementservice-actions-as-permissions).





To view examples of AWS IoT FleetWise identity-based policies, see [Identity-based policy examples for AWS IoT FleetWise](security_iam_id-based-policy-examples.md).

## Policy condition keys for AWS IoT FleetWise
<a name="security_iam_service-with-iam-id-based-policies-conditionkeys"></a>

**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](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*.

To see a list of AWS IoT FleetWise condition keys, see [Condition Keys for AWS IoT FleetWise ](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awskeymanagementservice.html#awskeymanagementservice-policy-keys) in the *Service Authorization Reference*. To learn with which actions and resources you can use a condition key, see [Actions Defined by AWS IoT FleetWise ](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awskeymanagementservice.html#awskeymanagementservice-actions-as-permissions).

To view examples of AWS IoT FleetWise identity-based policies, see [Identity-based policy examples for AWS IoT FleetWise](security_iam_id-based-policy-examples.md).

## Access control lists (ACLs) in AWS IoT FleetWise
<a name="security_iam_service-with-iam-acls"></a>

**Supports ACLs:** No 

Access control lists (ACLs) control which principals (account members, users, or roles) have permissions to access a resource. ACLs are similar to resource-based policies, although they do not use the JSON policy document format.

## Attribute-based access control (ABAC) with AWS IoT FleetWise
<a name="security_iam_service-with-iam-tags"></a>

**Supports ABAC (tags in policies):** Partial

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.

To control access based on tags, you provide tag information in the [condition element](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) of a policy using the `aws:ResourceTag/key-name`, `aws:RequestTag/key-name`, or `aws:TagKeys` condition keys.

If a service supports all three condition keys for every resource type, then the value is **Yes** for the service. If a service supports all three condition keys for only some resource types, then the value is **Partial**.

For more information about ABAC, see [Define permissions with ABAC authorization](https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction_attribute-based-access-control.html) in the *IAM User Guide*. To view a tutorial with steps for setting up ABAC, see [Use attribute-based access control (ABAC)](https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_attribute-based-access-control.html) in the *IAM User Guide*.

**Note**  
AWS IoT FleetWise only supports `iam:PassRole`, which is required for the `CreateCampaign` API operation.

## Using Temporary credentials with AWS IoT FleetWise
<a name="security_iam_service-with-iam-roles-tempcreds"></a>

**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](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*.

## Cross-service principal permissions for AWS IoT FleetWise
<a name="security_iam_service-with-iam-principal-permissions"></a>

**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](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_forward_access_sessions.html). 

## Service roles for AWS IoT FleetWise
<a name="security_iam_service-with-iam-roles-service"></a>

**Supports service roles:** No 

 A service role is an [IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html) 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](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-service.html) in the *IAM User Guide*. 

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

## Service-linked roles for AWS IoT FleetWise
<a name="security_iam_service-with-iam-roles-service-linked"></a>

**Supports service-linked roles:** No 

 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](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html). Find a service in the table that includes a `Yes` in the **Service-linked role** column. Choose the **Yes** link to view the service-linked role documentation for that service.

# Using service-linked roles for AWS IoT FleetWise
<a name="using-service-linked-roles"></a>

AWS IoT FleetWise uses AWS Identity and Access Management (IAM)[ service-linked roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-service-linked-role). A service-linked role is a unique type of IAM role that is linked directly to AWS IoT FleetWise. Service-linked roles are predefined by AWS IoT FleetWise and include the permissions that AWS IoT FleetWise needs to send metrics to Amazon CloudWatch. For more information, see [Monitor AWS IoT FleetWise with Amazon CloudWatch](monitoring-cloudwatch.md).

A service-linked role makes setting up AWS IoT FleetWise quicker because you don’t have to manually add the necessary permissions. AWS IoT FleetWise defines the permissions of its service-linked roles, and unless defined otherwise, only AWS IoT FleetWise can assume its roles. The defined permissions include the trust policy and the permissions policy. This permissions policy can't be attached to any other IAM entity.

You can delete a service-linked role only after first deleting their related resources. This protects your AWS IoT FleetWise resources because you can't inadvertently remove permission to access the resources.

For information about other services that support service-linked roles, see [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html), and look for the services that have **Yes** in the **Service-linked roles** column. To view the service-linked role documentation for that service, choose a **Yes** with a link.

## Service-linked role permissions for AWS IoT FleetWise
<a name="service-linked-role-permissions"></a>

AWS IoT FleetWise uses the service-linked role named **AWSServiceRoleForIoTFleetWise** – An AWS managed policy that is used for all out-of-the-box permissions for AWS IoT FleetWise.

The AWSServiceRoleForIoTFleetWise service-linked role trusts the following services to assume the role:
+ `IoTFleetWise`

The role permissions policy named [AWSIoTFleetwiseServiceRolePolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSIoTFleetwiseServiceRolePolicy.html) allows AWS IoT FleetWise to complete the following actions on the specified resources:
+ Action: `cloudwatch:PutMetricData` on resource: `*`

For information about changes to this policy, see [AWSIoTFleetwiseServiceRolePolicy policy updates](https://docs.aws.amazon.com/iot-fleetwise/latest/developerguide/managed-policy-updates.html).

The service-linked role has permissions to publish metrics to the following CloudWatch namespaces:
+ `AWS/IoTFleetWise` – For service-specific metrics
+ `AWS/Usage` – For usage metrics

You must configure permissions to allow an IAM entity (such as a user, group, or role) to create, edit, or delete a service-linked role. For more information, see [Service-linked role permissions](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#service-linked-role-permissions) in the *IAM User Guide*.

## Creating a service-linked role for AWS IoT FleetWise
<a name="create-service-linked-role"></a>

You don't need to manually create a service-linked role. When you register an account in the AWS IoT FleetWise console, the AWS CLI, or the AWS API, AWS IoT FleetWise creates the service-linked role for you. For more information, see [Configure your AWS IoT FleetWise settings](configure-settings.md).

### Creating a service-linked role in AWS IoT FleetWise (console)
<a name="create-service-linked-role-service-console"></a>

You don't need to manually create a service-linked role. When you register an account in the AWS IoT FleetWise console, the AWS CLI, or the AWS API, AWS IoT FleetWise creates the service-linked role for you.

### Editing a service-linked role for AWS IoT FleetWise
<a name="edit-service-linked-role"></a>

You can't edit the AWSServiceRoleForIoTFleetWise service-linked role in AWS IoT FleetWise. Because various entities might reference any service-linked role you create, you can't change the name of the role. However, you can edit the description of the role by using IAM. For more information, see [Editing a service-linked role](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#edit-service-linked-role) in the *IAM User Guide*.

### Cleaning up a service-linked role
<a name="service-linked-role-review-before-delete"></a>

Before you can use IAM to delete a service-linked role, you must first delete any resources used by the role.

**Note**  
If AWS IoT FleetWise is using the role when you try to delete the resources, then the deletion might fail. If that happens, wait for a few minutes and try the operation again. To learn how to delete the service-linked-role through the console, AWS CLI, or AWS API, see [Using service-linked roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html) in the *IAM User Guide*.

If you delete this service-linked role, and then need to create it again, you can register an account with AWS IoT FleetWise. AWS IoT FleetWise then creates the service-linked role for you again.

# Identity-based policy examples for AWS IoT FleetWise
<a name="security_iam_id-based-policy-examples"></a>

By default, users and roles don't have permission to create or modify AWS IoT FleetWise resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.

To learn how to create an IAM identity-based policy by using these example JSON policy documents, see [Create IAM policies (console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create-console.html) in the *IAM User Guide*.

For details about actions and resource types defined by AWS IoT FleetWise, including the format of the ARNs for each of the resource types, see [Actions, Resources, and Condition Keys for AWS IoT FleetWise ](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_awskeymanagementservice.html) in the *Service Authorization Reference*.

**Topics**
+ [Policy best practices](#security_iam_service-with-iam-policy-best-practices)
+ [Using the AWS IoT FleetWise console](#security_iam_id-based-policy-examples-console)
+ [Allow users to view their own permissions](#security_iam_id-based-policy-examples-view-own-permissions)
+ [Access resources in Amazon Timestream](#security_iam_id-based-policy-examples-register-account)

## Policy best practices
<a name="security_iam_service-with-iam-policy-best-practices"></a>

Identity-based policies determine whether someone can create, access, or delete AWS IoT FleetWise resources in your account. These actions can incur costs for your AWS account. When you create or edit identity-based policies, follow these guidelines and recommendations:
+ **Get started with AWS managed policies and move toward least-privilege permissions** – To get started granting permissions to your users and workloads, use the *AWS managed policies* that grant permissions for many common use cases. They are available in your AWS account. We recommend that you reduce permissions further by defining AWS customer managed policies that are specific to your use cases. For more information, see [AWS managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#aws-managed-policies) or [AWS managed policies for job functions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions.html) in the *IAM User Guide*.
+ **Apply least-privilege permissions** – When you set permissions with IAM policies, grant only the permissions required to perform a task. You do this by defining the actions that can be taken on specific resources under specific conditions, also known as *least-privilege permissions*. For more information about using IAM to apply permissions, see [ Policies and permissions in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html) in the *IAM User Guide*.
+ **Use conditions in IAM policies to further restrict access** – You can add a condition to your policies to limit access to actions and resources. For example, you can write a policy condition to specify that all requests must be sent using SSL. You can also use conditions to grant access to service actions if they are used through a specific AWS service, such as CloudFormation. For more information, see [ IAM JSON policy elements: Condition](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) in the *IAM User Guide*.
+ **Use IAM Access Analyzer to validate your IAM policies to ensure secure and functional permissions** – IAM Access Analyzer validates new and existing policies so that the policies adhere to the IAM policy language (JSON) and IAM best practices. IAM Access Analyzer provides more than 100 policy checks and actionable recommendations to help you author secure and functional policies. For more information, see [Validate policies with IAM Access Analyzer](https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-policy-validation.html) in the *IAM User Guide*.
+ **Require multi-factor authentication (MFA)** – If you have a scenario that requires IAM users or a root user in your AWS account, turn on MFA for additional security. To require MFA when API operations are called, add MFA conditions to your policies. For more information, see [ Secure API access with MFA](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa_configure-api-require.html) in the *IAM User Guide*.

For more information about best practices in IAM, see [Security best practices in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html) in the *IAM User Guide*.

## Using the AWS IoT FleetWise console
<a name="security_iam_id-based-policy-examples-console"></a>

To access the AWS IoT FleetWise console, you must have a minimum set of permissions. These permissions must allow you to list and view details about the AWS IoT FleetWise resources in your AWS account. If you create an identity-based policy that is more restrictive than the minimum required permissions, the console won't function as intended for entities (users or roles) with that policy.

You don't need to allow minimum console permissions for users that are making calls only to the AWS CLI or the AWS API. Instead, allow access to only the actions that match the API operation that they're trying to perform.

To ensure that users and roles can still use the AWS IoT FleetWise console, also attach the AWS IoT FleetWise `ConsoleAccess` or `ReadOnly` AWS managed policy to the entities. For more information, see [Adding permissions to a user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_change-permissions.html#users_change_permissions-add-console) in the *IAM User Guide*.

## Allow users to view their own permissions
<a name="security_iam_id-based-policy-examples-view-own-permissions"></a>

This example shows how you might create a policy that allows IAM users to view the inline and managed policies that are attached to their user identity. This policy includes permissions to complete this action on the console or programmatically using the AWS CLI or AWS API.

```
{
    "Version": "2012-10-17",		 	 	 
    "Statement": [
        {
            "Sid": "ViewOwnUserInfo",
            "Effect": "Allow",
            "Action": [
                "iam:GetUserPolicy",
                "iam:ListGroupsForUser",
                "iam:ListAttachedUserPolicies",
                "iam:ListUserPolicies",
                "iam:GetUser"
            ],
            "Resource": ["arn:aws:iam::*:user/${aws:username}"]
        },
        {
            "Sid": "NavigateInConsole",
            "Effect": "Allow",
            "Action": [
                "iam:GetGroupPolicy",
                "iam:GetPolicyVersion",
                "iam:GetPolicy",
                "iam:ListAttachedGroupPolicies",
                "iam:ListGroupPolicies",
                "iam:ListPolicyVersions",
                "iam:ListPolicies",
                "iam:ListUsers"
            ],
            "Resource": "*"
        }
    ]
}
```

## Access resources in Amazon Timestream
<a name="security_iam_id-based-policy-examples-register-account"></a>

Before using AWS IoT FleetWise, you must register your AWS account, IAM, and Amazon Timestream resources to grant AWS IoT FleetWise permission to send vehicle data to AWS Cloud on your behalf. To register, you need:
+ An Amazon Timestream database.
+ A table created in the specified Amazon Timestream database. 
+ An IAM role that allows AWS IoT FleetWise to send data to Amazon Timestream. 

For more information, including procedures and example policies, see [Configure your AWS IoT FleetWise settings](configure-settings.md).







# Troubleshooting AWS IoT FleetWise identity and access
<a name="security_iam_troubleshoot"></a>

Use the following information to help you diagnose and fix common issues that you might encounter when working with AWS IoT FleetWise and IAM.

**Topics**
+ [I am not authorized to perform an action in AWS IoT FleetWise](#security_iam_troubleshoot-no-permissions)
+ [I am not authorized to perform iam:PassRole](#security_iam_troubleshoot-passrole)
+ [I want to allow people outside of my AWS account to access my AWS IoT FleetWise resources](#security_iam_troubleshoot-cross-account-access)

## I am not authorized to perform an action in AWS IoT FleetWise
<a name="security_iam_troubleshoot-no-permissions"></a>

If the AWS Management Console tells you that you're not authorized to perform an action, then you must contact your administrator for assistance. Your administrator is the person that provided you with your sign-in credentials.

The following example error occurs when the `mateojackson` IAM user tries to use the console to view details about a fictional `myVehicle` resource but does not have the `iotfleetwise:GetVehicleStatus` permissions.

```
User: arn:aws:iam::123456789012:user/mateojackson is not authorized to perform: iotfleetwise:GetVehicleStatus on resource: myVehicle
```

In this case, Mateo asks his administrator to update his policies to allow him to access the `myVehicle` resource using the `iotfleetwise:GetVehicleStatus` action.

## I am not authorized to perform iam:PassRole
<a name="security_iam_troubleshoot-passrole"></a>

If you receive an error that you're not authorized to perform the `iam:PassRole` action, your policies must be updated to allow you to pass a role to AWS IoT FleetWise.

Some AWS services allow you to pass an existing role to that service instead of creating a new service role or service-linked role. To do this, you must have permissions to pass the role to the service.

The following example error occurs when an IAM user named `marymajor` tries to use the console to perform an action in AWS IoT FleetWise. However, the action requires the service to have permissions that are granted by a service role. Mary does not have permissions to pass the role to the service.

```
User: arn:aws:iam::123456789012:user/marymajor is not authorized to perform: iam:PassRole
```

In this case, Mary's policies must be updated to allow her to perform the `iam:PassRole` action.

If you need help, contact your AWS administrator. Your administrator is the person who provided you with your sign-in credentials.

## I want to allow people outside of my AWS account to access my AWS IoT FleetWise resources
<a name="security_iam_troubleshoot-cross-account-access"></a>

You can create a role that users in other accounts or people outside of your organization can use to access your resources. You can specify who is trusted to assume the role. For services that support resource-based policies or access control lists (ACLs), you can use those policies to grant people access to your resources.

To learn more, consult the following:
+ To learn whether AWS IoT FleetWise supports these features, see [How AWS IoT FleetWise works with IAM](security_iam_service-with-iam.md).
+ To learn how to provide access to your resources across AWS accounts that you own, see [Providing access to an IAM user in another AWS account that you own](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_aws-accounts.html) in the *IAM User Guide*.
+ To learn how to provide access to your resources to third-party AWS accounts, see [Providing access to AWS accounts owned by third parties](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html) in the *IAM User Guide*.
+ To learn how to provide access through identity federation, see [Providing access to externally authenticated users (identity federation)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_federated-users.html) in the *IAM User Guide*.
+ To learn the difference between using roles and resource-based policies for cross-account access, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*.

# AWS IoT FleetWise API actions and resources reference
<a name="api-permissions-reference"></a>

When you're [Managing access using policies](https://docs.aws.amazon.com/iot-fleetwise/latest/developerguide/security-iam.html#security_iam_access-manage) for an IAM identity, you can use the following table as a reference. The table lists each AWS IoT FleetWise API, the corresponding actions for which you can grant permissions to perform the action, and the AWS resource for which you can grant the permissions.

Specify the actions in the policy's `Action` field, and the resource value in the policy's `Resource` field. To specify an action, use the `iotfleetwise:` prefix followed by the action name. For example, `iotfleetwise:CreateSignalCatalog`.

Currently, AWS IoT FleetWise supports the following [Actions, resources, and condition keys](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awsiotfleetwise.html).

Use the scroll bar to see the rest of the table.


| AWS IoT FleetWise actions | Required permissions | Resources | 
| --- | --- | --- | 
| AssociateVehicleFleet | iotfleetwise:AssociateVehicleFleet |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:fleet/*fleet-id* arn:*partition*:iotfleetwise:*region*:*account\$1id*:vehicle/*vehicle-id*  | 
| CreateCampaign | iotfleetwise:CreateCampaign |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:campaign/*campaign-name* arn:*partition*:iotfleetwise:*region*:*account\$1id*:signal-catalog/*name* arn:*partition*:iotfleetwise:*region*:*account\$1id*:vehicle/*vehicle-id* arn:*partition*:iotfleetwise:*region*:*account\$1id*:fleet/*fleet-id*  | 
| CreateDecoderManifest | iotfleetwise:CreateDecoderManifest |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:decoder-manifest/*name* arn:*partition*:iotfleetwise:*region*:*account\$1id*:model-manifest/*name*  | 
| CreateFleet | iotfleetwise:CreateFleet |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:fleet/*fleet-id* arn:*partition*:iotfleetwise:*region*:*account\$1id*:signal-catalog/*name*  | 
| CreateModelManifest | iotfleetwise:CreateModelManifest |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:model-manifest/*name* arn:*partition*:iotfleetwise:*region*:*account\$1id*:signal-catalog/*name*  | 
| CreateSignalCatalog | iotfleetwise:CreateSignalCatalog |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:signal-catalog/*name*  | 
| CreateStateTemplate | iotfleetwise:CreateStateTemplate |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:state-template/*state-template-id* arn:*partition*:iotfleetwise:*region*:*account\$1id*:signal-catalog/*name*  | 
| CreateVehicle | iotfleetwise:CreateVehicle |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:vehicle/*vehicle-id* arn:*partition*:iotfleetwise:*region*:*account\$1id*:model-manifest/*name* arn:*partition*:iotfleetwise:*region*:*account\$1id*:decoder-manifest/*name*  | 
| BatchCreateVehicle | iotfleetwise:CreateVehicle |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:vehicle/*vehicle-id* arn:*partition*:iotfleetwise:*region*:*account\$1id*:model-manifest/*name* arn:*partition*:iotfleetwise:*region*:*account\$1id*:decoder-manifest/*name*  | 
| DeleteCampaign | iotfleetwise:DeleteCampaign |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:campaign/*campaign-name*  | 
| DeleteDecoderManifest | iotfleetwise:DeleteDecoderManifest |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:decoder-manifest/*name*  | 
| DeleteFleet | iotfleetwise:DeleteFleet |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:fleet/*fleet-id*  | 
| DeleteModelManifest | iotfleetwise:DeleteModelManifest |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:decoder-manifest/*name*  | 
| DeleteSignalCatalog | iotfleetwise:DeleteSignalCatalog |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:signal-catalog/*name*  | 
| DeleteStateTemplate | iotfleetwise:DeleteStateTemplate |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:state-template/*state-template-id*  | 
| DeleteVehicle | iotfleetwise:DeleteVehicle |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:vehicle/*vehicle-id*  | 
| DisassociateVehicleFleet | iotfleetwise:DisassociateVehicleFleet |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:vehicle/*vehicle-id* arn:*partition*:iotfleetwise:*region*:*account\$1id*:fleet/*fleet-id*  | 
| GetCampaign | iotfleetwise:GetCampaign |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:campaign/*campaign-name*  | 
| GetDecoderManifest | iotfleetwise:GetDecoderManifest |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:decoder-manifest/*name*  | 
| GetEncryptionConfiguration | iotfleetwise:GetEncryptionConfiguration |  | 
| GetFleet | iotfleetwise:GetFleet |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:fleet/*fleet-id*  | 
| GetLoggingOptions | iotfleetwise:GetLoggingOptions |  | 
| GetModelManifest | iotfleetwise:GetModelManifest |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:model-manifest/*name*  | 
| GetRegisterAccountStatus | iotfleetwise:GetRegisterAccountStatus |  | 
| GetSignalCatalog | iotfleetwise:GetSignalCatalog |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:signal-catalog/*name*  | 
| GetStateTemplate | iotfleetwise:GetStateTemplate |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:state-template/*state-template-id*  | 
| GetVehicle | iotfleetwise:GetVehicle |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:vehicle/*vehicle-id*  | 
| GetVehicleStatus | iotfleetwise:GetVehicleStatus |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:vehicle/*vehicle-id*  | 
| ImportDecoderManifest | iotfleetwise:ImportDecoderManifest |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:decoder-manifest/*name*  | 
| ImportSignalCatalog | iotfleetwise:ImportSignalCatalog |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:signal-catalog/*name*  | 
| ListCampaigns | iotfleetwise:ListCampaigns |  | 
| ListDecoderManifestNetworkInterfaces | iotfleetwise:ListDecoderManifestNetworkInterfaces |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:decoder-manifest/*name*  | 
| ListDecoderManifests | iotfleetwise:ListDecoderManifests |  | 
| ListDecoderManifestSignals | iotfleetwise:ListDecoderManifestSignals |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:decoder-manifest/*name*  | 
| ListFleets | iotfleetwise:ListFleets |  | 
| ListFleetsForVehicle | iotfleetwise:ListFleetsForVehicle |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:vehicle/*vehicle-id*  | 
| ListModelManifestNodes | iotfleetwise:ListModelManifestNodes |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:model-manifest/*name*  | 
| ListModelManifests | iotfleetwise:ListModelManifests |  | 
| ListSignalCatalogNodes | iotfleetwise:ListSignalCatalogNodes |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:signal-catalog/*name*  | 
| ListSignalCatalogs | iotfleetwise:ListSignalCatalogs |  | 
| ListStateTemplates | iotfleetwise:ListStateTemplates |  | 
| ListVehicles | iotfleetwise:ListVehicles |  | 
| ListVehiclesInFleet | iotfleetwise:ListVehiclesInFleet |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:fleet/*fleet-id*  | 
| ListTagsForResource | iotfleetwise:ListTagsForResource |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:signal-catalog/*name* arn:*partition*:iotfleetwise:*region*:*account\$1id*:model-manifest/*name* arn:*partition*:iotfleetwise:*region*:*account\$1id*:decoder-manifest/*name* arn:*partition*:iotfleetwise:*region*:*account\$1id*:vehicle/*vehicle-id* arn:*partition*:iotfleetwise:*region*:*account\$1id*:fleet/*fleet-id* arn:*partition*:iotfleetwise:*region*:*account\$1id*:campaign/*campaign-name* arn:*partition*:iotfleetwise:*region*:*account\$1id*:state-template/*state-template-id*  | 
| PutEncryptionConfiguration | iotfleetwise:PutEncryptionConfiguration |  | 
| PutLoggingOptions | iotfleetwise:PutLoggingOptions |  | 
| RegisterAccount | iotfleetwise:RegisterAccount |  | 
| TagResource | iotfleetwise:TagResource |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:signal-catalog/*name* arn:*partition*:iotfleetwise:*region*:*account\$1id*:model-manifest/*name* arn:*partition*:iotfleetwise:*region*:*account\$1id*:decoder-manifest/*name* arn:*partition*:iotfleetwise:*region*:*account\$1id*:vehicle/*vehicle-id* arn:*partition*:iotfleetwise:*region*:*account\$1id*:fleet/*fleet-id* arn:*partition*:iotfleetwise:*region*:*account\$1id*:campaign/*campaign-name* arn:*partition*:iotfleetwise:*region*:*account\$1id*:state-template/*state-template-id*  | 
| UntagResource | iotfleetwise:UntagResource |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:signal-catalog/*name* arn:*partition*:iotfleetwise:*region*:*account\$1id*:model-manifest/*name* arn:*partition*:iotfleetwise:*region*:*account\$1id*:decoder-manifest/*name* arn:*partition*:iotfleetwise:*region*:*account\$1id*:vehicle/*vehicle-id* arn:*partition*:iotfleetwise:*region*:*account\$1id*:fleet/*fleet-id* arn:*partition*:iotfleetwise:*region*:*account\$1id*:campaign/*campaign-name* arn:*partition*:iotfleetwise:*region*:*account\$1id*:state-template/*state-template-id*  | 
| UpdateCampaign | iotfleetwise:UpdateCampaign |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:campaign/*campaign-name*  | 
| UpdateDecoderManifest | iotfleetwise:UpdateDecoderManifest |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:decoder-manifest/*name*  | 
| UpdateFleet | iotfleetwise:UpdateFleet |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:fleet/*fleet-id*  | 
| UpdateModelManifest | iotfleetwise:UpdateModelManifest |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:model-manifest/*name*  | 
| UpdateSignalCatalog | iotfleetwise:UpdateSignalCatalog |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:signal-catalog/*name*  | 
| UpdateStateTemplate | iotfleetwise:UpdateStateTemplate |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:state-template/*state-template-id*  | 
| UpdateVehicle | iotfleetwise:UpdateVehicle |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:vehicle/*vehicle-id* arn:*partition*:iotfleetwise:*region*:*account\$1id*:model-manifest/*name* arn:*partition*:iotfleetwise:*region*:*account\$1id*:decoder-manifest/*name*  | 
| BatchUpdateVehicle | iotfleetwise:UpdateVehicle |  arn:*partition*:iotfleetwise:*region*:*account\$1id*:vehicle/*vehicle-id* arn:*partition*:iotfleetwise:*region*:*account\$1id*:model-manifest/*name* arn:*partition*:iotfleetwise:*region*:*account\$1id*:decoder-manifest/*name*  |