Infrastructure as Code: Complete AWS Guide to IaC Tools [2026] Managing cloud infrastructure manually is a recipe for inconsistencies, security gaps, and sleepless...

✍️ New blog post by Danny Steenman

Infrastructure as Code: Complete AWS Guide to IaC Tools [2026]

#iac #awscloudformation #awscdk #terraform

AWS CloudFormation StackSets now supports deployment ordering AWS CloudFormation StackSets offers deployment ordering for auto-deployment mode, enabling you to define the sequence in which your stack instances automatically deploy across accounts and regions. This capability allows you to coordinate complex multi-stack deployments where foundational infrastructure must be provisioned before dependent application components. Organizations managing large-scale deployments can now ensure proper deployment ordering without manual intervention. When creating or updating a CloudFormation StackSet, you can specify up to 10 dependencies per stack instances using the new DependsOn parameter in the AutoDeployment configuration, allowing StackSets to automatically orchestrate deployments based on your defined relationships. For example, you can make sure that your networking and security stack instance complete deployment before your application stack instances begin, preventing deployment failures due to missing dependencies. StackSets includes built-in cycle detection to prevent circular dependencies and provides error messages to help resolve configuration issues. This feature is available in all AWS Regions where CloudFormation StackSets is available at no additional cost. Get started by creating or updating your StackSets auto-deployement option through the CLI, SDK or the CloudFormation Console to define dependencies using stack instances ARNs. To learn more about StackSets deployment ordering, check out the detailed feature walkthrough on the https://aws.amazon.com/blogs/devops/take-fine-grained-control-of-your-aws-cloudformation-stacksets-deployment-with-stackset-dependencies/ or visit the https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-manage-auto-deployment.html#stacksets-orgs-auto-deployment-considerations.

AWS CloudFormation StackSets now supports deployment ordering

AWS CloudFormation StackSets offers deployment ordering for auto-deployment mode, enabling you to define the sequence in which your stack instances automatically deploy across acc...

#AWS #AwsCloudformation #AwsCloudformationStacksets

AWS CloudFormation StackSets now supports deployment ordering AWS CloudFormation StackSets offers deployment ordering for auto-deployment mode, enabling you to define the sequence in which your stack instances automatically deploy across accounts and regions. This capability allows you to coordinate complex multi-stack deployments where foundational infrastructure must be provisioned before dependent application components. Organizations managing large-scale deployments can now ensure proper deployment ordering without manual intervention. When creating or updating a CloudFormation StackSet, you can specify up to 10 dependencies per stack instances using the new DependsOn parameter in the AutoDeployment configuration, allowing StackSets to automatically orchestrate deployments based on your defined relationships. For example, you can make sure that your networking and security stack instance complete deployment before your application stack instances begin, preventing deployment failures due to missing dependencies. StackSets includes built-in cycle detection to prevent circular dependencies and provides error messages to help resolve configuration issues. This feature is available in all AWS Regions where CloudFormation StackSets is available at no additional cost. Get started by creating or updating your StackSets auto-deployement option through the CLI, SDK or the CloudFormation Console to define dependencies using stack instances ARNs. To learn more about StackSets deployment ordering, check out the detailed feature walkthrough on the AWS DevOps Blog or visit the AWS CloudFormation User Guide.

🆕 AWS CloudFormation StackSets now supports deployment ordering for automatic, sequential deployment across accounts and regions. Define dependencies to avoid failures; available in all regions at no extra cost. Use CLI, SDK, or Console to set u…

#AWS #AwsCloudformation #AwsCloudformationStacksets

Accelerate infrastructure development with AWS CloudFormation intelligent authoring in IDEs Today, https://docs.aws.amazon.com/cloudformation/ announces the launch of the AWS CloudFormation Language Server, a new capability that brings intelligent authoring, early validation, troubleshooting, and drift management directly into Integrated Development Environment (IDE) through the https://aws.amazon.com/visualstudio/. This new feature empowers developers to build infrastructure faster and deploy safely. With this launch, developers using Visual Studio, Kiro, and other compatible IDEs can now benefit from context-aware authoring powered by the Language Server. It offers built-in auto-complete, schema validation, policy checks using CloudFormation Guard, and deployment validation directly within the IDE. For example, it immediately flags invalid resource properties or missing IAM permission requirements, while the drift-aware deployment view highlights differences between your template and deployed infrastructure, helping you spot configuration changes made outside of CloudFormation. These capabilities help developers identify issues, such as syntax errors, missing permissions, or configuration mismatches before deployment. It also provides a drift view that highlights differences between the current template and the deployed stack configuration. By integrating validation and real-time feedback directly into the authoring experience, the CloudFormation Language Server keeps developers in their flow state, turning infrastructure coding into a seamless experience, and improves infrastructure safety. This unified experience enables developers to move from design to deployment faster while maintaining compliance and best practices, spending more time building and less time troubleshooting. The AWS CloudFormation Language Server is available in all AWS Commercial Regions where AWS CloudFormation is supported. To get started, install or https://marketplace.visualstudio.com/items?itemName=AmazonWebServices.aws-toolkit-vscode the AWS Toolkit. To learn more, refer to https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/ide-extension.html

Accelerate infrastructure development with AWS CloudFormation intelligent authoring in IDEs

