AWS Weekly Roundup: One-click Lambda setup prompt, OpenAI GPT-5.6 models on Bedrock, and more

Last week, my team visited Seoul to meet AWS Korea User Group (AWSKRUG) leaders, the largest cloud developer community in Korea with 20 meetup groups hosting over 100 events annually. We gathered feedback to support their communities and shared a pleasant time together. A notable launch was the one-click Lambda setup prompt for coding agents, which configures agents with AWS Serverless skills and the Serverless Model Context Protocol server, embedding best practices. The prompt references a setup guide including installation commands for Claude Code, Kiro, Cursor, GitHub Copilot, Codex, Devin Desktop, and OpenCode. Users can copy the agent prompt from the Lambda console or fetch the URL directly to use in AI agents. The Agent Toolkit for AWS provides current AWS knowledge and safe resource access, with installation instructions available via GitHub. Key launches last week include OpenAI GPT-5.6 Sol, Terra, and Luna models on Amazon Bedrock, offering flagship reasoning, balanced performance, and cost-efficient inference tiers accessible through the Responses API. Amazon S3 now allows same-day transitions to Standard-IA and One Zone-IA storage classes, reducing costs by up to 40% without the previous 30-day retention minimum. AWS Lambda supports self-managed code storage using customer S3 buckets, eliminating code storage limits and reducing function activation time by removing intermediate copies. Amazon Cognito now supports importing users with password hashes in CSV imports, enabling immediate sign-in without password resets. Additional updates include Amazon SQS's 20th anniversary reflecting on two decades of reliable messaging, the Strands Agents SDK demonstrating open AI protocols like MCP and A2A, an open source Bulk Executor for DynamoDB simplifying bulk operations without coding, and Kiro CLI enhancing AWS Support case workflows through MCP integration across real-world scenarios. AWS resolved a recent issue with Cost Explorer displaying inaccurate estimated billing data, which caused erroneous alerts and inflated estimates. The issue is fixed, and AWS is conducting a retrospective to prevent recurrence. For more details, visit the AWS Health Dashboard. Check back next Monday for another Weekly Roundup.