Use when working with Aws Pricing — aWS pricing helper for cost queries. ALWAYS use get_aws_cost script for pricing questions. Use when: - User asks about AWS resource costs or pricing - User wants to compare pricing across regions - User needs spot, on-demand, or reserved pricing info Triggers: aws pricing, aws cost, how much does, ec2 price, rds cost, s3 pricing.
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
MANDATORY RULE: Always answer pricing questions with the get_aws_cost helper. NEVER call external search tools or guess prices.
The helper script get_pricing_aws.sh lives in the sandbox skills directory.
You must source it before use:
source ./_skills/connections/aws/aws-pricing/scripts/get_pricing_aws.sh
Run get_aws_cost without stderr redirection or grep filtering so the agent receives the raw response.
If multiple pricing lookups are required, place every call in a single Bash script (one script per task).
source ./_skills/connections/aws/aws-pricing/scripts/get_pricing_aws.sh
get_aws_cost <resource> <region> [options]
| Category | Resources |
|---|---|
| EC2 | t3.micro, m5.large, g4dn.xlarge, c6i.large |
| RDS | db.t3.micro, db.r5.large |
| ElastiCache | cache.t3.micro, cache.r5.large |
| S3 | s3-standard, s3-ia, s3-glacier, s3-glacier-deep |
| Lambda | lambda-128mb, lambda-1gb, lambda-3gb |
| DynamoDB | dynamodb-ondemand, dynamodb-provisioned |
| EFS | efs-standard, efs-ia |
| EBS | gp3-100gb, io2-500gb, st1-1tb |
| CloudFront | cloudfront-standard |
| API Gateway | apigateway-rest, apigateway-http |
| SQS | sqs-standard, sqs-fifo |
| SNS | sns-standard |
| Route53 | route53-hosted-zone, route53-query |
| ALB | alb-standard |
| NAT Gateway | natgw-standard |
| VPC Endpoints | vpce-gateway, vpce-interface |
resource: Auto-detected from the naming pattern aboveregion: AWS location string (e.g., "Asia Pacific (Singapore)", "US East (N. Virginia)")options: --spot (include spot pricing), --detailed (verbose output), --no-reserved (skip reserved pricing)get_aws_cost t3.micro "US East (N. Virginia)" --spot
get_aws_cost db.t3.micro "Asia Pacific (Singapore)"
get_aws_cost s3-standard "US East (N. Virginia)"
get_aws_cost lambda-1gb "US East (N. Virginia)"
get_aws_cost cloudfront-standard "US East (N. Virginia)"
get_aws_cost apigateway-rest "US East (N. Virginia)"
get_aws_cost sqs-standard "US East (N. Virginia)"
Human-readable pricing data with service details, region, specs, on-demand, reserved, and spot pricing where available. If a resource is unsupported, the helper prints guidance for querying the AWS Pricing API manually.
Present results as a structured report:
Aws Pricing Report
══════════════════
Resources discovered: [count]
Resource Status Key Metric Issues
──────────────────────────────────────────────
[name] [ok/warn] [value] [findings]
Summary: [total] resources | [ok] healthy | [warn] warnings | [crit] critical
Action Items: [list of prioritized findings]
Target ≤50 lines of output. Use tables for multi-resource comparisons.
--help output.| Shortcut | Counter | Why |
|---|---|---|
| "I'll skip discovery and check known resources" | Always run Phase 1 discovery first | Resource names change, new resources appear — assumed names cause errors |
| "The user only asked for a quick check" | Follow the full discovery → analysis flow | Quick checks miss critical issues; structured analysis catches silent failures |
| "Default configuration is probably fine" | Audit configuration explicitly | Defaults often leave logging, security, and optimization features disabled |
| "Metrics aren't needed for this" | Always check relevant metrics when available | API/CLI responses show current state; metrics reveal trends and intermittent issues |
| "I don't have access to that" | Try the command and report the actual error | Assumed permission failures prevent useful investigation; actual errors are informative |
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Cloudflare GraphQL Analytics for zone traffic, firewall events, Workers metrics, and schema exploration. Use when querying Cloudflare analytics data or exploring the GraphQL API.
The English summary is being prepared. Showing the original description.
Use when working with Alloydb — google AlloyDB instance analysis, query insights, columnar engine optimization, maintenance windows, and cluster health.
The English summary is being prepared. Showing the original description.
Use when working with Aqua — aqua Security platform analysis. Covers container runtime protection, image assurance policies, compliance frameworks, vulnerability management, workload protection, and registry scanning. Use when analyzing container security posture, reviewing image compliance, investigating runtime alerts, or auditing security policies.
The English summary is being prepared. Showing the original description.
Use when working with Bigquery — google BigQuery job analysis, slot utilization, cost analysis, dataset management, and query optimization.
The English summary is being prepared. Showing the original description.
Use when working with Cassandra — apache Cassandra keyspace analysis, compaction strategies, repair status, nodetool operations, and cluster health monitoring.
The English summary is being prepared. Showing the original description.
Use when working with Checkov — checkov infrastructure-as-code security scanning. Covers Terraform, CloudFormation, Kubernetes, and Dockerfile scanning, policy management, custom checks, compliance frameworks, and suppression management. Use when scanning IaC for security misconfigurations, evaluating compliance, managing custom policies, or reviewing scan results.
The English summary is being prepared. Showing the original description.