AWS Lambda Adds Ruby 4.0 LTS Runtime
AWS Lambda now supports Ruby 4.0 as a managed runtime and container base image, available across all AWS Regions including China and GovCloud as of April 30, 2026. Ruby 4.0 is the language's latest long-term support release, with security and bug fix support committed through March 2029 — making it a stable foundation for new serverless Ruby workloads.
The new runtime integrates AWS Lambda Advanced Logging Controls, which was already available for other runtimes. Ruby 4.0 functions can now emit JSON-structured logs natively, configure log levels (DEBUG, INFO, WARN, ERROR, FATAL), and direct log output to a specific Amazon CloudWatch log group rather than the default function-named group. This makes log routing and centralized aggregation across services significantly easier without relying on custom log formatting libraries.
Deployment of Ruby 4.0 Lambda functions follows standard AWS tooling: the Lambda console, AWS CLI, AWS SAM, AWS CDK, and AWS CloudFormation are all supported. Container-based deployments can use the new Ruby 4.0 base image. For teams still running Ruby 2.x or 3.x in Lambda, AWS's migration documentation covers the main compatibility considerations, including gem dependencies that may require native extension rebuilds for the new runtime environment.
Read more — AWS
Codex on Amazon Bedrock: OpenAI's Coding Agent Meets AWS Infrastructure
AWS and OpenAI announced the availability of Codex on Amazon Bedrock in limited preview on April 28, 2026, as part of a broader partnership expansion that also brings GPT-5.5 and GPT-5.4 models to the Bedrock API. Codex, used by more than 4 million developers weekly for code generation, refactoring, test writing, and system explanation, is now accessible through AWS infrastructure using standard AWS credentials — no separate OpenAI account required.
Developers access Codex through its existing interfaces (Codex CLI, desktop app, and VS Code extension) but authenticate via AWS Identity and Access Management rather than OpenAI API keys. Enterprise security features apply automatically: IAM policies control access, AWS PrivateLink keeps traffic within the AWS network, encryption is managed through AWS KMS, and all API interactions are logged to AWS CloudTrail for audit purposes. Usage of Codex and OpenAI models through Bedrock counts toward existing AWS cloud commitments and EDP discounts.
Amazon Bedrock Managed Agents powered by OpenAI is a companion offering also entering limited preview. It lets developers deploy production-ready agents using OpenAI's model stack with improved execution speed and reasoning capabilities, managed through the Bedrock control plane alongside Claude and other Bedrock-hosted models. This means teams can mix models from different providers within a single, unified agent orchestration surface.
For enterprises already deeply invested in AWS security and compliance posture, accessing Codex through Bedrock significantly lowers the procurement and security review overhead compared to integrating a separate OpenAI API subscription. It also provides a single invoice and a unified approach to access governance across AI coding tools.
Read more — AWS
AWS MCP Server Reaches General Availability
AWS released the AWS MCP Server to general availability on May 6, 2026. The service is a managed remote Model Context Protocol server that gives AI coding agents and assistants secure, authenticated access to AWS services through standardized tool invocations — without requiring developers to maintain their own MCP infrastructure.
The GA release introduces two notable capabilities beyond the preview. First, IAM context keys are now supported, allowing fine-grained permission policies expressed in standard IAM syntax without requiring a separate IAM permission solely to use the MCP server. Second, a new run_script tool lets agents write and execute short Python scripts server-side in a sandboxed environment that inherits the caller's IAM permissions but has no outbound network access, enabling complex multi-step AWS resource operations in a single agent turn.
The service also transitions from Agent SOPs (standard operating procedures) to Skills — curated, opinionated playbooks for common AWS tasks that coding agents can discover and invoke. Enterprise monitoring is covered by AWS-MCP namespace metrics in Amazon CloudWatch and full API-level audit trails in AWS CloudTrail, satisfying the observability requirements that were blocking many enterprise adoption decisions during preview.
Supported AI clients include Claude Code, Kiro (AWS's recently announced IDE), Cursor, Codex, and any other MCP-compatible coding assistant. The AWS MCP Server is available in US East (N. Virginia) and Europe (Frankfurt) regions at no additional charge beyond the costs of the AWS resources agents create or interact with. The open-source MCP server code is maintained at github.com/awslabs/mcp for teams that prefer self-hosted deployments.
Read more — AWS Blog
Links & Sources
You May Also Enjoy
