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

How to just deploy matano in environments where cloud provisioning is guardrail-ed and controlled #172

Open
RVaidhy opened this issue Jul 31, 2023 · 3 comments

Comments

@RVaidhy
Copy link

RVaidhy commented Jul 31, 2023

Hi Matano Team,

We are trying to install Matano in our environment. Ours is a highly restricted environment so when we do matano init or deploy we are getting one or another permission issue. So is there a way we can create the required resources on our own and map it in any configuration file and make the init / deploy on our own ? Is it possible ? If so please let me know where can I find the configuration file details for the same. If not deploy matano in environments where cloud provisioning is guardrail-ed and controlled.

Thanks in advance. Anticipating your reply team.

@Samrose-Ahmed
Copy link
Contributor

Hi, Matano Open Source has a packaged self contained release. You can also build Matano from source. The deployment is done via the Matano CLI commands. This may or may not fit your environment's requirements, happy to accept a PR if you see a fix.

Our Matano Enterprise product has support for deployment using self managed Terraform.

@jiatann
Copy link

jiatann commented Aug 31, 2023

+1. Not having the ability to output terraform or CloudFormation resources that we can deploy ourselves is a major deal breaker for adopting or even trying out the open source version.

@fliphess
Copy link

fliphess commented Sep 10, 2023

I agree with @jiatann: A deployment method should not be reserved to enterprise: Please provide terraform deployment functionality for the OSS version too: I prefer to test Matano OSS before considering using an enterprise solution and in the current setup that is not possible.

As this is a security product, please consider support for environments that are actually using AWS security best-practises by not giving admin permissions to individual developers and users and restricts full admin access.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants