Aws Ec2 Setup
ListedHelps with AWS, setup and configuration as part of deploying and managing cloud infrastructure workflows.
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 aj-geddes/useful-ai-prompts --skill aws-ec2-setup -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
aj-geddes
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 failed 2 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: s3.amazonaws.com.
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.
Hosts contacted
s3.amazonaws.comundeclaredWhat it found
- skills/aws-ec2-setup/references/user-data-script.md:57contacts s3.amazonaws.com
wget https://s3.amazonaws.com/amazoncloudwatch-agent/ubuntu/amd64/latest/amazon-cloudwatch-agent.deb
No credential access: failed
Touches credential material in 1 place.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
What it found
- skills/aws-ec2-setup/references/terraform-ec2-configuration.md:122SSH private keys or config
public_key = file("~/.ssh/id_rsa.pub")
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 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 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 aj-geddes/useful-ai-prompts at 3f5182cfd7.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 3f5182cfd7
- Manifest
- skills/aws-ec2-setup/SKILL.md
- Scanned
- 6 files, 507 lines
About this skill
The aws-ec2-setup skill automates the provisioning and configuration of Amazon EC2 instances, handling everything from instance selection to security group rules. It streamlines the deployment process by generating ready-to-run scripts that align with specific infrastructure requirements.
When to use it
- Deploying new web servers or application containers in a production AWS environment.
- Setting up development environments with pre-configured software stacks like LAMP or Docker.
- Automating repetitive instance launches across multiple regions or account profiles.
- Creating baseline infrastructure for testing and staging environments quickly.
Key capabilities
- Selects appropriate EC2 instance types based on workload needs.
- Configures security groups to define inbound and outbound traffic rules.
- Generates shell scripts (Bash/PowerShell) for automated instance initialization.
- Manages key pair integration for secure SSH access.
Example prompts
- "Provision a t3.medium EC2 instance in us-east-1 with port 80 open for HTTP traffic."
- "Create a setup script for an Ubuntu server that installs Nginx and configures a basic welcome page."
- "Launch two identical instances in different availability zones for high availability testing."
Tips & gotchas
Ensure you have valid AWS credentials configured in your environment before execution to avoid authentication failures. Always review the generated security group rules carefully, as they directly control network access to your new instances.