Bluesky · Hashtag

#AmazonBedrock

71
posts · 30d
15
users
2
posts / day
4.7
posts / user
-10% vs last week

#AmazonBedrock is an active hashtag on Bluesky. In the last 30 days, 15 people shared 71 posts with it — around 2 a day. Activity is down 10% versus the previous week, peaking on Jul 23 with 7 posts.

#AmazonBedrock posts per day (last 30 days)

Related tags

Tags most often used together with #AmazonBedrock.

Posts with #AmazonBedrock

AWS News Feed on 🦋
@awsrecentnews.bsky.social
about 18 hours ago
🆕 Amazon Bedrock AgentCore in AWS GovCloud (US-West) now offers memory, policy, and harness for context-aware agents, enabling teams to build intelligent, scalable, and compliant agents with centralized controls and simplified orchestration. #AWS #AwsGovcloudUs #AmazonBedrock
Amazon Bedrock AgentCore adds memory, policy, and harness in AWS GovCloud (US-West)

aws.amazon.com

Amazon Bedrock AgentCore adds memory, policy, and harness in AWS GovCloud (US-West)

Today, Amazon Bedrock AgentCore introduces new capabilities in AWS GovCloud (US-West). AgentCore is the platform to build, connect, and optimize agents. With these capabilities, teams operating in regulated environments can build context-aware agents and take them from prototype to production faster, with the controls needed to scale across their organization.  AgentCore memory gives agents short-term memory for immediate conversation context and long-term memory that extracts persistent insights and preferences across sessions. Agents deliver more intelligent, personalized experiences without teams needing to manage complex memory infrastructure. Policy in AgentCore provides centralized, fine-grained controls for agent-tool interactions that operate outside agent code. Teams author policies in natural language that automatically convert to Cedar, the AWS open-source policy language. Policies attach them to an AgentCore gateway that evaluates each request before allowing or denying tool access.  The managed harness lets developers declare an agent's model, tools, and instructions through configuration and run it in just a few API calls without writing orchestration code, while AgentCore handles the environment, compute, memory, identity, and observability.    To learn more about AgentCore capabilities, visit the AgentCore product page. For a deeper walkthrough of AgentCore concepts and best practices, see the AgentCore Documentation to get started.

0 0 1
AWS News Feed on 🦋
@awsrecentnews.bsky.social
1 day ago
🆕 AWS releases AgentCore runtime instances for Amazon Bedrock, allowing EC2 agents without infrastructure. Choose GPU, memory, or compute-optimized EC2 types; long-running sessions up to 14 days. Available in multiple regions; manage via console, CLI, SDKs, or APIs. Pricing de… #AWS #AmazonBedrock
AgentCore runtime instances are now generally available

aws.amazon.com

AgentCore runtime instances are now generally available

Today, AWS announces runtime instances, a new feature in Amazon Bedrock AgentCore that lets you run agents on your own Amazon EC2 instances without managing infrastructure. AgentCore runtime provides purpose-built infrastructure to deploy and operate AI agents securely at scale. Runtime instances complement the existing microVM-based option in AgentCore runtime and give teams running sustained, resource-intensive, or specialized-hardware agents access to the breadth of EC2 instance types, while AgentCore handles provisioning, patching, scaling, and lifecycle management. Using the AWS Management Console, CLI, SDKs, or APIs, you create a capacity provider that specifies the EC2 instance types your agents need, including GPU-accelerated, memory-optimized, and compute-optimized families, and attach your agents to it. Runtime instances support long-running agent sessions of up to 14 days, while the default serverless, microVM-based runtime is designed for sessions of up to 8 hours that need fast startup . You can choose the right compute for each agent, or run a mix, without changing how you deploy or invoke your agents. You can use runtime instances in the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), and Europe (Ireland). You are charged for the management of the compute provisioned, in addition to your Amazon EC2 costs. To get started, visit AWS News Blog or AgentCore documentation. To learn about pricing, visit AgentCore pricing.

