You could pull it down from an S3 bucket that only the deployer and the ASG w/ IAM role have access to. I highly recommend versioning the bucket and make 2 for blue/green or red/black.
On Mon, Mar 11, 2019 at 5:46 AM Rafal Lukawiecki <[email protected]> wrote: > Hello Everyone, Hello Colin, > > I hope someone can explain, as I have been lost in this for over a week. I > would like to pass a small (4-5kB) tarball of files for the built-in cloud > init script of the official FreeBSD 12.0 EC2 AMI to get untarred and > processed (>, >>, or #!) upon instance launch. I have successfully done it > for over 2 years using Launch Configurations but I cannot make it work > using the new Launch Templates. > > No matter if base64 and upload via the console, or base64 and use aws cli, > or create an LC and convert to an LT, it only works with LC. > > So far, I can see that depending which route I use to upload the file, > when I download it back from the finished template/configuration there seem > to be 3 different userdata lengths, even though I always pass the same > input. It suggests to me that some other processing of that input happens, > and I am lost where to hunt for it. > > Have any of you nailed it down? What steps do you take to prepare it? > > Many thanks and regards from Ireland, > Rafal Lukawiecki > _______________________________________________ > [email protected] mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-cloud > To unsubscribe, send any mail to "[email protected]" > -- Philip M. Gollucci IT Executive and Engineering Leader http://www.linkedin.com/in/pgollucci/ 301.818.0719 _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-cloud To unsubscribe, send any mail to "[email protected]"
