Date: Wed, 20 Jan 2021 19:23:47 +0000 From: Rafal Lukawiecki <raf@rafal.net> To: Colin Percival <cperciva@tarsnap.com> Cc: freebsd-cloud@freebsd.org Subject: Re: FreeBSD on AWS Graviton (t4g) Message-ID: <5B51EB44-C74A-4CF4-8238-B5EAA84D3FFB@rafal.net> In-Reply-To: <010001772125f507-211cb868-142d-4c1c-a95b-f4c4176caa51-000000@email.amazonses.com> References: <010001772125f507-211cb868-142d-4c1c-a95b-f4c4176caa51-000000@email.amazonses.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 20 Jan 2021, at 18:54, Colin Percival <cperciva@tarsnap.com> wrote: >=20 > If you run 'shutdown' from inside the EC2 instance it should work fine. J= ust > don't use the EC2 API to stop the ARM instances. The Autoscaling Group terminates and launches instances, I am afraid, as it d= iscovers any issues. Unless I do a convoluted workaround of setting up a Clo= udWatch event looking for an alarm from the group to then call a Lambda that= in turn talks to the instance to shut it down...it may be attractive to wai= t till it works inside 13.0. :) Rafal=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5B51EB44-C74A-4CF4-8238-B5EAA84D3FFB>