[Bioc-devel] bioconductor AMI & shiny app

Robert Castelo robert.castelo at upf.edu
Thu May 22 16:47:53 CEST 2014

hi Dan,

On 05/21/2014 10:29 PM, Dan Tenenbaum wrote:
> Hi Robert,
> I started an instance of the BioC 2.14 AMI (is that the one you are
> working with?) and updated to the latest shiny server (apologies for
> the old one being on there).

yes, that was it.

> Looks like by default it listens on port 3838 (see
> /etc/shiny-server/shiny-server.conf) so I added that to my security
> group and went to http://ec2XXXXX.compute-1.amazonaws.com:3838 and it
> worked.

yes, it also worked for me at port 3838.

> So I will update that AMI to use that version of shiny server by
> default.
> I got this to work if I specified host as the "private IP" as
> displayed in the aws console (an IP address that for me anyway starts
> with 10.182).
> I got a message saying the popup was blocked, but I think that's ok,
> because it was trying to go to the wrong URL anyway (that internal IP
> which is not accessible from outside ec2). But in another window I
> went to
> http://ec2-XXXXX.compute-1.amazonaws.com:6219
> and the shiny app worked.

thanks for trying it out, the description of what you did gave me a 
hint, i was not trying to combine an address to launch the shiny app 
with a different address in the browser to connect. now, i could make it 
work by doing exactly how you say, using the private IP in the 'host' 
argument of 'runApp()' and replacing that IP in the browser by the 
public DNS name.

this procedure, however, looks a bit cumbersome to me, specially if a 
non-expert user is supposed to use the shiny app. do you know whether it 
is possible that the browser window opens automatically with the public 
DNS name?


More information about the Bioc-devel mailing list