✨ Extend Control Panel Parameter to include more use cases

[mshodge]

Describe the feature request.

At the moment, the SSM Parameter Store feature on the AP Control Panel is for Airflow jobs only. I would like to explore whether it is possible to extend this to other use cases. It would be beneficial to allow users to specify parameters for:

• API keys etc where users can add a parameter and give permissions for others (alpha users) to use it within their code too (current process might be to locally define secrets and keys in .env file for example, but they still need to send this key to colleagues if they want them to use it; AWS SSM Parameter Store would prevent accidental leak of keys). This can be done using S3 bucket currently, but this shouldn't be done that way ideally!
• Rotating keys for better security; as above, but instead of using static keys
• API authentication between systems; by giving an app who hosts an API end-point access to one part of a secret pair, and an app who uses that API end-point access to the other (as seen in ML deployments), we can secure the authentication of the API better. Especially if we can make use of rotating keys.

Describe the context.

No response

Value / Purpose

Required for improving security around API endpoints hosted on the Cloud Platform using Flask or FastAPI.

User Types

No response