AWS Autoscale Termination Policy vs Update Policy

Termination policy comes into picture when there is "Scale UP" OR "Scale Down". Ref:http://docs.aws.amazon.com/autoscaling/latest/userguide/as-instance-termination.html#custom-termination-policy Update Policy is when - Launch configuration is updated. For e.g. update AMI through autoscale group rolling. Ref: https://aws.amazon.com/premiumsupport/knowledge-center/auto-scaling-group-rolling-updates/ Short Description The AWS::AutoScaling::AutoScalingGroup resource supports an UpdatePolicy attribute. This is used to define how an Auto Scaling group resource is updated when an update to …

AWS – AutoScale – Update AMI through CF Template

Template - https://github.com/sangitaccount/AWS/blob/master/cfn-templates/AWS_AutoScale_ELB_Notification.template used to create single EC2 Instance with AutoScaling behind ELB. EC2 Instance provisioned ( take a note of AMI ). Using the same Cloud Formation Template I've update the stack with new AMI I did take screenshots of instance changes ( it is keeping the old instance alive till the new instance …

AWS cfn-signal not working in private subnets

I am writing Cloud Formation template for web service instances with auto scaling and elastic load balancer. My plan is to place the ELB in public subnet and instances in private subnets behind the load balancer. My private subnets are fully restricted without any NAT Gateway. SSH Access is also enabled through ELB. In Cloud Formation …

Puppet – Hiera Error

As mentioned here: https://ask.puppet.com/question/22498/error-400-on-server-could-not-find-data-item-nfsexports-in-any-hiera-data-file-and-no-default-supplied-at/ I was getting 400 error as puppet not able to find hiera value.. YAML files strictly follows indentation - I've copied and pasted values from different values which has placed 'TAB' instead of spaces. Find the tab and replace with spaces. #grep -P '/t' -r * <all hiera yaml files> On …

Docker – Knowledge Article

Use SMALLer base image - debian:jessie. Do not upgrade inside container. Docker works based on layers - every instruction commits a new layer. Docker also maintains cache so it can reuse the layers - Considering this keep all your base instructions as common as possible. Sometimes it can go other way that even when you …