ruprict (7) [Avatar] Offline
There are a few issues (so far) with the file when running on MacOS.

grep -P
doesn't work...
seems to get the job done.
sed -i
doesn't seem to mean the same thing. I just removed the -i
3. The
aws elasticbeanstalk create-environment
command fails b/c it wants an instance profile. I have a default IAM service-role and instance role for elasticbeanstalk, but this doesn't seem to matter.

Obvs, it's definitely possible that I am being an idiot. I am stuck on #3, meaning, I've run out of time (right now) to try and get this going.

BTW, any reason you didn't just use CloudFormation for this? Seems like it would be easier and less platform senstive.

Julien Vehent (14) [Avatar] Offline
Thanks for the report. Any chance you could submit a patch to the hosted version of the script at ?

I choose not to use cloudformation because it's a complicated language and explaining it would have taken its own chapter. That said, I imagine most people who run ops in aws at large scale use cloudformation or one of its wrapper.
306760 (1) [Avatar] Offline
I faced the same problem with creating the environment. Adding the following option to the ebs-options.json file seems to resolve this issue.

"Namespace": "aws:autoscaling:launchconfiguration",
"OptionName": "IamInstanceProfile",
"Value": "aws-elasticbeanstalk-ec2-role"