Posts

Postman API testing against Docker container

Image
Postman API testing against Docker container For an API Docker container on host port 5000.  Tip: 5000 maps to container's internal port 8080. You set the environment variables (without double braces): You set the actual exposed endpoint method for it. Tip: type the double braces twice and you will see all the environment variables and pick the one you want.  Tip:  this response is empty because no movies with Alpha in the title. You can also see it in Docker.  Tip: the question mark symbol is because EF Core redacts actual parameter values in its command logs by default (you'd need EnableSensitiveDataLogging() on the DbContext to see real values there) — it still shows the parameter names, types, and sizes, just masks the value for safety.
Post a Comment
Read more

ASP.NET Docker containers in AWS

  ASP.NET Docker containers in AWS     Integrating AI into a containerized .NET app on AWS creates a highly scalable, modern architecture. By leveraging AWS managed AI services (like Bedrock, SageMaker, Rekognition, or Polly) via the AWS SDK for .NET, you offload heavy ML compute to AWS while keeping your Docker containers lightweight. However, moving this architecture into a production-grade Docker and AWS environment introduces specific engineering challenges. Architecture Overview [ Frontend / Client ] │ (HTTPS) ▼ [ AWS ECS / EKS (Fargate) ] ──(VPC Endpoint)──► [ AWS AI Services ] └─► Docker Container (Bedrock, Rekognition, etc.) └─► ASP.NET Core API Application : ASP.NET Core Web API running the official .NET 8 or .NET 9 runtime. Container : Docker images deployed to ECS (Elastic Container Service) or EKS (Elastic Kubernetes Service) using Fargate (serverless containers). AI Layer : The .NET application interac...
Post a Comment
Read more