EC2 instance is going to terminate while stack is creating

[dklevakin]

Hello,

I'm trying to create a stack and faced with an issue.
EC2 container instance is terminating when I create the stack
I have grubbed system log

Starting hibagent...                              Ok
ci-info: no authorized ssh keys fingerprints found for user ec2-user.
ci-info: no authorized ssh keys fingerprints found for user ec2-user.
ec2: 
ec2: #############################################################
ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
ec2: 1024 SHA256:0HRM62KQcPYt7uT5rEfEfdCLTMDwrJg7FkSxvSmI6yc root@ip-172-16-31-15 (DSA)
ec2: 256 SHA256:vmMuN5aJ+N0VDsCG7PxZYm58r4Km0/7ffbFO7QsUtXY root@ip-172-16-31-15 (ECDSA)
ec2: 256 SHA256:o3bALTEo5/kwi+etXHWULhZIQwQPS2v87z5bBRcgtu4 no comment (ED25519)
ec2: 2048 SHA256:DM1q6yvpvgbbwh0ovBMuRsiCVL+Qbg8oy78zRsIM3eg root@ip-172-16-31-15 (RSA)
ec2: -----END SSH HOST KEY FINGERPRINTS-----
ec2: #############################################################
-----BEGIN SSH HOST KEY KEYS-----
ecdsa-sha2-nistp256 *********************T root@ip-172-16-31-15
-----END SSH HOST KEY KEYS-----
Cloud-init v. 0.7.6 finished at Mon, 23 Apr 2018 15:57:37 +0000. Datasource DataSourceEc2.  Up 166.09 seconds
[  166.298678] Adding 4095996k swap on /swap.  Priority:-1 extents:9 across:4644860k SSFS

Amazon Linux AMI release 2017.09
Kernel 4.9.81-35.56.amzn1.x86_64 on an x86_64

ip-172-16-31-15 login: [  172.300108] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
[  172.492575] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
[  172.772403] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
[  173.112984] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
[  173.312292] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
[  173.613613] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
[  173.837826] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
[  173.985410] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
[  174.095265] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
[  174.170559] cgroup: docker-runc (7847) created nested cgroup for controller "memory" which has incomplete hierarchy support. Nested cgroups may change behavior in the future.
[  174.180947] cgroup: "memory" requires setting use_hierarchy to 1 on the root
[  174.534063] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
/dev/fd/10: line 1: /sbin/plymouthd: No such file or directory
initctl: Event failed
Stopping docker: [  OK  ]
stopping awslogs
Stopping awslogs: [  OK  ]
Stopping sshd:  [  OK  ]
Shutting down sm-client: [  OK  ]
Shutting down sendmail: [  OK  ]
Stopping crond: [  OK  ]
Stopping acpi daemon: [  OK  ]
Shutting down ntpd: [  OK  ]
Stopping block device availability: Deactivating block devices:
  [LVM]: deactivating Volume Group docker... done
[  OK  ]
Stopping auditd: [  269.178746] audit: type=1305 audit(1524499161.030:87): audit_pid=0 old=2276 auid=4294967295 ses=4294967295 res=1
[  OK  ]
[  269.276278] audit: type=1305 audit(1524499161.130:88): audit_enabled=0 old=1 auid=4294967295 ses=4294967295 res=1
Shutting down system logger: [  OK  ]
Shutting down interface eth0:  [  OK  ]
Shutting down loopback interface:  [  OK  ]
Stopping cgconfig service: [  OK  ]
Stopping monitoring for VG docker: [  OK  ]
Stopping rngd: [  OK  ]
Stopping cfn-hup: [  OK  ]
Sending all processes the TERM signal... init: ecs post-stop process (8019) killed by TERM signal
[  OK  ]
Sending all processes the KILL signal... [  OK  ]
Saving random seed:  [  OK  ]
Turning off swap:  [  OK  ]
Unmounting file systems:  [  OK  ]
init: Re-executing /sbin/init
[  276.343996] EXT4-fs (xvda1): re-mounted. Opts: (null)
Halting system...
[  276.494089] ACPI: Preparing to enter system sleep state S5
[  276.499984] reboot: Power down
[  276.507425] acpi_power_off called

Could you point me where to dig further?