Here are some good practices for defining a Procfile for your application:
Put it in the root directory of your application source.
Use a Procfile for long-running application processes that shouldn't exit. Elastic Beanstalk monitors these processes and restarts any process that terminates.
All paths in the Procfile are relative to the root of the source bundle.
web: java -jar server.jar -Xms256m cache: java -jar mycache.jar web_foo: java -jar other.jar
In your case, you mention
but it does come back as if it has failed, to better understand the issue, I would recommend you to check the logs on the instances. Elastic Beanstalk names the log files after the process and stores them in /var/log. For example, the web process in the preceding example generates logs named
web-1.error.log for stdout and stderr, respectively.
Feel free to open a support case to AWS Premium Support if you want us to take a closer look into your logs file.
Disable Xray feature on local dev machine(Java Spring boot AOP project)asked 2 years ago
Are there any workshops on modernizing Java Spring Boot applications?Accepted Answerasked 2 years ago
Spring Boot app cannot run DDL commands on AWS Postgres 12.5 instanceasked 2 years ago
Loaded a Spring Boot Application to AWS Elastic Beanstalk, my Twilio Account was hackedasked a year ago
Spring Boot deployed on Elastic Beanstalk. Need to modify Ngnix to allow large filesasked 6 months ago
Unable to access Spring Boot application deployed on AWS EC2 instance (Windows Server 2022)asked 6 months ago
Procfile best practices for Spring Boot application?asked 10 months ago
Issue with authentication from Java Spring to AWS SES serviceasked 8 months ago
AWS MSK IAM - Authentication Failure Access Denied Spring Bootasked a month ago
2/2 checks passed but Spring Boot app with SQL database deployed on EC2 Ubuntu fails to load and connection times outasked 2 months ago