0 0 1
AWS News(Unofficial)
@awsnews.bsky.social
1 day ago
AgentCore runtime instances are now generally available Today, AWS announces runtime instances, a new feature in Amazon Bedrock AgentCore that lets you run agents on your own Amazon EC2 instances without managing infrastructure. AgentCore runtime provides purpose-built infra... #AWS #AmazonBedrock

aws.amazon.com

AgentCore runtime instances are now generally available

Today, AWS announces runtime instances, a new feature in Amazon Bedrock AgentCore that lets you run agents on your own Amazon EC2 instances without managing infrastructure. AgentCore runtime provides purpose-built infrastructure to deploy and operate AI agents securely at scale. Runtime instances complement the existing microVM-based option in AgentCore runtime and give teams running sustained, resource-intensive, or specialized-hardware agents access to the breadth of EC2 instance types, while AgentCore handles provisioning, patching, scaling, and lifecycle management. Using the AWS Management Console, CLI, SDKs, or APIs, you create a capacity provider that specifies the EC2 instance types your agents need, including GPU-accelerated, memory-optimized, and compute-optimized families, and attach your agents to it. Runtime instances support long-running agent sessions of up to 14 days, while the default serverless, microVM-based runtime is designed for sessions of up to 8 hours that need fast startup . You can choose the right compute for each agent, or run a mix, without changing how you deploy or invoke your agents. You can use runtime instances in the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), and Europe (Ireland). You are charged for the management of the compute provisioned, in addition to your Amazon EC2 costs. To get started, visit https://aws.amazon.com/blogs/aws/runtime-instances-persistent-compute-for-production-ai-agents-on-amazon-bedrock-agentcore/ or https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-instances-how-it-works.html. To learn about pricing, visit https://aws.amazon.com/bedrock/agentcore/pricing/.

0 0 1
AWS News Feed on 🦋
@awsrecentnews.bsky.social
2 days ago
🆕 Amazon Bedrock AgentCore introduces temporal policies for stateful authorization and rate limiting to manage AI traffic, ensuring safe, sequential actions and fair resource distribution. For details, see the announcement blog and documentation. #AWS #AmazonBedrock
Announcing temporal policies and rate limiting in Amazon Bedrock AgentCore

aws.amazon.com

Announcing temporal policies and rate limiting in Amazon Bedrock AgentCore

Amazon Bedrock AgentCore announces two new controls: temporal policies for stateful agent authorization and rate limiting for AI traffic. Temporal policies let you define stateful authorization rules that evaluate each request in the context of an agent's prior actions within a session, because a single tool call can be safe in isolation yet harmful given what preceded it. With temporal policies you can enforce workflow sequencing, require that a tool argument exactly matches the output of a prior call, require human approval before taking privileged actions, and enforce data freshness. Rate limiting enables per-user or per-group controls over how much traffic flows to the tools, models, and agents connected to your gateway. Using rules scoped by OAuth or AWS IAM, you can set rate limits on requests across all target types, tokens for inference targets, and concurrent connections to cap long-lived concurrent sessions, aiding downstream service availability and enforcing fair limit distribution.  For regional availability and to learn more, see the documentation, read the announcement blog, and explore the Dogwood reference implementation.

0 0 1
AWS News(Unofficial)
@awsnews.bsky.social
2 days ago
Announcing temporal policies and rate limiting in Amazon Bedrock AgentCore Amazon Bedrock AgentCore announces two new controls: temporal policies for stateful agent authorization and rate limiting for AI traffic. Temporal policies let you define stateful authorization ru... #AWS #AmazonBedrock

aws.amazon.com

Announcing temporal policies and rate limiting in Amazon Bedrock AgentCore

