메인 콘텐츠로 건너뛰기AWS Startups
  1. 프롬프트 라이브러리
  2. GitHub 리포지토리 배포

GitHub 리포지토리 배포

GitHub 리포지토리가 있습니까? 이 프롬프트를 사용하면 AWS에 배포하는 데 도움이 됩니다.

  • GitHub Integration
  • 지속적 통합

프롬프트

# GitHub Repository AWS Deployment Analysis
<instruction>
I will analyze the following extracted context and provide a comprehensive response based on its content. Please read the information carefully before proceeding with my analysis.
</instruction>
<context>
I have an existing GitHub repository that I want to deploy to AWS using the most efficient and cost-effective services. Please analyze my repository and recommend the optimal AWS architecture.
Repository Information:
GitHub URL: [Replace with your actual repository URL]
Primary Language/Framework: [e.g., Node.js, Python Flask, React, etc.]
Application Type: [e.g., web app, API, static site, microservice, etc.]
Current Infrastructure: [Describe any existing Docker, Terraform, CloudFormation, or deployment configs]
Analysis Requirements:
Please analyze my repository and determine:
Application architecture and dependencies
Database requirements (if any)
Static assets and frontend needs
API endpoints and backend services
Existing infrastructure as code (if present)
Build and deployment requirements
Deployment Preferences:
Cost Optimization: Prioritize AWS Free Tier and cost-effective services
Serverless First: Prefer serverless solutions unless specific requirements dictate otherwise
Managed Services: Use AWS managed services to reduce operational overhead
Auto-Scaling: Implement auto-scaling based on demand
Security: Follow AWS security best practices and least privilege access
Performance & Scale Requirements:
Expected Traffic: [e.g., 1000 users/month, 10k requests/day, etc.]
Geographic Distribution: [e.g., US-only, global, specific regions]
Performance Targets: [e.g., <2s page load, 99.9% uptime]
Scaling Needs: [e.g., handle traffic spikes, steady growth expected]
Budget Constraints:
Monthly Budget: [e.g., under $50, $100-200, etc.]
Cost Monitoring: Set up billing alerts and cost tracking
Optimization: Recommend cost optimization strategies
Please provide a comprehensive AWS deployment strategy that maximizes efficiency, minimizes costs, and follows AWS Well-Architected principles. Include specific service recommendations based on my repository's actual structure and requirements.
</context>
Based on the extracted context above, I will provide a clear, accurate, and relevant response that directly addresses the information presented. My analysis will be thorough while remaining focused on the key points contained in the context.
Please provide your response based solely on the information in the extracted context, without adding external information or making assumptions beyond what is explicitly stated. Present your answer in a concise format without unnecessary preamble or explanations.

어떻게 사용하나요?

베타

  1. AWS 환경 및 비용 관리 설정
  2. AWS CLI 설치
    • 운영 체제에 맞는 AWS CLI을(를) 다운로드하여 설치합니다.
  3. 프롬프트 복사
    • ‘프롬프트 복사’를 클릭하여 프롬프트를 클립보드에 복사합니다.
  4. 프롬프트 테스트
    • 프롬프트를 AI 도구(예: Q Developer CLI)에 붙여넣고 실행하여 결과를 생성합니다.
  5. 검토, 배포 및 모니터링
    • 생성된 리소스와 예상 비용을 검토합니다.
    • 우선 개발 환경에 배포합니다.
    • 프로덕션으로 전환하기 전에 성과와 지출을 모니터링하세요.

이러한 프롬프트를 사용하면 고지 사항에 동의하는 것으로 간주됩니다.