home / skills / partme-ai / full-stack-skills / cloud-aws-ec2

cloud-aws-ec2 skill

/skills/cloud-aws-ec2

This skill provides comprehensive guidance for creating, configuring, and managing AWS EC2 instances to streamline cloud compute workflows.

npx playbooks add skill partme-ai/full-stack-skills --skill cloud-aws-ec2

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
657 B
---
name: cloud-aws-ec2
description: Provides comprehensive guidance for AWS EC2 including instance creation, configuration, security groups, and EC2 management. Use when the user asks about AWS EC2, needs to create EC2 instances, configure EC2, or manage AWS compute resources.
license: Complete terms in LICENSE.txt
---

## When to use this skill

Use this skill whenever the user wants to:
- [待完善:根据具体工具添加使用场景]

## How to use this skill

[待完善:根据具体工具添加使用指南]

## Best Practices

[待完善:根据具体工具添加最佳实践]

## Keywords

[待完善:根据具体工具添加关键词]

Overview

This skill provides hands-on guidance and actionable steps for working with AWS EC2. It covers instance creation, configuration, networking, security groups, key management, and routine EC2 operations. The guidance is practical, cloud-ops focused, and suitable for developers and operators managing AWS compute resources.

How this skill works

The skill inspects user needs and recommends EC2 instance types, AMIs, storage options, and networking settings based on workload characteristics. It walks through CLI and Console commands, Terraform snippets, IAM considerations, and security group rules to implement recommended configurations. The skill also helps troubleshoot common issues such as SSH access, instance reachability, and permission errors.

When to use it

  • You need to provision new EC2 instances for development, staging, or production.
  • You want to design or review security groups, VPC settings, or IAM roles for EC2.
  • You need help selecting instance types, AMI options, or EBS sizing.
  • You are automating EC2 deployments with scripts, Terraform, or CloudFormation.
  • You need to troubleshoot SSH connectivity, boot issues, or instance health.

Best practices

  • Choose instance families and sizes based on CPU, memory, and I/O requirements and prefer newer generations for cost-efficiency.
  • Use IAM roles for EC2 instead of embedding credentials; grant least privilege for attached roles.
  • Define security groups with minimal inbound rules and use bastion hosts or Session Manager for secure access.
  • Use EBS volume types according to performance needs and enable snapshots or automated backups.
  • Tag instances and resources consistently for cost allocation and lifecycle management.

Example use cases

  • Create a web server cluster: pick AMI, instance type, security group for HTTP/HTTPS, and attach an Auto Scaling Group.
  • Migrate a CPU-bound batch job: recommend compute-optimized instances and EBS throughput settings.
  • Harden an EC2 environment: lock down security groups, enforce IAM roles, and enable AWS Systems Manager.
  • Automate infra: provide Terraform module example to launch instances with user-data and EBS volumes.
  • Troubleshoot SSH failure: checklist for key pair, security group, network ACLs, and instance status checks.

FAQ

How do I securely access EC2 instances without opening SSH to the world?

Use AWS Systems Manager Session Manager, or restrict SSH to a trusted IP range and require a bastion host. Always use IAM roles and avoid key reuse.

Which instance type should I pick for a small web app?

Start with a burstable general-purpose instance (t3 or t4g) for cost-efficiency, monitor performance, and scale to compute-optimized or memory-optimized types if needed.