# AWS Ec2 > Comprehensive skill for managing and deploying AWS EC2 instances, including scaling, security group configuration, and SDK usage examples. - Skill: `paulpas/aws-ec2` (Agent Skill) - Install (CLI): `npx skillmds@latest add paulpas/aws-ec2` - Raw SKILL.md: https://api.skillmd.com/api/skills/paulpas/aws-ec2/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: DevOps & Infra - License: MIT - Author: paulpas (https://skillmd.com/u/paulpas) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/paulpas/aws-ec2 --- \ndescription: Comprehensive skill for managing and deploying AWS EC2 instances, including scaling, security group configuration, and SDK usage examples. license: MIT compatibility: opencode metadata: version: "1.0.0" domain: cncf triggers: aws ec2, ec2 instances, aws sdk, scaling, security groups, instance management archetypes: - educational - tactical related-skills: aws-iam, aws-sdk, aws-s3 output-format: code role: implementation scope: infrastructure --- # AWS EC2 Management Skill Deploy, configure, and manage Elastic Compute Cloud (EC2) instances on AWS with scalable architectures and rigorous security practices. This skill will cover: ## TL;DR Checklist - [ ] Choose the appropriate EC2 instance types for workloads. - [ ] Implement Auto Scaling Groups for managing instance scaling. - [ ] Configure security groups with the principle of least privilege. - [ ] Understand how to manage instances using the AWS SDK (Boto3). --- ## Purpose and Use Cases * **Primary Purpose**: Provide scalable computation capacity in the cloud while allowing users to manage infrastructure through comprehensive SDK usage. * **Common Use Cases**: 1. Hosting web applications in a highly available configuration. 2. Running background processing workloads and batch jobs. 3. Developing and testing applications in scalable environments. 4. Implementing data analytics workflows using compute clusters. --- ## Architecture Design Patterns ### Pattern 1: Launch and Manage EC2 Instances ```python import boto3 from botocore.exceptions import ClientError def launch_instance(ami_id, instance_type='t2.micro', key_name='my-key', security_group='my-sg'): ec2 = boto3.resource('ec2') try: instance = ec2.create_instances( ImageId=ami_id, MinCount=1, MaxCount=1, InstanceType=instance_type, KeyName=key_name, SecurityGroups=[security_group] ) print(f'Instance created: {instance[0].id}') # Log instance ID return instance[0].id except ClientError as e: print(f'Error occurred: {e}') # Example usage launch_instance('ami-12345678', 't2.micro', 'my-key', 'my-sg') ``` ### Pattern 2: Configure Security Groups ```python def create_security_group(group_name, description, vpc_id): ec2 = boto3.client('ec2') try: response = ec2.create_security_group(GroupName=group_name, Description=description, VpcId=vpc_id) sg_id = response['GroupId'] print(f'Security Group {sg_id} created successfully') return sg_id except ClientError as e: print(e) # Example usage create_security_group('MySecurityGroup', 'My security group for EC2 instances', 'vpc-12345678') ``` ### Pattern 3: Scaling EC2 Instances with Auto Scaling ```yaml AWSTemplateFormatVersion: '2010-09-09' Resources: LaunchConfiguration: Type: AWS::AutoScaling::LaunchConfiguration Properties: ImageId: ami-12345678 InstanceType: t2.micro SecurityGroups: - my-sg KeyName: my-key AutoScalingGroup: Type: AWS::AutoScaling::AutoScalingGroup Properties: LaunchConfigurationName: !Ref LaunchConfiguration MinSize: 1 MaxSize: 10 DesiredCapacity: 2 VPCZoneIdentifier: - subnet-12345678 Tags: - Key: Name Value: MyEC2Instance PropagateAtLaunch: true ScalingPolicy: Type: AWS::AutoScaling::ScalingPolicy Properties: AutoScalingGroupName: !Ref AutoScalingGroup PolicyType: SimpleScaling ScalingAdjustment: 1 Cooldown: 300 ``` --- ## Integration Approaches 1. **Load Balancing**: EC2 instances can be integrated with Elastic Load Balancing (ELB) for optimized routing of traffic. 2. **Auto Scaling**: Use Auto Scaling Groups to automatically adjust capacity based on load. 3. **CloudWatch Monitoring**: Monitor EC2 metrics with CloudWatch to ensure performance and health. 4. **IAM Roles**: Use IAM to define permissions for EC2 instances securely. --- ## Common Pitfalls ### ❌ Misconfigured Security Groups **Solution**: Always configure security groups with the principle of least privilege and routinely audit them. ### ❌ Indiscriminate Scaling **Solution**: Tune your Auto Scaling policies carefully to match your application load patterns. ### ❌ Not Using Tags **Solution**: Tag instances for better resource management and reporting. --- ## Best Practices - **Select the Right Instance Type**: Use the right instance types based on workload requirements. - **Scale Wisely**: Always implement Auto Scaling for production workloads to handle changes in traffic. - **Monitor**: Utilize CloudWatch for real-time monitoring and alarms on the health of EC2 instances. - **Optimize Costs**: Regularly analyze your usage and consider using Reserved Instances or Spot Instances for cost savings. --- ## Conclusion Using AWS EC2 enables powerful cloud-based computing at scale. This skill provides essential patterns and practices to manage and deploy EC2 instances effectively. --- --- ## Constraints ### MUST DO - Configure all AWS resources with explicit tagging for cost allocation, ownership tracking, and compliance - Use AWS SDK (Boto3) typed clients instead of resource API where type safety matters — prefer client() over resource() - Implement error handling that distinguishes between retryable (Throttling, RequestLimitExceeded) and non-retryable errors - Use IAM roles with least-privilege policies scoped to specific actions and resources, never wildcard permissions ### MUST NOT DO - Do not hardcode AWS credentials — use IAM roles, environment variables, or AWS Secrets Manager - Avoid unencrypted S3 buckets or RDS instances in production without explicit KMS encryption configuration - Never launch EC2 instances without specifying a security group and subnet — always use VPC networking explicitly - Do not use the default endpoint region — always specify the target region explicitly in all SDK calls ## Live References > Authoritative documentation links for this skill's domain. The model follows markdown links at load time to resolve external references and inline content. - [Primary Documentation](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-launch-wizard.html) - [API Reference or Getting Started](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html) - [Configuration Guide](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instancedata-data-retrieval.html) - [Best Practices](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-security-groups.html) - [Common Patterns or Tutorials](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/monitoring-instances-consoles.html)