How do I install the Launching Ec2 Instance With Best Practices skill?

Run npx skillmds@latest add aibot88/launching-ec2-instance-with-best-practices in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Launching Ec2 Instance With Best Practices safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Launching Ec2 Instance With Best Practices?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Launching Ec2 Instance With Best Practices free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Launching Ec2 Instance With Best Practices?

aibot88 (@aibot88) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Launching Ec2 Instance With Best Practices by aibot88

Name: Launching Ec2 Instance With Best Practices
Rating: 4.2 (5 reviews)
Author: aibot88

Launching Ec2 Instance With Best Practices

Launches an EC2 instance with secure, cost-efficient defaults including AMI selection, burstable instance sizing, least-privilege IAM roles, hardened security groups, encrypted EBS volumes, and comprehensive tagging. Use when deploying new EC2 instances following AWS best practices for security and cost optimization.

aibot88 Updated Sep 9, 2026 3 repo stars

File contents

Launching EC2 Instances with Best Practices

Overview

Domain expertise for launching EC2 instances with sensible defaults optimized for security, cost-efficiency, and operational best practices. Covers AMI selection, instance type recommendation, network configuration, IAM role creation, security group hardening, storage configuration, tagging strategy, and post-launch verification.

Launch an EC2 instance

To launch a fully configured EC2 instance with best-practice defaults, follow the procedure exactly. See EC2 instance launch procedure.

The procedure handles:

Intelligent defaults based on workload type and environment
Network validation (VPC, subnet, public/private placement)
AMI selection with architecture compatibility checks
Least-privilege IAM roles for required AWS service access
Hardened security groups with minimal port exposure
Encrypted gp3 storage with environment-appropriate retention
Comprehensive tagging for cost tracking and organization
Post-launch verification and connection instructions

Troubleshooting

Insufficient instance capacity

Try a different availability zone or instance type (e.g., t3a instead of t3). See the full troubleshooting guide in the launch procedure.

Instance immediately terminates

Check console output with aws ec2 get-console-output. Verify EBS volume size is sufficient and AMI is compatible with the instance type.

Cannot connect via SSH

Verify the security group allows SSH from your IP, key file permissions are 400, and the instance is running. Consider AWS Systems Manager Session Manager as an alternative.

---name: launching-ec2-instance-with-best-practicesdescription: Launches an EC2 instance with secure, cost-efficient defaults including AMI selection, burstable instance sizing, least-privilege IAM roles, hardened security groups, encrypted EBS volumes, and comprehensive tagging. Use when deploying new EC2 instances following AWS best practices for security and cost optimization.--- # Launching EC2 Instances with Best Practices ## Overview Domain expertise for launching EC2 instances with sensible defaults optimized for security, cost-efficiency, and operational best practices. Covers AMI selection, instance type recommendation, network configuration, IAM role creation, security group hardening, storage configuration, tagging strategy, and post-launch verification. ## Launch an EC2 instance To launch a fully configured EC2 instance with best-practice defaults, follow the procedure exactly. See [EC2 instance launch procedure](references/launch-ec2-instance-with-best-practices.md). The procedure handles: - Intelligent defaults based on workload type and environment - Network validation (VPC, subnet, public/private placement) - AMI selection with architecture compatibility checks - Least-privilege IAM roles for required AWS service access - Hardened security groups with minimal port exposure - Encrypted gp3 storage with environment-appropriate retention - Comprehensive tagging for cost tracking and organization - Post-launch verification and connection instructions ## Troubleshooting ### Insufficient instance capacity Try a different availability zone or instance type (e.g., t3a instead of t3). See the full troubleshooting guide in the [launch procedure](references/launch-ec2-instance-with-best-practices.md). ### Instance immediately terminates Check console output with `aws ec2 get-console-output`. Verify EBS volume size is sufficient and AMI is compatible with the instance type. ### Cannot connect via SSH Verify the security group allows SSH from your IP, key file permissions are `400`, and the instance is running. Consider AWS Systems Manager Session Manager as an alternative.

Frequently asked questions