Launching Ec2 Instance With Best Practices
AWSOfficialPublished by AWS
- Skill
- Workflow
- Cloud and DevOps
- Apache-2.0
- Medium risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured workflow for launching AWS EC2 instances while adhering to security and operational best practices. It guides users through parameter collection, intelligent default selection based on workload type, and configuration of essential infrastructure components like IAM roles, security groups, and encrypted storage. The process ensures that instances are tagged correctly and configured for their specific environment, promoting consistency and reducing manual configuration errors.
What it does
- Collects and validates required deployment parameters from the user
- Determines optimal instance sizing and configuration based on workload type
- Configures least-privilege IAM roles and hardened security groups
- Applies encrypted EBS volumes and comprehensive resource tagging
- Provides post-launch verification and connection guidance
- Offers troubleshooting steps for common deployment issues
When to use it
- When you need to provision new EC2 instances following AWS best practices
- When you want to ensure consistent security and cost-optimization settings
- When you need assistance selecting appropriate instance types for specific workloads
- When you want to automate the setup of IAM roles and security groups for new instances
Advantages
- Reduces manual configuration errors through standardized workflows
- Ensures security hardening by default with least-privilege access
- Optimizes costs by suggesting appropriate instance sizes and storage
- Simplifies resource management with automated tagging and configuration
Usage examples
- “I need to launch a web server in us-east-1.”
- The agent will prompt for any missing required parameters, then configure a t3-series instance with public access, appropriate security groups, and monitoring enabled.
- “Help me set up a database instance for my development environment.”
- The agent will suggest a private subnet placement, larger root volume, and specific security group rules suitable for database workloads.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/aws/launching-ec2-instance-with-best-practices/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip launching-ec2-instance-with-best-practices.zip -d .agents/skills
Documentation by AWS
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.
Files
- ATTRIBUTION.mdAdded by AutoGineer967 B
- LICENSELicence file added by AutoGineer9.9 KiB
- NOTICELicence file added by AutoGineer67 B
- SKILL.md2.1 KiB
- references/launch-ec2-instance-with-best-practices.md62.4 KiB
NOTICE
Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
What our scanner noticed· Medium risk
- References to credential files
- Instructions that use the network
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- AWS
- Publisher
- AWS (Official)
- Source
- aws/agent-toolkit-for-aws · skills/specialized-skills/ec2-skills/launching-ec2-instance-with-best-practices · commit 0a218f8
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- NOTICE (added by AutoGineer from NOTICE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by AWS.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download launching-ec2-instance-with-best-practices.zip