Trigger a stack update after a cloudwatch alarm action

Registered by Angus Salkeld on 2013-02-07

To make templates more powerful (like what the loadbalancer resource does internally) we need to automatically
trigger a stackupdate after a cloudwatch alarm action (one that causes changes to the stack).

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Angus Salkeld
Direction:
Needs approval
Assignee:
Angus Salkeld
Definition:
New
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Angus Salkeld on 2013-04-03
Completed by
Angus Salkeld on 2013-04-03

Related branches

Whiteboard

----
Clint Byrum (SpamapS):
In particular what is powerful about the loadbalancer is that it gets informed of the list of instances that have stated their dependence on it whenever said list changes. This would be generically useful beyond the load balancer case:

* Databases could restrict access to only those instances which depend on them, narrowing attack vectors.
* Monitoring systems can refresh their configuration to reflect the actual state of the cluster.
----

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.