Can't generate a working customized EC2 AMI from Amazon Beanstalk sample appl -
as want install jenkins (ex-hudson) operate continuous integration processes on aws beanstalk, need custom ami because parameters in tomcat & linux have changed jenkins
i run process of installing , customizing instance started beanstalk until end , jenkins works charm on it.
but, can't reuse ami generated @ end of customization: health check done beanstalk doesn't see ec2 instance although beanstalk started , works fine.
in order understand issue, reduced failing process following:
- a) create new bt application / environment based on sample provided amazon (only parameter had keypair ssh ec2 instance)
- b) when ec2 instance started, use ec2 flash ami
- c) modify bt env config changing original aws ami (id: 100fff79 - tomcat 6 64 bits) 1 genrated in (b)
- d) bt rebuilds when change ami id
- e) rebuild restarts ec2 instance.
- f) starts fine (can ssh it) health checking fails , env turns red status.
can replicate process , tell me doing wrong ? (i use ami of (b) starting point jenkins customization.?
additional info can provide: when ssh-ing ec2 instance, grep apache, java, thin & bluepilld described @ bottom of https://forums.aws.amazon.com/thread.jspa?threadid=59027&tstart=25 shows 4 expected processes disappeared. hence, failure.
please, !
regards
didier
will answer own question: right way obtain working customized ami beanstalk not try flash running instance launched beanstalk rather start template ami beanstalk (ami-100fff79 tomcat 6 64 bits in case) ec2 console , customize there, flash , you're done.
you can "edit configuration" bt environment changing ami new 1 , works fine.
regards didier
Comments
Post a Comment