Aws Cloudformation Ecs
CheckedProvides AWS guidance and assistance for deploying and managing cloud infrastructure.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add giuseppe-trisciuoglio/developer-kit --skill aws-cloudformation-ecs --full-depth -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
giuseppe-trisciuoglio
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned giuseppe-trisciuoglio/developer-kit at fe73fb33a0.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- fe73fb33a0
- Scanned
- 4 files, 2,968 lines
About this skill
The aws-cloudformation-ecs skill enables AI agents to provision and manage Amazon ECS clusters and services directly through AWS CloudFormation templates, automating infrastructure-as-code workflows. It streamlines the deployment of containerized applications by handling complex resource dependencies and configuration updates without manual intervention.
When to use it
- Automatically spin up new ECS clusters with specific instance types and security groups for development environments.
- Update existing service configurations, such as scaling policies or task definitions, via declarative templates.
- Ensure consistent infrastructure state across multiple AWS accounts by applying standardized CloudFormation stacks.
- Orchestrate the full lifecycle of containerized workloads, including creation, modification, and teardown of ECS resources.
Key capabilities
- Provision Amazon ECS clusters and services using YAML or JSON CloudFormation templates.
- Manage associated networking resources like VPCs, subnets, and security groups within the stack.
- Define task execution roles and container definitions for seamless application deployment.
- Handle stack operations including create, update, delete, and rollback actions programmatically.
Example prompts
- "Create an AWS CloudFormation stack to deploy a new ECS cluster with three t3.medium instances in us-east-1."
- "Update the existing ECS service definition to increase the desired task count from 2 to 5 using CloudFormation."
- "Delete the CloudFormation stack associated with our staging environment's ECS resources to free up costs."
Tips & gotchas
Ensure your AWS account has the necessary IAM permissions for cloudformation:* and ecs:* actions before attempting to execute these tasks. Complex templates may require pre-existing VPC configurations; verify network prerequisites to avoid deployment failures.