Today, https://docs.aws.amazon.com/cloudformation/ announces the launch of the AWS CloudFormation Language Server, a new capability that brings intelligent authoring, early vali...

#AWS #AwsCloudformation

AWS CloudFormation accelerates dev-test cycle with early validation and simplified troubleshooting https://docs.aws.amazon.com/cloudformation/ now offers capabilities that allow customers to catch deployment errors before resource provisioning begins and resolve them more efficiently. Change set creation now provides early feedback on common deployment errors. Stack events are now grouped by an operation ID with access through the new describe-operation API to accelerate analysis of deployment errors. This empowers developers to reduce deployment cycle times and cut troubleshooting time from minutes to seconds. When you create a https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-changesets.html, CloudFormation now validates your template against three common failure causes: invalid property syntax, resource name conflict with existing resources in your account, and S3 bucket emptiness constraint on delete operations. If validation fails, the change set status shows ‘FAILED’ with a detailed status on the validation failure. You can then view details for each failure, including the property path associated with them, to pinpoint exactly where issues occur in your template. When you execute a validated change set, the deployment can still fail because of resource-specific runtime errors, such as resource limits or service-specific constraints. For troubleshooting runtime errors, every stack operation now receives a unique ID. You can zoom into the stack events for an operation and filter down to the events that caused the deployment to fail. This allows you to quickly identify root causes, reducing your troubleshooting time. Get started by creating change sets through the CloudFormation Console, CLI, or SDK. View stack events by operation ID in the CloudFormation Console Events tab or via describe-events API. To learn more, visit the https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/validate-stack-deployments.html and https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/troubleshooting.html#basic-ts-guide User Guide.

AWS CloudFormation accelerates dev-test cycle with early validation and simplified troubleshooting

https://docs.aws.amazon.com/cloudformation/ now offers capabilities that allow customers to catch deployment errors before resource provisioning begins and...

#AWS #AwsGovcloudUs #AwsCloudformation

AWS CloudFormation accelerates dev-test cycle with early validation and simplified troubleshooting AWS CloudFormation now offers capabilities that allow customers to catch deployment errors before resource provisioning begins and resolve them more efficiently. Change set creation now provides early feedback on common deployment errors. Stack events are now grouped by an operation ID with access through the new describe-operation API to accelerate analysis of deployment errors. This empowers developers to reduce deployment cycle times and cut troubleshooting time from minutes to seconds. When you create a change set, CloudFormation now validates your template against three common failure causes: invalid property syntax, resource name conflict with existing resources in your account, and S3 bucket emptiness constraint on delete operations. If validation fails, the change set status shows ‘FAILED’ with a detailed status on the validation failure. You can then view details for each failure, including the property path associated with them, to pinpoint exactly where issues occur in your template. When you execute a validated change set, the deployment can still fail because of resource-specific runtime errors, such as resource limits or service-specific constraints. For troubleshooting runtime errors, every stack operation now receives a unique ID. You can zoom into the stack events for an operation and filter down to the events that caused the deployment to fail. This allows you to quickly identify root causes, reducing your troubleshooting time. Get started by creating change sets through the CloudFormation Console, CLI, or SDK. View stack events by operation ID in the CloudFormation Console Events tab or via describe-events API. To learn more, visit the validate deployment and troubleshooting User Guide.

🆕 AWS CloudFormation now validates templates early, catches errors before provisioning, and groups stack events by operation ID for faster troubleshooting, reducing deployment cycle times and cutting troubleshooting from minutes to seconds.

#AWS #AwsGovcloudUs #AwsCloudformation

Safely handle configuration drift with AWS CloudFormation drift-aware change sets https://docs.aws.amazon.com/cloudformation/ launches drift-aware change sets that can compare an IaC template with the actual state of infrastructure and bring drifted resources in line with their template definitions. Configuration drift occurs when infrastructure managed by IaC is modified via the AWS Management Console, SDK, or CLI. With drift-aware change sets, you can revert drift and keep infrastructure in sync with templates. Additionally, you can preview the impact of deployments on drifted resources and prevent unexpected changes. Customers can modify infrastructure outside of IaC when troubleshooting operational incidents. This creates the risk of unexpected changes in future IaC deployments, impacts the security posture of infrastructure, and hampers reproducibility for testing and disaster recovery. https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-changesets.html can compare a template with your last-deployed template, but do not consider drift. Drift-aware change sets provide a three-way diff between a new template, last-deployed template, and actual infrastructure state. If your diff predicts unintended overwrites of drift, you can update your template values and recreate the change set. During change set execution, CloudFormation will match resource properties with template values and recreate resources deleted outside of IaC. If a provisioning error occurs, CloudFormation will restore infrastructure to its actual state before deployment. To get started, create a change set for an existing stack from the CloudFormation Console and choose “Drift-aware” as the change set type. Alternatively, pass the --deployment-mode REVERT_DRIFT parameter to the https://docs.aws.amazon.com/AWSCloudFormation/latest/APIReference/API_CreateChangeSet.html from the AWS CLI or SDK. To learn more, visit the https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/drift-aware-change-sets.html. Drift-aware change sets are available in AWS Regions where CloudFormation is available. Refer to the https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ to learn more.

Safely handle configuration drift with AWS CloudFormation drift-aware change sets

https://docs.aws.amazon.com/cloudformation/ launches drift-aware change sets that can compare an IaC template with the actual state of infrastructure and bring drifted reso...

