AMI postConfigure creates additional instance with non-matching local EBS volume

Build tested: 1.0.7-1 AMI (binary), non-root user (mariadb-user)

I created an instance with 1TB local disk and use it to setup a 2UM combo stack. 1TB cpimport failed because PM2 ran out of disk space. It turned out that the local disk for PM2 is only 100GB.

PM1
[mariadb-user@ip-172-30-0-236 tests]$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/xvda2 1000G 99G 902G 10% /
devtmpfs 120G 0 120G 0% /dev
tmpfs 120G 16M 120G 1% /dev/shm
tmpfs 120G 17M 120G 1% /run
tmpfs 120G 0 120G 0% /sys/fs/cgroup
tmpfs 24G 0 24G 0% /run/user/1002
/dev/xvdz1 2.0T 1.1T 918G 55% /data

/dev/xvdz1 is an EBS volume where my 1TB source is.

PM2
[mariadb-user@ip-172-30-0-147 ~]$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/xvda2 100G 98G 2.3G 98% /
devtmpfs 120G 0 120G 0% /dev
tmpfs 120G 11M 120G 1% /dev/shm
tmpfs 120G 17M 120G 1% /run
tmpfs 120G 0 120G 0% /sys/fs/cgroup
tmpfs 24G 0 24G 0% /run/user/1002
[mariadb-user@ip-172-30-0-147 ~]$