heathdutton / aws-eb-cron

Makes it easy & safe to run cron tasks on just the leading instance in an Elastic Beanstalk cluster.

aws-eb-cron's Issues

What if we have one instance only

Hi.

I found this and gave it a try.
It is working fine with 2+ instances, but does not do anything if 1 instance only.

In particular this check:
if [[ -z "$EC2_INSTANCE_ID" ]]
looks weird to me... Isn't this always false (assuming we always have 1 instance)?

Apart from that I get a couple of errors when using it with 1 instance only:
chmod: cannot access ‘/opt/elasticbeanstalk/support/envvars’: No such file or directory
grep: /opt/elasticbeanstalk/support/envvars: No such file or directory
Adding a new variable.
/bin/aws-eb-cron: line 90: /opt/elasticbeanstalk/support/envvars: No such file or directory
chmod: cannot access ‘/opt/elasticbeanstalk/support/envvars’: No such file or directory
/bin/aws-eb-cron: line 99: /tmp/AWS_EB_CRON: Permission denied

Any ideas? I'm far from a bash script expert...

Thanks!

I added the AmazonEC2ReadOnlyAccess policy but still shows 401 - Unauthorized

I have attached the above policy to my ec2 user role, still got this error.