Amazon Elasticache
AWSOfficialPublished by AWS
- Skill
- Tool integration
- Cloud and DevOps
- Apache-2.0
- Medium risk
- Has scripts
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The Amazon ElastiCache skill provides a structured, modular approach to managing in-memory data stores on AWS. It guides developers through the entire lifecycle of ElastiCache and Valkey, from initial requirements gathering and provisioning to complex data modeling, AI-driven vector search, and operational monitoring. The skill enforces best practices for connection safety, security, and infrastructure-as-code, ensuring reliable performance for caching, session management, and GenAI workloads.
What it does
- Assesses workload requirements to recommend optimal ElastiCache configurations.
- Automates provisioning and connectivity setup for serverless and node-based clusters.
- Provides implementation patterns for common use cases like cache-aside, session stores, and rate limiting.
- Supports advanced AI workloads including semantic caching, RAG, and vector similarity search.
- Delivers operational diagnostics for performance tuning, cost optimization, and troubleshooting.
- Manages migration paths from self-managed Redis or between different deployment models.
When to use it
- When you need to reduce database load or improve API response times with an in-memory cache.
- When implementing AI agent memory, RAG retrieval, or semantic caching for LLM applications.
- When migrating existing Redis workloads to a managed AWS environment.
- When troubleshooting performance issues like high latency, replication lag, or memory pressure.
- When setting up secure, production-ready caching infrastructure using IaC.
Advantages
- Standardizes deployment and operational patterns across development teams.
- Ensures compliance with security best practices like TLS and IAM authentication.
- Reduces configuration errors through automated input validation and tagging.
- Provides clear guidance on engine selection and version-specific feature availability.
- Simplifies complex tasks like cross-region migration and vector search setup.
Usage examples
- “I need to speed up my RDS database. Should I use ElastiCache?”
- The agent will initiate the requirements sub-skill to analyze your workload, stack, and latency needs, then provide a recommendation on whether ElastiCache is the right fit.
- “How do I set up a Valkey cluster for vector search?”
- The agent will route to the genai sub-skill, verify you are using a node-based Valkey 8.2+ cluster, and provide the necessary configuration and code to enable vector similarity search.
- “My cache hit rate is low and latency is spiking. Can you help me troubleshoot?”
- The agent will activate the monitoring sub-skill to analyze your metrics, identify potential hot keys or memory imbalance, and suggest specific remediation steps.
- “Help me migrate my self-managed Redis to ElastiCache.”
- The agent will guide you through the migration sub-skill, performing preflight checks and validating your source configuration for a zero-downtime cutover.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/aws/amazon-elasticache/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip amazon-elasticache.zip -d .agents/skills
Documentation by AWS
ElastiCache
A modular ElastiCache toolkit organized as a registry of sub-skills. Each sub-skill handles one domain of ElastiCache work. The router below matches user intent to the right sub-skill, then loads only the references needed for that sub-skill.
How this skill works
Match the user's request against the semantic categories in the registry below. Match on meaning, not exact wording ("help me figure out which data structures to use" matches
data-modelingeven without the word "pattern").Disambiguation: If the user's intent matches multiple sub-skills, apply these rules in order:
If
.elasticache/requirements.jsonexists withinfrastructure.endpointset, prefermonitoringordata-modeling(the user has an existing cache).If no cache exists (no requirements.json or no endpoint), prefer
requirements.If still ambiguous, ask one clarifying question: "Are you looking to set up something new, or troubleshoot something existing?"
Check the Guardrails section before recommending an engine or deployment model.
Read
references/{sub-skill-id}/instructions.mdfor the matched sub-skill. If the file is not found at a relative path, check your prompt or environment for the skill directory absolute path and retry with{skill-directory}/references/{sub-skill-id}/instructions.md.If the request spans multiple sub-skills, execute them in pipeline order.
If a sub-skill requires upstream context (engine, deployment model, endpoint) not yet in session memory, route to the upstream sub-skill first.
If no sub-skill matches, activate
requirementsfirst.If a script or CLI call fails, show the error to the user and suggest a specific fix before retrying.
Sub-skill registry
Each entry has: an ID (directory name under references/), a domain description, semantic categories for matching, and upstream/downstream dependencies.
| ID | Name | Domain | Semantic Categories | Upstream | Downstream |
|---|---|---|---|---|---|
requirements | Solution Fit | Gathers workload, stack, scale, latency, persistence, and budget through workspace scan + structured interview. Decides whether ElastiCache is the right service and hands off with a routing recommendation. | I need a cache, speed up my app, reduce database load, lower Bedrock cost, should I use ElastiCache, what's best for my workload, evaluating cache options, ElastiCache vs X, Valkey vs X, vague new workload | — | setup, data-modeling, genai, monitoring, migration |
setup | Create and Connect | Provisioning, connectivity, security, authentication, IaC, deployment choice. Gets the user to a working cache with least friction. Covers engine selection, serverless vs node-based, VPC, TLS, RBAC/IAM, jump-host/SSM tunnels, CLI/SDK/CFN/CDK/Terraform starters. | create a cache, set up ElastiCache, provision, Valkey cluster, connect Lambda/ECS/EKS/EC2, VPC, security groups, TLS, RBAC, IAM auth, jump host, SSM tunnel, CloudFormation, CDK, Terraform, engine selection, serverless vs node-based, backup, snapshot, restore, export | requirements (optional) | data-modeling, genai, monitoring |
data-modeling | Application Patterns | Picks data structures, key schema, TTL strategy, invalidation approach, and client code for non-AI patterns: cache-aside, session store, rate limiting, leaderboards, counters, pub/sub, streams, shopping carts, job queues, activity feeds. | session store, rate limiting, leaderboard, cache-aside, query caching, counters, streams, pub/sub, shopping cart, job queue, activity feed, key schema, TTL, invalidation, data structures | setup (cache must exist) | monitoring |
genai | AI and Vector Workloads | Classifies request into Mode 1 (plain cache), Mode 2 (semantic response cache), or Mode 3 (full vector search). Selects Valkey and forces node-based Valkey 8.2 or above (recommend 9.0) when server-side vector similarity is needed. Covers semantic caching, agent memory, RAG retrieval, recommendation, personalization, conversation/session persistence for AI agents, and framework wiring (Strands, mem0, LangChain). | semantic cache, RAG, agent memory, conversational memory, vector search, embeddings, recommendation, personalization, Bedrock latency, Bedrock cost, LLM caching, Strands, mem0, LangChain, conversation history, AI session store, embedding provider, framework integration | setup (cache must exist) | monitoring |
monitoring | Operate and Observe | Diagnoses performance, cost, and reliability using metrics first, then recommends the smallest change. Covers dashboards, alarms, log delivery, cost reporting, event routing, troubleshooting high CPU / memory / replication lag / connection spikes / low hit rate / hot keys / big keys / slot imbalance / latency spike root cause. | cache is slow, cost too high, hit rate low, high CPU, memory pressure, replication lag, connection spikes, dashboards, alarms, CloudWatch, cost comparison, troubleshoot, hot key, uneven shard load, one node pinned, big key, memory bloat, which key is biggest, keyspace distribution, prefix analysis, cost attribution by tenant, memory imbalance, one shard full, slot memory skew, latency spike, slow command incident, root cause for latency bump | — | setup, migration |
migration | Engine and Platform Migration | Selects the migration path and sequences preflight, validation, cutover, and rollback. Covers self-managed Redis → ElastiCache, Redis OSS → Valkey, node-based ↔ serverless, version upgrades. Hard validate-before-migrate gate. | migrate, Redis OSS to Valkey, self-managed to ElastiCache, node-based to serverless, serverless to node-based, engine upgrade, version upgrade, zero-downtime cutover, rollback | — | setup, monitoring |
Pipeline order
Sub-skills run independently, but common multi-step journeys follow these pipelines:
requirements→setup→ (data-modeling|genai) →monitoringmigration→setup→monitoringmonitoring→setup|migration(if metrics indicate)
State handoff: requirements.json
.elasticache/requirements.json is the single source of truth for cross-sub-skill state. Each sub-skill reads it at start and writes its section after completing work. Read before writing; merge, do not overwrite.
| Section | Owner | Key fields |
|---|---|---|
| top-level | requirements | engine, deployment_model, region, runtime, patterns, use_case, vpc_id, subnet_ids, security_group_ids |
infrastructure | setup | cache_name, resource_id, engine_version, topology, endpoint, port, auth_model, tls, client_library, execution_path, access_mode, tunnel_instance_id, embedding_provider, embedding_model, embedding_dim, embedding_module |
genai | genai | mode, mode_2_path, framework |
migration | migration | source_type, source_host, migration_path, cutover_status |
Ownership note:
deployment_modelis set byrequirementsduring initial interview.migrationmay update it after an engine or deployment model switch (e.g., node-based to serverless).
requirements.json should include "schema_version": 1 and "last_updated": "<ISO timestamp>" at the top level. Every sub-skill that writes to requirements.json must update last_updated. If last_updated is older than 7 days, warn the user that cached state may be stale.
requirements.json tracks one active cache. If the user works with multiple caches in the same project, confirm which cache is active before reading or writing state.
When a sub-skill needs upstream context (engine, endpoint, auth model), check requirements.json first. If the field is null or the file does not exist, route to the upstream sub-skill.
Global rules (apply to every sub-skill)
Execution path. Use AWS CLI, SDK (boto3), CloudFormation, or CDK as the primary path for control-plane work. Use valkey-py as the primary path for data-plane work.
Response depth. Summary (2-3 sentences) for "should I" or "which" questions. Standard (recommendation + config + code + next steps) by default. Expert (full decision matrix with alternatives, cost, security caveats) for "why" or "compare all" questions. Escalate on user request; never downgrade unprompted.
Session memory. Track region, VPC, engine, deployment model, auth model, compute runtime, and language. Carry forward across sub-skills. Do not re-ask. If the user overrides a value, update it everywhere. Inferred values (from workspace scan or IaC) must be re-confirmed before high-risk decisions (engine, deployment model, security posture); low-risk inferences (language, framework, region) can be used as defaults silently.
Source priority. Always answer from skill-local files first (sub-skill references, then
scripts/). Do not fetch external documentation or web search unless the local files cannot answer the query. When local files are insufficient, fall back to official AWS docs: https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/ for features and https://aws.amazon.com/elasticache/pricing/ for pricing. Never invent price points or version constraints. If the user references a Valkey or Redis version, feature, or pricing tier not covered in local files, fall back to https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/ before answering. Do not extrapolate from local content that may be outdated.Freshness disclaimer. When outputting pricing, version constraints, or feature availability, include a one-line disclaimer: "For current pricing see https://aws.amazon.com/elasticache/pricing/. For current feature availability see https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/."
Connection safety. Never create a Valkey/Redis client at module level (top of file, import time). Initialize connections inside a function or on first use. Module-level connections crash applications that import the module before the cache is reachable.
Code environment. Use
python3(notpython) in all commands and shebangs. Do not generatepip installorpytestcommands in application code. Prefer the agent's file-writing tool over shell redirection for writing files.Input validation (write operations only). Before running any create, modify, or delete CLI command or SDK call that uses user-provided values (cache name, region, subnet IDs, security group IDs, VPC ID, KMS key, snapshot name), validate them with
scripts/input_validator.py. Runpython3 scripts/input_validator.py cache_name=<val> region=<val> ...or importvalidate_allas a library. Skip validation for read-only operations (describe, list) where bad input is harmless.Resource tagging (always apply on resource creation). When creating any cache (
create-serverless-cache,create-replication-group,create-cache-cluster), ALWAYS include these tags:--tags Key=managed_by,Value=aws-skills Key=skill,Value=elasticache Key=skill_version,Value=1.0.0 Key=created_by,Value=elasticache-skill Key=generation_model,Value={your-model-id}Example:
--tags Key=managed_by,Value=aws-skills Key=skill,Value=elasticache Key=skill_version,Value=1.0.0 Key=created_by,Value=elasticache-skill Key=generation_model,Value=claude-sonnet-4-20250514Set
generation_modelto your own model identifier. Include these tags even if the user does not mention tagging. If the user provides additional tags, append these to their tags rather than replacing them.
Reference loading
Load additional references only when the current turn's answer requires them.
On-demand pointers (not preloaded; fetch when the trigger applies):
references/shared-ux/production-readiness.md— when the user asks if their cache is ready for production, or after setup completes and the user wants to go to productionreferences/shared-ux/action-safety.md— before any destructive action (risk levels, never-auto-execute list)references/shared-ux/error-remediation.md— when the user hits a specific ElastiCache error code (MOVED, CROSSSLOT, CLUSTERDOWN, MULTI/EXEC+IAM, etc.)references/shared-foundation/boundary-doc.md— when the user asks what this skill coversreferences/shared-foundation/attribution.md— when generating CLI commands, SDK code, or IaC templatesreferences/shared-foundation/architecture-diagrams.md— when the user asks for architecture diagrams or visual referencereferences/shared-runtime/lambda.md— when connecting from Lambda (cold start gotchas, IAM auth code, lazy init)references/shared-runtime/ecs.md— when connecting from ECS (SIGTERM shutdown, connection pool drain, task definition)references/shared-runtime/eks.md— when connecting from EKS (IRSA, service mesh bypass, SecurityGroupPolicy CRD)references/shared-runtime/api-gateway.md— when integrating with API Gateway (no direct path, caching layers comparison)references/shared-runtime/rds-acceleration.md— when caching RDS/Aurora queries (thundering herd, stampede protection, invalidation)references/shared-runtime/secret-injection.md— when the user asks about credential management per compute platformreferences/shared-security/encryption-defaults.md— when adding encryption to an existing unencrypted cluster (TLS two-step migration, at-rest immutability)references/shared-security/config-guardrails.md— when the user wants continuous compliance monitoring (AWS Config rules, custom Lambda rules)references/shared-security/vpc-patterns.md— when debugging port/security-group issues (port 6380 serverless reader, anti-patterns)
Folder convention:
references/contains 10 folders. 6 match the sub-skills (requirements,setup,data-modeling,genai,monitoring,migration) and are routing destinations. The 4shared-*folders (shared-foundation,shared-ux,shared-security,shared-runtime) are cross-cutting material loaded on demand, not routing destinations.
Guardrails
| Priority | Rule |
|---|---|
| CRITICAL | Vector search MUST use node-based Valkey 8.2 or above. Serverless does NOT support vector search. Never suggest serverless for vector search. Apply this regardless of which sub-skill activates. |
| CRITICAL | Do not invent price points or version constraints. Use scripts/price_calculator.py and current AWS docs when precision matters. |
| HIGH | Do not recommend Memcached when the user needs persistence, replication, RBAC or IAM auth, sorted sets, streams, pub/sub, or vector search. |
| HIGH | Do not assume local laptop access works directly. ElastiCache is VPC-centric; explain VPC, tunnel, or jump-host access when needed. |
| STANDARD | Do not trigger on every generic Redis mention. Trigger when the user is clearly asking about AWS, managed caching, migration, connectivity, pricing, operations, or AWS service integration. |
| STANDARD | For ambiguous "cache" requests inside AWS contexts, activate this skill and start with requirements. |
Product truths
ElastiCache Serverless deploys in under a minute and removes infrastructure management.
Valkey serverless pricing is 33% lower than other supported engines; node-based Valkey pricing is 20% lower.
Serverless caches have in-transit encryption always enabled (cannot be disabled).
IAM auth is available for all ElastiCache Valkey versions (7.2 is the baseline Valkey version on ElastiCache) and Redis OSS 7.0+.
Valkey version ladder: 7.2 (baseline), 8.0 (20% more data per node (capacity improvement), per-slot metrics), 8.1 (Bloom filters, COMMANDLOG, SET IFEQ, 20% less memory via new hash table (efficiency improvement)), 8.2 (vector search), 9.0 (recommended default for new clusters). Recommend Valkey 9.0 for new clusters unless a specific feature dictates otherwise.
Vector search is available for Valkey 8.2 or above on node-based clusters (recommend 9.0).
Global Datastore is available for node-based clusters only. It does not support IPv6 or Local Zones. Global Datastore supports AUTH and RBAC. Cross-region failover must be promoted manually (no autofailover across regions). At-rest encryption must be enabled on all clusters in the Global Datastore, but each cluster can use a separate KMS key per region.
Online migration from self-managed Redis to ElastiCache requires: (source) AUTH must not be enabled,
protected-modeset tono, replication and administrative commands must not be renamed (e.g.,sync,psync,info,config,command,cluster); (target) encryption in-transit disabled, Multi-AZ enabled, engine version Redis OSS 5.0.6+ or Valkey 7.2+, not part of a Global Datastore, data tiering disabled. Shard counts must match between source and target. All source Redis instances must use the same port. Online migration is not supported for serverless caches (node-based targets only). Seereferences/migration/topology-validation.mdfor the full checklist.
Files
- ATTRIBUTION.mdAdded by AutoGineer924 B
- LICENSELicence file added by AutoGineer9.9 KiB
- NOTICELicence file added by AutoGineer67 B
- SKILL.md17.8 KiB
- assets/examples/sample_commandstats.csv882 B
- assets/examples/sample_input_simple.csv449 B
- references/data-modeling/command-availability.md6.1 KiB
- references/data-modeling/common-patterns.md8.6 KiB
- references/data-modeling/instructions.md9.9 KiB
- references/data-modeling/memcached-recipe.md5.2 KiB
- references/data-modeling/recipe-gallery.md8.2 KiB
- references/genai/agent-memory.md5.9 KiB
- references/genai/elasticache-search.md16.9 KiB
- references/genai/embedding-providers.md8.6 KiB
- references/genai/framework-guide.md4.9 KiB
- references/genai/instructions.md9.7 KiB
- references/genai/rag-retrieval.md9.3 KiB
- references/genai/semantic-cache.md8.9 KiB
- references/genai/session-store.md6.4 KiB
- references/migration/auth-migration.md14.4 KiB
- references/migration/feature-comparison.md10.9 KiB
- references/migration/global-datastore-operations.md8.0 KiB
- references/migration/instructions.md14.8 KiB
- references/migration/rollback-procedures.md16.9 KiB
- references/migration/self-managed-migration.md14.6 KiB
- references/migration/sizing-assessment.md6.8 KiB
- references/migration/topology-validation.md8.1 KiB
- references/migration/upgrade-patching.md13.2 KiB
- references/migration/valkey-migration-guide.md13.5 KiB
- references/monitoring/alarm-packs.md8.4 KiB
- references/monitoring/big-key-hunter.md6.8 KiB
- references/monitoring/client-tuning-and-diagnostics.md11.8 KiB
- references/monitoring/cloudwatch-dashboards.md7.7 KiB
- references/monitoring/cost-reporting.md11.9 KiB
- references/monitoring/event-routing.md9.5 KiB
- references/monitoring/hot-key-detection.md10.8 KiB
- references/monitoring/instructions.md8.8 KiB
- references/monitoring/key-space-distribution-by-prefix.md6.8 KiB
- references/monitoring/log-delivery.md7.9 KiB
- references/monitoring/slot-memory-imbalance-detection.md6.7 KiB
- references/monitoring/slow-log-cross-signal-diagnosis.md8.5 KiB
- references/monitoring/troubleshooting.md17.9 KiB
- references/requirements/instructions.md9.9 KiB
- references/setup/auth-model-selector.md3.3 KiB
- references/setup/cluster-topology.md3.6 KiB
- references/setup/connection-guide.md6.4 KiB
- references/setup/connectivity-diagnostics.md6.9 KiB
- references/setup/create-secure-cache.md8.4 KiB
- references/setup/engine-selection.md2.1 KiB
- references/setup/iac-best-practices.md7.3 KiB
- references/setup/iac-reference.md6.2 KiB
- references/setup/iam-policies.md2.7 KiB
- references/setup/instructions.md8.6 KiB
- references/setup/serverless-vs-node.md12.7 KiB
- references/setup/service-quotas.md2.9 KiB
- references/shared-foundation/architecture-diagrams.md8.0 KiB
- references/shared-foundation/attribution.md3.7 KiB
- references/shared-foundation/boundary-doc.md4.9 KiB
- references/shared-runtime/api-gateway.md5.4 KiB
- references/shared-runtime/ecs.md7.5 KiB
- references/shared-runtime/eks.md10.5 KiB
- references/shared-runtime/lambda.md10.1 KiB
- references/shared-runtime/rds-acceleration.md12.6 KiB
- references/shared-runtime/secret-injection.md14.1 KiB
- references/shared-security/config-guardrails.md8.0 KiB
- references/shared-security/encryption-defaults.md4.2 KiB
- references/shared-security/vpc-patterns.md2.8 KiB
- references/shared-ux/action-safety.md9.8 KiB
- references/shared-ux/error-remediation.md12.1 KiB
- references/shared-ux/production-readiness.md5.5 KiB
- scripts/collect_metrics.shScript5.2 KiB
- scripts/command_classifier.pyScript6.2 KiB
- scripts/find_tunnel_host.pyScript7.2 KiB
- scripts/generate_dashboards.pyScript27.1 KiB
- scripts/input_validator.pyScript10.6 KiB
- scripts/migration_preflight.pyScript19.5 KiB
- scripts/price_calculator.pyScript14.4 KiB
- scripts/pricing.pyScript20.2 KiB
- scripts/security_audit.pyScript19.5 KiB
- scripts/serverless_estimator.pyScript28.4 KiB
- scripts/start_tunnel.pyScript11.7 KiB
- scripts/test_connection.pyScript13.3 KiB
- scripts/validate_references.pyScript10.6 KiB
scripts/input_validator.py
#!/usr/bin/env python3
"""
ElastiCache Input Validator
Validates and sanitizes user-provided values before they are interpolated into
CLI commands. Prevents shell injection and ensures identifiers conform to AWS
naming rules.
Usage (as a library):
from input_validator import validate_cache_name, sanitize_for_cli, validate_all
ok, err = validate_cache_name("my-cache")
safe = sanitize_for_cli("my-cache; rm -rf /")
errors = validate_all({"cache_name": "my-cache", "region": "us-east-1"})
Usage (standalone -- validates a set of key=value pairs):
python input_validator.py cache_name=my-cache region=us-east-1 subnet_id=subnet-abc123
"""
from __future__ import annotations
import re
import sys
from typing import Optional
# ---------------------------------------------------------------------------
# Individual validators
# ---------------------------------------------------------------------------
# Each function returns (is_valid: bool, error_message: str | None).
# A None error_message means the value is valid.
# ---------------------------------------------------------------------------
def validate_cache_name(name: str) -> tuple[bool, Optional[str]]:
"""Validate an ElastiCache cache or cluster name.
Rules:
- 1 to 40 characters
- Alphanumeric characters and hyphens only
- Must start with a letter
- No consecutive hyphens
- Must not end with a hyphen
Note: Serverless cache names must be lowercase. Node-based cluster names
are case-insensitive (AWS lowercases them). This validator enforces
lowercase to ensure compatibility with both deployment types.
"""
if not name:
return False, "Cache name must not be empty"
if len(name) > 40:
return False, f"Cache name must be 1-40 characters (got {len(name)})"
if not re.match(r'^[a-z]', name):
return False, "Cache name must start with a lowercase letter (serverless requires lowercase; node-based is case-insensitive but lowercased by AWS)"
if not re.match(r'^[a-z0-9-]+$', name):
return False, "Cache name may only contain lowercase alphanumeric characters and hyphens"
if '--' in name:
return False, "Cache name must not contain consecutive hyphens"
if name.endswith('-'):
return False, "Cache name must not end with a hyphen"
return True, None
def validate_replication_group_id(rg_id: str) -> tuple[bool, Optional[str]]:
"""Validate a replication group ID.
Same rules as cache name: 1-40 chars, alphanumeric + hyphens, starts with
a letter, no consecutive hyphens, no trailing hyphen.
"""
if not rg_id:
return False, "Replication group ID must not be empty"
if len(rg_id) > 40:
return False, f"Replication group ID must be 1-40 characters (got {len(rg_id)})"
if not re.match(r'^[a-zA-Z]', rg_id):
return False, "Replication group ID must start with a letter"
if not re.match(r'^[a-zA-Z0-9-]+$', rg_id):
return False, "Replication group ID may only contain alphanumeric characters and hyphens"
if '--' in rg_id:
return False, "Replication group ID must not contain consecutive hyphens"
if rg_id.endswith('-'):
return False, "Replication group ID must not end with a hyphen"
return True, None
def validate_subnet_id(subnet_id: str) -> tuple[bool, Optional[str]]:
"""Validate an AWS subnet ID (subnet-<8-17 hex chars>)."""
if not subnet_id:
return False, "Subnet ID must not be empty"
if not re.match(r'^subnet-[0-9a-f]{8,17}$', subnet_id):
return False, "Subnet ID must match pattern subnet-<8-17 hex characters> (e.g. subnet-0abc1234def56789a)"
return True, None
def validate_security_group_id(sg_id: str) -> tuple[bool, Optional[str]]:
"""Validate an AWS security group ID (sg-<8-17 hex chars>)."""
if not sg_id:
return False, "Security group ID must not be empty"
if not re.match(r'^sg-[0-9a-f]{8,17}$', sg_id):
return False, "Security group ID must match pattern sg-<8-17 hex characters> (e.g. sg-0abc1234def56789a)"
return True, None
def validate_region(region: str) -> tuple[bool, Optional[str]]:
"""Validate an AWS region code (e.g. us-east-1, eu-west-2, ap-southeast-1)."""
if not region:
return False, "Region must not be empty"
if not re.match(r'^[a-z]{2}-[a-z]+-\d+$', region):
return False, "Region must match AWS region pattern (e.g. us-east-1, eu-west-2)"
return True, None
def validate_engine_version(version: str) -> tuple[bool, Optional[str]]:
r"""Validate an engine version string.
Accepted formats:
- Major only: "7" (used by serverless MajorEngineVersion)
- Major.minor: "7.1", "8.2"
- Major.minor.patch: "7.0.4", "7.1.0"
"""
if not version:
return False, "Engine version must not be empty"
if not re.match(r'^\d+(\.\d+){0,2}$', version):
return False, "Engine version must match pattern <major>[.<minor>[.<patch>]] (e.g. 7, 7.1, 7.0.4)"
return True, None
def validate_vpc_id(vpc_id: str) -> tuple[bool, Optional[str]]:
"""Validate an AWS VPC ID (vpc-<8-17 hex chars>)."""
if not vpc_id:
return False, "VPC ID must not be empty"
if not re.match(r'^vpc-[0-9a-f]{8,17}$', vpc_id):
return False, "VPC ID must match pattern vpc-<8-17 hex characters> (e.g. vpc-0abc1234def56789a)"
return True, None
def validate_kms_key_id(key_id: str) -> tuple[bool, Optional[str]]:
"""Validate a KMS key ID.
Accepts either:
- A UUID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
- A KMS key ARN: arn:aws:kms:<region>:<account>:key/<key-id>
- A KMS alias ARN: arn:aws:kms:<region>:<account>:alias/<alias-name>
"""
if not key_id:
return False, "KMS key ID must not be empty"
uuid_pattern = r'^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$'
arn_pattern = r'^arn:aws:kms:[a-z0-9-]+:\d{12}:(key|alias)/[a-zA-Z0-9/_-]+$'
if re.match(uuid_pattern, key_id):
return True, None
if re.match(arn_pattern, key_id):
return True, None
return False, (
"KMS key ID must be a UUID (e.g. 12345678-1234-1234-1234-123456789abc) "
"or a KMS ARN (e.g. arn:aws:kms:us-east-1:123456789012:key/<key-id>)"
)
def validate_snapshot_name(name: str, serverless: bool = False) -> tuple[bool, Optional[str]]:
"""Validate a snapshot name.
Rules:
- 1 to 255 characters for serverless snapshots, 1 to 40 for node-based
- Alphanumeric characters and hyphens only
- Must start with a letter
- No consecutive hyphens
- Must not end with a hyphen
"""
if not name:
return False, "Snapshot name must not be empty"
max_len = 255 if serverless else 40
if len(name) > max_len:
label = "serverless" if serverless else "node-based"
return False, f"Snapshot name must be 1-{max_len} characters for {label} (got {len(name)})"
if not re.match(r'^[a-zA-Z]', name):
return False, "Snapshot name must start with a letter"
if not re.match(r'^[a-zA-Z0-9-]+$', name):
return False, "Snapshot name may only contain alphanumeric characters and hyphens"
if '--' in name:
return False, "Snapshot name must not contain consecutive hyphens"
if name.endswith('-'):
return False, "Snapshot name must not end with a hyphen"
return True, None
# ---------------------------------------------------------------------------
# CLI sanitization safety net
# ---------------------------------------------------------------------------
# Shell metacharacters that could enable command injection
_SHELL_METACHARACTERS = re.compile(r'[;&|`$(){}!<>\'\"\\\n\r\x00]')
def sanitize_for_cli(value: str) -> str:
"""Strip shell metacharacters from a value as a defense-in-depth safety net.
This is NOT a substitute for proper validation -- always validate inputs
first using the validate_* functions. This function provides an additional
layer of protection by removing characters that could be interpreted by
a shell if a value is accidentally interpolated into a command string.
Returns the sanitized string with all shell metacharacters removed.
"""
return _SHELL_METACHARACTERS.sub('', value)
# ---------------------------------------------------------------------------
# Bulk validation
# ---------------------------------------------------------------------------
# Map of recognized parameter keys to their validator functions
_VALIDATORS = {
"cache_name": validate_cache_name,
"replication_group_id": validate_replication_group_id,
"subnet_id": validate_subnet_id,
"security_group_id": validate_security_group_id,
"region": validate_region,
"engine_version": validate_engine_version,
"vpc_id": validate_vpc_id,
"kms_key_id": validate_kms_key_id,
"snapshot_name": validate_snapshot_name,
}
def validate_all(params: dict) -> list[str]:
"""Validate all recognized keys in a parameter dict.
Takes a dict like {"cache_name": "my-cache", "region": "us-east-1"} and
validates every key that has a known validator. Keys not recognized are
silently skipped (they may be application-specific parameters).
Returns a list of error messages. An empty list means all recognized
parameters passed validation.
"""
errors = []
for key, value in params.items():
validator = _VALIDATORS.get(key)
if validator is None:
continue
if not isinstance(value, str):
errors.append(f"{key}: expected a string, got {type(value).__name__}")
continue
is_valid, error_msg = validator(value) # type: ignore[operator]
if not is_valid:
errors.append(f"{key}: {error_msg}")
return errors
# ---------------------------------------------------------------------------
# CLI entrypoint
# ---------------------------------------------------------------------------
def main():
"""Validate key=value pairs passed on the command line."""
if len(sys.argv) < 2:
print("Usage: python input_validator.py key=value [key=value ...]")
print("Example: python input_validator.py cache_name=my-cache region=us-east-1")
print()
print("Recognized keys:", ", ".join(sorted(_VALIDATORS.keys())))
sys.exit(0)
params = {}
for arg in sys.argv[1:]:
if '=' not in arg:
print(f"Error: argument '{arg}' is not in key=value format")
sys.exit(2)
key, value = arg.split('=', 1)
params[key] = value
errors = validate_all(params)
if errors:
print("Validation FAILED:")
for err in errors:
print(f" - {err}")
sys.exit(1)
else:
print("All inputs valid.")
sys.exit(0)
if __name__ == "__main__":
main()
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs Python, Needs Node.js
Security
What our scanner noticed· Medium risk
- References to credential files
- Instructions that use the network
- Scripts that your agent may run
This skill includes scripts that your agent may run. Read them before you use it.
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- AWS
- Publisher
- AWS (Official)
- Source
- aws/agent-toolkit-for-aws · skills/specialized-skills/database-skills/amazon-elasticache · commit 0a218f8
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- NOTICE (added by AutoGineer from NOTICE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by AWS.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download amazon-elasticache.zip