How AWS Application Cost Profiler works with IAM

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

Application Cost Profiler identity-based policies

With IAM identity-based policies, you can specify allowed or denied actions and resources in addition to the conditions under which actions are allowed or denied. Application Cost Profiler supports specific actions. 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 Application Cost Profiler use the following prefix before the action: application-cost-profiler:. For example, to grant someone permission to view the details of your Application Cost Profiler report definition, you include the application-cost-profiler:GetReportDefinition action in their policy. Policy statements must include either an Action or NotAction element. Application Cost Profiler 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": [
      "application-cost-profiler:ListReportDefinitions",
      "application-cost-profiler:GetReportDefinition"

The following are the actions available in Application Cost Profiler. Each allows the API action of the same name. For more information about the Application Cost Profiler API, see AWS Application Cost Profiler API Reference.

• application-cost-profiler:ListReportDefinitions – Allows listing the report definition for your AWS account, if any.

• application-cost-profiler:GetReportDefinition – Allows getting the details of the report definition for your Application Cost Profiler report.

• application-cost-profiler:PutReportDefinition – Allows creating a new report definition.

• application-cost-profiler:UpdateReportDefinition – Allows updating a report definition.

• application-cost-profiler:DeleteReportDefinition – Allows deleting a report (only available through the Application Cost Profiler API).

• application-cost-profiler:ImportApplicationUsage – Allows requesting Application Cost Profiler import usage data from a specified Amazon S3 bucket.

Resources

Application Cost Profiler does not support specifying resource Amazon Resource Names (ARNs) in a policy.

Condition keys

Application Cost Profiler 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.

Examples

To view examples of Application Cost Profiler identity-based policies, see AWS Application Cost Profiler identity-based policy examples.

Application Cost Profiler resource-based policies

Application Cost Profiler does not support resource-based policies.

Authorization based on Application Cost Profiler tags

Application Cost Profiler does not support tagging resources or controlling access based on tags.

Application Cost Profiler IAM roles

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

Using temporary credentials with Application Cost Profiler

You can use temporary credentials to sign in with federation, 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.

Application Cost Profiler 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 administrator can view but not edit the permissions for service-linked roles.

Application Cost Profiler does not support service-linked roles.

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 administrator can change the permissions for this role. However, doing so might break the functionality of the service.

Application Cost Profiler does not support service roles.