Skip to content
The Chat Archive
claude-3-5-haiku-20241022· Anthropic LMArena Human Preference 140K

can you prepare some examples for ec2, lambda, eventbridge, eni, igw and so on

  1. User

    can you prepare some examples for ec2, lambda, eventbridge, eni, igw and so on

  2. Assistant

    I'll provide naming examples for each AWS service, following the universal template: <Org>-<Proj>-<Env>-<Region>-<Service>-<ResourceType>-<Identifier>

    EC2 Resources

    # Instances
    acme-webshop-prod-us-east-1-ec2-inst-web-01
    nasa-datapipeline-dev-us-west-2-ec2-inst-worker-02
    
    # Security Groups
    acme-webshop-prod-us-east-1-ec2-sg-web-access
    nasa-analytics-stg-eu-west-1-ec2-sg-data-processing
    
    # Elastic Network Interfaces (ENI)
    acme-webshop-prod-us-east-1-ec2-eni-frontend-lb
    nasa-research-dev-us-west-2-ec2-eni-backend-cluster
    

    Lambda Functions

    # Function Names
    acme-payments-prod-us-east-1-lambda-func-checkout-processor
    nasa-satellite-dev-us-west-2-lambda-func-data-ingestion
    
    # Layer Names
    acme-common-prod-us-east-1-lambda-layer-utils
    nasa-ml-stg-eu-central-1-lambda-layer-tensorflow
    

    EventBridge Resources

    # Event Buses
    acme-ecommerce-prod-us-east-1-eventbridge-bus-main
    nasa-telemetry-dev-us-west-2-eventbridge-bus-satellite
    
    # Rules
    acme-inventory-prod-us-east-1-eventbridge-rule-stock-update
    nasa-mission-stg-eu-west-1-eventbridge-rule-sensor-alert
    

    Network Infrastructure

    # Internet Gateway (IGW)
    acme-webshop-prod-us-east-1-vpc-igw-main
    nasa-research-dev-us-west-2-vpc-igw-secondary
    
    # VPC
    acme-webshop-prod-us-east-1-vpc-network-main
    nasa-analytics-stg-eu-central-1-vpc-network-data
    
    # Subnets
    acme-webshop-prod-us-east-1-vpc-subnet-public-a
    nasa-research-dev-us-west-2-vpc-subnet-private-b
    
    # Network ACLs
    acme-webshop-prod-us-east-1-vpc-nacl-web-tier
    nasa-mission-stg-eu-west-1-vpc-nacl-restricted
    

    Additional Complex Examples

    # Multi-tier Web Application
    acme-webshop-prod-us-east-1-ec2-asg-frontend
    acme-webshop-prod-us-east-1-ec2-asg-backend
    acme-webshop-prod-us-east-1-rds-cluster-userdb
    acme-webshop-prod-us-east-1-elasticache-redis-session
    
    # Scientific Research Infrastructure
    nasa-climate-dev-us-west-2-lambda-func-data-processor
    nasa-climate-dev-us-west-2-s3-bucket-raw-data
    nasa-climate-dev-us-west-2-eventbridge-rule-data-arrival
    nasa-climate-dev-us-west-2-sns-topic-alert-system
    

    Pro Tips for Naming

    1. Be consistent
    2. Include environment (dev/stg/prod)
    3. Include region for multi-region setups
    4. Use meaningful identifiers
    5. Keep names under 64 characters
    6. Use lowercase
    7. Use hyphens as separators

    Common Mistakes to Avoid

    ❌ WebShopProductionServer ❌ nasa_research_database ❌ ec2-instance-with-very-long-descriptive-name-that-exceeds-recommended-length

    ✅ acme-webshop-prod-us-east-1-ec2-inst-web-01 ✅ nasa-research-dev-us-west-2-rds-cluster-main

    Recommendation

    • Create a naming convention document
    • Use Infrastructure as Code (Terraform/CloudFormation) to enforce
    • Consider using AWS Config rules to validate resource names

    Would you like me to elaborate on any specific naming strategy or provide more detailed examples for a particular service?

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.