ProjectTech4DevAI / ProjectTech4DevAI/kaapi-backend
ECS Deploy: Fix resource prefix issue
@Ayush8923 is already working on this.
Since Sep 4, 2026.
- Dominant language
- Python
- Stars
- 18
- Forks
- 10
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 14
Description
Is your feature request related to a problem?
There is a mismatch in the AWS_RESOURCE_PREFIX and cluster-name during the staging ECS deploy workflow, causing failures and ambiguity due to multiple clusters.
Describe the solution you'd like
- Correct the
AWS_RESOURCE_PREFIXand cluster-name secrets to target the appropriate staging ECS cluster. - Verify that the deploy to staging ECS is successful.
Original issue
Context
During KMS v2 staging ECS validation, the deploy workflow failed on an AWS_RESOURCE_PREFIX / cluster-name mismatch — the workflow was targeting platform-staging names rather than the correct staging ECS cluster names.
There are two clusters (AI-platform-staging and kaapi-staging) with different DBs and secrets, which contributed to the ambiguity.
Acceptance Criteria
- Correct the
AWS_RESOURCE_PREFIX/ cluster-name secrets so the deploy workflow targets the correct staging ECS cluster. - Verify a clean deploy to staging ECS.
Owner: Prashant · This week
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.