Discover more about what's new at AWS with AWS CloudFormation introduces the option to troubleshoot provisioning errors before rollback, accelerating deployments

AWS IAM helps you control who can access your AWS resources and what they are allowed to do. This short guide explains users, policies, roles, and the importance of least privilege.

What Happened On October 22, 2026, AWS announced four updates relevant to teams operating AI applications and their infrastructure: CloudFormation force rollback: A single continue-update-rollback operation can return a stuck…

AWS CloudFormation || Templates || Stacks || Parameters || Drift Detection

While exploring the latest AWS updates, I came across a really interesting improvement for Kafka + Lambda.

Explore how Amazon Bedrock AgentCore and Apache SkyWalking can help developers collect AI agent execution sessions, analyze agent behaviour locally, identify issues, and improve performance. Learn how observability and session evaluation contribute to building more reliable, transparent, and production-ready AI agents.

AWS CloudFormation is the foundational tool of infrastructure-as-code for thousands of organizations running workloads on AWS. But as teams push the boundaries of what CloudFormation can do natively, custom resources have emerged as a powerful extension mechanism that unlocks a broad range of possibilities. Yet, when it comes to building resilient, multi-Region deployments with custom […]

Discover how AWS helps businesses protect critical data, recover applications, and maintain business continuity during unexpected failures. Explore disaster recovery strategies, essential AWS services, and practical solutions for building resilient cloud applications.

If you're a college student planning to enter cloud computing or DevOps, you've probably seen the huge number of services offered by AWS. EC2, S3, IAM, VPC, Lambda, EKS, CloudFormation and the list goes on. The challenge isn't finding resources to learn AWS. It's knowing what to learn first, what comes next, and which skills actually matter when building real applications.

This article demonstrates how to use AWS CDK with CloudFormation custom resources to automatically orchestrate SageMaker AI endpoint auto scaling during configuration updates.

Updating a SageMaker AI endpoint that has Application Auto Scaling registered makes AWS CloudFormation and AWS CDK deployments fail. This post shows how to build a reusable AWS CDK construct with CloudFormation custom resources that deregisters and re-registers auto scaling automatically, so you can update the endpoint and its scaling in a single deployment.

Updating a SageMaker AI endpoint that has Application Auto Scaling registered makes AWS CloudFormation and AWS CDK deployments fail. This post shows how to build a reusable AWS CDK construct with CloudFormation custom resources that deregisters and re-registers auto scaling automatically, so you can update the endpoint and its scaling in a single deployment.

An interactive, real-time visual diagram inside AWS CloudFormation that highlights state drift on deployed resources with one-click options to revert changes or sync them back into code.

https://docs.aws.amazon.com/cloudformation/ now makes it simpler to complete an update rollback and get back to deploying. An update rollback returns your stack to a known good state. Starting today, if some resources cannot roll back automatically, force rollback enables you to complete the rollback it in a single operation. It works across every CloudFormation workflow, from the https://docs.aws.amazon.com/cli/latest/reference/cloudformation/, and SDKs to https://docs.aws.amazon.com/cdk/v2/guide/ and AI agents. With force rollback, CloudFormation completes the update rollback and returns your stack to a deployable state in a single operation, instead of requiring you to identify, list, and retry the operation for each affected resource. Any resource that still needs attention, such as one affected a change outside CloudFormation, is recorded for you to review and resolve it before your next deployment. To get started, run continue update rollback with the force rollback option, then create a https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/drift-aware-change-sets.html to review any configuration differences before your next deployment. To learn more, see   https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-continueupdaterollback.html in the AWS CloudFormation User Guide. Force rollback is available in all Regions at no additional cost. Refer to the   https://docs.aws.amazon.com/general/latest/gr/cfn.html#cfn_region for service availability details.

