ACUVA

Your Accurate Search for New Technology

AWS Marketplace now offers pricing model flexibility and simplified deployment for AI agents and tools

By

AWS Marketplace now offers flexible pricing models, simplified authentication, and streamlined deployment for AI agents and tools. The new capabilities include contract-based and usage-based pricing for Amazon Bedrock AgentCore Runtime containers, and simplified OAuth credential management through Quick Launch for API-based AI agents and tools. Customers can also use supported remote MCP servers procured through AWS Marketplace as MCP targets on AgentCore Gateway, making it easier for them to connect to AI agents and tools from AWS Partners at scale. The improvements reduce deployment complexity while offering pricing models that better align with diverse customer needs.

For Partners, the new capabilities for AI agents and tools streamline management and provide additional pricing options through AWS Marketplace. Partners can now manage all their AI agents and tools listings from one page in the AWS Marketplace Management Portal, reducing the complexity of managing multiple listings across different interfaces. With usage-based and contract-based pricing options for AgentCore Runtime compatible products, Partners have more flexibility to implement pricing strategies that align with their business models and customers’ needs.

Customers can learn more in the buyer guide and start exploring AI agent solutions in AWS Marketplace on the solutions page . For partners interested in implementing the capabilities, visit the seller guide and complete the workshop.

Amazon VPC IPAM automates prefix list updates

By

Today, AWS announced the ability for Amazon VPC IP Address Manager (IPAM) to automate prefix lists updates with prefix list resolver (PLR). This feature allows network administrators to automatically update prefix lists based on their business logic in IPAM improving their operational posture and reducing overhead.

Using IPAM PLR, you can define business rules for synchronizing prefix lists with IP address ranges from various resources, such as VPCs, subnets and IPAM pools. These prefix lists can then be referenced in resources such as route tables and security groups across your AWS environment, based on your connectivity requirements. Previously, you had to manually update your prefix lists to add or remove IP address ranges based on changes to your AWS environment. This was operationally complex and error prone. IPAM PLR automates prefix list updates requiring no manual intervention, improving your operational posture.

This feature is now available in all AWS Regions where Amazon Sagemaker Unified Studio is supported, including AWS China Regions, and AWS GovCloud (US) Regions.

To learn more about this feature, view the AWS IPAM documentation . For details on pricing, refer to the IPAM tab on the Amazon VPC Pricing Page .

The Model Context Protocol (MCP) Proxy for AWS is now generally available

By

Today, AWS announces the general availability of the Model Context Protocol (MCP) Proxy for AWS, a client-side proxy that enables MCP clients to connect to remote, AWS-hosted MCP servers using AWS SigV4 authentication. The Proxy supports popular agentic AI development tools like Amazon Q Developer CLI, Kiro, Cursor, and popular agent frameworks like Strands Agents. Customers can connect to remote MCP servers with AWS credentials using the Proxy to automatically handle MCP protocol communications via SigV4. The Proxy also helps customers to connect to MCP servers built on Amazon Bedrock AgentCore Gateway or Runtime using SigV4 authentication.

This release allows developers and agents to extend development workflows to include AWS service interactions from AWS MCP server tools. For example, you can use AWS MCP servers to work with resources like AWS S3 buckets or Amazon RDS tables through existing MCP servers with SigV4. The MCP Proxy for AWS includes safety controls such as read-only mode to prevent unintended changes, configurable retry logic for reliability, and logging for troubleshooting. Customers can install the Proxy from source, through Python package managers, or by using a container making it simple to configure with their preferred MCP-supported development tool.

The MCP Proxy for AWS is open-source and available now. Visit the AWS GitHub repository to view the installation and configuration options and start connecting with remote AWS MCP Servers today. 

Amazon RDS extends IPv6 support for publicly accessible databases

By

Amazon Relational Database Service (RDS) now extends the Internet Protocol Version 6 (IPv6) support to publicly accessible databases , in addition to the existing support for privately accessible databases within a VPC. This allows you to configure dual-stack (IPv4 and IPv6) connectivity for your publicly accessible RDS and Aurora databases.

IPv6 provides an expanded address space, enabling you to scale your application on AWS beyond the limitations of IPv4 addresses. With IPv6, you can assign easy to manage contiguous IP ranges to micro-services and can get virtually unlimited scale for your applications. Moreover, with support for both IPv4 and IPv6, you can gradually transition applications from IPv4 to IPv6, enabling safer migration.

This feature is available in all AWS regions where IPv6 support for privately accessible RDS databases within a VPC is already available. Get started with the AWS CLI or AWS Management Console .

To learn more about configuring your environment for IPv6, please refer to the IPv6 User Guide .

Scroll Up