@amarjeet, FWIW, I find it easiest to deploy Pedestal services to ElasticBeanstalk in a Docker container.

@ddeaguiar I think I can try that

thanks

The lein pedestal-service template creates a Dockerfile which should be suitable for most cases. Keep in mind that EB uses nginx to proxy all requests to your container so you may need to create an nginx config file if you need control over that.

okay, just started with this. lets see if I can make it work

It should be straight forward. You’ll just need to create a Dockerrun.aws.json file. I recommend using the eb cli for pushing change to you environment.

tried building docker image, its not been able to build. Error: `Get https://registry-1.docker.io/v2/: dial tcp: lookup http://registry-1.docker.io on 192.168.65.1:53: read udp 192.168.65.2:45426->192.168.65.1:53: i/o timeout Docker image could not be built.`

m updating docker - lets see

@ddeaguiar any clear way to create a jar build? I am getting this error - javax/servlet/http/HttpServletRequest

i tried lein uberjar

Creating an uberjar should just work. You need to undo the changes you made to create a war file

I will try by creating a fresh pedestal service app

Are both the situations incorrect, in terms of config?

Uberjar issue resolved

Hey @ddeaguiar I am able to run the docker image locally, but the beanstalk is not recognizing Dockerfile when I am deploying standalone.jar

I am doing it via the beanstalk consol

@amarjeet did you create a Dockerrun.aws.json file?

no, i thought Dockerfile would work

nope, you need one more piece

https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_docker_image.html

You can provide Elastic Beanstalk with only the Dockerrun.aws.json file, or with a .zip archive containing both the Dockerrun.aws.json and Dockerfile files. When you provide both files, the Dockerfile describes the Docker image and the Dockerrun.aws.json file provides additional information for deployment as described later in this section.

so there are a couple ways to do this, you can deploy your docker image to an ecs registry repo or build the image at deployment time

I do the later when working with EB

so, it seems like the configs in this file are created when I was creating the beanstalk environment, so any specific part of the config should I mention (thats is mandatory) in the .json file

The config you need in that file is minimal

it will amount to environment variable mappings (if any), port mappings, memory settings and log mount points

hmm, okay

will just try

my recommendation is to just first deploy a vanilla pedestal-service

once you have that working, then deploy your app which can have external dependencies

make sense

you can then tailor your eb config to create the roles required to access aws services, etc

hmm, yeah

gonna try this