Amazon AWS just released (on 13th February 2017) a new feature that allows to change a size of an EBS volume.
This allows to increase the size of an EBS volume on an existing instance, while it is running.
It is important to note that changing the volume size,...
You can install the ZIP installation and unzip it in the EFS.
Alternatively, install using Debian/RPM and mount the EFS to /var/opt/jfrog/artifactory in advance.
Alternative approach can be to only configure the Filestore to use the EFS.
That 150GB disk that r5ad.xlarge comes with is known as ephemeral storage - its content is wiped when you stop the instance. If you need persistent storage you can use r5a.xlarge that doesn't have the ephemeral storage disk and simply give it a bigger EBS disk.
Either you can increase the size of the root disk during instance creation or create another EBS ...
Firstly I would argue that backup time does not matter, as it usually doesn't correlate with the restore time.
In regards to restore time, snapshots restore on volumes almost instantly, as data is only copied onto the volume from S3 when requested.
So as long as you only request actually used data from the volume, it would only matter how much data is ...
What I do (and that's not exactly answering your question) is as follow:
Create an EBS volume and attach it to the instance doc is here
Rescan the scsi buses echo '- - -' > /sys/bus/scsi/devices/host1/scsi_host/host1/scan (you may have to adapt the host number)
Create a physical volume with pvcreate on the new disk found (fdisk -l to list all disk)
The import of JSONDecoderError from json module is a valid syntax only starting from Python 3.5, while in previous versions it was a subclass of ValueError class. Apparently the latest version of awsebcli 3.20.0 should launch with python >= 3.5 instead of python <= 2.7.
Apparently nothing suggested worked for me. Though I used the official aws ...