On peut "remettre" ou plutot rendre disponible de nouveau un message SQS en changeant sa visibility timeout à 0

Truc con : on ne peut pas utiliser le résultat du get-repository-policy dans le set-repository-policy pour cloner.

Il faut au passage enlever les \n qui trainent dans la réponse

 $ cat monitor_beanstalk.py
#!/bin/python

import boto3
import pprint
pp = pprint.PrettyPrinter(indent=4)


#List all env and status and instances health

client = boto3.client('elasticbeanstalk')


envs = client.describe_environments()['Environments']

#pp.pprint(envs)


for env in envs:
    print 'ApplicationName: {} EnvironmentName: {} Health: {} HealthStatus: {} Status: {}'.format(env['ApplicationName'].ljust(30),env['EnvironmentName'].ljust(30),env['Health'].ljust(10),env.get('HealthStatus', 'N/A').ljust(10),env['Status'].ljust(10))
    if (env['Health'] != 'Green') or (env.get('HealthStatus', 'N/A') != 'Ok' and env.get('HealthStatus', 'N/A') != 'N/A'):
        print '\nProblem'
        details = client.describe_environment_health(EnvironmentName=env['EnvironmentName'],AttributeNames=['All'])
        #pp.pprint(details)
        print details['Causes']
        print details['InstancesHealth']
        print '\n'

why EFS sucks

If you enable s3 enpoint in your route table, it's kind of tricky to know if the endpoint is really working. Two things to validate:
1) traceroute tcp before and after (traceroute -T s3-us-west-1.amazonaws.com 443)
You will see more hope when endpoint not activated
2) try an s3 sync cross region with enpoint activated : it should failed since it's not supported (yet @ 2017-05-02)

Good boy atlassian!