#AWS #AwsCloudformation #AwsGovcloudUs

Safely handle configuration drift with AWS CloudFormation drift-aware change sets AWS CloudFormation launches drift-aware change sets that can compare an IaC template with the actual state of infrastructure and bring drifted resources in line with their template definitions. Configuration drift occurs when infrastructure managed by IaC is modified via the AWS Management Console, SDK, or CLI. With drift-aware change sets, you can revert drift and keep infrastructure in sync with templates. Additionally, you can preview the impact of deployments on drifted resources and prevent unexpected changes. Customers can modify infrastructure outside of IaC when troubleshooting operational incidents. This creates the risk of unexpected changes in future IaC deployments, impacts the security posture of infrastructure, and hampers reproducibility for testing and disaster recovery. Standard change sets can compare a template with your last-deployed template, but do not consider drift. Drift-aware change sets provide a three-way diff between a new template, last-deployed template, and actual infrastructure state. If your diff predicts unintended overwrites of drift, you can update your template values and recreate the change set. During change set execution, CloudFormation will match resource properties with template values and recreate resources deleted outside of IaC. If a provisioning error occurs, CloudFormation will restore infrastructure to its actual state before deployment. To get started, create a change set for an existing stack from the CloudFormation Console and choose “Drift-aware” as the change set type. Alternatively, pass the --deployment-mode REVERT_DRIFT parameter to the CreateChangeSet API from the AWS CLI or SDK. To learn more, visit the CloudFormation User Guide. Drift-aware change sets are available in AWS Regions where CloudFormation is available. Refer to the AWS Region table to learn more.

🆕 AWS CloudFormation's drift-aware change sets detect and revert configuration drift, ensuring infrastructure matches IaC templates, preventing unexpected changes and security risks, available in CloudFormation regions.

#AWS #AwsCloudformation #AwsGovcloudUs

AWS CloudFormation Hooks adds granular invocation details for Hooks invocation summary Building on the Hooks Invocation Summary launched in September 2025, AWS CloudFormation Hooks now supports granular invocation details. Hook authors can supplement their Hook evaluation responses with detailed findings, finding severity, and remediation advice. The Hooks console now displays these details at the individual control level within each invocation, enabling developers to quickly identify and resolve specific Hook failures. Customers can easily drill down from the invocation summary to see exactly which controls passed, failed, or were skipped, along with specific remediation guidance for each failure. This granular visibility eliminates guesswork when debugging Hook failures, allowing teams to pinpoint the exact control that blocked a deployment and understand how to fix it. The detailed findings accelerate troubleshooting and streamline compliance reporting by providing actionable insights at the individual control level. The Hooks invocation summary page is available in all commercial and GovCloud (US) regions. To learn more, visit the https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/hooks-view-invocations.html documentation.

AWS CloudFormation Hooks adds granular invocation details for Hooks invocation summary

Building on the Hooks Invocation Summary launched in September 2025, AWS CloudFormation Hooks now supports granular invocation details. Hook authors can supplement the...

#AWS #AwsCloudformation #AwsGovcloudUs

AWS CloudFormation Hooks adds granular invocation details for Hooks invocation summary Building on the Hooks Invocation Summary launched in September 2025, AWS CloudFormation Hooks now supports granular invocation details. Hook authors can supplement their Hook evaluation responses with detailed findings, finding severity, and remediation advice. The Hooks console now displays these details at the individual control level within each invocation, enabling developers to quickly identify and resolve specific Hook failures. Customers can easily drill down from the invocation summary to see exactly which controls passed, failed, or were skipped, along with specific remediation guidance for each failure. This granular visibility eliminates guesswork when debugging Hook failures, allowing teams to pinpoint the exact control that blocked a deployment and understand how to fix it. The detailed findings accelerate troubleshooting and streamline compliance reporting by providing actionable insights at the individual control level. The Hooks invocation summary page is available in all commercial and GovCloud (US) regions. To learn more, visit the AWS CloudFormation Hooks View Invocations documentation.

🆕 AWS CloudFormation Hooks now provide detailed invocation specifics, including findings, severity, and remediation tips, helping developers quickly pinpoint and fix Hook failures, and simplify troubleshooting.

#AWS #AwsCloudformation #AwsGovcloudUs

Tark Labs routine #67: AWS CloudFormation is pretty informative, not very clear, though. Deep dive to the CloudTrail and you will find the problem! 👍 #awsamplify #awscloudtrail #awscloudformation #techforbusiness #tarklabs #airontark

AWS End User Messaging now supports CloudFormation for SMS Today, https://aws.amazon.com/end-user-messaging/ SMS announces support for AWS CloudFormation, enabling customers to deploy and manage SMS resources using AWS CloudFormation templates. Using AWS CloudFormation, customers can standardize how they setup and manage their SMS resources along side their other AWS resources in the development environment simplifying deployments and delivery pipelines. SMS resources supported via CloudFormation include phone numbers, sender IDs, configuration sets, protection configurations, opt-out lists, resource policies, and phone pools. AWS End User Messaging provides developers with a scalable and cost-effective messaging infrastructure without compromising the safety, security, or results of their communications. Developers can integrate messaging to support uses cases such as one-time passcodes (OTP) at sign-ups, account updates, appointment reminders, delivery notifications, promotions and more. Support for CloudFormation for SMS resources is available in all AWS Regions where End User Messaging is available, see the https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ table. To learn more, see https://aws.amazon.com/end-user-messaging/. 

