Amazonaws APIs
148 APIs6,711 Endpoints16 Categories
Categories
API Catalog(8 of 148)
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.
6 endpointsAWS Budgets
AWS Budgets lets you plan and track service usage, service costs, and reservation utilisation across an AWS account or organisation. The API supports four budget types: cost budgets, usage budgets, RI utilisation budgets, and RI coverage budgets, each with thresholds that trigger notifications to subscribers when actual or forecasted spend crosses the limit. Budget actions extend this with automatic responses such as applying a restrictive IAM policy, stopping EC2 or RDS instances, or attaching a deny policy to a Service Control Policy when a budget is exceeded.
23 endpointsAWS Cost and Usage Report Service
Jentic publishes the only available OpenAPI specification for AWS Cost and Usage Report Service, keeping it validated and agent-ready. AWS Cost and Usage Report (CUR) Service programmatically manages report definitions that deliver detailed AWS billing line items - one row per resource per hour - to Amazon S3 in CSV or Parquet. The API has four operations: create, modify, list, and delete report definitions. Reports underpin enterprise billing, chargeback, and FinOps analytics in tools like Athena, QuickSight, and third-party platforms.
Connect Your Agent
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.