elastic-beanstalk

Where does elastic beanstalk t2 server store my node.js app files?

让人想犯罪 __ 提交于 2019-12-02 14:21:39
From an architecture perspective I'm trying to get a better understand of how and where files deployed to eb (t2) server are stored. I see some .zip files in s3 that show when I upload something via the eb interface, though how/where exactly does this get end up on my ec2(t2) server? It's in the /tmp/deployment/application folder during deployment and the moved to /var/app/current afterward. In case you search them, the node logs are in /var/log/nodejs/nodejs.log and the application will bind to 8081 no matter what PORT environment variable you set in the Environment Variables in the console.

Amazon Elastic Beanstalk node and npm non-standard install locations

|▌冷眼眸甩不掉的悲伤 提交于 2019-12-02 14:14:44
Amazon Beanstalk installs node and npm into really obscure places - and I'm not sure they won't change if EB decides to use a newer version of node, which would cause my application to break. These are the locations for node and npm: /opt/elasticbeanstalk/node-install/node-v0.8.24-linux-x64/bin/node /opt/elasticbeanstalk/node-install/node-v0.8.24-linux-x64/bin/npm I'm worried about the 0.8.24 part changing and I'd rather not grep for things in cron or monit scripts when trying to find something that is normally just /usr/bin/XXX . how do I get a consistent filepath for these executables? and

Does traffic skip my AWS ELB if I don't specify its security group in my EB environment's inbound rules?

时间秒杀一切 提交于 2019-12-02 13:35:52
I have an AWS Elastic Beanstalk environment that is created with an Elastic Load Balancer, and which specifies the default ELB security group ("ELB created security group used when no security group is specified during ELB creation") as the source for inbound HTTP. If I replace this default ELB security group as the source for my environment's security group's inbound rules with a port range does traffic still come through the ELB and is it still filtered by the ELB's security group's rules or does traffic then "skip" the ELB (or at least it's security group) and come directly to my instances?

Celery + Django on Elastic Beanstalk causing error: <class 'xmlrpclib.Fault'>, <Fault 6: 'SHUTDOWN_STATE'>

只愿长相守 提交于 2019-12-02 11:36:31
I've a Django 2 application deployed on AWS Elastic Beanstalk. I configured Celery in order to exec async tasks on the same machine. Since I added Celery, every time I redeploy my application eb deploy myapp-env I get the following error: ERROR: [Instance: i-0bfa590abfb9c4878] Command failed on instance. Return code: 2 Output: (TRUNCATED)... ERROR: already shutting down error: <class 'xmlrpclib.Fault'>, <Fault 6: 'SHUTDOWN_STATE'>: file: /usr/lib64/python2.7/xmlrpclib.py line: 800 error: <class 'xmlrpclib.Fault'>, <Fault 6: 'SHUTDOWN_STATE'>: file: /usr/lib64/python2.7/xmlrpclib.py line: 800.

Socket Io in AWS ElasticBeanStalk Node

允我心安 提交于 2019-12-02 10:55:08
I have a node js application in Elastic Bean stalk.We are considering using socket io for a feature . I read in some places that socket io support has to be manually enabled in AWS elasticbeanstalk. Specifically when it uses the default NGINX proxy. I read By default an elastic beanstalk instance has an nginx proxy in front of it that is not configured to allow webSockets. Is this correct information? If so , how to enable socket io support in AWS EB? This is correct information. You'll need to do some additional configuration for your Elastic Beanstalk deployment to get WebSockets(Socket.io

Getting 502 proxy error after deploying app to AWS

两盒软妹~` 提交于 2019-12-02 10:27:18
I deployed an Application to AWS elastic beanstalk. When I try to open the application, I am getting 502 proxy error Saying following message. Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /. Reason: Error reading from remote server Apache/2.2.31 (Amazon) Server at mehe.us-west-2.elasticbeanstalk.com Port 80 Strange part is when I run the application from localhost(Still connected to amazon database) the application is working fine, but after deloying it is not working. Here's the link to application Any

AWS Worker tier cron - server error #500 - “post http 1.1 500 AWS aws-sqsd/2.0”

社会主义新天地 提交于 2019-12-02 09:22:07
I'm trying to set up a cronjob at Elastic Beanstalk. The task is being scheduled. For testing purposes it should run every minute... However it is not working. It is a Django app. The app is running in two Environments, one is the worker and the other one is "hosting" the application. This part is working. The command is running but it's not being executed (the files are not being deleted). Here is views.py : @login_required def delete_expired_files(request): users = DemoUser.objects.all() for user in users: documents = Document.objects.filter(owner=user.id) if documents: for doc in documents:

AWS's Elastic Beanstalk not using my virtualenv: “No module named boto”

为君一笑 提交于 2019-12-02 06:35:02
I'm trying to use AWS's Elastic Beanstalk, but when I run eb start , I get "ImportError: No module named boto Cannot run aws.push for local repository HEAD." I am in the virtual environment of my Django project. I ran pip install boto and it was successful. I did pip freeze > requirements.txt , git add requirements.txt , and git commit -m 'Added boto to requirements.txt' , all successful. Then I got into the python shell and imported boto without any resulting errors. Finally, I ran eb start on the normal command line again. Same "no module named boto" error. It seems like the eb start command

Getting peewee to work on elastic beanstalk

点点圈 提交于 2019-12-02 04:24:32
I'm trying to install the peewee package on an elastic beanstalk instance to control a bottle application. I think the problem is with the MySQL-python dependency, but peewee doesn't load either. My requirements file looks like this: bottle==0.11.6 peewee==2.1.1 MySQL-python I also tried MySQL-python as MySQL-python==1.2.4b4 . For a number of reasons which I believe are summed up here , this doesn't work; peewee isn't installed and I get this error message in the log: 2013-05-18 06:57:08,407 [INFO] (15947 MainThread) [directoryHooksExecutor.py-29] [root directoryHooksExecutor info] Script

Elastic Beanstalk SQSD Error on worker start

孤者浪人 提交于 2019-12-02 03:22:41
I've deployed a nodejs worker. However whenever I try to start it, it gets red and this error is showned: ERROR Instance: i-6eef007a Module: AWSEBAutoScalingGroup ConfigSet: null Command failed on instance. Return code: 1 Output: Error occurred during build: Command 01-start-sqsd failed . I don't know if it's related, sometimes I get this error on the screen: IamInstanceProfile: The environment does not have an IAM instance profile associated with it. To improve deployment speed please associate an IAM instance profile with the environment. I've already given permission to SQS and set key and