dropwizard-dev to bcc, +dropwizard-user You probably need to set an inbound security group rule to open up the port on which your Dropwizard application is serving. For instance, if you're running your server on port 8080 of an EC2 instance, you need to attach a security group to that instance that opens up port 8080 to public traffic.
Provided you have the port open, you should be able to curl the instance at the public IP or DNS name exposed by Amazon. On Thu, Jul 28, 2016 at 5:31 PM, Dan Cody <miniposad...@gmail.com> wrote: > Hi, > > How would I deploy dropwizard to AWS. I was able to get the JAR onto the > EC2 box and It runs fine but I cannot access the endpoints through the > url. I am not sure if I am deploying the jar in the correct location or if > an EC2 is the correct instance. > > Thanks > > -- > You received this message because you are subscribed to the Google Groups > "dropwizard-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to dropwizard-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Evan Meagher -- You received this message because you are subscribed to the Google Groups "dropwizard-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to dropwizard-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
