[chore][queue-service] ECS 배포 파이프라인 및 인프라 설정 추가

[rlaxxwls13]

🌱 설명

이 PR에서 어떤 작업을 했는지 간략하게 설명해주세요.

Queue Service를 AWS ECS에 배포하기 위한 CI/CD 파이프라인 및 인프라 설정을 추가했습니다.

📌 관련 이슈

이 PR과 연관된 이슈 번호를 작성해주세요. (이슈 없으면 생략 가능)

close #28

💻 커밋 유형

해당하는 항목에 x를 채워주세요.

• feat : 새로운 기능 추가
• fix : 버그 수정 (긴급 핫픽스 포함)
• refactor : 리팩토링
• chore : 빌드 설정, 의존성 업데이트 등
• docs : 문서 수정
• comment : 주석 추가 및 변경
• rename : 파일 / 폴더 이동 또는 이름 변경
• remove : 파일 삭제
• test : 테스트 코드 추가 / 수정

📝 체크리스트

PR 올리기 전에 아래 항목을 확인해주세요.

• develop 브랜치 기준으로 feature 브랜치를 생성했나요?
• 코드 컨벤션 및 스타일 가이드를 준수했나요?
• 관련 이슈와 연결했나요?
• 설명이 필요한 부분 / 어려운 부분 / 공유가 필요한 부분에 주석을 추가했습니다.
• 제가 작성한 코드를 스스로 리뷰했습니다.
• 기존 테스트와 충돌하지 않음을 확인했나요?

📚 추가 설명

리뷰어가 참고해야 할 내용, 첨부 이미지 등이 있다면 자유롭게 추가해주세요. (선택)

ECS Fargate IP 등록 이슈 사전 방지

ECS Fargate 환경에서는 Spring Cloud의 InetUtils가 컨테이너 IP를 선택할 때 ECS 메타데이터 IP(169.254.172.2, 모든 컨테이너 동일)를 우선 선택하는 경우가 있습니다. 이로 인해 Eureka에 잘못된 IP로 등록되어 다른 서비스가 호출 시 자기 자신을 호출하게 됩니다.

이를 방지하기 위해 application.yml에 RFC1918 사설 IP 대역(10.x, 172.x, 192.168.x)을 우선 선택하도록 설정했습니다.

spring:
  cloud:
    inetutils:
      preferred-networks:
        - 10\.
        - 172\.
        - 192\.168\.

CI/CD 통합

기존 ci.yml(빌드/테스트만)을 deploy.yml로 통합했습니다.

배포 검증 완료

• ✅ GitHub Actions 빌드 + ECR 푸시
• ✅ ECS Task 정상 시작
• ✅ Eureka에 정상 IP(172.31.x.x)로 등록
• ✅ Gateway 통해 Queue API 호출 동작

---

Summary by CodeRabbit

• Chores
  • 배포 파이프라인이 업데이트되었습니다.
  • 인프라 설정이 최적화되었습니다.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: first-ticket/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: e44d41ca-187c-4239-b138-32ed24be5955

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/28-deploy

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/deploy.yml:
- Around line 103-109: The ECS deploy step using
aws-actions/amazon-ecs-deploy-task-definition@v2 currently sets
wait-for-service-stability: false which skips post-deployment health
verification; either change the parameter to wait-for-service-stability: true in
the Deploy to ECS step (the aws-actions/amazon-ecs-deploy-task-definition@v2
action with task-definition: task-definition.json, service:
queue-service-service, cluster: first-ticket-cluster) to have the workflow wait
for service stability, or keep it false but add a separate post-deployment
validation job that pings the service / checks ECS task health and fails the
workflow on unhealthy results.
- Around line 33-109: Update the GitHub Actions steps that use older action
versions: change uses: actions/upload-artifact@v5 in the "Upload test report (on
failure)" step to actions/upload-artifact@v7 (current v7.0.1) and change uses:
docker/setup-buildx-action@v3 in the "Set up Docker Buildx" step to
docker/setup-buildx-action@v4 (current v4.0.0); keep the step names ("Upload
test report (on failure)" and "Set up Docker Buildx") and the surrounding YAML
unchanged so only the action version strings are bumped.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository: first-ticket/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: dc6b0b89-886e-44e3-b769-4258ce68a660

📥 Commits

Reviewing files that changed from the base of the PR and between 99fad9d and 859c0d8.

📒 Files selected for processing (3)

• .github/workflows/ci.yml
• .github/workflows/deploy.yml
• src/main/resources/application.yml

💤 Files with no reviewable changes (1)

• .github/workflows/ci.yml