Ansible can be told to run locally on the command line with the `-c' option or can be told via the
`connection: local' declaration in the playbook. The default connection method is `remote'.
Reference: http://docs.ansible.com/ansible/intro_inventory.html#non-ssh-connection-types

Elastic Beanstalk worker environments support Amazon Simple Queue Service (SQS) dead letter queues. A dead letter queue is a queue where other (source) queues can send messages that for some reason could not be successfully processed. A primary benefit of using a dead letter queue is the ability to sideline and isolate the unsuccessfully processed messages. You can then analyze any messages sent to the dead letter queue to try to determine why they were not successfully processed.
http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features-managing-env- tiers.html#worker-d eadletter

An EBS snapshot is tied to its region and can only be used to create volumes in the same region.
You can copy a snapshot from one region to another. For more information, see Copying an Amazon EBS Snapshot.
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/resources.html

Explanation
This is mentioned in the AWS documentation
Configure
This event occurs on all of the stack's instances when one of the following occurs:
* An instance enters or leaves the online state.
* You associate an Elastic IP address with an instance or disassociate one from an instance.
* You attach an Elastic Load Balancing load balancer to a layer, or detach one from a layer.
For example, suppose that your stack has instances A, B, and C, and you start a new instance, D.
After D has finished running its setup recipes, AWS OpsWorks Stacks triggers the Configure event on A, B, C, and D.
If you subsequently stop A, AWS Ops Works Stacks triggers the Configure event on B, C, and D.
AWS OpsWorks Stacks responds to the Configure event by running each layer's Configure recipes, which update the instances' configuration to reflect the current set of online instances. The Configure event is therefore a good time to regenerate configuration files. For example, the HAProxy Configure recipes reconfigure the load balancer to accommodate any changes in the set of online application server instances.
You can also manually trigger the Configure event by using the Configure stack command. For more information on Opswork lifecycle events, please refer to the below URL:
* http://docs.aws.amazon.com/opsworks/latest/userguide/workingcookbook-events.html