canonical: https://jentic.com/apis/amazonaws.com/aws-applicationcostprofiler

# AWS Application Cost Profiler

AWS Application Cost Profiler reports the cost of shared AWS resources broken down by tenant or application using customer-supplied usage data. It accepts uploaded usage records, joins them with billing data, and emits cost reports to S3 on a configurable schedule.

## For AI agents

Use the AWS Application Cost Profiler API to report shared-resource AWS costs by tenant or application on AWS, with 6 operations covering the full control-plane lifecycle.

## Scope

Does not handle billing payment, budget alerts, or tag-based cost allocation - use for tenant-level shared-resource cost reporting only.

## Capabilities

- Define cost reports that emit per-tenant or per-application cost breakdowns to an S3 bucket
- Import usage data files from S3 that map shared resource consumption to tenant identifiers
- Update report definitions to change schedule, format, or destination
- List existing report definitions in the account
- Delete a report definition when the workload no longer needs it

## Use cases

### Per-tenant cost reporting for a multi-tenant SaaS

Operate shared compute, storage, or database infrastructure across multiple tenants and produce per-tenant cost reports by uploading usage records that attribute resource consumption to tenant identifiers. Application Cost Profiler joins those records with AWS billing data and emits CSV reports to a chosen S3 bucket on a daily or monthly schedule. Initial setup is typically under a day.

Example prompt: Create a daily report definition named 'tenant-cost-daily' that writes to s3://billing-reports/tenant-daily/ and import the latest usage data file from s3://usage-uploads/2026-06/.

### Internal chargeback for shared platform teams

Charge internal product teams for their share of a centrally-run platform by uploading usage records keyed by team identifier. The resulting cost reports become the source of truth for monthly chargeback. This replaces ad-hoc cost spreadsheets with a managed, auditable pipeline. Reports refresh on the schedule defined in the report definition.

Example prompt: Create a monthly report definition called 'team-chargeback' configured for CSV format and import the previous month's team-keyed usage records.

### Automated usage-data ingestion pipeline

Land usage data files in an S3 bucket from upstream collectors, then call ImportApplicationUsage on each new file to register it for the next report run. Combined with EventBridge or Lambda triggers, this becomes a hands-off ingestion pipeline that produces fresh cost reports without manual operator intervention.

Example prompt: Call ImportApplicationUsage with the S3 location s3://usage-uploads/2026-06-01/usage.csv to register the latest day's records.

### AI agent producing tenant cost reports through Jentic

A finance operations agent can run the entire Application Cost Profiler workflow without direct AWS console access by calling its operations through Jentic. It registers report definitions, imports usage files, and lists report status using scoped credentials, so the agent never sees the underlying AWS access keys. This compresses month-end cost-reporting work to a single agent intent.

Example prompt: Search Jentic for 'report aws costs broken down by tenant', load the schemas for PutReportDefinition and ImportApplicationUsage, and execute them in sequence for the current month's data.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /reportDefinition | Create a new cost report definition |
| GET | /reportDefinition | List configured report definitions |
| GET | /reportDefinition/{reportId} | Get a single report definition |
| PUT | /reportDefinition/{reportId} | Update a report definition |
| DELETE | /reportDefinition/{reportId} | Delete a report definition |
| POST | /importApplicationUsage | Import a usage data file from S3 |

## Key resources

- **ReportDefinitions** — Configured cost reports describing schedule, format, and S3 destination
- **ApplicationUsage** — Customer-supplied usage records that map shared-resource consumption to tenants

## Why Jentic

- **Setup:** Wiring AWS Application Cost Profiler by hand means creating IAM credentials, choosing the right regional host from applicationcostprofiler.{region}.amazonaws.com, signing every request with AWS SigV4, and adding your own retry handling. Through Jentic you install once, import AWS Application Cost Profiler from the API Directory, store the AWS access key once, and your agent calls it.
- **Permission scoping:** AWS Application Cost Profiler puts the report id in the URL path (/reportDefinition/{reportId}), so a rule can pin your agent to one report definition: it can read and update that report and nothing else. You choose the operations it may call, so destructive ones like deleting a report definition are not included unless you add them.
- **Credential handling:** Your AWS access key for AWS Application Cost Profiler is stored once, encrypted, by your own Jentic One instance and signed with SigV4 at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'report AWS costs broken down by tenant' or 'import a usage data file from S3', and Jentic returns the matching AWS Application Cost Profiler operation with its input schema so the agent calls the right endpoint without browsing the AWS service reference.

## Related APIs

- **AWS Budgets** — AWS Budgets monitors total spend with alert thresholds rather than allocating cost across tenants
- **Cost Explorer** — Cost Explorer surfaces AWS-native cost dimensions like service and tag, not customer-supplied tenant identifiers
- **Backup** — AWS Backup is a common shared resource whose costs may need per-tenant attribution

## FAQ

### What authentication does the AWS Application Cost Profiler API use?

The AWS Application Cost Profiler API uses AWS Signature Version 4 (HMAC) request signing with IAM-issued credentials, the same scheme as every AWS service API. Jentic's your Jentic One instance stores those AWS credentials encrypted in the vault, generates short-lived signed requests at execution time, and never passes raw access keys into the agent's context.

### Can I create a daily tenant cost report with the AWS Application Cost Profiler API?

Yes - the AWS Application Cost Profiler API exposes 6 operations including the actions needed for that scenario. Use the operations listed in the key endpoints section as the starting point, then chain calls as needed for your workflow.

### What are the rate limits for the AWS Application Cost Profiler API?

AWS applies per-account, per-region request rate limits to the AWS Application Cost Profiler control plane. Specific limits are not encoded in the OpenAPI spec; consult the AWS service quotas console for the AWS Application Cost Profiler entry, and design retries with exponential backoff to absorb throttling responses.

### How do I report aws costs broken down by tenant through Jentic?

Run pip install jentic, then call client.search('report aws costs broken down by tenant') to discover the AWS Application Cost Profiler operations that match. Load the schema for the chosen operation with client.load(...) and execute it with client.execute(...). Jentic handles AWS request signing automatically against the credentials stored in your Jentic One instance.

### Is the AWS Application Cost Profiler API free to call?

AWS does not charge for control-plane API calls themselves on most AWS Application Cost Profiler operations, but the underlying resources you create or operate (fleets, queries, deployments, and so on) incur usage charges according to the AWS Application Cost Profiler pricing page. Refer to the AWS pricing page for the service to estimate cost.

### Which operations should an agent call first when working with the AWS Application Cost Profiler API?

For most workflows, agents should start by listing existing resources to understand the current state, then call the create or update operation that matches the intent. The endpoints listed under Key Endpoints in the catalog give a ranked starting set.

### Can I limit what my agent is allowed to do with the AWS Application Cost Profiler API?

Yes. Because you self-host Jentic One, your own rules decide which AWS Application Cost Profiler operations the agent may call and which AWS credentials it may use. Since the report id sits in the URL path (/reportDefinition/{reportId}), a rule can pin the agent to a single report definition so it can read and update that one report and nothing else. You choose the allowed operations, so destructive calls like deleting a report definition stay out of reach unless you add them.