Hi Again Moritz 
 
 I can not recreate your problem regarding the "Launch AMI" action.
  Could you retry with the current head build and provide more feedback
  if the problem persists?
  I retries and still the wizard does not open. It does work for the M7 milestone. I will try and download the nightly EPP packet tomorrow and see if there is something with my workspace. 
 
 
 I have got some times to test this out here is my results. 
 
 2) Head version using Gangmede as dev platform, works fine (my workspace here is quite new). 
 
 3) Head version using Europa as dev platform, doesn't work. I don't know why, I stepped through the code. Nothing strange happens, line 114 in eu.geclipse.aws.ec2.ui.actions.LaunchAMI.java is executed as expected.  Maybe something is messed up in my workspace (which is quite old) and line 77 (DebugPlugin.getDefault().getLaunchManager();) returns something that will not launch ?? If nobody else have any problems, then I guess that this is ok, and it will work for me when we are switching to Ganymede as the main development platform anyway.     
 
 Thanks, Harald G.  
 
 Thanks, Harald G. 
 
 greets
  Moritz
  
 
 
 Thanks,
  
 Harald G.
  
 
 
 
 
 
 
 Quoting Moritz Post <mpost@xxxxxxxxxxxxxx>:
  
 
 
 
 Hi Harald
  
 
 
 
 
 
 I am happy to hear that you are trying out the AWS implementation. The
  
 
 behaviour you are describing is originating from the fact that only
  
 
 images to which you have explicit launch access are listed under My
  
 
 Images.
  
 
 
 
 
 
 This means, that you will need to set explicit details here like:
  
 
 "ec2-modify-image-attribute <ami-id> -l -a <theAwsAccountId>" (the
  
 
 account id is not your aws access id btw ;)).
  
 
 This did the trick, it shows up now.
  
 
 
 
 This lists your image
  
 under MyImages. Thereby it is also possible to list images which do not
  
 
 belong to you but to whom you have execution rights. Agreeable this is
  
 
 a little confusing and therefore it is planned to refactor this
  
 
 category structure and to create something like:
  
 
 
 
 
 
 -Images
  
 
 +- All Images - Describe all AMIs, public, private or owned, that the
  
 
 user has access to.
  
 
 +- My Owned Images - Images which the user has created and can access/run
  
 
 +- My Accessible Images - Images which do not belong to the user but to
  
 
 which he has the rights to run
  
 
 
 
 
 
 I hope this did help you a little. Your feedback is greatly appreciated :)
  
 
 
 
 
 
 regards
  
 
 Moritz
  
 
 
 
 
 
 
 
 
 
 Dear Moritz
  
 
 
 
 
 
 
 
 I finally got around to try out the AWS in this regard I have a   question. I managed to create my own image and registered it   (ami-148d697d). Within g-Eclipse I can see my running instances  in  the "Computing" folder, my AMI named haraldgImg shows up in  the  "Storage" folder and I can mount it and browse through it, I  can  also see me gsg-keypair in the "Services/Keyairs" folder. My   problem is that in the "My Images" folder there is nothing. How  do  I get my AMI to show up here so that I can Launch it from its   context menu? I am using the head version of g-Eclipse.
  
 
 
 
 
 
 
 
 
 
 
 
 
 PS: I send this to the dev list in case someone else is also try  it  out and have the same question.
  
 
 
 
 
 
 
 
 Thanks,
  
 
 
 Harald G.
  
 
 
 _______________________________________________
  
 
 
 geclipse-dev mailing list
  
 
 
 geclipse-dev@xxxxxxxxxxx
  
 
 
 https://dev.eclipse.org/mailman/listinfo/geclipse-dev
  
 
 
 
 
 
 
 _______________________________________________
  
 
 geclipse-dev mailing list
  
 
 geclipse-dev@xxxxxxxxxxx
  
 
 https://dev.eclipse.org/mailman/listinfo/geclipse-dev
  
 
 
 
 
 
 
 
 _______________________________________________
  
 geclipse-dev mailing list
  
 geclipse-dev@xxxxxxxxxxx
  
 https://dev.eclipse.org/mailman/listinfo/geclipse-dev
  
 _______________________________________________ geclipse-dev mailing list geclipse-dev@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/geclipse-dev 
 
  |