[chef] AWS Cookbook + Snapshot Tracking

[Hector Castro < >]

I'm currently in the middle of assembling a process that takes a Chef 
bootstrapped AMI and yields a fully functional (data as well) server.  My 
goal is to have EBS snapshot IDs of primary EBS volumes available to the 
bootstrapped node in some way (data bags, node attributes) so that the data 
that becomes available is not stale.

The AWS cookbook has a nice LWRP for EBS that handles snapshots — but doesn't 
give you a way to save its ID for later use (unlike the create action that 
saves volume IDs to node attributes).

Would there be any value in adding an array of snapshot IDs to the 
corresponding volume ID node attribute on snapshot creation?  I mentioned it 
in #chef today and received some initial concern over having to maintain an 
accurate representation of available snapshots in the node attributes — a 
valid concern.  Any other feedback or suggestions to alternate approaches are 
welcome. 

Thanks,

--
Hector