jeremylongshore/tons-of-skills-marketplace / plugins/devops/auto-scaling-configurator/skills/configuring-auto-scaling-policies
configuring-auto-scaling-policies
VerifiedConfigure use when you need to work with auto-scaling. This skill provides auto-scaling configuration with comprehensive guidance and automation. Trigger with phrases like "configure auto-scaling", "set up elastic scaling", or "implement scaling".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.1 KB |
| assets/README.md | markdown | 369 B |
| assets/config_template.yaml | config | 3.2 KB |
| assets/example_aws_scaling_policy.json | config | 2.1 KB |
| assets/example_hpa.yaml | config | 2.3 KB |
| references/README.md | markdown | 68 B |
| scripts/README.md | markdown | 423 B |
| scripts/generate_config.pyexecutable | script | 3.6 KB |
assets/config_template.yaml
View on GitHub# Auto-Scaling Configuration Template
# --- Global Settings ---
global:
# Enable or disable auto-scaling globally
enabled: true
# Default cooldown period (in seconds) after a scaling event
cooldown: 300 # seconds (5 minutes)
# --- Application Configuration ---
application:
name: example-value # Application Name (e.g., web-app, api-server)
type: web # Application type (e.g., web, api, worker)
# Resource limits (CPU, Memory)
resources:
cpu:
min: 0.5 # Minimum CPU units
max: 4 # Maximum CPU units
memory:
min: 512 # Minimum memory in MB
max: 4096 # Maximum memory in MB
# --- Scaling Policies ---
scaling_policies:
# --- CPU Utilization Scaling ---
cpu_utilization:
enabled: true
target_utilization: 70 # Target CPU utilization percentage
scale_up_threshold: 80 # CPU usage percentage to trigger scale-up
scale_down_threshold: 40 # CPU usage percentage to trigger scale-down
scale_up_increment: 1 # Number of instances to add during scale-up
scale_down_decrement: 1 # Number of instances to remove during scale-down
# --- Memory Utilization Scaling ---
memory_utilization:
enabled: true
target_utilization: 75 # Target Memory utilization percentage
scale_up_threshold: 85 # Memory usage percentage to trigger scale-up
scale_down_threshold: 50 # Memory usage percentage to trigger scale-down
scale_up_increment: 1 # Number of instances to add during scale-up
scale_down_decrement: 1 # Number of instances to remove during scale-down
# --- Request Latency Scaling ---
request_latency:
enabled: false # Enable only if latency metrics are available
target_latency: 200 # Target request latency in milliseconds
scale_up_threshold: 500 # Latency in milliseconds to trigger scale-up
scale_down_threshold: 100 # Latency in milliseconds to trigger scale-down
scale_up_increment: 1 # Number of instances to add during scale-up
scale_down_decrement: 1 # Number of instances to remove during scale-down
# --- Custom Metric Scaling ---
custom_metric:
enabled: false # Enable only if a custom metric is available
metric_name: YOUR_VALUE_HERE # Name of the custom metric
target_value: YOUR_VALUE_HERE # Target value for the custom metric
scale_up_threshold: YOUR_VALUE_HERE # Threshold to trigger scale-up
scale_down_threshold: YOUR_VALUE_HERE # Threshold to trigger scale-down
scale_up_increment: 1 # Number of instances to add during scale-up
scale_down_decrement: 1 # Number of instances to remove during scale-down
# --- Infrastructure Configuration ---
infrastructure:
platform: aws # Cloud platform (e.g., aws, azure, gcp, on-prem)
region: us-east-1 # Cloud region
instance_type: t3.medium # Instance type for new instances
min_instances: 1 # Minimum number of instances
max_instances: 5 # Maximum number of instances
# --- Monitoring Configuration ---
monitoring:
# Integration with monitoring tools (e.g., CloudWatch, Prometheus)
# Configure details for your monitoring system here
# Example:
type: cloudwatch # Monitoring system type
namespace: MyApp # Monitoring namespace
metric_prefix: MyAppInstance # Metric prefixRelated skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |