-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Create a CLI to run or deploy any Streamlit POC #327
Comments
The new CLI has been developed and now I'm going through each POC to identify what (if any) additional resources the POC would need to run locally or deployed. For example, Amazon Bedrock + Amazon RDS - it would require RDS deployment/configuration. I'm adding the additional resources to the The design will allow the extended resources to be synthesized with the base POC stack or, if running locally only, deploy only the extended resources, without deploying the streamlit POC. The CLI can also be used to destroy any of the deployed POCs in CloudFormation. New documentation will be developed to cover running the CLI, and update the READMEs in each POC to reflect usage of the CLI. Additionally, contribution documentation needs to be updated to reflect the new functionality surrounding CDK deployments and extensions. New architecture documentation will be developed to describe the core POC deployed architecture. Any POC extensions should also contain extension architecture. |
To help users get a POC up and running quickly, creating a unified Command Line Interface (CLI) with simple commands can ease efforts and make learning about Amazon Bedrock easier.
Additionally, many customer want the option to deploy a POC to a sandbox environment and allow a team to access the POC. To support this, a base CDK Construct should be developed for deploying Streamlit POC to ECS Fargate with Load Balancing.
For POCs that require additional resources for functionality (S3, RDS, Redshift) a secondary construct should be defined within the POC, extending a base construct or abstract class (TBD). The goal is to both validate any required configurations (e.g. if there are existing resources being used, have those arns been provided) and deploy any resources that are needing creation/deployment.
The CLI should also handle any additional configurations specific to the POC, ensuring the constructs are fully defined.
This issue should be based from #326, as projen will be required to help ensure consistency of new POCs and deployable resources.
The text was updated successfully, but these errors were encountered: