Please enable JavaScript.

Coggle requires JavaScript to display documents.

CF (clouodformation, best practise, depends on, cfn-init, wait, AMI,…

- - - - https://aws.amazon.com/blogs/aws/aws-cloudformation-template-editors-for-visual-studio-and-eclipse/
    - - AWS Toolkit for Visual Studio Demo
  - - - AWS CloudFormation is used mainly for automating deployments of different applications. If your application
      - has cross-region and multi-accounts deployment requirements, you should consider using StackSets. This will
      - allow you to do these kinds of deployment simultaneously with ea
  - - - As your infrastructure grows, there will be some cases where you need to declare the same resources to
      - multiple CloudFormation templates. In these instances, it is a good practice to use nested stacks. You can
      - create separate templates for these common resources and reference that on other templates. This way, you’ll
      - avoid copying and pasting the same configuration on your templates, and this also simplifies stack updates.
- - - - As a part of user experience, you want to pause completion of the CloudFormation template and display of the output section until all resources are properly provisioned and in a working state.
      - There are resource dependencies where some additional scripts and packages on your instance must be properly configured before other AWS resources can contact them. For example, for successful backend configuration, a front end application should be in a running state.
      - An environment in which Active Directory should be in a running state before other instances perform authentication.
      - A NAT instance should be in working state before private subnet instances try to fetch packages from the outside world.
    - - When the WaitCondition resource is created, a timer is started.
      - The WaitCondition becomes CREATE_COMPLETE after it receives a success signal.
      - If no signal is received before the timeout, the WaitCondition enters the CREATE_FAILED state and the stack creation is rolled back.
- - - - enables you to detect whether a stack's actual configuration differs, or has drifted, from
      - its expected configuration. Use CloudFormation to detect drift on an entire stack, or on individual
      - resources within the stack.
      - ○ A resource is considered to have drifted if any if its actual property values differ from the
      - expected property values.
      - ○ A stack is considered to have drifted if one or more of its resources have drifted