cloudXabide | to the Cloud

I assume this is a bit of a dated set of procedures... as-in, there is probably a better way to deal with LUKS nowadays.  Also - at some point I will (hopefully) be writing a blog entry about LUKS key accessed from centralized key server. Assessment cryptsetup luksDump /dev/sda1 cryptsetup luksOpen --test-passphrase --key-slot 3 --key-file /root/.keyfile /dev/sda1 Setup # If there is already a crypttab, update it... otherwise, create a new one if [ -f /etc/crypttab ] then    sed -i -e '1i# <target name>    <source device>        <key file>    <options>' /etc/crypttab else   echo "# <target name>    <source device>        <key file>    <options> " > /etc/crypttab fi # Create a "key file" and add it to the device (interactive step) dd if=/dev/urandom of=/root/.keyfile bs=32 count=1 chmod 0400 /root/.ke...

The commonality for ANYone trying to do this, is the "TemplateDescription" == "(SO0044) - AWS Landing Zone Initiation Template".  Cool, I'll just run an "aws cloudformation list-stacks"... select the key fields, run a filter ... oh... wait.. you CAN'T apply a filter to this output.  :-(  The only filter capability that the "cloudformation" option has is for "status". At some point I hope to "the answer", but I want to document my attempt at creating a solution along the way. Here is a command to get some useful output... $ aws cloudformation list-stacks --region=us-east-1 --query "StackSummaries[].[StackName, TemplateDescription]" --output text Now... the trouble with this command, it will produce 2 outputs... what if the StackName has spaces.  Well, as it turns out, a StackName will *NOT* have spaces. "Stack name must contain only letters, numbers, dashes. Must start with a letter." That...

It's been a few months now since I transitioned away from "infrastructure" and started moving "to the cloud".  I think one ideal prevails:  it's not what you know, it's what you can learn... and use.  What I have found - Cloud makes many things easy (or seem easy)  things like H/A, fault-tolerance, message queues, geo-aware content delivery, automatic replication.... alright...  but, there is a (sometimes) a price for all of that.  Users have a LOT of power at their fingertips, and few controls.  Things can, and do, get out of hand. This post will be: just another Automated Landing Zone post.... Often referred to as "Landing Zone" and in text apps as "ALZ" - the solution is widely deployed and has become well recognized.  Now, ALZ is not service.  Instead, it is a solution that provides the framework to deploy and manage accounts in an Enterprise-grade way. It provides: controls auditing baseline networking automation remed...