• Sales: 1-800-961-2888
  • Support: 1-800-961-4454

Rackspace Cloud Essentials 1 - Generating Your API Key


NOTE: This article is written for our first generation Cloud Control Panel.  A version of this article is also available for our Next-Generation Cloud Control Panel.

After reading the previous article on the Control Panel Overview, you should be able to successfully log in to the Rackspace Cloud Control Panel and navigate to your available services.  Our Control Panel is a useful GUI tool for accessing all of our services, but there may be times when you want to manage your assets through a scripting interface like the API, or Application Programming Interface.  

Before you can start using our APIs, you will need to generate your API Key.  Your API Key is a unique alphanumeric identifier associated with your account and is used for universal authentication commands for all of your services.  

Note: One thing we'd like to mention before we get started, when you regenerate your API key, any 3rd party applications such as iDevices or Android applications will be disconnected until you set the new API key in your application.  If you're using your API as a part of a server code with site or application, this too will also break and could potentially affect your day to day operations.  We recommend updating your API key for any application you had connected with the previous API. 

  • To generate your API Key for the first time, you will need to look under the Left Navigation menu > Hosting > Cloud Files.  You may ask, why is your API Key located under Cloud Files?  This is because, until recently, the API functionality was primarily used together with Cloud Files so it was convenient to have the interface for generating the API Key live under the Cloud Files section.  Now you can use your API key to activate the Mobile applications, create new Cloud Servers and Cloud Load Balancers, or to configure DNS as a service through a scripting interface.
  • Generate your API Key by clicking on the Activate Now button.  The blank fields for API Key and Username will then be populated with your account information.

  • Once you have activated your Cloud Files account by generating your API key, you will now see the File Manager interface for Cloud Files.

  • To retrieve the Key at a later time, navigate to Your Account -> API Access.

  • To generate a new Key at a later time navigate to Your Account -> API Access and click on the Generate New Key button in the Generate A New API Access Key section.

GenerateKeys2.JPG

Now that you have generated your API Key, let's continue with the rest of our tour of the Control Panel with an Overview of the Billing Services available to you.
 



© 2011-2013 Rackspace US, Inc.

Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License


See license specifics and DISCLAIMER

8 Comments

Hi,

Does this key stays same forever or it will expire at some point?

API keys do not expire at this time, though you can generate a replacement key at any time through the control panel.

Can I have a different API Key per container?

Not per container, but our Identity API 2.0 allows sub-users and roles on an account. We're working on expanding this functionality into the control panel as well.

There's a thread on this subject on our product feedback forum if you'd like more information:

http://feedback.rackspace.com/forums/71021-product-feedback/suggestions/979763-let-accounts-have-more-than-1-api-key

Please update this to the REACH control panel. This method is out of date and confusing to new users.

Hey Tom,

We recently just added this ability into our Next-Gen control panel. Select your account/number at the top, then select "Api Keys" and you'll be able to see your existing api key, or generate a new one. Please let us know if you have any other questions.

-Rae

I didn't like having the v1.0 api key on every machine that I use cloudfiles on or being automatically deployed through chef in our environment either as a dataag or node attributes... so I setup haproxy+stunnel to proxy requests to cloudfiles through stunnel but first it writes the api key and username to the headers before sending it through stunnel to the auth server which returns the token to the client...

https://gist.github.com/0bce6c160dbd84b482c7

Very nice approach! If anyone else tries this, make sure you follow Paige's lead and restrict haproxy to the localhost, requiring a connection through a secure tunnel from client machines.

Add new comment