beanstalk | PHP beanstalk connection and connection pool library | Command Line Interface library

I think the issue was with the orbs as after I update to the node: circleci/node@4.7.0, I had no issue with NodeJS installation and build the project.

This makes sense as the cI/CD pipeline not suppose to run the software and hence, the NodeJS version should be irrelevent.

Okay, so I decided to just launch a new environment using the same exact configuration and code and it worked. Looks like Elastic Beanstalk environments can break and once that happens, there is no fixing it apparently.

AWS Linux 2 has changed a lot of how elastic beanstalk works and how it is configured. Regardless of whether you are doing an in-place upgrade or spinning up a new environment, here is a list of things that will be different to run through before making the upgrade. Most of the items here are things that are different in Elastic Beanstalk config that live in .ebextensions.

1. There are differences in sub-package dependencies between Python 3.6 and 3.8. You should test your requirements file on Python 3.8 and make sure it's compatible, especially if you use a generated requirements.txt.

2. AWS Linux 2 no longer allows you to write Apache config using a file directive in .ebextensions. These modifications now need to live in .platform/httpd/conf.

3. The virtual environment is no longer active while running container_commands. Any container commands that use your code need to have source $PYTHONPATH/activate run first.

4. Generated files now get wiped on config changes, so commands like django's collectstatic need to get moved to hooks.

5. Postgres client is no longer available normally though yum. To install it, you need to do:

Keep it easy.
Certs inside your application are complex - they are hard to manage and you will get problems to run your application in a modern cloud environment (start new environments, renew certs, scale your application, ...).

Simple conclusion: Dont implement any certs.

As Mike already pointed out in the comments: WebSockets are just upgraded HTTP(S) connections. A normal webserver (nginx, apache) takes care about the certs. It can be done in kubernetes (as ingress-controller) or with a "bare-metal" webserver.
Both of them should act as a reverse-proxy. This means: Your java-application doesn't know anything about certs. It has just unencrypted connections - like in your code on port 6868.
But the client will not use this port. 6868 is only internally reachable.

The client will call your reverse-proxy at the normal HTTPS port (=443). The reverse-proxy will forward the connection to your java-application.

Here some links for further information:

• nginx reverse-proxy
• nginx reverse-proxy for websocket
• tutorial for java behind reverse-proxy
• LetsEncrypt for automatic and free certs

According to the docs, Platform hooks need to be executable. Of note, this means they need to be executable according to git, because that's what Elastic Beanstalk uses to deploy.

You can check if they are executable via git ls-files -s .platform; you should see 100755 before any shell files in the output of this command. If you see 100644 before any of your shell files, run git add --chmod=+x -- .platform/*/*/*.sh to make them executable.

I see you are trying to run main js file which is generated after build in case of ssr. To run that you need a script or Procfile as per aws documentation. To do this I added Procfile to my s3 bucket and then run the build command

buildspec file

The solution is to use a Configuration deployment platform hook for any commands that change the files in the deployment directory. Note that this is different from an Application deployment platform hook.

Using the example of the collectstatic command, the best thing to do is to move it from a container command to a pair of hooks, one for standard deployments and one for configuration changes.

To do this, remove the collectstatic container command. Then, make two identical files:

• .platform/confighooks/predeploy/predeploy.sh
• .platform/hooks/predeploy/predeploy.sh

Each file should have the following code:

Depends. If this is something that you have to do often, then maybe you could consider setting up the proper CodePipeline with Elastic Beanstaslk target.

As per docs, you need to attach the below policies for the AWS user to be able to deploy your project when using the GitHub action you have specified:

1. AWSElasticBeanstalkWebTier
2. AWSElasticBeanstalkManagedUpdatesCustomerRolePolicy

Adding the above will fix the problem, while also ensuring that you have no future issues when using this GitHub action.