mcpField
L
launching-ec2-instance-with-best-practices

launching-ec2-instance-with-best-practices

github.com/awsCloud & DevOps3.3k6.4k installsUpdated 1d ago
Repository

About launching-ec2-instance-with-best-practices

A domain skill for teams launching AWS EC2 instances. It guides configuration from AMI and networking through post-launch checks, with attention to security and cost controls.

Key features

  1. 01Workload- and environment-based defaults
  2. 02VPC, subnet, and placement validation
  3. 03AMI and instance architecture checks
  4. 04Least-privilege IAM roles and hardened security groups
  5. 05Encrypted storage and resource tagging
  6. 06Post-launch checks and connection guidance

Use cases

  1. 01Launch EC2 instances for a given environment
  2. 02Limit network port exposure
  3. 03Configure AWS service access for instances
  4. 04Troubleshoot capacity, startup, or SSH issues

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/aws/agent-toolkit-for-aws --skill launching-ec2-instance-with-best-practices

After installing, type/launching-ec2-instance-with-best-practicesin Claude Code to confirm it loaded.

Bundled filesreferences/launch-ec2-instance-with-best-practices.md

Details

From the project README

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.

Comments

Markdown supported