Cloudformation | Techlist.io

awsJul 27, 20263 min readCurated summary

AWS Weekly Roundup: Local Zone in Athens, Claude Opus 5 on AWS, Lambda durable execution for .NET, and more (July 27, 2026) | Amazon Web Services

The week’s AWS updates focus on bringing infrastructure closer to users, expanding AI capabilities, and improving reliability and observability. Highlights include a new Athens Local Zone, Claude Opus 5 availability, durable Lambda workflows for .NET, and unified Amazon Bedrock AgentCore telemetry. The post also points to new data, contact-center, developer-productivity, and community resources. ## AWS Local Zone in Athens - AWS launched its second EMEA Local Zone in Athens, Greece. - It supports: - Amazon EC2 C7i, M7i, and R7i instances - Amazon S3 One Zone-Infrequent Access - Amazon EBS and EBS Local Snapshots - Amazon ECS - Greek organizations can process and store data locally to help satisfy data-residency requirements. - The zone enables single-digit-millisecond latency for workloads such as gaming, media production, and financial services while still connecting to the nearest AWS Region. ## New AI and Serverless Capabilities - **Claude Opus 5 on AWS** is available through Amazon Bedrock and Claude Platform on AWS. - It provides top-tier Opus-level intelligence. - Bedrock enables zero data retention by default, supporting stricter governance requirements. - **Lambda durable execution for .NET** is now generally available. - C# developers can create long-running, multi-step workflows without custom checkpointing or external orchestration. - Workflows can pause for up to one year. - Use cases include payment pipelines, AI agents, and human approvals. ## Improved Agent Observability - Amazon Bedrock AgentCore now stores traces, prompts, inputs, outputs, and application logs in a single CloudWatch log group. - Engineers can investigate individual agent invocations without searching multiple destinations. - Agent-level access controls and customer-managed key encryption are also supported. ## Contact Center, Data, and Developer Updates - Amazon Connect added more natural agentic voice experiences across more than 50 languages. - The service now includes over 100 new voice options and improved handling of tone and sentiment. - SageMaker Unified Studio can query Amazon OpenSearch data alongside Redshift, S3, and relational database assets. - CloudWatch coding agent insights measures the organizational impact of tools such as Claude Code, Codex, and GitHub Copilot using OpenTelemetry telemetry without custom instrumentation. ## Additional Resources and Events - AWS published guidance for evaluating AI agents with Strands Agents and Bedrock AgentCore. - A new guide covers multi-region resiliency for CloudFormation custom resources. - Amazon SES introduced pricing plans intended to make large-scale email costs more predictable. - Upcoming opportunities include AWS Summits and AWS Community Day Belo Horizonte on August 22. Together, these releases suggest AWS is prioritizing lower-latency regional infrastructure, production-ready AI workflows, and better operational visibility. Builders should assess the Athens Local Zone for residency-sensitive workloads, consider durable Lambda execution for complex .NET processes, and adopt the new observability tools as agent deployments grow.

Read original

Cloudformation AWS Amazon Bedrock Aws Lambda+4

awsMay 6, 20263 min readCurated summary

The AWS MCP Server is now generally available | Amazon Web Services