AWS End User Messaging now supports CloudFormation for SMS

Today, https://aws.amazon.com/end-user-messaging/ SMS announces support for AWS CloudFormation, enabling customers to deploy and manage SMS resources using AWS CloudFormation templates. Using AWS...

#AWS #AwsCloudformation #AwsGovcloudUs

AWS End User Messaging now supports CloudFormation for SMS Today, AWS End User Messaging SMS announces support for AWS CloudFormation, enabling customers to deploy and manage SMS resources using AWS CloudFormation templates. Using AWS CloudFormation, customers can standardize how they setup and manage their SMS resources along side their other AWS resources in the development environment simplifying deployments and delivery pipelines. SMS resources supported via CloudFormation include phone numbers, sender IDs, configuration sets, protection configurations, opt-out lists, resource policies, and phone pools. AWS End User Messaging provides developers with a scalable and cost-effective messaging infrastructure without compromising the safety, security, or results of their communications. Developers can integrate messaging to support uses cases such as one-time passcodes (OTP) at sign-ups, account updates, appointment reminders, delivery notifications, promotions and more. Support for CloudFormation for SMS resources is available in all AWS Regions where End User Messaging is available, see the AWS Region table. To learn more, see AWS End User Messaging.

🆕 AWS End User Messaging now supports CloudFormation for SMS, standardizing deployment of phone numbers and sender IDs, simplifying integration and management with other AWS resources. Available in all regions.

#AWS #AwsCloudformation #AwsGovcloudUs

CloudFormation Hooks adds Managed Controls and Hook Activity Summary AWS CloudFormation Hooks now supports managed proactive controls, enabling customers to validate resource configurations against AWS best practices without writing custom Hooks logic. Customers can select controls from the AWS Control Tower Controls Catalog and apply them during CloudFormation operations. When using CloudFormation, customers can configure these controls to run in warn mode, allowing teams to test controls without blocking deployments and giving them the flexibility to evaluate control behavior before enforcing policies in production. This significantly reduces setup time, eliminates manual errors, and ensures comprehensive governance coverage across your infrastructure. AWS also introduced a new Hooks Invocation Summary page in the CloudFormation console. This centralized view provides a complete historical record of Hooks activity, showing which controls were invoked, their execution details, and outcomes such as pass, warn, or fail. This simplifies compliance reporting issues faster. With this launch, customers can now leverage AWS-managed controls as part of their provisioning workflows, eliminating the overhead of writing and maintaining custom logic. These controls are curated by AWS and aligned with industry best practices, helping teams enforce consistent policies across all environments. The new summary page delivers essential visibility into Hook invocation history, enabling faster issue resolution and streamlined compliance reporting. The Hook invocation summary page is available in all commercial and GovCloud (US) regions, and control selection is available in all in all commercials regions. To learn more, visit the https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/proactive-controls-hooks.html andhttps://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/hooks-view-invocations.html documentations.

CloudFormation Hooks adds Managed Controls and Hook Activity Summary

AWS CloudFormation Hooks now supports managed proactive controls, enabling customers to validate resource configurations against AWS best practices without writing custom Hooks logic. C...

#AWS #AwsCloudformation #AwsGovcloudUs

CloudFormation Hooks adds Managed Controls and Hook Activity Summary AWS CloudFormation Hooks now supports managed proactive controls, enabling customers to validate resource configurations against AWS best practices without writing custom Hooks logic. Customers can select controls from the AWS Control Tower Controls Catalog and apply them during CloudFormation operations. When using CloudFormation, customers can configure these controls to run in warn mode, allowing teams to test controls without blocking deployments and giving them the flexibility to evaluate control behavior before enforcing policies in production. This significantly reduces setup time, eliminates manual errors, and ensures comprehensive governance coverage across your infrastructure. AWS also introduced a new Hooks Invocation Summary page in the CloudFormation console. This centralized view provides a complete historical record of Hooks activity, showing which controls were invoked, their execution details, and outcomes such as pass, warn, or fail. This simplifies compliance reporting issues faster. With this launch, customers can now leverage AWS-managed controls as part of their provisioning workflows, eliminating the overhead of writing and maintaining custom logic. These controls are curated by AWS and aligned with industry best practices, helping teams enforce consistent policies across all environments. The new summary page delivers essential visibility into Hook invocation history, enabling faster issue resolution and streamlined compliance reporting. The Hook invocation summary page is available in all commercial and GovCloud (US) regions, and control selection is available in all in all commercials regions. To learn more, visit the AWS CloudFormation Proactive Control Hooks and AWS CloudFormation Hooks View Invocations documentations.

🆕 AWS CloudFormation Hooks now support managed controls and a Hook Activity Summary for better governance, reducing setup time and manual errors. Available in all regions.

#AWS #AwsCloudformation #AwsGovcloudUs

