Skip to content

Latest commit

 

History

History
96 lines (75 loc) · 5.17 KB

AWS-Toolkit-for-Eclipse.mediawiki

File metadata and controls

96 lines (75 loc) · 5.17 KB

Table of Contents

Introduction

The AWS Toolkit for Eclipse is an open source plug-in for the Eclipse Java IDE that makes it easier for developers to develop, debug, and deploy Java applications using Amazon Web Services. With the AWS Toolkit for Eclipse, users can get started faster and be more productive when building AWS applications.

This wiki page documents how to configure the AWS Toolkit for Eclipse to provision and control cloud resources on Eucalyptus. This enables developers to build and deploy Java applications in either private or public cloud environments by simply changing the target cloud.

Prerequisites

The instructions assume the reader has an AWS account and access to a Eucalyptus cloud. To install Eucalyptus for evaluation purposes we recommend the FastStart installer. If you do not have local resources to deploy Eucalyptus, you may request a free account on the Eucalyptus Community Cloud.

You will also require the following

Configuration for Eucalyptus

This section describes how to configure the AWS Toolkit for Eclipse to communicate with your Eucalyptus cloud. The set of available regions is contained in the file regions.xml, which can be found in <eclipse_workspace_dir></eclipse_workspace_dir>/.metadata/.plugins/com.amazonaws.eclipse.core/regions/regions.xml

Open the regions.xml file and add the following entry: ```xml

  &lt;region&gt;
    &amp;lt;displayname&amp;gt;My Euca Cloud&amp;lt;/displayname&amp;gt;
    &amp;lt;systemname&amp;gt;eucacloud&amp;lt;/systemname&amp;gt;
        &amp;lt;flag&amp;#45;icon&amp;gt;flags/usa.png&amp;lt;/flag&amp;#45;icon&amp;gt;
        &amp;lt;min&amp;#45;toolkit&amp;#45;version&amp;gt;1.1.0.0&amp;lt;/min&amp;#45;toolkit&amp;#45;version&amp;gt;
    &amp;lt;services&amp;gt;
      &amp;amp;lt;service name=&amp;amp;quot;S3&amp;amp;quot;&amp;amp;gt;http://&amp;amp;#91;your.euca.server&amp;amp;#93;:8773/services/Walrus/&amp;amp;lt;/service&amp;amp;gt;
      &amp;amp;lt;service name=&amp;amp;quot;IAM&amp;amp;quot;&amp;amp;gt;http://&amp;amp;#91;your.euca.server&amp;amp;#93;:8773/services/Euare/&amp;amp;lt;/service&amp;amp;gt;
      &amp;amp;lt;service name=&amp;amp;quot;EC2&amp;amp;quot;&amp;amp;gt;http://&amp;amp;#91;your.euca.server&amp;amp;#93;:8773/services/Eucalyptus/&amp;amp;lt;/service&amp;amp;gt;
      &amp;amp;lt;service name=&amp;amp;quot;AutoScaling&amp;amp;quot;&amp;amp;gt;http://&amp;amp;#91;your.euca.server&amp;amp;#93;:8773/services/AutoScaling/&amp;amp;lt;/service&amp;amp;gt;
      &amp;amp;lt;service name=&amp;amp;quot;CloudWatch&amp;amp;quot;&amp;amp;gt;http://&amp;amp;#91;your.euca.server&amp;amp;#93;:8773/services/CloudWatch/&amp;amp;lt;/service&amp;amp;gt;
    &amp;lt;/services&amp;gt;
  &lt;/region&gt;

```

Note that you have to replace '[your.euca.server]' with the URL to your Eucalyptus front end. For example, this is the correct snippet to add when using the Eucalyptus Community Cloud: ```xml

  &lt;region&gt;
    &amp;lt;displayname&amp;gt;EucalyptusCC&amp;lt;/displayname&amp;gt;
    &amp;lt;systemname&amp;gt;ecc&amp;#45;1&amp;lt;/systemname&amp;gt;
        &amp;lt;flag&amp;#45;icon&amp;gt;flags/usa.png&amp;lt;/flag&amp;#45;icon&amp;gt;
        &amp;lt;min&amp;#45;toolkit&amp;#45;version&amp;gt;1.1.0.0&amp;lt;/min&amp;#45;toolkit&amp;#45;version&amp;gt;
    &amp;lt;services&amp;gt;
      &amp;amp;lt;service name=&amp;amp;quot;S3&amp;amp;quot;&amp;amp;gt;http://communitycloud.eucalyptus.com:8773/services/Walrus/&amp;amp;lt;/service&amp;amp;gt;
      &amp;amp;lt;service name=&amp;amp;quot;IAM&amp;amp;quot;&amp;amp;gt;http://communitycloud.eucalyptus.com:8773/services/Euare/&amp;amp;lt;/service&amp;amp;gt;
      &amp;amp;lt;service name=&amp;amp;quot;EC2&amp;amp;quot;&amp;amp;gt;http://communitycloud.eucalyptus.com:8773/services/Eucalyptus/&amp;amp;lt;/service&amp;amp;gt;
      &amp;amp;lt;service name=&amp;amp;quot;AutoScaling&amp;amp;quot;&amp;amp;gt;http://communitycloud.eucalyptus.com:8773/services/AutoScaling/&amp;amp;lt;/service&amp;amp;gt;
      &amp;amp;lt;service name=&amp;amp;quot;CloudWatch&amp;amp;quot;&amp;amp;gt;http://communitycloud.eucalyptus.com:8773/services/CloudWatch/&amp;amp;lt;/service&amp;amp;gt;
    &amp;lt;/services&amp;gt;
  &lt;/region&gt;

``` Be sure to restart Eclipse if it was running while editing the regions.xml file. Also, be sure to add your Eucalyptus key ID and secret key to the AWS Toolkit preferences

Latest Testing

The AWS Toolkit for Eclipse is usually tested each time there is a major or minor Eucalyptus release. Testing is currently a manual process and aims to validate the following capabilities

  • Start, reboot & stop / terminate instances
  • View instance status
  • Create, attach, detach, delete volumes
  • Create, delete snapshots
  • View images list
  • Create, modify and delete security groups
  • Create, browse and delete Walrus buckets
  • Bundle EMI
  • Deploy simple web application into Eucalyptus cloud
The information below describes the last known testing.

Latest Test: May 30, 2013

VERSIONS IN PLAY

  • Eclipse: Juno Service Release 2
  • AWS Java SDK: 1.4.5
  • Eucalyptus: 3.3 Milestone 6
What currently works:
  • View instances, their status and public IP, copy public DNS name
  • View, create, delete Volumes
  • View, create and delete Snapshots
  • View, create, modify and delete Security Groups
  • View image list [NOTE:]
  • View list of S3 Buckets
Remaining issues:

  • Cannot browse bucket contents
These issues have not yet been filed because it's not yet known what level the problem is at (Eucalyptus, AWS Java API, or AWS Toolkit for Eclipse). Please update this page if you figure this out before me.

  • Regarding Instances: Cannot start, stop, terminate, attach/detach volumes.
  • Regarding Instance Metadata: These columns are unexpectedly blank: State, Type, Availability Zone, Key Pair, Launch Time, Security Groups, Tags.
  • Simply viewing the instance list gets you an NPE. I mean the list appears, but something broke here because the pop-up menu that should appear when selecting an instance doesn't even show. And selecting an instance from the list causes an "Unhandled event loop exception" in the ec2 UI code.
category.HOWTO