awslabs / awslabs/ssosync

Expand the Options for storing the sensitive parameters to include binary secrets and SSM Parameter Store

Open
#180 2 comments 1 reaction 0 assignees View on GitHub
enhancement
Dominant language
Go
Stars
666
Forks
213
Avg merge
1d 7h
Merged PRs (30d)
4

Description

**Is your feature request related to a problem? Please describe.**
Currently sensitive configuration data must be stored in AWS Secrets Manager secrets, however for some customers using SSM Parameter Store may be sufficient (since they do not need cross account/cross region support) and wish to reduce the operating cost of the SSOSync deployment.

**Describe the solution you'd like**
Add detection for and support of SSM parameter store secrets and binary secrets in Secrets Manager.

**Additional context**
Requests originally raised under the following issues:
- [SSOSync fails to get binary secrets #130](https://github.com/awslabs/ssosync/issues/130)
- [Allow use of Systems Manager Parameters instead of Secrets Manager Secrets #93](https://github.com/awslabs/ssosync/issues/93)

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the existing AWS Secrets Manager handling and the linked issues #130 and #93. The work is complete when SSM Parameter Store values and binary Secrets Manager secrets are detected and supported by SSOSync.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, go
Domain
cloud
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.