AWS CloudFormation now supports targeted resource scans in the IaC generator Today, AWS CloudFormation introduced a new resource scanning workflow for the CloudFormation IaC generator, further simplifying the process of generating Infrastructure-as-Code (IaC) templates for existing resources in your AWS account. IaC generator allows you to onboard existing resources to CloudFormation in three easy steps. First, you initiate a scan of resources in your AWS account. Second, you select resources for template generation and review suggestions for related resources. Third, a CloudFormation template is generated for selected resources. You can then import resources into a CloudFormation stack, download the template for deployment, or convert the template into a CDK app in your preferred programming language, such as TypeScript or Python. With this launch, you can specify the resource types that IaC generator will cover in the resource scanning step. Instead of scanning all resources by default, you can now focus only on the resources relevant to your workload, reducing scan time and effort. This improves the efficiency of the template generation process and streamlines iterative workflows, such as migration of a prototype workload to CloudFormation. To get started, open the AWS CloudFormation Console and select IaC generator in the navigation panel. You can also use IaC generator from the AWS CLI and AWS SDK. Learn more: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/generate-IaC.html The IaC generator is available in AWS Regions where CloudFormation is available. https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/iac-generator-start-resource-scan.html

AWS CloudFormation now supports targeted resource scans in the IaC generator

Today, AWS CloudFormation introduced a new resource scanning workflow for the CloudFormation IaC generator, further simplifying the process of generating Infrastructure-as-Code ...

#AWS #AwsGovcloudUs #AwsCloudformation

AWS CloudFormation now supports targeted resource scans in the IaC generator Today, AWS CloudFormation introduced a new resource scanning workflow for the CloudFormation IaC generator, further simplifying the process of generating Infrastructure-as-Code (IaC) templates for existing resources in your AWS account. IaC generator allows you to onboard existing resources to CloudFormation in three easy steps. First, you initiate a scan of resources in your AWS account. Second, you select resources for template generation and review suggestions for related resources. Third, a CloudFormation template is generated for selected resources. You can then import resources into a CloudFormation stack, download the template for deployment, or convert the template into a CDK app in your preferred programming language, such as TypeScript or Python. With this launch, you can specify the resource types that IaC generator will cover in the resource scanning step. Instead of scanning all resources by default, you can now focus only on the resources relevant to your workload, reducing scan time and effort. This improves the efficiency of the template generation process and streamlines iterative workflows, such as migration of a prototype workload to CloudFormation. To get started, open the AWS CloudFormation Console and select IaC generator in the navigation panel. You can also use IaC generator from the AWS CLI and AWS SDK. Learn more: User guide The IaC generator is available in AWS Regions where CloudFormation is available. CloudFormation documentation for Partial Scanning

🆕 AWS CloudFormation now supports targeted resource scans in IaC generator, allowing focused scans on specific resource types, reducing effort and improving efficiency for template generation and migration workflows.

#AWS #AwsGovcloudUs #AwsCloudformation

AWS CloudFormation Hooks' new invocation targets and managed Hooks are available in the AWS GovCloud (US) Regions https://aws.amazon.com/cloudformation/?nc2=h_ql_prod_mg_cf Hooks now supports three new invocation points for stacks, change sets, and https://docs.aws.amazon.com/cloudcontrolapi/latest/userguide/what-is-cloudcontrolapi.html (CCAPI) in the AWS GovCloud (US) Regions. You can now evaluate CloudFormation create/update/delete stack and change set operations, and CCAPI create/update operations. With this launch, you can standardize your proactive evaluations beyond CloudFormation resource properties by enabling safety checks that consider the entire context of a stack, a CloudFormation change set, and/or a CCAPI resource configuration. CloudFormation Hooks also extended two new managed hooks to the AWS GovCloud (US) Regions. The managed Lambda and Guard Hook simplify your hooks authoring experience by pointing to an AWS Lambda function or an S3 bucket containing https://docs.aws.amazon.com/cfn-guard/latest/ug/what-is-guard.html domain specific language rules. Today’s launch allows GovCloud customers and partners to leverage the new invocation points and the new managed hooks to help enforce organizational best practices easily and minimize the risk of non-compliant resources being provisioned. With this launch, all CloudFormation Hooks’ features are available in 32 AWS regions globally: US East (Ohio, N. Virginia), US West (N. California, Oregon), Canada (Central, Calgary), Asia Pacific (Singapore, Tokyo, Seoul, Mumbai, Hong Kong, Osaka, Jakarta, Hyderabad, Malaysia, Sydney, Melbourne), Europe (Ireland, Stockholm, Frankfurt, Milan, London, Zurich, Paris, Spain), Middle East (UAE, Bahrain, Tel Aviv), South America (São Paulo), Africa (Cape Town), and the AWS GovCloud (US-East, US-West) Regions. To get started, you can use the new Hooks console workflow within the CloudFormation console, AWS CLI, or new CloudFormation Hooks resources. To learn more, refer to https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/what-is-cloudformation-hooks.html.  

AWS CloudFormation Hooks' new invocation targets and managed Hooks are available in the AWS GovCloud (US) Regions

aws.amazon.com/cloudformation/ Hooks now supports three new invocation points for stacks, change sets, and https...

#AWS #AwsGovcloudUs #AwsCloudformation

