I just verified that ec2-api-tools work with such user data when pointed at a eucalyptus server: $ ec2-run-instances -k mykey --user-data " << FOO >" emi-247011C0 RESERVATION r-45F60808 admin admin-default INSTANCE i-523209EF emi-247011C0 0.0.0.0 0.0.0.0 pending mykey 0 m1.small 2009-10-27T19:37:32+0000 sm-zone-1a eki-41E516CA eri-253A1644 monitoring-false $ euca-run-instances -k mykey --user-data " << FOO >" emi-247011C0 Warning: failed to parse error message from AWS: <unknown>:1:0: syntax error EC2ResponseError: 403 Forbidden Failure: 403 Forbidden
$ dpkg-query --show euca2ools euca2ools 1.0+bzr20091007-0ubuntu1.1~ppa
I also verified that inside the instance created by ec2-run-instances the meta-data server has the correct value for user-data.
I just verified that ec2-api-tools work with such user data when pointed at a eucalyptus server:
m1.small 2009-10- 27T19:37: 32+0000 sm-zone-1a eki-41E516CA eri-253A1644 monitoring-false
$ ec2-run-instances -k mykey --user-data " << FOO >" emi-247011C0
RESERVATION r-45F60808 admin admin-default
INSTANCE i-523209EF emi-247011C0 0.0.0.0 0.0.0.0 pending mykey 0
$ euca-run-instances -k mykey --user-data " << FOO >" emi-247011C0
Warning: failed to parse error message from AWS: <unknown>:1:0: syntax error
EC2ResponseError: 403 Forbidden
Failure: 403 Forbidden
$ dpkg-query --show euca2ools -0ubuntu1. 1~ppa
euca2ools 1.0+bzr20091007
I also verified that inside the instance created by ec2-run-instances the meta-data server has the correct value for user-data.