> For the complete documentation index, see [llms.txt](https://docs.graph.build/EGeX4aTAJLlpg9Hh8kfl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.graph.build/EGeX4aTAJLlpg9Hh8kfl/getting-started-tutorial/installation/aws/deploy-with-cloudformation/aws-marketplace-template/aws-marketplace-template-options.md). # AWS Marketplace Template Options Use one of the templates below to automatically deploy the Graph.Build platform components you need. Each template is preconfigured for a different use case. Image tags in the live templates use the current Marketplace / `:latest` channels (for example `studio-ui:latest` and `studio-node:aws_marketplace_latest`). Do not treat older version pins in screenshots or archived notes as authoritative. ### Studio Only Templates Lightweight Graph.Build Studio deployments for single-user or small team usage. #### What's Included: * Images: current Studio UI + Studio Node Marketplace tags * Instance Types: t3.medium to t3.xlarge * Infrastructure: Single ECS instance, Application Load Balancer, EFS storage * Networking: Public/private subnets (create new or use existing VPC) * Optional: SSH access, CloudFront for instant HTTPS Use Case: Standalone studio for data modelling and visualisation without transformers or graph database. ### Studio and Transformer Templates Graph.Build Studio with standalone transformer capabilities for data ingestion and processing without graph database connectivity. * marketplace-ss: Studio + Semi-Structured Transformer (JSON, CSV, XML processing) * marketplace-sql: Studio + SQL Transformer (relational database ingestion) * marketplace-ss-sql: Studio + Both Transformers (combined capabilities) #### What's Included: * Images: current Studio + transformer Marketplace tags * Instance Types: t3.xlarge or t3.2xlarge * Infrastructure: Single ECS instance, Application Load Balancer, EFS storage, S3 integration * Transformers: Standalone mode (no Kafka or graph-writer, output to S3) * Networking: Public/private subnets (create new or use existing VPC) * Optional: SSH access, CloudFront for instant HTTPS Use Case: Data ingestion and transformation workflows with studio interface, outputting processed data to S3 for later consumption. Studio and Semi-Structured Transformer\ Studio and SQL Transformer\ Studio, SQL Transformer and Semi-Structured Transformer\ ### Studio, Transformer, Kafka and Writer Templates Full Graph.Build pipeline with streaming architecture for real-time data ingestion and graph database integration. * marketplace-sql-writer: Studio + SQL Transformer + Kafka + Graph Writer * marketplace-ss-writer: Studio + Semi-Structured Transformer + Kafka + Graph Writer * marketplace-latest: Studio + both Transformers + Kafka + Graph Writer #### What's Included: * Images: current Studio, transformer, Kafka, and graph-writer Marketplace tags * Instance Types: t3.xlarge or t3.2xlarge * Infrastructure: Single ECS instance, Application Load Balancer, EFS storage, S3 integration * Data Pipeline: Transformer → Kafka → Graph Writer → configured graph database endpoint * Networking: Public/private subnets (create new or use existing VPC) * Optional: SSH access, CloudFront for instant HTTPS Use Case: End-to-end data transformation and graph database loading with a streaming message queue for reliable, scalable ingestion. Studio, SQL Transformer, Kafka, Graph Writer\ Studio, Semi Structured Transformer, Kafka, Graph Writer\ Studio, Semi Structured Transformer, SQL Transformer, Kafka, Graph Writer\