lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Gershman <montan...@gmail.com>
Subject Re: Solr Scale Toolkit Access Denied Error
Date Mon, 09 Jun 2014 14:10:56 GMT
Thanks, Tim.  Worked like a charm. Appreciate your timely assistance.


On Sat, Jun 7, 2014 at 9:13 PM, Timothy Potter <thelabdude@gmail.com> wrote:

> Hi Mark,
>
> Sorry for the trouble! I've now made the ami-1e6b9d76 AMI public;
> total oversight on my part :-(. Please try again. Thanks Hoss for
> trying to help out on this one.
>
> Cheers,
> Tim
>
> On Fri, Jun 6, 2014 at 6:46 PM, Mark Gershman <montana88@gmail.com> wrote:
> > Thanks, Hoss.
> >
> > I did substitute the previous AMI ID from the mid-May release of the
> > toolkit and the build process does proceed further; however, it appears
> the
> > the AMI changed enough that it is not compatible with the new toolkit
> > release.  In doing a little more research, I'm inclined to believe that
> the
> > permissions on the AMI may be the source of the problem and will post to
> > the issue tracker per your suggestion.
> >
> >
> > Mark Gershman
> >
> >
> > On Fri, Jun 6, 2014 at 7:41 PM, Chris Hostetter <
> hossman_lucene@fucit.org>
> > wrote:
> >
> >>
> >> : My guess is that the customized toolkit AMI (ami-1e6b9d76) at AWS is
> not
> >> : accessible by my AWS credentials.  Is this an AMI permissioning issue
> or
> >> is
> >> : it a problem with my particular account or how it is configured at
> AWS.
> >>  I
> >> : did not experience this specific problem when working with the
> previous
> >> : iteration of the Solr Scale Toolkit back toward the latter part of
> May.
> >>  It
> >> : appears that the AMI was updated from ami-96779efe to ami-1e6b9d76
> with
> >> the
> >> : newest version of the toolkit.
> >>
> >> I'm not much of an AWS expert, but i seem to recall that if you don't
> >> have your AWS security group setup properly this type of error can
> >> happen? is it possible that when you were trying out solr-scale-tk
> before
> >> you had this setup, but now you don't?
> >>
> >> https://github.com/LucidWorks/solr-scale-tk
> >>
> >> > You'll need to setup a security group named solr-scale-tk (or update
> the
> >> > fabfile.py to change the name).
> >> >
> >> > At a minimum you should allow TCP traffic to ports: 8983, 8984-8989,
> >> > SSH, and 2181 (ZooKeeper). However, it is your responsibility to
> review
> >> > the security configuration of your cluster and lock it down
> >> appropriately.
> >> >
> >> > You'll also need to create an keypair (using the Amazon console) named
> >> > solr-scale-tk (you can rename the key used by the framework, see:
> >> > AWS_KEY_NAME). After downloading the keypair file (solr-scale-tk.pem),
> >> > save it to ~/.ssh/ and change permissions: chmod 600
> >> > ~/.ssh/solr-scale-tk.pem
> >>
> >> ...if I'm wrong, and there really is a problem with the security on the
> >> AMI, the best place to report that would be in the project's issue
> >> tracker...
> >>
> >> https://github.com/LucidWorks/solr-scale-tk/issues
> >>
> >>
> >>
> >> -Hoss
> >> http://www.lucidworks.com/
> >>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message