<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Cloudbreak - AWS generate role fails in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-AWS-generate-role-fails/m-p/117831#M17058</link>
    <description>&lt;P&gt;I got it.  This is related to IAM permission issue.  The IAM user I was using did not have any permissions attached it to.  I am sure I can plug away and find correct permission.  However, I just grabbed my root credentails and used in cloudbreak. works.&lt;/P&gt;</description>
    <pubDate>Sat, 30 Jan 2016 04:53:58 GMT</pubDate>
    <dc:creator>sunile_manjee</dc:creator>
    <dc:date>2016-01-30T04:53:58Z</dc:date>
    <item>
      <title>Cloudbreak - AWS generate role fails</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-AWS-generate-role-fails/m-p/117830#M17057</link>
      <description>&lt;P&gt;I am running sudo cbd aws generate-role and it fails with &lt;/P&gt;&lt;P&gt;A client error (SignatureDoesNotMatch) occurred when calling the CreateRole operation: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.&lt;/P&gt;&lt;P&gt;I have verifed my key and private key in Profile is correct.  I also installed AWS CLI to test my key and it connects.  I am not able to create the roles via cbd aws generate-role.  Any help would be greate&lt;/P&gt;</description>
      <pubDate>Sat, 30 Jan 2016 03:54:16 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-AWS-generate-role-fails/m-p/117830#M17057</guid>
      <dc:creator>sunile_manjee</dc:creator>
      <dc:date>2016-01-30T03:54:16Z</dc:date>
    </item>
    <item>
      <title>Re: Cloudbreak - AWS generate role fails</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-AWS-generate-role-fails/m-p/117831#M17058</link>
      <description>&lt;P&gt;I got it.  This is related to IAM permission issue.  The IAM user I was using did not have any permissions attached it to.  I am sure I can plug away and find correct permission.  However, I just grabbed my root credentails and used in cloudbreak. works.&lt;/P&gt;</description>
      <pubDate>Sat, 30 Jan 2016 04:53:58 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-AWS-generate-role-fails/m-p/117831#M17058</guid>
      <dc:creator>sunile_manjee</dc:creator>
      <dc:date>2016-01-30T04:53:58Z</dc:date>
    </item>
    <item>
      <title>Re: Cloudbreak - AWS generate role fails</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-AWS-generate-role-fails/m-p/117832#M17059</link>
      <description>&lt;P&gt;Hi,
If you have any other please let us know.
Actually the aws role json can find here: &lt;A href="https://github.com/sequenceiq/cloudbreak-deployer/blob/master/include/aws-roles.bash#L162" target="_blank"&gt;https://github.com/sequenceiq/cloudbreak-deployer/blob/master/include/aws-roles.bash#L162&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 31 Jan 2016 02:10:22 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-AWS-generate-role-fails/m-p/117832#M17059</guid>
      <dc:creator>rdoktorics</dc:creator>
      <dc:date>2016-01-31T02:10:22Z</dc:date>
    </item>
  </channel>
</rss>

