- 新しい順
- 投票が多い順
- コメントが多い順
Hi Abhinav,
thanks for your reply. What you describe is what I was hoping for, but it seems it doesn't work like this.
The documentation doesn't list a --instance-id
parameter and if I try it, the reply is Unknown options: --instance-id
.
The create-instance-export-task
actually kind of works, because it will terminate with an error description for instances that can't be exported (marketplace AMI, more than one volume etc.). This is useful because these checks seem to run before the check if the instance is currently running, so it can be used on active instances. The command is
aws ec2 create-instance-export-task --description "test export" \
--instance-id i-012345... \
--target-environment vmware \
--export-to-s3-task DiskImageFormat=vmdk,ContainerFormat=ova,S3Bucket=yourtestbucket
where the bucket exists and has permissions according to the documentation.
Note that this will create the export task if the machine is exportable and currently stopped, I couldn't find a way around that. Since I now found out that almost none of the instances are exportable, because they were created from a marketplace AMI, I need to find a different solution anyway.
Cheers,
Marc
関連するコンテンツ
- 質問済み 7年前
Thanks for letting me know my mistake