elastic-beanstalk

I am trying to deploy a spring boot app into one EB worker tier but seems that EB it is not ready to manage this kind of project. Have I to mandatory generate a .war from my spring boot app? Thanks! I have found the problem. EB expects a .war file and Spring Boot app usually is launche by a embedded Tomcat or Jetty. I have found the solution in this guide: http://spring.io/guides/gs/convert-jar-to-war/ Summing up: Add tomcat dependency with provided scope in pom.xml <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-tomcat</artifactId> <scope>provided<

When trying to deploy my application, I recently got the following error: ERROR: Service:AmazonCloudFormation, Message:Stack named 'awseb-e-123-stack' aborted operation. Current state: 'UPDATE_ROLLBACK_IN_PROGRESS' Reason: The following resource(s) failed to update: [AWSEBRDSDatabase]. ERROR: Updating RDS database named: abcdefg12345 failed Reason: DB Security Groups can no longer be associated with this DB Instance. Use VPC Security Groups instead. ERROR: Failed to deploy application. How do you switch over a DB Security Group to a VPC Security Group? Steps for using the Elastic Beanstalk

I am trying to upload my rails project on AWS Beanstalk. I've already run eb init, eb start and configured the database settings to point to RDS. After I pushed using git aws.push and waited for AWS server to be started, the link provided says: "502 Bad Gateway nginx" In the logs ------------------------------------- /var/app/support/logs/passenger.log ------------------------------------- App 6861 stderr: [ 2014-05-29 13:26:59.1308 6893/0x00000001e50050(Worker 1) utils.rb:68 ]: *** Exception RuntimeError in Rack application object (Missing `secret_key_base` for 'production' environment, set

I am working on a wider web application using AWS infrastructure. It has two 'worker' components which read work from SQS and write the results to an RDS database. One of these is Python and I already have this working on a single Elastic Beanstalk instance. The second uses .NET and I am currently working out how to deploy it. For production, both will be elastic with multiple instances. As these processing components are not web applications (i.e. they do not respond to http requests), I have to explicitly start them off. For the Python example, I use the .ebextensions file: container

I am new to Elastic Beanstalk, trying to serve a Node.js Express app and utilize serving our static files separately with Nginx. None of the tutorials I've come across are explicit in how to define the virtual path. I'm attempting to do this through the AWS console in the browser. I am trying to add a virtual path/directory setup for the static files. In the console I'm at Elastic Beanstalk > myapp > configuration > Static Files But no matter what I add here I get this error message: I've also tried adding the full directory path ( /var/app/current/dist/public/images/ ). Is there another

I am in the process of migrating a website for a client to AWS. I have everything configured and working except that the client would like to be able to accept payments on there website. I followed several guides on how to get SSL working using elastic beanstalk. Currently I have it set up to use a source bundle and I created a config file in the .ebextensions file that looks like this: Resources: sslSecurityGroupIngress: Type: AWS::EC2::SecurityGroupIngress Properties: GroupName: {Ref : AWSEBSecurityGroup} IpProtocol: tcp ToPort: 443 FromPort: 443 CidrIp: 0.0.0.0/0 packages: yum: mod24_ssl :

I am having a problem deploying an EB instance with a custom .ebextensions file. This is the relevant part in that file: container_commands: 01_migrate: command: 'python db_migrate.py' 02_npm_build: command: 'npm install && npm run prod' As you can see, these commands are for migrating my PostgreSQL database (via a Flask backend) and building my React .jsx files. If I leave these commands out, the deployment completes perfectly well. However, once I put them in, looking at the eb-activity.log it stalls at this part forever (as far as I can tell): [2017-04-10T02:39:24.106Z] INFO [3023] -

I have a few Rails applications and I use Git as the version control system. I use either GitHub or Beanstalk as the repository hosts. What I am trying to is quite simple in theory. Somehow show the latest commit ID number (hash?) in the footer of the web application. So that when I am looking at the web application I can check that it's committed and deployed correctly. I can imagine there are two methods to tackle this. The first would be a possible feature of Git that allows the output of the commit ID. The second would be a post-commit web hook (both Beanstalk and GitHub allow this). Has

I have a website that runs HTTPS correctly in my local environment. When I upload it to AWS it just times out or redirects forever. My setup in AWS is an Elastic Beanstalk application, an RDS database running MS SQL, I added a Load Balancer to forward the HTTPS requests, and I have a SSL certificate properly assigned to the Load Balancer. From all I can tell my app is running, in fact, Entity Framework fired off and correctly built my database in my RDS instance. I just can't reach the website through the internet. I've tried setting the Listeners different ways. If I set them like this, it

I've provisioned a default clean node.js app via Elastic Beanstalk, and have a node.js script trying to run npm install inside the project directory ( /var/app/current/deploy-dist ), however, the following permission error is thrown: npm WARN locking Error: EACCES: permission denied, open '/tmp/.npm/_locks/staging-f212e8d64a01707f.lock' npm WARN locking at Error (native) npm WARN locking /tmp/.npm/_locks/staging-f212e8d64a01707f.lock failed { Error: EACCES: permission denied, open '/tmp/.npm/_locks/staging-f212e8d64a01707f.lock' npm WARN locking at Error (native) npm WARN locking errno: -13,