Skip to content
DevMeme
6991 of 7435
AWS Infrastructure as React JSX: Terraform Generation via Component Syntax
AWS Post #7663, on Jan 30, 2026 in TG

AWS Infrastructure as React JSX: Terraform Generation via Component Syntax

Description

A product landing page screenshot for a tool branded 'Infrastructure as Code, Reimagined' that lets users write AWS infrastructure definitions using React JSX with Tailwind-inspired className syntax and generates production-ready Terraform. The dark-themed page features the headline 'AWS infrastructure as <React/>' with React in green and the closing tag in orange. Below are 'Open Studio' (orange button) and 'View on GitHub' buttons. A code editor shows a file 'infrastructure.jsx' with status 'Ready to deploy', containing JSX components like <Infrastructure>, <VPC className="cidr-10.0.0.0/16 region-us-east-1">, <RDS className="engine-postgres multi-az" />, <Fargate className="mem-2gb cpu-1 port-8080" />, and <Lambda className="runtime-nodejs22" />. Output shows generated Terraform files: main.tf, variables.tf, outputs.tf, backend.tf

Comments

31
Anonymous ★ Top Pick Finally, frontend developers can provision infrastructure without learning anything new -- just slap className on it and pray the Terraform plan doesn't have 47 resources to destroy
  1. Anonymous ★ Top Pick

    Finally, frontend developers can provision infrastructure without learning anything new -- just slap className on it and pray the Terraform plan doesn't have 47 resources to destroy

  2. @kkirisora 5mo

    PH-ahhh color scheme

    1. dev_meme 5mo

      Because we, eh, LOVE to work with infra!

      1. @kkirisora 5mo

        no. in aws you don't love to work with infra. infra loves to work you;)

  3. @darkelink 5mo

    https://www.react2aws.xyz/

  4. @Strangerx 5mo

    I have strong flashbacks of XML-like CloudFormation notation

    1. Adam G 5mo

      Precisely

  5. @Strangerx 5mo

    <Comment mode="well-actually"> An entire infrastructure cannot, in general, be correctly modeled as a rooted ordered directed tree; it is more accurately represented as a directed acyclic graph (DAG). </Comment>

    1. @Algoinde 5mo

      i see you're using xml not in the spirit of the spec, that would be <comment mode="well-actually"> thank you very much

      1. @Strangerx 5mo

        Rewritten in jsx👌 Thanks for review!

        1. @Algoinde 5mo

          jsx would imply there's js, this is just x(ml)

    2. Adam G 5mo

      Based

    3. @pavlus_0 5mo

      You have ids to link to other nodes

      1. @Strangerx 5mo

        exactly so you end up with plain resources list linked with ids, which isn't that nice https://t.me/dev_meme/7663?comment=186254

        1. @pavlus_0 5mo

          It's a solved problem if you have an editor made in this century and has "highlight occurrences" function and/or "go-to next". Also, if you can recreate an HTML page from JSX, you can highlight related nodes on hover/click.

          1. @Strangerx 5mo

            It is solved for json, yaml and even hcl using this-century-made editor, no need to get backward step into xml notation, lmao

            1. @pavlus_0 5mo

              HCL sucks, actually.

              1. @Strangerx 5mo

                ur mom tried it once, came back somewhat satisfied idk what else to say here

                1. @pavlus_0 5mo

                  I see you work for HashiCorp

          2. @Strangerx 5mo

            we can, but for what reason?

            1. @Algoinde 5mo

              you can represent a DAG with a single protobuf string encoded in base64, doesn't make it good DX at all i think people sleep on visual tools, because visual tools all have a million issues and not enough flexibility

              1. @Algoinde 5mo

                so we have weird schemas which try to encode relationship information in a fundamentally linear text format

                1. @Algoinde 5mo

                  also fucking directed graphs, i recently finished reading several chapters of a book on graph theory to make this shit

                2. @Strangerx 5mo

                  visual tools have only one fundamental issue — they are all visuals

                  1. @Algoinde 5mo

                    text is also visual if you think about it

  6. @Strangerx 5mo

    isn't that nice, huh?

  7. @H3R3T1C 5mo

    this is one of these moments that i think that the humanity needs to be hit by a meteorite

  8. @hy60koshk 5mo

    • You already know jsx, thus you should know js, which implies you know json • Visual hierarchy - Nested components show relationships at a glance - as long as you're not brainwashed by google and use 4-space-sized indentation in your json (or got your eyes trained for 2 spaces, whatever) • Semantically relevant property names in your config • Instant feedback - because what can possibly be easier to parse by js (which, in turn, will generate the output) than js-fucking-object-notation

  9. Adam G 5mo

    Literally XML

  10. @Algoinde 5mo

    it really isn't, but I wanted to have full mental model of the mathematical concept

  11. @Algoinde 5mo

    https://beta.enka.network/endfield/aic/

Use J and K for navigation