AWS CloudFormation Hooks' new invocation targets and managed Hooks are available in the AWS GovCloud (US) Regions AWS CloudFormation Hooks now supports three new invocation points for stacks, change sets, and AWS Cloud Control API (CCAPI) in the AWS GovCloud (US) Regions. You can now evaluate CloudFormation create/update/delete stack and change set operations, and CCAPI create/update operations. With this launch, you can standardize your proactive evaluations beyond CloudFormation resource properties by enabling safety checks that consider the entire context of a stack, a CloudFormation change set, and/or a CCAPI resource configuration. CloudFormation Hooks also extended two new managed hooks to the AWS GovCloud (US) Regions. The managed Lambda and Guard Hook simplify your hooks authoring experience by pointing to an AWS Lambda function or an S3 bucket containing AWS CloudFormation Guard domain specific language rules. Today’s launch allows GovCloud customers and partners to leverage the new invocation points and the new managed hooks to help enforce organizational best practices easily and minimize the risk of non-compliant resources being provisioned. With this launch, all CloudFormation Hooks’ features are available in 32 AWS regions globally: US East (Ohio, N. Virginia), US West (N. California, Oregon), Canada (Central, Calgary), Asia Pacific (Singapore, Tokyo, Seoul, Mumbai, Hong Kong, Osaka, Jakarta, Hyderabad, Malaysia, Sydney, Melbourne), Europe (Ireland, Stockholm, Frankfurt, Milan, London, Zurich, Paris, Spain), Middle East (UAE, Bahrain, Tel Aviv), South America (São Paulo), Africa (Cape Town), and the AWS GovCloud (US-East, US-West) Regions. To get started, you can use the new Hooks console workflow within the CloudFormation console, AWS CLI, or new CloudFormation Hooks resources. To learn more, refer to Hooks User Guide.

🆕 AWS CloudFormation Hooks now support new invocation points and managed hooks in AWS GovCloud (US), enabling proactive evaluations and best practice enforcement across stack operations and CCAPI resource configurations, available in 32 global regions.

#AWS #AwsGovcloudUs #AwsCloudformation

AWS Weekly Roundup: New AWS Mexico (Central) Region, simultaneous sign-in for multiple AWS accounts, and more (January 20, 2025) As winter maintains its hold over where I live in the Netherlands, rare moments of sunlight become precious gifts. This weekend offered one such treasure—while cycling along a quiet canal, golden rays broke through the typically gray Dutch sky, creating a perfect moment of serenity. These glimpses of brightness feel particularly special during January, when […]

AWS Weekly Roundup: New AWS Mexico (Central) Region, simultaneous sign-in for multiple AWS accounts, and more (January 20, 2025)

As winter maintains its hold over where I live in the Netherland...

#AWS #AmazonEc2 #Announcements #AwsCloudformation #AwsManagementConsole #Launch #News #WeekInReview

Announcing AWS CloudFormation support for AWS Transfer Family web apps You can now use AWS CloudFormation templates to create and manage your AWS Transfer Family web apps. This enables you to define and deploy Transfer Family web apps via infrastructure-as-code so you can automate centralized management at scale. With CloudFormation templates, you can programmatically provision and configure your Transfer Family web app, associated customizations, and S3 access grants in a single deployment. This eliminates time-consuming manual configurations and ensures you maintain consistent, secure implementations across departments. You can rapidly scale your file transfer interfaces from hundreds to thousands of users while maintaining strict security and compliance standards through version-controlled infrastructure templates. AWS CloudFormation support is available in all regions where Transfer Family web apps are available. To learn more about Transfer Family web apps, visit the Transfer Family User Guide and read our blog. For sample templates and detailed documentation, visit the AWS CloudFormation documentation.

🆕 Announcing AWS CloudFormation support for AWS Transfer Family web apps

#AWS #AwsCloudformation #AwsTransferFamily

Announcing AWS CloudFormation support for AWS Transfer Family web apps You can now use AWS CloudFormation templates to create and manage your AWS Transfer Family web apps. This enables you to define and deploy Transfer Family web apps via infrastructure-as-code so you can automate centralized management at scale. With CloudFormation templates, you can programmatically provision and configure your Transfer Family web app, associated customizations, and S3 access grants in a single deployment. This eliminates time-consuming manual configurations and ensures you maintain consistent, secure implementations across departments. You can rapidly scale your file transfer interfaces from hundreds to thousands of users while maintaining strict security and compliance standards through version-controlled infrastructure templates. AWS CloudFormation support is available https://docs.aws.amazon.com/transfer/latest/userguide/web-app.html#webapp-regions. To learn more about Transfer Family web apps, visit the https://docs.aws.amazon.com/transfer/latest/userguide/web-app.html and read our https://aws.amazon.com/blogs/aws/announcing-aws-transfer-family-web-apps-for-fully-managed-amazon-s3-file-transfers/. For sample templates and detailed documentation, visit the https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_Transfer.html.

Announcing AWS CloudFormation support for AWS Transfer Family web apps

You can now use AWS CloudFormation templates to create and manage your AWS Transfer Family web apps. This enables you to define and deploy Transfer Family web apps via infrastruct...

#AWS #AwsCloudformation #AwsTransferFamily

AWS Weekly Roundup: AWS Step Functions, AWS CloudFormation, Amazon Q Developer, and more (February 10, 2024) We are well settled into 2025 by now, but many people are still catching up with all the exciting new releases and announcements that came out of re:Invent last year. There have been hundreds of re:Invent recap events around the world since the beginning of the year, including in-person all-day official AWS events with multiple […]

AWS Weekly Roundup: AWS Step Functions, AWS CloudFormation, Amazon Q Developer, and more (February 10, 2024)

We are well settled into 2025 by now, but many people are still catchi...

#AWS #AmazonQDeveloper #Announcements #AwsCloudformation #AwsConfig #AwsStepFunctions #Launch #News #WeekInReview

Reshape your AWS CloudFormation stacks seamlessly with stack refactoring AWS CloudFormation introduces a new capability called stack refactoring that makes it easy to reorganize cloud resources across your CloudFormation stacks. Stack refactoring enables you to move resources from one stack to another, split monolithic stacks into smaller components, and rename the logical name of resources within a stack. This enables you to adapt your stacks to meet architectural patterns, operational needs, or business requirements. As your workloads scale and requirements evolve, re-architecting resources into a new stack structure can become necessary. For example, you may need to split a monolithic stack for easier resource lifecycle management or rename resource logical IDs to align with new naming conventions. Previously, refactoring a stack required multiple manual steps, such as updating templates to retain targeted resources, removing them from current stacks, and then importing them into new stacks. Stack refactoring improves the speed and safety of this process. To refactor a stack, you first provide the CloudFormation templates that reflect the desired stack structure. Then, you generate a preview of the refactor operation, allowing you to confirm that the refactoring changes align with your requirements. If the planned changes meet your expectations, you can execute the refactor operation through an atomic workflow. This new capability enables seamless and continuous adaptation to evolving architectural patterns. Stack refactor is available in all AWS Regions where CloudFormation is supported. To get started, update your CloudFormation templates to reflect the desired stack structure, then use the AWS CLI or SDK to perform the refactor operation. Visit our https://aws.amazon.com/blogs/devops/introducing-aws-cloudformation-stack-refactoring/ to learn more about this feature.  

Reshape your AWS CloudFormation stacks seamlessly with stack refactoring

AWS CloudFormation introduces a new capability called stack refactoring that makes it easy to reorganize cloud resources across your CloudFormation stacks. Stack refactoring enables...

#AWS #AwsGovcloudUs #AwsCloudformation

Reshape your AWS CloudFormation stacks seamlessly with stack refactoring AWS CloudFormation introduces a new capability called stack refactoring that makes it easy to reorganize cloud resources across your CloudFormation stacks. Stack refactoring enables you to move resources from one stack to another, split monolithic stacks into smaller components, and rename the logical name of resources within a stack. This enables you to adapt your stacks to meet architectural patterns, operational needs, or business requirements. As your workloads scale and requirements evolve, re-architecting resources into a new stack structure can become necessary. For example, you may need to split a monolithic stack for easier resource lifecycle management or rename resource logical IDs to align with new naming conventions. Previously, refactoring a stack required multiple manual steps, such as updating templates to retain targeted resources, removing them from current stacks, and then importing them into new stacks. Stack refactoring improves the speed and safety of this process. To refactor a stack, you first provide the CloudFormation templates that reflect the desired stack structure. Then, you generate a preview of the refactor operation, allowing you to confirm that the refactoring changes align with your requirements. If the planned changes meet your expectations, you can execute the refactor operation through an atomic workflow. This new capability enables seamless and continuous adaptation to evolving architectural patterns. Stack refactor is available in all AWS Regions where CloudFormation is supported. To get started, update your CloudFormation templates to reflect the desired stack structure, then use the AWS CLI or SDK to perform the refactor operation. Visit our user guide to learn more about this feature.

🆕 Reshape your AWS CloudFormation stacks seamlessly with stack refactoring

#AWS #AwsGovcloudUs #AwsCloudformation

AWS Weekly Roundup: New AWS Mexico (Central) Region, simultaneous sign-in for multiple AWS accounts, and more (January 20, 2025) As winter maintains its hold over where I live in the Netherlands, rare moments of sunlight become precious gifts. This weekend offered one such treasure—while cycling along a quiet canal, golden rays broke through the typically gray Dutch sky, creating a perfect moment of serenity. These glimpses of brightness feel particularly special during January, when […]

AWS Weekly Roundup: New AWS Mexico (Central) Region, simultaneous sign-in for multiple AWS accounts, and more (January 20, 2025)

As winter maintains its hold over where I live in the Netherlands, rare moment...

#AWS #AmazonEc2 #Announcements #AwsCloudformation #AwsManagementConsole #Launch #News

Announcing AWS User Notifications GA on AWS CloudFormation AWS User Notifications is now supported on AWS CloudFormation, allowing you to easily provision and manage User Notification resources as part of your application's infrastructure-as-code (IaC). You can easily use User Notification to Configure Notifications to be sent via the Console Notifications Center, email, AWS Chatbot, or mobile push notifications to the AWS Console Mobile App to keep you informed about important events like Amazon CloudWatch Alarms. With this new capability, you can define Notification Configurations as part of your IaC practices. Specify notification configurations for specific resource types within your CloudFormation templates. For example, set up notifications to trigger when an Auto Scaling group scales out, an ELB is provisioned, or an RDS database is modified. You have granular control over which events will trigger notifications and who should receive them. This integration simplifies cloud operations by consolidating monitoring configuration right alongside your IaC templates. No more context switching between services - your notifications are defined declaratively within your infrastructure code. Setting up stack notifications is easy - just add the Notifications or NotificationContacts resource type (e.g., AWS::Notifications::NotificationConfiguration) in your CloudFormation template to configure the desired events and channels. For more information, visit the https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_Notifications.html and https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_NotificationsContacts.html resource type reference. To learn more about User Notifications, visit the https://aws.amazon.com/notifications/ and https://docs.aws.amazon.com/notifications/latest/userguide/what-is-service.html.  

Announcing AWS User Notifications GA on AWS CloudFormation

AWS User Notifications is now supported on AWS CloudFormation, allowing you to easily provision and manage User Notification resources as part of your application's infrastructure-as-code (IaC). You can easily ...

#AWS #AwsCloudformation

Announcing AWS User Notifications GA on AWS CloudFormation AWS User Notifications is now supported on AWS CloudFormation, allowing you to easily provision and manage User Notification resources as part of your application's infrastructure-as-code (IaC). You can easily use User Notification to Configure Notifications to be sent via the Console Notifications Center, email, AWS Chatbot, or mobile push notifications to the AWS Console Mobile App to keep you informed about important events like Amazon CloudWatch Alarms. With this new capability, you can define Notification Configurations as part of your IaC practices. Specify notification configurations for specific resource types within your CloudFormation templates. For example, set up notifications to trigger when an Auto Scaling group scales out, an ELB is provisioned, or an RDS database is modified. You have granular control over which events will trigger notifications and who should receive them. This integration simplifies cloud operations by consolidating monitoring configuration right alongside your IaC templates. No more context switching between services - your notifications are defined declaratively within your infrastructure code. Setting up stack notifications is easy - just add the Notifications or NotificationContacts resource type (e.g., AWS::Notifications::NotificationConfiguration) in your CloudFormation template to configure the desired events and channels. For more information, visit the Notifications and NotificationsContacts resource type reference. To learn more about User Notifications, visit the product page and documentation.

🆕 Announcing AWS User Notifications GA on AWS CloudFormation

#AWS #AwsCloudformation

Accelerate AWS CloudFormation troubleshooting with Amazon Q Developer assistance AWS CloudFormation now offers generative AI assistance powered by Amazon Q Developer to help troubleshoot unsuccessful CloudFormation deployments. This new capability provides easy-to-understand analysis and actionable steps to simplify the resolution of the most common resource provisioning errors encountered during CloudFormation deployments. When creating or modifying a CloudFormation stack, CloudFormation can encounter errors in resource provisioning, such as missing required parameters for an EC2 instance or inadequate permissions. Previously, troubleshooting a failed stack operation could be a time-consuming process. After identifying the root cause of the failure, you had to search through blogs and documentation for solutions and determine the next steps, leading to longer resolution times. Now, when you review a failed stack operation in the CloudFormation Console, CloudFormation automatically highlights the likely root cause of the failure. You can click the "Diagnose with Q" button in the error alert box and Amazon Q Developer will provide a human-readable analysis of the error, helping you understand what went wrong. If you need further assistance, you can click the "Help me resolve" button to receive actionable resolution steps tailored to your specific failure scenario, helping you accelerate resolution of the error. To get started, open the CloudFormation Console and navigate to the stack events tab for a provisioned stack. This feature is available in AWS Regions where AWS CloudFormation and Amazon Q Developer are available. Refer to the AWS Region table for service availability details. Visit our https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-troubleshooting-with-amazon-q.html to learn more about this feature.  

Accelerate AWS CloudFormation troubleshooting with Amazon Q Developer assistance

AWS CloudFormation now offers generative AI assistance powered by Amazon Q Developer to help troubleshoot unsuccessful CloudFormation deployments. This new ...

#AWS #AmazonQ #AmazonMachineLearning #AwsCloudformation

AWS CloudFormation Hooks now allows AWS Cloud Control API resource configurations evaluation https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/what-is-cloudformation-hooks.html now allow you to evaluate resource configurations from https://docs.aws.amazon.com/cloudcontrolapi/ create and update operations. Hooks allow you to invoke custom logic to enforce security, compliance, and governance policies on your resource configurations. CCAPI is a set of common application programming interfaces (APIs) that is designed to make it easy for developers to manage their cloud infrastructure in a consistent manner and leverage the latest AWS capabilities faster. By extending Hooks to CCAPI, customers can now inspect resource configurations prior to CCAPI create and update operations, and block or warn the operations if there is a non-compliant resource found. Before this launch, customers would publish Hooks that would only be invoked during CloudFormation operations. Now, customers can extend their resource Hook evaluations beyond CloudFormation to CCAPI based operations. Customers with existing resource Hooks, or who are using the recently launched pre-built Lambda and Guard hooks, simply need to specify https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/hooks-concepts.html#hook-terms-hook-target in the hooks’ configuration. Hooks is available in all https://aws.amazon.com/about-aws/global-infrastructure/regions_az/. The CCAPI support is available for customers who use CCAPI directly or third-party IaC tools that have CCAPI providers support. To get started, refer to Hooks user guide and CCAPI user guide for more information. Learn the detail of this feature from this https://aws.amazon.com/blogs/devops/introducing-aws-cloudformation-hooks-invoked-via-aws-cloud-control-api-ccapi/.  

AWS CloudFormation Hooks now allows AWS Cloud Control API resource configurations evaluation

docs.aws.amazon.com/cloudformation-cli/lates... now allow you to evaluate resource configurations from ht...

#AWS #AwsGovcloudUs #AwsCloudformation