On Sat, Jul 20, 2019 at 11:26:38PM +0300, Mustafa Akdemir wrote: > Can i use Debian GNU/Linux 9 (Stretch) AMI by upgrading to Debian > GNU/Linux 10 (Buster) for Wordpress web site server until Debian GNU/Linux > 10 (Buster) AMI will be published. May it cause any problem by upgrading > Debian GNU/Linux 9 (Stretch) AMI?
Hi Mustafa. Upgrading an instance from stretch to buster should be essentially the same as any other stretch->buster upgrade. If desired, you can also create your own AMIs from scratch using the same FAI configs that the cloud team uses to generate the official images. In that case, the resulting image will be essentially indistinguishable from the official ones, except they'll be owned by your account. The steps to do this are: install fai-server, fai-config, and fai-setup-storage (>= 5.7) and qemu-utils. Clone the FAI configs from https://salsa.debian.org/cloud-team/debian-cloud-images.git Generate an image using: /usr/sbin/fai-diskimage --verbose --hostname debian \ --class DEBIAN,CLOUD,BUSTER,BACKPORTS,EC2,IPV6_DHCP,AMD64,GRUB_CLOUD_AMD64,LINUX_IMAGE_BASE,LAST \ --size 8G --cspace /path/to/debian_cloud_images/build/fai_config \ /tmp/image.raw Then write the resulting /tmp/image.raw file to a dedicated 8 GB EBS volume with: # dd if=/tmp/image.raw of=/dev/FOO bs=512k Then register the EBS volume as an AMI using the 'aws ec2 register-image' command from the awscli package. Be sure to enable EnaSupport and SriovNetSupport. You may find the wrapper script at https://salsa.debian.org/noahm/ec2-image-builder/blob/master/bin/volume-to-ami.sh convenient. This script is used in the publication of the stretch AMIs, but not the buster AMIs. The process is essentially the same, though. noah