Amazon Bedrock AgentCore announces two new controls: temporal policies for stateful agent authorization and rate limiting for AI traffic. Temporal policies let you define stateful authorization rules that evaluate each request in the context of an agent's prior actions within a session, because a single tool call can be safe in isolation yet harmful given what preceded it. With temporal policies you can enforce workflow sequencing, require that a tool argument exactly matches the output of a prior call, require human approval before taking privileged actions, and enforce data freshness. Rate limiting enables per-user or per-group controls over how much traffic flows to the tools, models, and agents connected to your gateway. Using rules scoped by OAuth or AWS IAM, you can set rate limits on requests across all target types, tokens for inference targets, and concurrent connections to cap long-lived concurrent sessions, aiding downstream service availability and enforcing fair limit distribution.  For regional availability and to learn more, see the https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/what-is-bedrock-agentcore.html, read the https://aws.amazon.com/blogs/machine-learning/control-agent-behaviors-and-cost-beyond-a-single-action-new-capabilities-in-amazon-bedrock-agentcore/ and explore the https://github.com/dogwood-policy. 

0 0 1
AWS News(Unofficial)
@awsnews.bsky.social
4 days ago
Amazon Bedrock launches Web Search for OpenAI GPT models Today, we are announcing the general availability of Web Search on Amazon Bedrock, a built-in server side tool that performs web search entirely within AWS, enabling OpenAI models (GPT-5.4, GPT-5.5, and GPT-5.6 Sol/Ter... #AWS #AmazonBedrock

aws.amazon.com

Amazon Bedrock launches Web Search for OpenAI GPT models

Today, we are announcing the general availability of Web Search on Amazon Bedrock, a built-in server side tool that performs web search entirely within AWS, enabling OpenAI models (GPT-5.4, GPT-5.5, and GPT-5.6 Sol/Terra/Luna) to ground responses with current web knowledge while maintaining data residency within your secured AWS environment with zero data egress. Previously, adding web grounding required onboarding a third-party search provider, managing separate API keys and billing, building custom orchestration, and conducting additional compliance reviews for each external vendor. Web Search removes this heavy lifting by enable grounding with a single parameter in an existing API call, with no vendor onboarding, no external APIs to orchestrate, and no additional vendor security reviews to conduct. Web Search is built by Amazon, informed by years of experience across Alexa+, Amazon Quick and Kiro. It combines a web index operated by Amazon, spanning tens of billions of documents refreshed continually, with a built-in knowledge graph that provides verified facts. Rather than returning raw pages, Web Search performs semantic snippet extraction, delivering context-efficient results optimized for the model's context window with low latency. Web Search integrates through a standardized tool-use interface, compatible with the OpenAI Responses API. Simply add the web search tool to your API call, and Bedrock handles the entire search lifecycle server-side; a single API call returns a grounded response with citations. Web Search on Amazon Bedrock is generally available today in US East (N. Virginia), US East (Ohio), and US West (Oregon). To get started, read our blog post https://aws.amazon.com/blogs/machine-learning/introducing-web-search-on-amazon-bedrock-for-foundation-model-grounding/, review the https://docs.aws.amazon.com/bedrock/ for technical documentation, and visit the https://aws.amazon.com/bedrock/pricing/ for cost details.

0 1 1
AI Bloom
@ai-bloom.warp-studio.com
4 days ago
Amazon Bedrockへのウェブ検索機能統合:基盤モデルのリアルタイムグラウンディングを強化 Amazon Bedrockにウェブ検索機能が導入され、基盤モデルの最新情報に基づいた応答生成を強化。 #AmazonBedrock #RAG #基盤モデル #ウェブ検索 #AIエージェント
Amazon Bedrockへのウェブ検索機能統合:基盤モデルのリアルタイムグラウンディングを強化

ai.warp-studio.com

Amazon Bedrockへのウェブ検索機能統合:基盤モデルのリアルタイムグラウンディングを強化

Amazon Bedrockにウェブ検索機能が導入され、基盤モデルの最新情報に基づいた応答生成を強化。

0 0 1
Gunnar Grosch
@gunnargrosch.com
over 1 year ago
🔥 Revolutionize your AI workflows with Amazon Bedrock's new Prompt Optimization Preview! 🚀 Optimize prompts for improved performance and unlock new possibilities with large language models. Don't miss out on this game-changing innovation! aws.amazon.com/about-aws/wh... #AmazonBedrock
Video thumbnail
Play button
1 1 8
AWS News Feed on 🦋
@awsrecentnews.bsky.social
5 days ago
🆕 AWS launches Context Ontology Accelerator, an open-source tool to quickly build business ontologies for AI agents, cutting manual creation from months to days. Available on GitHub, it leverages Amazon Neptune and OpenSearch Serverless, with a fully managed opt… #AWS #AmazonNeptune #AmazonBedrock
Amazon Web Services now introduces Context Ontology Accelerator

aws.amazon.com

Amazon Web Services now introduces Context Ontology Accelerator

Today, AWS announces Context Ontology Accelerator, an open source accelerator that helps organizations build an ontology of their business — a machine-readable model of their products, customers, policies, and the rules that define how they operate so AI agents make accurate, consistent, explainable, and auditable decisions. Context Ontology Accelerator connects to your structured and/or unstructured data sources, and uses AI to draft an ontology; your domain experts review, edit, and approve every element of it. The approved ontology is stored in a knowledge graph you own, expressed in open W3C standards so it works with any standards-based tooling, and any agent can consume it through the included Model Context Protocol (MCP) server. Organizations building AI agents need more trust in their agents' decisions, with outputs they can explain and audit. The context those agents require — entities, rules, policies, relationships — is scattered across dozens of systems with conflicting schemas and naming conventions. Teams spend months reconciling definitions and encoding them into prompts and point integrations, and because the results are not traceable, teams block agents from moving from proof-of-concept to production. Context Ontology Accelerator reduces what would take months of manual ontology authoring into days — from connecting data to serving governed answers to agents. Context Ontology Accelerator is available today on GitHub under Apache 2.0. The initial release uses Amazon Neptune as the graph store, Amazon OpenSearch Serverless as the vector store, and foundation models hosted on Amazon Bedrock; deploy it yourself or engage AWS Professional Services. Context Ontology Accelerator’s managed, user-defined ontology capability will become a fully managed feature native to AWS Context. Customers who get started with Context Ontology Accelerator to create ontologies will be able to use and manage them with AWS Context. To learn more, read the documentation.

0 0 1
AWS News(Unofficial)
@awsnews.bsky.social
5 days ago
Amazon Web Services now introduces Context Ontology Accelerator Today, AWS announces Context Ontology Accelerator, an open source accelerator that helps organizations build an ontology of their business — a machine-readable model of their products, customers, ... #AWS #AmazonNeptune #AmazonBedrock

aws.amazon.com

Amazon Web Services now introduces Context Ontology Accelerator

Today, AWS announces Context Ontology Accelerator, an open source accelerator that helps organizations build an ontology of their business — a machine-readable model of their products, customers, policies, and the rules that define how they operate so AI agents make accurate, consistent, explainable, and auditable decisions. Context Ontology Accelerator connects to your structured and/or unstructured data sources, and uses AI to draft an ontology; your domain experts review, edit, and approve every element of it. The approved ontology is stored in a knowledge graph you own, expressed in open W3C standards so it works with any standards-based tooling, and any agent can consume it through the included Model Context Protocol (MCP) server. Organizations building AI agents need more trust in their agents' decisions, with outputs they can explain and audit. The context those agents require — entities, rules, policies, relationships — is scattered across dozens of systems with conflicting schemas and naming conventions. Teams spend months reconciling definitions and encoding them into prompts and point integrations, and because the results are not traceable, teams block agents from moving from proof-of-concept to production. Context Ontology Accelerator reduces what would take months of manual ontology authoring into days — from connecting data to serving governed answers to agents. Context Ontology Accelerator is available today on GitHub under Apache 2.0. The initial release uses Amazon Neptune as the graph store, Amazon OpenSearch Serverless as the vector store, and foundation models hosted on Amazon Bedrock; deploy it yourself or engage AWS Professional Services. Context Ontology Accelerator’s managed, user-defined ontology capability will become a fully managed feature native to AWS Context. Customers who get started with Context Ontology Accelerator to create ontologies will be able to use and manage them with AWS Context. To learn more, read the https://aws.github.io/context-ontology-accelerator/.

0 1 1

Posts are pulled live from Bluesky and cached briefly. Posts with content labels are hidden.