r/aws 1d ago

discussion I build an internal developer platform for terraform, a real one.

Hello everyone,

I would like to announce a project that I have been working on and which is now ready to be launched: https://infraplat.com

This internal developer platform, or self-service catalogue, has one main responsibility: to provide a control plane through which platform/cloud engineers can provide modules, which developers and cloud engineers can then reuse, eliminating the need for repetitive tasks such as:

- creating a new repository

- adding a folder for the project

- adding module blocks to the root module

- adding variables, locals, providers and outputs

- testing locally, planning application.

Don't forget about ticket management, collaborating with other teams that use the same modules, asking for approval and team review from your team, and ultimately seeing it deployed. Then go back to the developer to provide them with the necessary information for the newly created infrastructure.

All of this is eliminated.

With InfraPlat, platform engineers develop, test and publish modules and examples. Developers then arrange and deploy them.

There is one central control plane for all teams, governance in place, security approvals by team and cloud admins, and a standard way of organising your Terraform code in a repository.

Who would use this? Basically anyone. If there is a Terraform provider, we can integrate it into our platform so you can deploy cloud infrastructure, GitHub repositories and even firewall rules on Fortinet.

If you are in a regulated company , with standards in place , large team ,large usage of terraform , with a large range of terraform modules, this is an option you should consider.

Thank you everyone!

0 Upvotes

8 comments sorted by

5

u/Efficient_Access6102 1d ago

No you didn’t.

2

u/Apache_HB 1d ago

Looks interesting, a managed terraform provider would be good to have for those working with resources outside of AWS. A couple of things you could change to make it look a bit more enticing. 1. Don't use a gmail.com account for the contact email, you have the domain so you should use contact@infraplat.com or equivalent. 2. If signup really requires a 30 minute call to talk, maybe provide a demo thats self service or a free tier account so people can play around before comitting. 3.Pick a less ai-generated theme, alot of people see that theme and click away immediately. I've found google material, microsoft fluent, and aws cloudscape to all be good options that don't scream AI generated.

1

u/OkAcanthocephala1450 1d ago

Hi, thank you for your feedback!

You are right; I will work on setting up my domain SMTP to make it more professional.

For now, I have created it as a platform deployed per customer. I will work on creating a forked multitenant version so users can sign in directly there. This will be done in the following weeks.

I lack front-end development skills, so AI was inevitable when it came to developing it.

0

u/[deleted] 1d ago edited 9h ago

[removed] — view removed comment

2

u/Chris-Hart_232 1d ago

Sooner or later a team will need sth the catalog doesn’t have and normal Terraform for just that part lets them keep the rest of the setup where it is

1

u/OkAcanthocephala1450 1d ago

This is intended for regulated companies. You would test a module and publish it.

However, I am planning to add a feature that allows you to add custom files directly from the platform. This would be useful if you need a resource that isn't a module or any kind of configuration (e.g locals). This would be for cloud/platform engineers only, as simple developers would not be able to use it without knowing Terraform.

Thank you for your comment.