<?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: Is the Cloudera Live AWS Code single use? in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-the-Cloudera-Live-AWS-Code-single-use/m-p/36231#M11698</link>
    <description>&lt;P&gt;Thanks. Just tried and got the form. It would be great if someone could make the forms easily accessible. If you notice, even though all the other webpages that link to &lt;A href="http://www.cloudera.com/live" target="_blank"&gt;http://www.cloudera.com/live&lt;/A&gt; mention about filling out a form/getting access none of these words appear on the actual page - "access", "form", etc ... all it states is what Cloudera Live does without explaining how to actually use it. It is possible that there are other users like myself, who having not found the terms would find it much easier to shift to a competing Hadoop product which might be more readily available to the end-user.&lt;/P&gt;</description>
    <pubDate>Thu, 14 Jan 2016 13:17:25 GMT</pubDate>
    <dc:creator>xbsd</dc:creator>
    <dc:date>2016-01-14T13:17:25Z</dc:date>
    <item>
      <title>Is the Cloudera Live AWS Code single use?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-the-Cloudera-Live-AWS-Code-single-use/m-p/34991#M11694</link>
      <description>&lt;P&gt;For example, if the Cloudformation stack is deleted, can the same access code be used again or do we have to re-register for another?&lt;/P&gt;</description>
      <pubDate>Wed, 09 Dec 2015 18:27:51 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-the-Cloudera-Live-AWS-Code-single-use/m-p/34991#M11694</guid>
      <dc:creator>ange</dc:creator>
      <dc:date>2015-12-09T18:27:51Z</dc:date>
    </item>
    <item>
      <title>Re: Is the Cloudera Live AWS Code single use?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-the-Cloudera-Live-AWS-Code-single-use/m-p/35007#M11695</link>
      <description>You need to register for a new access code every time you deploy a cluster.&lt;BR /&gt;</description>
      <pubDate>Wed, 09 Dec 2015 23:04:52 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-the-Cloudera-Live-AWS-Code-single-use/m-p/35007#M11695</guid>
      <dc:creator>Sean</dc:creator>
      <dc:date>2015-12-09T23:04:52Z</dc:date>
    </item>
    <item>
      <title>Re: Is the Cloudera Live AWS Code single use?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-the-Cloudera-Live-AWS-Code-single-use/m-p/36176#M11696</link>
      <description>&lt;P&gt;We have been trying to test Cloudera Live, but the website and the process to request an access code is extremely elusive. There are links that all point to the Cloudera Live page where the user is expected to find a "form" to fill out - but there isn't one there. We had started a cluster, but had to terminate it and I am trying to find a way to request a new access code, which is extremely difficult if not impossible due to the way the site is designed. It is almost as if Cloudera doesn't want users to be able to test this !&lt;/P&gt;</description>
      <pubDate>Wed, 13 Jan 2016 14:32:02 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-the-Cloudera-Live-AWS-Code-single-use/m-p/36176#M11696</guid>
      <dc:creator>xbsd</dc:creator>
      <dc:date>2016-01-13T14:32:02Z</dc:date>
    </item>
    <item>
      <title>Re: Is the Cloudera Live AWS Code single use?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-the-Cloudera-Live-AWS-Code-single-use/m-p/36177#M11697</link>
      <description>The links to the form are in the form of the 3 buttons, "Cloudera&lt;BR /&gt;Enterprise", "Cloudera + Tableau", and "Cloudera + Zoomdata" at&lt;BR /&gt;&lt;A href="http://www.cloudera.com/live." target="_blank"&gt;www.cloudera.com/live.&lt;/A&gt; I agree that isn't as clear as it used to be - I'll&lt;BR /&gt;see if that can be updated soon.&lt;BR /&gt;&lt;BR /&gt;To answer your question, Cloudera Live AWS codes are single use, but you&lt;BR /&gt;can register for new access codes.&lt;BR /&gt;</description>
      <pubDate>Wed, 13 Jan 2016 14:48:58 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-the-Cloudera-Live-AWS-Code-single-use/m-p/36177#M11697</guid>
      <dc:creator>Sean</dc:creator>
      <dc:date>2016-01-13T14:48:58Z</dc:date>
    </item>
    <item>
      <title>Re: Is the Cloudera Live AWS Code single use?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-the-Cloudera-Live-AWS-Code-single-use/m-p/36231#M11698</link>
      <description>&lt;P&gt;Thanks. Just tried and got the form. It would be great if someone could make the forms easily accessible. If you notice, even though all the other webpages that link to &lt;A href="http://www.cloudera.com/live" target="_blank"&gt;http://www.cloudera.com/live&lt;/A&gt; mention about filling out a form/getting access none of these words appear on the actual page - "access", "form", etc ... all it states is what Cloudera Live does without explaining how to actually use it. It is possible that there are other users like myself, who having not found the terms would find it much easier to shift to a competing Hadoop product which might be more readily available to the end-user.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Jan 2016 13:17:25 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-the-Cloudera-Live-AWS-Code-single-use/m-p/36231#M11698</guid>
      <dc:creator>xbsd</dc:creator>
      <dc:date>2016-01-14T13:17:25Z</dc:date>
    </item>
  </channel>
</rss>

