Teams struggle to move secrets safely between AWS and Kubernetes
Kubernetes operators report having to extract AWS Secrets Manager key/value pairs and list them individually in configuration, then update that configuration when the secret changes. A related Terraform request describes a different risk: reading Kubernetes secrets through a data source puts their values in Terraform state. Together, these signals point to friction in infrastructure secret handling, though the AWS-to-Kubernetes sync pain is the clearest repeated need.
For kubernetes and Terraform operators. Mentioned from Aug 2021 to Jan 2025 on GitHub.
4 different people described this problem in 2 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 6.5/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
We have the same use case and struggling since very long time. Any clue or reference would be appreciated please !
Same here, it's really painful to sync by hand and extract every key from Secrets Manager JSON
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 5 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks