Jump to content

Search the Community

Showing results for tags 'cloudformation'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • Welcome New Members !
    • General Discussion
    • Site News
  • DevOps & SRE
    • DevOps & SRE General Discussion
    • Databases, Data Engineering, Data Science, BI & AI
    • Development & Programming
    • Deployments, CI/CD & GitOps
    • Docker, Containers, Microservices & Serverless
    • Infrastructure-as-Code
    • Kubernetes
    • Linux
    • Monitoring, Observability & Logging
    • Security
  • Cloud Providers
    • Amazon Web Services
    • Google Cloud Platform
    • Microsoft Azure
    • Red Hat OpenShift

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL

LinkedIn Profile URL

About Me

Development Experience

Cloud Experience

Current Role



Favourite Tools


Found 22 results

  1. Amazon Connect now supports AWS CloudFormation for security profiles. You can now use AWS CloudFormation templates to deploy Amazon Connect security profiles —along with the rest of your AWS infrastructure— in a secure, efficient, and repeatable way, allowing you to apply consistent security policies across instances. CloudFormation allows you to track changes over time, apply updates in a controlled and automated manner, and includes version controls so you can easy roll back changes if needed. For more information, see Amazon Connect Resource Type Reference in the AWS CloudFormation User Guide. View the full article
  2. AWS HealthImaging now supports AWS CloudFormation. With CloudFormation support, you can now use CloudFormation templates to create and delete your AWS HealthImaging resources. This helps you automate and standardize DevOps processes across your AWS accounts and AWS Regions for AWS HealthImaging. View the full article
  3. Infrastructure as Code (IaC) has emerged as a critical tenet in cloud computing, making efficient resource management possible across cloud environments. Terraform and AWS CloudFormation are two leading tools in IaC that facilitate the provisioning and management of infrastructure resources. While both offer similar functionalities, their fundamental differences make each suitable for different use cases. In this blog post, we will learn about the key differences between Terraform and CloudFormation. But first, let's understand what Terraform and CloudFormation are... View the full article
  4. Today, AWS Backup announces support for AWS CloudFormation resource exclusion, allowing you to exclude resources from your application backups. AWS Backup is a fully managed service that centralizes and automates data protection across AWS services and hybrid workloads. Now, when assigning resources to backup plans, you can exclude specific resources within your CloudFormation stacks, optimizing cost on non-critical resources. View the full article
  5. Changes to AWS CloudFormation-based stacks and resources are now available as event notifications in Amazon EventBridge. Customers can use these event notifications to build and scale loosely-coupled event-driven applications. With this feature, customers can trigger actions in real-time after they create, update, or delete either their CloudFormation stacks or resources in their CloudFormation stacks without having to write single-use custom code or develop new software. View the full article
  6. AWS CloudFormation StackSets launched a new feature that allows you to deploy stack sets to selected AWS accounts in an Organizational Unit (OU) in a single operation. You can use this feature to target or skip stack sets deployment to AWS accounts within an OU. For example, you can use this feature to skip deployment of an AWS Config policy in AWS accounts that already have the policy within an OU. In a few clicks, you can re-deploy stack sets to those AWS accounts in which the earlier stack sets deployment had failed. Similarly, you can skip stack set deployment to suspended AWS accounts in an OU. View the full article
  7. AWS CloudFormation announces the general availability (GA) of AWS CloudFormation Guard 2.1 (cfn-guard), which enhances Guard 2.0 with new features. CloudFormation Guard is an open-source domain-specific language (DSL) and command line interface (CLI) that helps enterprises keep their AWS infrastructure and application resources in compliance with their company policy guidelines. CloudFormation Guard provides compliance administrators with a simple, policy-as-code language to define rules that can check for both required and prohibited resource configurations. It enables developers to validate their templates (CloudFormation Templates, K8s configurations, and Terraform JSON configurations) against those rules. View the full article
  8. This article will explore CloudFormation basic best practices you can use to build and maintain CloudFormation templates; https://bridgecrew.io/blog/basic-best-practices-guidelines-cloudformation-security/
  9. AWS CloudFormation announces the launch of the CloudFormation Public Registry, a new searchable collection of extensions that allows you to discover, provision, and manage third-party extensions, which include resource types (provisioning logic) and modules published by AWS Partner Network (APN) Partners and the developer community. You can also create and publish your own extensions on the CloudFormation Public Registry, allowing anyone to use them. Today, you can centrally search and use over 35 extensions published on the Public Registry by APN Partners and AWS Quick Starts. You can view the identity verification for each extension publisher on the Public Registry. APN Partners who collaborated on this launch include MongoDB, Datadog, Atlassian Opsgenie, JFrog, Trend Micro, Splunk, Aqua Security, FireEye, Sysdig, Snyk, Check Point, Spot by NetApp, Gremlin, Stackery, and Iridium. View the full article
  10. You can now define your infrastructure and applications in AWS CloudFormation with reusable building blocks called modules. A module encapsulates one or more resources and their respective configurations for reuse across your organization. View the full article
  11. AWS CloudFormation is extending change sets to support applications modeled with nested stacks, enhancing the predictability of update operations. With this launch, you can now preview the changes to your application and infrastructure resources across the entire nested stack hierarchy and proceed with the update only when you confirm that all the changes are as intended. View the full article
  12. AWS Service Catalog administrators can now add Service Catalog governance to their existing AWS CloudFormation stacks. Once imported into Service Catalog, administrators can manage stack updates, govern parameters, and enforce tagging. With this new feature, long-running stacks can be governed while leaving the underlying resources untouched. View the full article
  13. Homepage About AWS CloudFormation provides a common language for you to describe and provision all the infrastructure resources in your cloud environment. CloudFormation allows you to use a simple text file to model and provision, in an automated and secure manner, all the resources needed for your applications across all regions and accounts. This file serves as the single source of truth for your cloud environment. AWS CloudFormation is available at no additional charge, and you pay only for the AWS resources needed to run your applications. Benefits MODEL IT ALL AWS CloudFormation allows you to model your entire infrastructure in a text file. This template becomes the single source of truth for your infrastructure. This helps you to standardize infrastructure components used across your organization, enabling configuration compliance and faster troubleshooting. AUTOMATE AND DEPLOY AWS CloudFormation provisions your resources in a safe, repeatable manner, allowing you to build and rebuild your infrastructure and applications, without having to perform manual actions or write custom scripts. CloudFormation takes care of determining the right operations to perform when managing your stack, and rolls back changes automatically if errors are detected. IT'S JUST CODE Codifying your infrastructure allows you to treat your infrastructure as just code. You can author it with any code editor, check it into a version control system, and review the files with team members before deploying into production.
  14. AWS CodeArtifact now supports AWS CloudFormation, enabling customers to create and manage CodeArtifact repositories with CloudFormation. View the full article
  15. Amazon S3 Object Ownership is now generally available with the addition of support for AWS CloudFormation. S3 Object Ownership is a new S3 feature that enables bucket owners to automatically assume ownership of objects that are uploaded to their buckets by other AWS Accounts. This helps you to standardize ownership of new objects in your bucket, and to share and manage access to these objects at scale via resource-based policies such as a bucket policy or an access point policy. Whether your S3 bucket receives data from other AWS accounts, or stores output from AWS services like AWS CloudTrail, S3 Object Ownership simplifies the work of creating and maintaining shared data sets on Amazon S3. View the full article
  16. AWS IoT SiteWise now supports AWS CloudFormation, enabling customers to create and manage SiteWise Asset Models, Assets and Gateway resources using CloudFormation. View the full article
  17. Amazon Elastic Container Service (Amazon ECS) on AWS Fargate capacity providers is now supported in AWS CloudFormation, which makes it easier to manage and run Amazon ECS tasks across Fargate and Fargate Spot. You can now use CloudFormation to automate the management of Fargate capacity providers, associate them with ECS clusters, and specify capacity provider strategies at the cluster and service level by using a CloudFormation template. View the full article
  18. Amazon Elastic Container Service (Amazon ECS) on AWS Fargate capacity providers is now supported in AWS CloudFormation, which makes it easier to manage and run Amazon ECS tasks across Fargate and Fargate Spot. You can now use CloudFormation to automate the management of Fargate capacity providers, associate them with ECS clusters, and specify capacity provider strategies at the cluster and service level by using a CloudFormation template. View the full article
  19. AWS CloudFormation now supports increased limits on five service quotas - template size, resources, parameters, mappings, and outputs. The maximum size of a template that can be passed in an S3 Object is now 1MB (previously 450KB). The new per template limits for the maximum number of resources is 500 (previously 200), parameters is 200 (previously 60), mappings is 200 (previously 100), and outputs is 200 (previously 60). View the full article
  20. In this post, we discuss and build a managed continuous integration and continuous deployment (CI/CD) pipeline that uses AWS CloudFormation Guard to automate and simplify pre-deployment compliance checks of your AWS CloudFormation templates. This enables your teams to define a single source of truth for what constitutes valid infrastructure definitions, to be compliant with your company guidelines and streamline AWS resources’ deployment lifecycle... View the full article
  21. What cloud providers do you work with? Google Cloud Platform (GCP)? Amazon AWS? Microsoft Azure? Which services? Are you using a managed Kubernetes such as GKE, AKS, Openshift or EKS? How do you manage your cloud resources? How do you manage the release cycle of the infrastructure and applications that you deploy? If the above […] The post Cloud Orchestration Language Roundup: A Comparison appeared first on DevOps.com. View the full article
  22. Developing and managing cloud infrastructure is a complex process. It becomes a sticky wicket especially when you have a distributed team. With the continuous alterations in technology and methods, it has become trickier to provision, deploy and configure resources when we need to identify errors and come up with solutions on the go. Infrastructure as a Code (IaC) comes in handy in this situation. IaC is a method of defining your infrastructure through configuration files, also known as codes. It allows you to automate your infrastructure using high-level descriptive coding language-based configuration files. Plus, IaC helps you to supervise your configuration files as in a software code that comes with code repositories. However, when it's about implementing infrastructure as code on AWS, people often boil down to Cloudformation and Terraform.
  • Forum Statistics

    Total Topics
    Total Posts
  • Create New...