Skip to content
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

Add on-prem S3 to the use case as the default for s3 storage for any edge demo #70

Open
LaVLaS opened this issue Sep 11, 2023 · 3 comments
Labels
kind/enhancement New feature or request priority/normal An issue with the product; fix when possible

Comments

@LaVLaS
Copy link
Contributor

LaVLaS commented Sep 11, 2023

Instead of requiring paid S3 access for anyone who wants to run this demo, we should integrate an on-prem S3 service, like minio, to provide a self-contained demo environment that does not rely on external services. This would also help reduce any potential credential leaks when mutiple people attempt to deploy this use case in their environment.

As a parallel task, any AWS s3 buckets that are required for prepping an environment for the use should only be read-only access and treated a source repository for seeding the initial artifacts for a demo

@grdryn
Copy link
Member

grdryn commented Sep 12, 2023

This might make #57 unnecessary.

@LaVLaS
Copy link
Contributor Author

LaVLaS commented Sep 13, 2023

This might make #57 unnecessary.

I think we can host read-only, anonymous buckets for artifacts to be consumed as the initial seed for any use case. I think this would consist of binary objects that are not easily versioned by git. This issue is an attempt to ensure that a running use case does not require external S3 for these small use cases

@LaVLaS LaVLaS added the priority/high Important issue that needs to be resolved asap. Releases should not have too many o label Sep 13, 2023
@piotrpdev piotrpdev added the kind/enhancement New feature or request label Oct 5, 2023
@adelton
Copy link
Contributor

adelton commented Oct 13, 2023

Is this for the model storage, or for the ACM Observability?

@LaVLaS LaVLaS added priority/normal An issue with the product; fix when possible and removed priority/high Important issue that needs to be resolved asap. Releases should not have too many o labels Oct 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request priority/normal An issue with the product; fix when possible
Projects
Status: No status
Status: No status
Development

No branches or pull requests

4 participants