phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick Dimiduk <>
Subject Re: EMR Bootstrap failing
Date Fri, 06 Mar 2015 22:34:18 GMT
Hi Ryan,

The Apache Phoenix community doesn't manage the EMR bootstrap actions,
those are handled by EMR themselves. Unless one of the EMR folks is lurking
here, you'll probably have better luck by raising the issue on the AWS EMR

We do however manage our own getting started docs, and those for AWS
integration on Our docs are on github, would you be
willing to submit a pull request based on your more recent experiences?

Thanks a lot!

On Fri, Mar 6, 2015 at 10:47 AM, Ryan Desmond <>

> Hello Phoenix users,
> I noticed that the CLI command for EMR is outdated and, at least for me,
> not working. The bootstrap action fails. I'm referencing this page,
> I'm also unable to view the file using the following command,
> "aws s3 cp
> s3://beta.elasticmapreduce/bootstrap-actions/phoenix/
> ."
> I recieve:
> "A client error (403) occurred when calling the HeadObject operation:
> Forbidden"
> Also, regarding the EMR CLI command, you may want to consider using the
> updated CLI syntax and ensuring the file is accessible and up to date. ie,
> aws emr create-cluster --name "Phoenix Test Cluster" --ami-version 3.3
> --applications Name=HBase --use-default-roles --ec2-attributes
> KeyName=[KEY] --instance-type c1.xlarge --instance-count 3
> --bootstrap-action Path="s3://beta.elasticmapreduce/bootstrap-
> actions/phoenix/",Name="Phoenix Bootstrap"
> Best Regards,
> Ryan
> --
> Ryan Desmond
> Solutions Architect
> Concurrent Inc.

View raw message