Aws Cloudformation | Techlist.io

awsJul 6, 20263 min readCurated summary

AWS Weekly Roundup: Claude Sonnet 5 on AWS, Amazon WorkSpaces for AI agents, AWS service availability updates, and more (July 6, 2026) | Amazon Web Services

The July 6, 2026 AWS roundup highlights new infrastructure, AI, observability, and developer productivity capabilities. Major announcements include Claude Sonnet 5 on AWS, generally available WorkSpaces for AI agents, faster SageMaker inference scaling, and log-query alarms in CloudWatch. It also details AWS service lifecycle changes and upcoming community events. ## Featured AWS Launches - **Claude Sonnet 5 on AWS** - Anthropic’s latest Sonnet model is available for coding, agentic workflows, and professional tasks. - It can navigate large codebases, use tools accurately, and preserve state across long-running tasks. - **Amazon WorkSpaces for AI agents** - AI agents can securely operate desktop applications in managed WorkSpaces environments. - Organizations can use existing applications without modernization or custom integrations. - **OpenSearch log analytics optimization** - A new engine provides up to four times better price-performance in internal benchmarks. - It combines log aggregation with OpenSearch’s full-text search capabilities. - **Faster SageMaker AI inference scaling** - Container image caching can reduce generative AI scale-out time by up to half. - SageMaker supports up to two times faster end-to-end scaling during demand increases. - **CloudWatch alarms from log queries** - Users can create alarms directly from log query results and define thresholds in one workflow. - This removes the need to create metric filters or custom metrics first. ## Additional Infrastructure and Developer Updates - **EC2 C9g and C9gd instances** - Powered by AWS Graviton5 processors. - Offer up to 25% more compute performance than Graviton4 instances, five times more cache, faster memory, and optional local NVMe storage. - **CloudFormation Express mode** - Provides deployment confirmation within seconds. - Helps developers and AI agents iterate more quickly, at no additional cost in commercial Regions. - **Amazon EKS version rollbacks** - Kubernetes upgrades can be reversed within seven days. - Rollbacks avoid rebuilding clusters and reduce the risk of failed upgrades. - **ACME support in AWS Certificate Manager** - Automates issuance and renewal of public TLS certificates using the standard ACME protocol. ## AWS Service Availability Changes AWS updated its lifecycle guidance on June 30, 2026, including alternatives and migration support. - **Moving to maintenance for new customers from July 30** - Amazon Bedrock Agents becomes Bedrock Agents Classic. - Amazon Cognito Sync, Amazon Kendra, Amazon Q Business, Simple AD, and several other services and features will no longer accept new customers. - A number of SageMaker AI features are affected, including Clarify, Debugger, Ground Truth, Model Monitor, and Studio Lab. - AWS IoT Device Defender Detect changes on August 31, 2026. - **Entering sunset** - Amazon WorkSpaces PCoIP and Pool. - AWS Managed Services Advanced. - AWS re:Post Private. - SageMaker AI Profiler. - **End of support** - Amazon Chime SDK Carrier Voice Focus. - SageMaker AI Ground Truth Plus. ## Upcoming AWS Events - AWS Summits will take place throughout the second half of 2026. - AWS Community Day Belo Horizonte is scheduled for August 22. - The AWS Builder Center offers community discussions, technical content, and information about upcoming virtual and in-person events. Organizations using affected AWS services should review the relevant lifecycle documentation and contact AWS Support to plan migrations before availability or support deadlines.

Read original

Aws Cloudformation Kubernetes AWS Amazon Sagemaker+4

awsJun 30, 20262 min readCurated summary

Accelerate your infrastructure deployments by up to 4x with AWS CloudFormation Express mode | Amazon Web Services

AWS CloudFormation Express mode speeds deployments by marking them complete once resource configuration is applied, rather than waiting for full stabilization checks. AWS says this can reduce deployment times by up to four times, while resources continue becoming operational in the background. It is intended for rapid infrastructure iteration and scenarios where eventual stabilization is acceptable, not workflows requiring resources to be fully ready before proceeding. ## How Express Mode Works - Standard CloudFormation deployments wait for post-configuration stabilization checks. - Express mode completes earlier, immediately after configuration is applied. - Resources continue stabilizing asynchronously. - CloudFormation retries dependent resources that encounter transient provisioning failures. - The provisioning process itself is unchanged; only the point at which deployment completion is reported changes. ## Performance Improvements - Creating an SQS queue with a dead-letter queue took: - Standard mode: 64 seconds - Express mode: up to 10 seconds - Deleting a Lambda function with attached network interfaces took: - Standard mode: 20–30 minutes - Express mode: up to 10 seconds in AWS’s benchmark ## Best Use Cases - Iteratively building infrastructure one component at a time. - Testing individual application components. - AI-assisted infrastructure development requiring sub-minute feedback. - Production workflows that can tolerate resources stabilizing after deployment completion. ## Enabling Express Mode - In the AWS Console, select **Enable** under stack deployment options. - With the CLI or SDKs, set the deployment configuration mode to `EXPRESS`: ```bash aws cloudformation create-stack \ --stack-name my-app \ --template-body file://template.yaml \ --deployment-config '{"mode": "EXPRESS", "disableRollback": true}' ``` - AWS CDK supports: ```bash cdk deploy --express ``` - No CloudFormation template changes are required. - Express mode supports existing templates, change sets, nested stacks, and IaC or AI tools such as Kiro. - Enabling it on a parent stack also applies it to nested stacks. ## Rollback and Operational Considerations - Rollback is disabled by default in Express mode to maximize iteration speed. - For production use, rollback can be restored with `"disableRollback": false`. - Teams should otherwise provide monitoring and cleanup procedures for failed deployments. - IAM templates should continue following least-privilege principles. ## Availability - Express mode is available at no additional cost in all AWS commercial Regions. - AWS recommends standard deployment behavior when resources must be fully operational before traffic shifting or testing. For fast development and AI-driven infrastructure iteration, Express mode is a useful optimization. Use it selectively, while retaining standard mode—or explicitly enabling rollback—when deployment readiness and failure recovery are critical.

Read original

Aws Cloudformation Aws Lambda Infrastructure As Code Aws Cli+4

awsJun 18, 20262 min readCurated summary

Amazon ECS introduces new high-resolution metrics for faster service auto scaling | Amazon Web Services

Amazon ECS now supports 20-second high-resolution metrics for faster service auto scaling. AWS reports that scale-out triggers improved from 363 to 86 seconds, while total scaling and task provisioning dropped from 386 to 109 seconds. The update helps applications handle traffic spikes more reliably, reduce excess baseline capacity, and achieve aggressive scaling with simpler target-tracking policies. ## Faster Scaling with High-Resolution Metrics - ECS service auto scaling can use predictive, scheduled, or reactive target-tracking policies. - New 20-second metrics allow ECS to detect workload changes faster than standard 60-second metrics. - AWS benchmarking showed: - 76% faster scale-out triggering, or 4.2× improvement. - 72% faster total scaling and task provisioning, or 3.5× improvement. - Faster scaling can reduce latency and failures during sudden demand increases. ## Lower Costs and Simpler Configuration - Applications may reduce baseline task counts because capacity can be added quickly during spikes. - This can lower compute costs without sacrificing availability. - High-resolution target tracking can provide aggressive scaling behavior that previously required custom step-scaling policies. ## Configuration and Supported Metrics - Enable high-resolution metrics for the ECS service, then configure a target-tracking scaling policy. - New options include: - `ECSServiceAverageCPUUtilizationHighResolution` - `ECSServiceAverageMemoryUtilizationHighResolution` - The feature works with AWS Fargate, ECS Managed Instances, and Amazon EC2. - It can be configured through the ECS console, AWS SDKs, AWS CLI, Application Auto Scaling, or CloudFormation. - Existing services must first enable high-resolution metrics and complete deployment before their scaling policy can be updated. ## Cost and Availability - The ECS feature itself has no additional charge. - High-resolution CloudWatch metrics incur additional CloudWatch costs, unlike standard 60-second metrics. - The capability is available now. For workloads with unpredictable or rapid traffic changes, enabling high-resolution metrics with target tracking can improve responsiveness while reducing the need for overprovisioned ECS tasks.

Read original

Aws Cloudformation Amazon Ec2 Aws Cli Amazon Ecs+4

awsMay 25, 20263 min readCurated summary

AWS Weekly Roundup: AWS Local Zones in Istanbul, open-source ExtendDB, Kiro Web, and more (May 25, 2026) | Amazon Web Services

