amazon web services - Failed to start Elastic Beanstlk -
i'm trying first elastic beanstalk configuration, , failed that's did:
mkdir .ebextensions vi 01installation.config
config:
packages: apt: apache2: [] libapache2-mod-wsgi: [] git: [] apache2-threaded-dev: [] commands: 01_download_apache_mod_dumpost: command: sudo git clone https://github.com/danghvu/mod_dumpost.git 02_command: command: alias apxs2=apxs 03_change_log_level: command: sudo sed -i 's/loglevel warn/loglevel debug/' /etc/apache2/apache2.conf 04a_install_mod_dumpost: command: sudo make 04b_install_mod_dumpost: command: sudo make install
next downloaded aws-elastic-beanstalk-cli
, created alias eb:
alias eb="python2.7 ~/aws-elasticbeanstalk-cli-2.4.0/eb/linux/python2.7/eb"
than in working directory did:
git init . git add . git commit -m "initital setup"
than did:
eb init eb start
after answered question in cli, got this:
waiting environment "workerbeanstalk-env" launch. 2013-07-31 10:25:27 info createenvironment starting. 2013-07-31 10:25:33 info using elasticbeanstalk-us-east-xxxxxxxxxxx amazon s3 storage bucket environment data. 2013-07-31 10:25:52 info created load balancer named: xxxxxxxxxxxxxxxx 2013-07-31 10:26:13 info created security group named: xxxxxxxxxxx4 2013-07-31 10:26:17 info created auto scaling launch configuration named: xxxxxxxxxxxxxxx 2013-07-31 10:27:15 info created auto scaling group named: xxxxxxxxxxxxxxxxx 2013-07-31 10:27:15 info waiting ec2 instances launch. may take few minutes. 2013-07-31 10:27:19 info created auto scaling group policy named: arn:aws:autoscaling:us-east-xxxxxxxxxxxxxxx:scalingpolicy:xxxxxxxxxxxxxxxxxx:autoscalinggroupname/xxxxxxxxxxxxxx-awsebautoscalinggroup-xxxxxxxxxxxxx:policyname/xxxxxxxxxxxxk-awsebautoscalingscaledownpolicy-xxxxxxxxx 2013-07-31 10:27:19 info created auto scaling group policy named: arn:aws:autoscaling:us-east-1:xxxxxxxxxx:scalingpolicy:xxxxxxxxxxxxxxx:autoscalinggroupname/xxxxxxxxxx-stack-awsebautoscalinggroupxxxxxxxxxxxxxxxxx:policyname/awseb-xxxxxxxxxxx-stack-awsebautoscalingscaleuppolicyxxxxxxxxxxxxxxxx 2013-07-31 10:27:23 info created cloudwatch alarm named: awsebxxxxxxxxxx-awsebcloudwatchalarmlow-xxxxxxxxxxxx 2013-07-31 10:27:23 info created cloudwatch alarm named: awseb-xxxxxxxxxxk-awsebcloudwatchalarmhigh-xxxxxxxxxxxxxxxxxxx 2013-07-31 10:29:32 error responses [i-32xxxxx3] received, commands failed. 2013-07-31 10:30:39 info launched environment: workerbeanstalk-env
the last line shows launched, helath check shown in red. tried ssh instance check have been installed or downloaded, had no luck obviously, because didnt provide key-pair, (if me figure out specify key-pair great too) main question did wrong, , why doesn't launching?
re question - if me figure out specify key-pair great too
as using elastic beanstalk, easiest way via ebs console - "configuration" screen.
under settings "instances" (click gear wheel on right), there's field "ec2 key pair".
if there none listed, have create pair in ec2 menu - network & security -> key pairs
Comments
Post a Comment