AWS CloudFormation now makes it simpler to complete an update rollback and get back to deploying. An update rollback returns your stack to a known good state. Starting today, if some resources cannot roll back automatically, force rollback enables you to complete the rollback it in a single operation. It works across every CloudFormation workflow, from the AWS CLI, and SDKs to AWS CDK and AI agents. With force rollback, CloudFormation completes the update rollback and returns your stack to a deployable state in a single operation, instead of requiring you to identify, list, and retry the operation for each affected resource. Any resource that still needs attention, such as one affected a change outside CloudFormation, is recorded for you to review and resolve it before your next deployment. To get started, run continue update rollback with the force rollback option, then create a drift-aware change set to review any configuration differences before your next deployment. To learn more, see  Continue rolling back an update  in the AWS CloudFormation User Guide. Force rollback is available in all Regions at no additional cost. Refer to the  AWS Region table  for service availability details.

AWS CloudFormation now makes it simpler to complete an update rollback and get back to deploying. An update rollback returns your stack to a known good state. Starting today, if some resources cannot roll back automatically, force rollback enables you to complete the rollback it in a single operation. It works across every CloudFormation workflow, from the AWS CLI, and SDKs to AWS CDK and AI agents. With force rollback, CloudFormation completes the update rollback and returns your stack to a deployable state in a single operation, instead of requiring you to identify, list, and retry the operation for each affected resource. Any resource that still needs attention, such as one affected a change outside CloudFormation, is recorded for you to review and resolve it before your next deployment. To get started, run continue update rollback with the force rollback option, then create a drift-aware change set to review any configuration differences before your next deployment. To learn more, see  Continue rolling back an update  in the AWS CloudFormation User Guide. Force rollback is available in all Regions at no additional cost. Refer to the  AWS Region table  for service availability details.

Discover how to start learning AWS Cloud from scratch using free learning resources, hands-on projects, digital badges, and a step-by-step certification preparation plan. A practical guide for students, freshers, and aspiring cloud professionals.

AWS Identity and Access Management (IAM) helps control who can access AWS resources and what actions they can perform. Explore IAM users, groups, roles, policies, and essential security practices for building a more secure cloud environment.

What Happened On October 7, 2026, AWS added feature-level availability notifications and advanced filters to AWS Capabilities by Region. Users can follow a service or an individual feature in selected…

Day 16 of my 90-day AWS challenge: how AWS CloudFormation builds and manages resources from a template instead of manual clicks, the key concepts (stacks, parameters, outputs, change sets), and how I created, updated, and deleted my first stack.

Run a standard Node.js web server on AWS Lambda with Lambda Web Functions, a new type of Lambda function. Deploy it with one command or AWS CloudFormation and get a public HTTPS endpoint with no adapt...

In this article, I explore how AWS services like Amazon S3, SageMaker, and EC2 can work together to build and deploy a real-world AI/ML application. My goal is to strengthen my cloud computing skills through practical learning, understand the ML deployment workflow, and share my journey with the developer community. 🚀

Security is one of the fundamental pillars of AWS. In this article, we will explore AWS Identity and Access Management (IAM), how users, groups, roles, and policies work, and why the principle of least privilege is essential for protecting cloud resources.

Amazon SageMaker Unified Studio now supports custom Tooling blueprints, giving domain administrators the ability to define the foundation of every project by using their own AWS CloudFormation templates. Administrators can tailor project environments to meet organization-specific requirements, such as IAM role names that comply with company naming standards or custom permissions boundaries instead of AWS managed policies. Amazon SageMaker Unified Studio administrators start by authoring a CloudFormation template that describes the project environment they need, then register it as a custom Tooling blueprint. The service validates the template at registration and again after each project deployment, confirming that the required resources exist before any team member uses the project. Templates can include any CloudFormation-supported resource, such as AWS Lake Formation grants, Amazon Athena workgroups, or VPC security groups, and work across multiple AWS accounts and Regions without per-project edits. At deployment time, the service automatically populates reserved template parameters, such as the project ID and domain ID, so administrators define the template once and apply it everywhere. This feature is available in all AWS Regions where Amazon SageMaker Unified Studio is available. To learn more, visit the Custom blueprints as Tooling documentation.