On the last step i keep gettings those errors:
euca-register --debug --snapshot snap-XXXXXX --description "XXXXXX" --name "Fedora14-ebs" --kernel aki-XXXXXX --architecture x86_64 -A XXXXXXXX -S XXXXXXXX YYYYYYYYYYY/fedora14.x86_64.manifest.xml
InvalidManifest: HTTP 404 (Not Found) response for URL http://s3.amazonaws.com:80/YYYYYYYYYY/fedora14.x86_64.manifest.xml: check your manifest path is correct and in the correct region.
YYYYYY is like my other images(its a number on the other images i created from the web interface)
if i try a different bucket(a s3 bucket i already have) i get the following errors:
InvalidManifest: HTTP 403 (Forbidden) response for URL http://s3.amazonaws.com:80/XXXXXXXXXXXXX/fedora14_64bits.manifest.xml: check your S3 ACLs are correct.
How can i validate my ACLs are corrected? my access and secret key im sure are, im just not so sure about my cert and pk.
On Thu, Apr 14, 2011 at 01:13, Garrett Holmstrom <gholms@xxxxxxxxxxxxxxxxx> wrote:
On 4/13/2011 13:43, Kurt Seifried wrote:If you install euca2ools from the Fedora or EPEL repositories you should
> If you use the command line EC2 tools from Amazon you'll run into a
> few snags during install, I've documented getting them running on
> Fedora:
>
> http://kurt.seifried.org/2010/12/08/getting-amazone-aws-ec2-api-tools-working-properly/
be able to do the entire process without having to mess with either Java
or Amazon's proprietary tools. ÂJust replace each command's leading
"ec2" with "euca" (e.g. "ec2-register" becomes "euca-register").
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
_______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud
