Tech Meridian ← ENTITY INDEX
PROMY MERIDIAN RU

COMPANY · ENTITY #12032

AWS CDK

Related event timeline, sources and context from the news index.

EVENT TIMELINE

4

MODELS · 1 SOURCE · AWS Machine Learning

Fleet-wide edge computer-vision pipeline sample using Amazon SageMaker Python SDK v3 and Neo

AWS published a sample (aws-samples GitHub) updating its 2023 visual-inspection pattern to the Amazon SageMaker Python SDK v3, replacing the deprecated SageMaker Edge Manager with SageMaker Neo. The dual-branch SageMaker Pipeline trains a per-camera anomaly autoencoder and a ResNet18 classifier, evaluates models through quality gates, compiles approved artifacts with SageMaker Neo to produce device-optimized builds (ONNX + Neo-compiled library), and uses Step Functions, an SQS FIFO queue, a DynamoDB semaphore, Lambda, SNS, and EventBridge for fleet orchestration and paced retraining; deployment is via AWS CDK and a full synthetic run costs about $0.07 in compute.

6.0

CODING · 1 SOURCE · AWS Machine Learning

CDK construct orchestrates SageMaker endpoint auto scaling during updates

AWS describes a reusable AWS CDK construct that replaces native Application Auto Scaling resources with three CloudFormation custom resources to deregister and then re-register auto scaling around SageMaker real-time endpoint updates. The approach (Deregister, Endpoint update, Register Scalable Target, Attach Scaling Policy) uses asynchronous custom-resource handlers, a ConfigHash to force re-invocation, and provider-generated Lambda and Step Functions helpers so endpoint configuration and auto scaling parameters can be updated in a single deployment without manual steps or broken CloudFormation stacks.

6.0

CODING · 1 SOURCE · AWS Machine Learning

Measured autoscaling for TTS on Amazon SageMaker using Kokoro-82M

A how-to demonstrates deploying Kokoro-82M (an 82M-parameter non-autoregressive TTS) as a custom container on an Amazon SageMaker AI real-time endpoint via AWS CDK and replacing a guessed autoscaling target with one derived from two live measurements: Q_max (max per-instance concurrency inside the SLO) and T_total (end-to-end scale-out time). The deployment uses SageMaker's native ConcurrentRequestsPerModel metric (reported to CloudWatch) and supports both InvokeEndpointWithResponseStream and InvokeEndpointWithBidirectionalStream transports; tooling converts client-measured concurrency into CloudWatch units and the example run reported a 1.0 ratio between measured and published values.

6.0

CODING · 1 SOURCE · AWS Machine Learning

Amazon Bedrock AgentCore guide for ambient agents with event-driven, human-in-the-loop workflows

AWS published a walkthrough and reference implementation showing how to build "ambient" agents on Amazon Bedrock AgentCore that react to event streams (S3, EventBridge, scheduled tasks), pause for human approval via a single ask_human tool, and resume—using AgentCore Runtime plus serverless AWS components (Lambda, DynamoDB, SQS) and Bedrock foundation models. The post includes a sample deployment path requiring AWS CLI, CDK v2, Docker, and an ECR-hosted agent container, and notes session timeouts align with Lambda's 15-minute limit in the reference.

6.0