Blog_dumb

Part 1 covered the Snowflake database setup and established the foundational infrastructure for this no-code machine learning (ML) workflow. Part 2 of this blog series covers complete data preparation and model building workflow using Amazon SageMaker Canvas, demonstrating how to connect directly to Snowflake data sources, transform and prepare data using Data Wrangler’s visual transformations, […]

Part 1 covered the Snowflake database implementation setup and established the foundational infrastructure for our no-code machine learning (ML) workflow. Part 2 walked through the complete data preparation and model building workflow using Amazon SageMaker Canvas, demonstrating how to connect directly to Snowflake data sources, transform and prepare data using Data Wrangler visual transformations, and

AI agents can automate complex workflows but might take actions that don’t align with your organization’s policies or regulatory constraints if used without proper controls. To address this, we built Policy in Amazon Bedrock AgentCore so teams can implement controls that are applied across agents running in Amazon Bedrock AgentCore. This was recently expanded with

Scaling agentic AI across an enterprise requires architectural patterns that preserve flexibility while avoiding vendor lock-in. This post is Part 2 of our series on multi-agent systems at scale. In this post, we examine how machine learning (ML) teams operate agentic AI systems across a “multi-everything” environment of frameworks, models, and providers. We also cover

Scaling cloud migrations with agentic AI on Amazon Bedrock AgentCore starts with recognizing where large-scale migrations break down. Discovery consumes weeks per application. Engineers write infrastructure code from scratch for each workload. Post-migration operations devolve into reactive firefighting. Multiply those bottlenecks across over 300 applications and a fixed fiscal year deadline, and migration programs struggle

Agentic AI is changing how you work, and vector search powers the retrieval layer that makes agents accurate, contextual, and grounded in real data. Agents plan, reason, and take action across multi-step workflows, making fast, relevant access to your organization’s knowledge essential. That knowledge already has a home across databases, object stores, search engines, and

If you manage Fast Healthcare Interoperability Resources (FHIR) APIs, you must balance open patient data access with strict data protection requirements. Static security rules require constant updates as clinical workflows evolve, and maintaining them manually creates compliance gaps. With Amazon Bedrock, a fully managed service that provides access to foundation models (FMs) through a single

When an AI agent uses Web Search to ground its answers on behalf of a customer, the organization behind that agent needs domain and date filters to control which sources the agent consults and how fresh those sources must be. A financial-services agent shouldn’t ground its answers in an unvetted blog. A product-information agent shouldn’t

Mortgage lending runs on documents. Every loan starts with a familiar set: earnings statements, W-2s, bank statements, driver’s licenses, voided checks, and insurance applications. Every lender processes them at scale. The challenge of classifying, extracting, and validating high volumes of documents isn’t unique to mortgage lending. Organizations in banking, insurance, healthcare, and the public sector

Asynchronous invocation patterns for Amazon Bedrock AgentCore agents in serverless pipelines remove idle compute costs while your AI agent processes requests. A common example is document validation: in a real-estate financing back office, an agent can read a property record or loan contract, reason about whether the information is complete and consistent, and return a