Thanks, Tim. Worked like a charm. Appreciate your timely assistance.
On Sat, Jun 7, 2014 at 9:13 PM, Timothy Potter 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 o
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 wrote:
> Thanks, Hoss.
>
> I did substitute the previous AMI ID
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 th
: 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 pre
I've been attempting to experiment with the recently updated Solr Scale
Tool Kit mentioned here:
http://searchhub.org/2014/06/03/introducing-the-solr-scale-toolkit/
After making the very well documented configuration changes at AWS and
installing Python, I was able to use the toolkit to connect
