![Debug Stack (awscli)
$
$ aws cloudformation describe-stack-events --stack-name test-stack | jq ‘.StackEvents[] |
{Timestamp,ResourceStatus,ResourceType,ResourceStatusReason}’
"Timestamp": "2017-04-17T23:12:51.059Z",
"ResourceStatus": "CREATE_FAILED",
"ResourceType": "AWS::S3::Bucket",
"ResourceStatusReason": "capital-saratoga-region-aws-user-group already exists in stack
arn:aws:cloudformation:us-east-1:740427342325:stack/test-stack/50d535e0-23c1-11e7-9f58-
50faeaee44fd"](https://image.slidesharecdn.com/cloudformation101-170420210803/85/Cloudformation101-38-320.jpg)
Ad
More Related Content
What's hot (20)
Similar to Cloudformation101 (20)
Ad
Recently uploaded (20)
Ad
Cloudformation101
- 2. What is CloudFormation? CloudFormation is a zero cost AWS service for provisioning resources in a predictable, repeatable and automated way. ** While CloudFormation does not cost anything the resources CloudFormation provisions do https://github.com/dpigliavento/cloudformation
- 3. Why Use CloudFormation? • No more clicking • How do you know what changed and when? • Infrastructure as code • version controlled, know exactly what changed and when • Easy to integrate in deployment pipeline • Easy to replication infrastructure • Build a common set of templates used across your organization
- 4. Rules of the Road: • Do not start with CloudFormation! • Learn first in the console • Understand available options for a given service before jumping into CloudFormation • Don’t reinvent the wheel • Find a template online to start with • CloudFormation designer is a GUI tool for authoring templates • Do not manually change resources CloudFormation deployed • Future updates could potentially fail as a result
- 5. CloudFormation Concepts • Template • AWS infrastructure blueprint • JSON or YAML formatted document • Stack • A collection of resources that are managed as a single unit • Group resources that live the same lifecycle in a single stack • Change Set • dry-run for updating an existing stack • provides the list of actions that will be taken
- 6. • Update behavior of stack resources • Updates with no Interruption • Updates with Some Interruption • Replacement • Unintended Resource Deletion • Be careful with certain resources, if a change is not allowed for a given parameter CloudFormation will destroy the existing and create a new resource (.i.e DynamoDB local index)
- 8. CloudFormation Template Anatomy (YAML)
- 9. CloudFormation Template Anatomy Required: No 2010-09-09 is currently the only available options. This setting identifies the capabilities of the template. Play it safe and include this in all your templates. When AWS does decide to add a new version you don’t need to update existing templates.
- 10. CloudFormation Template Anatomy Required: Yes • The meat of a CloudFormation template • All the AWS resources and their respective properties
- 11. CloudFormation Template Anatomy Required: No • Description of the template and the created stack
- 12. CloudFormation Template Anatomy Required: No • Input parameters for customizing deployed resources • Allows you to generalize CloudFormation templates for reuse
- 13. CloudFormation Template Anatomy Required: No • Provides a hash map of values that can be referenced within your template • Common use case is regional or environment specific values
- 14. CloudFormation Template Anatomy Required: No • Allows you to define conditionals controlling when a resource is created or a property is defined
- 15. CloudFormation Template Anatomy Required: No • Values you stack can output for information purposes or to provide cross stack references
- 18. S3 Example - Template
- 19. S3 Example - Template
- 20. Intrinsic Functions Use intrinsic functions in your templates to assign values to properties that are not available until runtime • Fn::Base64 • Condition Functions • Fn::And • Fn::Equals • Fn::If • Fn::Not • Fn::Or • Fn::FindInMap • Fn::GetAtt • Fn::GetAZs • Fn::ImportValue • Fn::Join • Fn::Select • Fn::Split • Fn::Sub • Ref YAML Syntactic Sugar !ImportValue !Sub !Ref
- 21. Pseudo Parameters Predefined parameters available in your CloudFormation templates • AWS::AccountId • AWS::NotificationARNs • AWS::NoValue • AWS::Region • AWS::StackId • AWS::StackName
- 22. S3 Example - Template
- 23. S3 Example - Template Resource Logical Id should not be changed once created.
- 24. S3 Example – Changed Existing Logical ID
- 25. • Do not change logical id once created. • Logical Ids are relevant only to the stack they are deployed. You can reference within a single stack but not outside from other stacks. • Logical Ids must be unique within a given stack.
- 26. Extend S3 Template Cross-Region Replication
- 27. S3 Example - Template Input validation • AllowedValues • AllowdPatterns via regex • MinValue/MaxValue for Integer • MinLength/MaxLength for strings
- 28. S3 Example - Template ReplicateBucket is True if RemoteRegion parameter is NOT equal to Disabled
- 29. S3 Example - Template CreateRole is True if ReplicationRole parameter is and empty string and the condition ReplicateBucket is True
- 30. S3 Example - Template S3 cross-region replication requires that versioning be enabled on the bucket
- 31. S3 Example - Template Conditional parameter block, AWS::NoValue will remove the parameter when set.
- 32. S3 Example - Template
- 33. Dependencies Cloudformation resources have implicit dependences based on the Ref and GetAtt functions but you can explicitly define them as well.
- 34. Deploying Stacks Using AWSCLI
- 35. Deploying Stack (awscli) - Success $ $ aws cloudformation deploy --stack-name test-stack --template-file stack.yaml –region us-west-2 Waiting for changeset to be created.. Waiting for stack create/update to complete Successfully created/updated stack - test-stack
- 36. Deploying Stack (awscli) - Failure $ $ aws cloudformation deploy --stack-name test-stack --template-file stack.yaml Waiting for changeset to be created.. Waiting for stack create/update to complete Failed to create/update the stack. Run the following command to fetch the list of events leading up to the failure aws cloudformation describe-stack-events --stack-name test-stack
- 37. Debug Stack (awscli) $ $ aws cloudformation describe-stack-events --stack-name test-stack { "StackEvents": [ { "StackId": "arn:aws:cloudformation:us-east-1:740427342325:stack/test-stack/50d535e0-23c1-11e7-9f58-50faeaee44fd", "EventId": "6a0ad860-23c3-11e7-8311-500c286e44d1", "ResourceStatus": "UPDATE_ROLLBACK_COMPLETE", "ResourceType": "AWS::CloudFormation::Stack", "Timestamp": "2017-04-17T23:13:06.110Z", "StackName": "test-stack", "PhysicalResourceId": "arn:aws:cloudformation:us-east-1:740427342325:stack/test-stack/50d535e0-23c1-11e7-9f58-50faeaee44fd", "LogicalResourceId": "test-stack" }, ...
- 38. Debug Stack (awscli) $ $ aws cloudformation describe-stack-events --stack-name test-stack | jq ‘.StackEvents[] | {Timestamp,ResourceStatus,ResourceType,ResourceStatusReason}’ "Timestamp": "2017-04-17T23:12:51.059Z", "ResourceStatus": "CREATE_FAILED", "ResourceType": "AWS::S3::Bucket", "ResourceStatusReason": "capital-saratoga-region-aws-user-group already exists in stack arn:aws:cloudformation:us-east-1:740427342325:stack/test-stack/50d535e0-23c1-11e7-9f58- 50faeaee44fd"
- 47. Exports
- 48. EC2 Example Template – Userdata Script
- 49. How does CloudFormation know when my EC2 instance is ready?
- 50. CloudFormation Signaling • Allows for external validation to occur before CloudFormation considers a resource complete • Ensures that your EC2 configuration is complete before CloudFormation continues • Can be a Create and/or Update policy for EC2 and ASG
- 51. EC2 Example Template – CreatePolicy
- 52. EC2 Example Template – cfn-signal
- 54. Cloudformation Helper Scripts • A set of tools to assist with the configuration of EC2 that are preinstalled on Amazon provided images • cfn-signal: Notifies CloudFormation of a state change • cfn-init: Uses resource metadata for instance bootstrap • cfn-get-metadata: Get resource metadata • cfn-hub: A daemon to check for updates to metadata and execute custom hooks when changes are detected
- 55. cfn-init Helper Script • Tool that completes initial bootstrap based on metadata provided in CloudFormation template • Commands • Files • Users • Groups • Packages • Services • Sources • Preinstalled on Amazon provided images • State based approach to instance configuration • Can be executed multiple times to bring instance to desired state
- 56. EC2 Example Template – cfn-init
- 57. cfn-init vs userdata • userdata is procedural and will only run once • cfn-init is state based • Can be run multiple times to bring instance to desired state • Validation and logging built in