<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Secrets Manager on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/secrets-manager/</link><description>Recent content in Secrets Manager on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 08 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/secrets-manager/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 14: Deploying to AWS ECS Fargate &amp;amp; Secrets Management</title><link>https://ai-blog.noorshomelab.dev/scalable-nodejs-api-platform/14-aws-ecs-fargate/</link><pubDate>Thu, 08 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/scalable-nodejs-api-platform/14-aws-ecs-fargate/</guid><description>&lt;h2 id="chapter-14-deploying-to-aws-ecs-fargate--secrets-management"&gt;Chapter 14: Deploying to AWS ECS Fargate &amp;amp; Secrets Management&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 14! So far, we&amp;rsquo;ve built a robust, containerized Node.js API. In this chapter, we take a significant leap towards production by deploying our application to a scalable, serverless environment: AWS Elastic Container Service (ECS) with Fargate. This move shifts our operational burden, allowing us to focus more on development rather than infrastructure management.&lt;/p&gt;
&lt;p&gt;Deploying to a cloud environment like AWS ECS Fargate is crucial for real-world applications. It provides high availability, scalability, and integration with other AWS services, ensuring our API can handle varying loads and remain resilient. We&amp;rsquo;ll leverage Fargate&amp;rsquo;s serverless compute engine to run our Docker containers without provisioning or managing servers. A critical aspect of production deployment is secure secrets management. We will integrate AWS Secrets Manager to handle sensitive environment variables like database credentials and API keys, ensuring they are never hardcoded or exposed.&lt;/p&gt;</description></item></channel></rss>