Multi-Account AWS DevOps Agent Integration Failing due to 1:1 GitHub App Org Limit

[hugo-burke]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Apps

Body

Technical Context

We are implementing a multi-tenant AWS architecture for multiple distinct projects with repositories under a single GitHub Organization. Following AWS best practices, each project has a dedicated AWS DevOps Agent space inside its isolated Production account. This agent uses cross-account roles to manage that project's Dev, Test, and Stage environments.

The Problem

Since the projects are distinct, we want a single DevOps agent space per project, which needs its own independent connection to our shared GitHub Organization/Repository.

However, GitHub enforces a global 1:1 constraint for App installations per Organization. Once Project A successfully links its AWS CodeConnection, Project B is blocked from establishing its own independent connection because GitHub states the App is "already installed" at the Org level.

Questions

• Roadmap: Is support for multiple AWS DevOps Agent App installations (or multi-app registration patterns) per GitHub Organization currently in the pipeline?
• Alternative Patterns: Given the AWS best practice of having one DevOps Agent space per project, what is the recommended architectural workaround to maintain strict tenant isolation without resorting to cross-account resource sharing between completely different projects?

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