AWS’s latest updates focus on expanding regional infrastructure, improving developer workflows, and making cloud and AI services more portable. The Istanbul Local Zone strengthens data residency and low-latency capabilities in Türkiye, while tools such as ExtendDB, OpenAI-compatible SageMaker APIs, and Kiro Web reduce migration and development friction. Together, these releases emphasize flexibility, operational resilience, and easier local testing. ## AWS Local Zone in Istanbul - AWS opened a new Local Zone in Istanbul, Türkiye. - It provides nearby compute, storage, and networking with single-digit millisecond latency. - Organizations can keep and process data within Turkish borders to support residency and compliance requirements. - The zone supports latency-sensitive workloads in sectors such as finance, government, telecommunications, and healthcare. - Applications can combine Istanbul infrastructure with the broader AWS Region, enabling hybrid architectures without operating a private data center. ## Security and AI Service Updates - **Security Hub Extended** now integrates with 21 curated partner solutions across nine security categories, including endpoint protection, threat intelligence, and cloud security posture management. - **Amazon SageMaker AI** supports OpenAI-compatible inference APIs, allowing existing OpenAI-based applications to use SageMaker with minimal or no SDK changes. - **Secrets Manager Agent** can pre-fetch secrets at startup, reducing cold-start delays, and can assume IAM roles for workloads with different permission boundaries. - **Amazon Bedrock** introduced tools for advanced prompt optimization and migration across foundation models. ## Open-Source and Local Development Tools - AWS open-sourced **ExtendDB**, a DynamoDB-compatible adapter for alternative storage backends. - It supports local development and testing without a live AWS connection. - It can help teams retain DynamoDB API semantics while controlling the underlying storage layer. - **AWS SAM CLI** now supports CloudFormation Language Extensions locally, improving consistency between local testing and production deployments. ## Developer Experience and Reliability - **Kiro Web** brings AWS’s AI-assisted, spec-driven development environment to browsers, providing access to chat and agent capabilities without installing the desktop IDE. - AWS updated default retry behavior across SDKs and CLI tools. - Improvements include smarter backoff and better throttling handling. - Production applications should become more resilient to transient failures without additional configuration. ## Container Image Changes - Bitnami images are being removed from Amazon ECR Public. - Teams currently using those images should review the migration timeline and update image references to Bitnami’s own registry to avoid interruptions. ## Upcoming AWS Events - AWS Summit Amsterdam: May 27 - AWS Summit Bangkok: May 28 - AWS Summit Milan: May 28 Builders should evaluate the Istanbul Local Zone for residency- or latency-sensitive systems, consider ExtendDB and SAM improvements for local workflows, and review the Bitnami registry change before images are removed from ECR Public.

Read original

Aws Cloudformation AI AWS Amazon Bedrock+4

awsMar 12, 20262 min readCurated summary

Introducing account regional namespaces for Amazon S3 general purpose buckets | Amazon Web Services

Amazon S3 now lets customers create general purpose buckets in an account regional namespace, making bucket names predictable and reusable across AWS Regions. Names combine a customer-selected prefix with an account-, Region-, and namespace-specific suffix, preventing other accounts from claiming them. The feature preserves existing general purpose bucket capabilities while improving governance and automation. ## Account Regional Bucket Namespaces - Bucket names use a format such as `mybucket-123456789012-us-east-1-an`. - The suffix identifies the AWS account and Region, ensuring that other accounts cannot create buckets using it. - The combined prefix and suffix must be between 3 and 63 characters. - Buckets support the same features as general purpose buckets in the global namespace. ## Governance and Policy Controls - IAM policies and AWS Organizations service control policies can enforce namespace usage. - The new `s3:x-amz-bucket-namespace` condition key allows organizations to require account regional bucket creation. ## Creating Buckets - In the S3 console, select **Account regional namespace** when creating a bucket. - AWS CLI requests use the `--bucket-namespace account-regional` option. - SDKs can pass `BucketNamespace: "account-regional"` to the `CreateBucket` API. - Applications can use STS to retrieve the account ID and the SDK’s Region to construct compliant names. ## Infrastructure as Code - CloudFormation templates can use `AWS::AccountId` and `AWS::Region` to construct bucket names. - The `BucketNamespace: "account-regional"` property enables the feature. - `BucketNamePrefix` can be used when only the customer-defined prefix should appear in the template; AWS adds the account regional suffix automatically. ## Limitations and Availability - Existing global-namespace buckets cannot be renamed into the account regional namespace; new buckets must be created. - The feature applies only to S3 general purpose buckets. - S3 table and vector buckets use account-level namespaces, while directory buckets use zonal namespaces. - It is available in 37 AWS Regions, including AWS China and GovCloud Regions, with no additional cost. Organizations can adopt account regional namespaces to simplify bucket provisioning, prevent naming conflicts, and enforce consistent naming through IAM, Organizations policies, and infrastructure-as-code tools.

Read original

Aws Cloudformation Amazon S3 Aws Cli Aws Iam+3