You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In AWSEC2JCloudsProvider, when we create a new Instance we do not provide any information about the EBS volume that will be attached to the new VM. Therefore, by default, JClouds creates a gp2 volume (regular SSD) with the same size than the source image.
According to Amazon, when a new EBS volume is created, the flag deleteOnTermination is set to true but it seems that it is not the default behavior of JClouds.
The VM's template must therefore be cutomized with specific volume informations, see the method mapNewVolumeToDeviceName for instance.
Without this fix we will continue to pay for the remaining volumes after VMs deletion!
The text was updated successfully, but these errors were encountered:
In AWSEC2JCloudsProvider, when we create a new Instance we do not provide any information about the EBS volume that will be attached to the new VM. Therefore, by default, JClouds creates a
gp2
volume (regular SSD) with the same size than the source image.According to Amazon, when a new EBS volume is created, the flag
deleteOnTermination
is set totrue
but it seems that it is not the default behavior of JClouds.The VM's template must therefore be cutomized with specific volume informations, see the method mapNewVolumeToDeviceName for instance.
Without this fix we will continue to pay for the remaining volumes after VMs deletion!
The text was updated successfully, but these errors were encountered: