This insight was synthesized by AI from public community discussions. We do not display original user posts or comments verbatim—all content has been rewritten and aggregated. Verify before acting on it.
Custom Terraform Provider for AWS Amplify GitHub Apps
A specialized open-core Terraform provider that properly manages AWS Amplify GitHub App connections, including callback URLs, secrets, and webhook configuration. The provider fills the exact gap left by the official AWS provider, with a free community edition and a paid Pro tier for team management and multi-account support.
Why this matters
You manage AWS Amplify apps with Terraform across multiple environments. Every new app your team creates defaults to a deprecated OAuth connection, and you must manually switch each one to the GitHub App in the AWS Console. You tried every Terraform configuration option — removing tokens, toggling auto-branch creation — nothing works. You searched CloudFormation and AWS CLI for alternatives but found none. The official provider has had this gap for three years. You just want your Terraform apply to result in a properly connected Amplify app without a follow-up manual step, and you are willing to adopt a custom provider if it solves this cleanly.
- · Built for DevOps teams and platform engineers using Terraform to manage AWS Amplify applications who need GitHub App connections instead of deprecated OAuth, particularly teams managing multiple apps across multiple environments.
- · Most likely monetization: Freemium with open-core provider and paid Pro features.
The Pain · Narrative
You manage AWS Amplify apps with Terraform across multiple environments. Every new app your team creates defaults to a deprecated OAuth connection, and you must manually switch each one to the GitHub App in the AWS Console. You tried every Terraform configuration option — removing tokens, toggling auto-branch creation — nothing works. You searched CloudFormation and AWS CLI for alternatives but found none. The official provider has had this gap for three years. You just want your Terraform apply to result in a properly connected Amplify app without a follow-up manual step, and you are willing to adopt a custom provider if it solves this cleanly.
Score Breakdown
Market Signal
Go-to-Market
DevOps engineers at startups and mid-size companies running 5+ AWS Amplify apps with GitHub, managed through Terraform, who have hit this exact issue
~5,000 teams globally are directly affected by this specific Amplify GitHub App gap
GitHub marketplace listing and direct engagement on the open issue thread
$29/month Pro tier per organization, free community edition for individual use
50 GitHub stars and 5 paying Pro users within 30 days of provider release
MVP Scope · 1–2 weeks
- Investigate AWS Amplify API for GitHub App connection endpoints by capturing Console API calls
- Scaffold a custom Terraform provider in Go using the Terraform Plugin Framework
- Implement a basic resource type for Amplify GitHub App connection with create and read operations
- Write integration tests against a sandbox AWS account with a test Amplify app
- Publish the provider to the Terraform Registry as a community provider
- Implement update and delete operations for the GitHub App connection resource
- Add resource import functionality for existing manually-configured Amplify apps
- Build a simple licensing server for Pro tier feature gating
- Create documentation site with quickstart, examples, and troubleshooting guide
- Post the provider to the open GitHub issue thread to gather early adopters
Differentiation
Why This Might Fail
Self-rebuttal — the most important trust signal
- 1The AWS Amplify API may not expose GitHub App connection creation programmatically — if the Console uses an internal endpoint or browser-based flow, the provider cannot replicate the behavior without fragile automation that breaks on AWS UI changes.
- 2Open-core freemium Terraform providers struggle with monetization because the community edition may fully solve the problem, leaving no compelling reason to upgrade to the paid tier.
- 3If HashiCorp ships this feature in the official AWS provider, the custom provider becomes instantly redundant and loses its entire user base overnight.
Evidence Summary
How AI synthesized this insight — no verbatim quotes
Roughly 6 commenters confirmed every Amplify app provisioned through Terraform requires manual switching to GitHub App connections. One user specifically analyzed the root cause, noting that a new resource type would be needed because GitHub App connections are coupled with callback URLs and secrets that no existing Terraform resource handles. The 3-year unresolved status of the issue and explicit requests for any workaround via alternative IaC tools indicate users would adopt a custom provider that solves this cleanly.
Action Plan
Validate this opportunity before writing code
Recommended Next Step
Build
Strong demand signals detected. Real pain, real willingness to pay — start building an MVP.
Landing Page Copy Kit
Ready-to-paste copy based on real Reddit community language — no editing required
Headline
Custom Terraform Provider for AWS Amplify GitHub Apps
Sub-headline
A specialized open-core Terraform provider that properly manages AWS Amplify GitHub App connections, including callback URLs, secrets, and webhook configuration. The provider fills the exact gap left by the official AWS provider, with a free community edition and a paid Pro tier for team management and multi-account support.
Who It's For
For DevOps teams and platform engineers using Terraform to manage AWS Amplify applications who need GitHub App connections instead of deprecated OAuth, particularly teams managing multiple apps across multiple environments
Feature List
✓ Custom Terraform resource for Amplify GitHub App connection creation ✓ Automatic callback URL and secret management ✓ Resource import for existing Amplify apps with manual GitHub App connections ✓ State reconciliation between Terraform and actual AWS configuration ✓ Pro tier: multi-account support, team access controls, audit logging
Where to Validate
Share your landing page in r/GitHub · hashicorp/terraform-provider-aws — that's exactly where these pain points were discovered.
Sign up to unlock full deep analysis
GTM, MVP scope, why-it-might-fail, ActionPlan Copy Kit. Free signup grants 10 detail views/month.
Other opportunities in the same theme
Auto-clustered by AI from related discussions