

<feed xmlns="http://www.w3.org/2005/Atom">
  <id>/</id>
  <title>Rajesh Sitaraman</title>
  <subtitle>Rajesh Sitaraman - 👨🏻‍💻 ai architect AWS LLM RAG agentic ai building production grade gen ai solutions</subtitle>
  <updated>2026-04-01T21:22:13+00:00</updated>
  <author>
    <name>Rajesh Sitaraman</name>
    <uri>/</uri>
  </author>
  <link rel="self" type="application/atom+xml" href="/feed.xml"/>
  <link rel="alternate" type="text/html" hreflang="en"
    href="/"/>
  <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator>
  <rights> © 2026 Rajesh Sitaraman </rights>
  <icon>/assets/img/favicons/favicon.ico</icon>
  <logo>/assets/img/favicons/favicon-96x96.png</logo>


  
  <entry>
    <title>Benchmarking Amazon Bedrock LLM Latency: A Multi-Model Comparison</title>
    <link href="/posts/bedrock-model-benchmark/" rel="alternate" type="text/html" title="Benchmarking Amazon Bedrock LLM Latency: A Multi-Model Comparison" />
    <published>2026-04-01T00:00:00+00:00</published>
  
    <updated>2026-04-01T00:00:00+00:00</updated>
  
    <id>/posts/bedrock-model-benchmark/</id>
    <content src="/posts/bedrock-model-benchmark/" />
    <author>
      <name>Rajesh Sitaraman</name>
    </author>

  
    
    <category term="aws" />
    
    <category term="ai" />
    
  

  
    <summary>
      





      
  disclaimer: This post focuses strictly on inference latency, not model quality, accuracy, or reasoning performance. A model that responds in 400ms is not “better” than one that responds in 2 seconds. It is simply faster to start streaming tokens. The right model for your use case depends on many factors beyond latency. This benchmark measures one thing: how quickly each model delivers its fi...
    </summary>
  

  </entry>

  
  <entry>
    <title>The Curious Case of SSE Streaming Agent Responses on AWS Lambda</title>
    <link href="/posts/the-curious-case-of-sse/" rel="alternate" type="text/html" title="The Curious Case of SSE Streaming Agent Responses on AWS Lambda" />
    <published>2026-02-15T00:00:00+00:00</published>
  
    <updated>2026-03-22T19:55:21+00:00</updated>
  
    <id>/posts/the-curious-case-of-sse/</id>
    <content src="/posts/the-curious-case-of-sse/" />
    <author>
      <name>Rajesh Sitaraman</name>
    </author>

  
    
    <category term="aws" />
    
    <category term="ai" />
    
  

  
    <summary>
      





      
  This article was originally published on the AWS Builder Center.


The Setup
We built a service that runs LLM inference on AWS and streams results back to clients in real-time using Server-Sent Events (SSE). Think of any chat-style LLM application the user submits a prompt, and tokens appear progressively as the model generates them, rather than waiting for the entire response to complete.

...
    </summary>
  

  </entry>

  
  <entry>
    <title>Simple guide for RAG using Strands Agents and Amazon S3 Vectors</title>
    <link href="/posts/simple-guide-for-rag-using-strands/" rel="alternate" type="text/html" title="Simple guide for RAG using Strands Agents and Amazon S3 Vectors" />
    <published>2025-09-12T00:00:00+00:00</published>
  
    <updated>2026-03-17T17:34:47+00:00</updated>
  
    <id>/posts/simple-guide-for-rag-using-strands/</id>
    <content src="/posts/simple-guide-for-rag-using-strands/" />
    <author>
      <name>Rajesh Sitaraman</name>
    </author>

  
    
    <category term="aws" />
    
    <category term="ai" />
    
  

  
    <summary>
      





      
  This article was originally published on the AWS Builder Center.


Intro
This guide demonstrates how to build a RAG (Retrieval-Augmented Generation) system using Strands Agents and Amazon’s latest S3 Vectors service. You’ll learn to set up AWS Bedrock Knowledge Base, create vector storage for document embedding, and implement metadata filtering for precise information retrieval. We’ll walk t...
    </summary>
  

  </entry>

  
  <entry>
    <title>Browser Use Agent with Amazon Bedrock</title>
    <link href="/posts/browser-use-agent-with-amazon-bedrock/" rel="alternate" type="text/html" title="Browser Use Agent with Amazon Bedrock" />
    <published>2025-03-31T00:00:00+00:00</published>
  
    <updated>2026-03-22T19:56:19+00:00</updated>
  
    <id>/posts/browser-use-agent-with-amazon-bedrock/</id>
    <content src="/posts/browser-use-agent-with-amazon-bedrock/" />
    <author>
      <name>Rajesh Sitaraman</name>
    </author>

  
    
    <category term="ai" />
    
    <category term="aws" />
    
  

  
    <summary>
      





      
  This article was originally published on the AWS Builder Center.


AI-powered automation is changing how we interact with the web, but most solutions are either too complex or too rigid. Meet Browser Use, a simple yet powerful tool that lets AI agents seamlessly interact with websites. It extracts HTML, navigates elements, and supports multi-step workflows all with an intuitive API.

Now, im...
    </summary>
  

  </entry>

  
  <entry>
    <title>Using the AWS CDK Custom Resource Provider Framework</title>
    <link href="/posts/aws-cdk-custom-resource/" rel="alternate" type="text/html" title="Using the AWS CDK Custom Resource Provider Framework" />
    <published>2023-01-09T00:00:00+00:00</published>
  
    <updated>2026-03-15T04:41:43+00:00</updated>
  
    <id>/posts/aws-cdk-custom-resource/</id>
    <content src="/posts/aws-cdk-custom-resource/" />
    <author>
      <name>Rajesh Sitaraman</name>
    </author>

  
    
    <category term="aws" />
    
  

  
    <summary>
      





      
  “The information provided in this blog post is generated by ChatGPT, a machine learning model trained on a dataset of text. The views and opinions expressed in this post are solely those of the model and do not reflect the views of the creators or any individual associated with the training of the model. The information provided in this post is for general informational purposes only and is ...
    </summary>
  

  </entry>

</feed>


