Help us improve
Share bugs, ideas, or general feedback.
From developer-kit-aws
Provides AWS CloudFormation patterns for ElastiCache Redis or Memcached infrastructure, including subnet groups, parameter groups, security controls, replication groups, and cross-stack outputs. Use for cache tiers, high-availability setups, encryption, and VPC placement.
npx claudepluginhub giuseppe-trisciuoglio/developer-kit --plugin developer-kit-awsHow this skill is triggered — by the user, by Claude, or both
Slash command
/developer-kit-aws:aws-cloudformation-elasticacheThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to model ElastiCache infrastructure with CloudFormation without turning `SKILL.md` into a full service manual.
Provides AWS CloudFormation patterns for CloudFront distributions with origins (ALB, S3, Lambda@Edge, VPC), CacheBehaviors, Functions, SecurityHeaders, WAF, ACM, parameters, and cross-stack references. Use for CDN setup, caching, and performance optimization.
Guides securing Redis and Amazon ElastiCache for Redis with authentication, encryption, network isolation, and access control. Useful when building, reviewing, or auditing cache configurations.
Provides Terraform HCL snippets for AWS compute (ECS/Fargate, EKS, Lambda) and storage (S3) with security-first and production-ready patterns. Useful for infrastructure automation.
Share bugs, ideas, or general feedback.
Use this skill to model ElastiCache infrastructure with CloudFormation without turning SKILL.md into a full service manual.
Focus on the delivery decisions that matter most:
Use the bundled references/ documents for larger production templates and service-specific detail.
Use this skill when:
AWS::ElastiCache::CacheCluster and AWS::ElastiCache::ReplicationGroupTypical trigger phrases include cloudformation elasticache, redis replication group, memcached cluster, cache subnet group, and export redis endpoint.
Use:
ReplicationGroup for production Redis-style deployments that need failover, replicas, or shardingCacheCluster for Memcached or simple single-node cache scenariosDo not start with resource YAML before deciding whether the application needs durability, read replicas, cluster mode, or just an ephemeral cache.
Create and wire:
Keep the cache private unless there is a very unusual and well-reviewed reason not to.
For production-style Redis deployments, decide on:
For lower environments, document when a cheaper single-node configuration is acceptable.
Parameterize only the settings that truly vary between environments, such as node type, subnet IDs, or snapshot retention.
Export outputs that other stacks need, typically:
Before deployment:
Parameters:
CacheNodeType:
Type: String
Default: cache.t4g.small
Resources:
CacheSubnetGroup:
Type: AWS::ElastiCache::SubnetGroup
Properties:
Description: Private subnets for the cache tier
SubnetIds: !Ref PrivateSubnetIds
CacheSecurityGroup:
Type: AWS::EC2::SecurityGroup
Properties:
GroupDescription: Application access to Redis
VpcId: !Ref VpcId
RedisReplicationGroup:
Type: AWS::ElastiCache::ReplicationGroup
Properties:
ReplicationGroupDescription: Application Redis cluster
Engine: redis
CacheNodeType: !Ref CacheNodeType
NumNodeGroups: 1
ReplicasPerNodeGroup: 1
AutomaticFailoverEnabled: true
MultiAZEnabled: true
CacheSubnetGroupName: !Ref CacheSubnetGroup
SecurityGroupIds:
- !Ref CacheSecurityGroup
TransitEncryptionEnabled: true
AtRestEncryptionEnabled: true
Outputs:
RedisPrimaryEndpoint:
Description: Primary endpoint used by the application stack
Value: !GetAtt RedisReplicationGroup.PrimaryEndPoint.Address
Export:
Name: !Sub "${AWS::StackName}-RedisPrimaryEndpoint"
Keep outputs small and stable so consumer stacks do not break unnecessarily.
references/examples.md instead of expanding the root skill endlessly.references/examples.mdreferences/reference.mdaws-cloudformation-vpcaws-cloudformation-securityaws-cloudformation-ecsaws-cloudformation-lambda