The AWS MCP Server is now generally available as a managed way for AI agents to access AWS securely through IAM-authenticated tools. It combines live AWS documentation, access to more than 15,000 API operations, and sandboxed scripting so agents can produce more current, efficient, and production-ready results. The post concludes that this solves major limitations of model-only AWS assistance without granting agents unrestricted credentials. ## Why AI Agents Struggle with AWS - Models may lack knowledge of recently launched services such as Amazon S3 Vectors, Aurora DSQL, and Bedrock AgentCore. - Agents often default to the AWS CLI instead of AWS CDK or CloudFormation. - Generated IAM policies are frequently broader than necessary. - The resulting infrastructure may work in demos but fail production standards. ## Core AWS MCP Server Tools - `call_aws` can execute more than 15,000 AWS API operations using the user’s existing IAM credentials. - `search_documentation` and `read_documentation` retrieve current AWS documentation and best practices at query time. - The compact tool set reduces model context usage and is intended to support newly launched APIs within days. ## General Availability Improvements - IAM context keys allow fine-grained access control through standard IAM policies without requiring a separate server permission. - Documentation retrieval no longer requires authentication. - Reduced token consumption improves complex, multi-step workflows. - The `run_script` tool executes short Python scripts in a server-side sandbox. - The sandbox inherits IAM permissions. - It has no network access or access to the user’s local filesystem and shell. - It can combine multiple API calls, filter results, and calculate outputs in one round trip. ## Skills and AWS Best Practices - Skills replace Agent SOPs with curated guidance for common AWS tasks. - AWS service teams contribute and maintain the Skills. - They help agents avoid mistakes, use validated patterns, reduce hallucinations, and consume fewer tokens. - Keeping the tool list small makes agent behavior more predictable. ## Enterprise Security and Observability - IAM policies and Service Control Policies can separate human permissions from agent permissions. - For example, a user may perform write operations while the MCP server is restricted to read-only access. - CloudWatch metrics under the `AWS-MCP` namespace distinguish agent activity from direct human calls. - AWS CloudTrail records all API calls for auditing and compliance. ## Demonstration with Claude Code - Without the MCP Server, Claude Opus 4.6 suggested several valid ways to store embeddings on S3 but missed Amazon S3 Vectors because the service launched after its training cutoff. - With the MCP Server, Claude Code searched current AWS documentation and correctly identified S3 Vectors. - Claude Code can connect through the open-source `mcp-proxy-for-aws`, which bridges local IAM credentials and MCP’s OAuth 2.1 requirement. - The server works with Claude Code, Kiro, Cursor, Codex, and other MCP-compatible clients. ## Availability and Cost - The service is available in US East (N. Virginia) and Europe (Frankfurt). - It can make API calls across AWS Regions. - There is no additional charge for the MCP Server; users pay for AWS resources and applicable data transfer. The AWS MCP Server is a practical foundation for giving agents current AWS knowledge and controlled operational access. Teams should pair it with narrowly scoped IAM policies, read-only defaults where possible, and CloudWatch or CloudTrail monitoring.

Read original

Cloudformation Model Context Protocol Python AWS+4

awsMar 26, 20262 min readCurated summary

Customize your AWS Management Console experience with visual settings including account color, region and service visibility | Amazon Web Services

AWS has expanded User Experience Customization (UXC) to let administrators tailor the Management Console by account color, visible Regions, and visible services. These settings help teams distinguish accounts and reduce clutter by showing only relevant resources. They affect console appearance only and do not restrict access through the CLI, SDKs, APIs, or Amazon Q Developer. ## Account Color Customization - Administrators can assign a color to an AWS account through **Account display settings**. - The color appears in the console navigation bar to make account purpose easier to recognize. - Teams can use colors such as: - Orange for development - Light blue for testing - Red for production ## Region Visibility - Administrators can configure which AWS Regions appear in the console’s Region selector. - They can either show all available Regions or select a specific list. - After saving, only the chosen Regions appear in the navigation bar. - This reduces unnecessary scrolling and helps users focus on approved or relevant Regions. ## Service Visibility - Administrators can select which AWS services appear in the **All services** menu and console search results. - Services can be searched for or selected by category, such as Popular services. - Hidden services are removed from the console interface but remain accessible through programmatic tools. ## Programmatic Configuration - Account customization can be managed through the `AWS::UXC::AccountCustomization` CloudFormation resource. - The resource supports: - `AccountColor` - `VisibleServices` - `VisibleRegions` - Example configurations can expose services such as `s3`, `ec2`, and `lambda`, while limiting Regions to `us-east-1` and `us-west-2`. - Templates can be deployed with the AWS CLI using `aws cloudformation deploy`. AWS administrators can use these settings to create a clearer, more focused console experience without changing permissions or underlying account access.

Read original

Cloudformation AWS API Cli+3