Cloudformation Deployment in usw1

gist.md

Steps

• land patch in cloud-tools repo
• deploy stack with incorrect CGW
• downtime VPN connection, nagios1.private.releng.usw1 in nagios
• delete correct CGW
  • VPN goes down
• update template, re-deploy with correct CGW and with a 'private' subnet
• verify VPN is back up
• adjust nagios configuration as necessary for new VPN parameters
• move nagios1 to the new private subnet
  • stop
  • make new AMI
  • deploy AMI in correct subnet (AZ must match: us-west-1a)
  • attach existing EBS volume (vol-b9a4eaed) to new instance
  • start and test
• verify nagios1 accessible
  • set up new security group
• re-enable monitoring of network, nagios1 (it's all just downtimed, so not strictly necessary)
• clean up
  • leftover volumes
  • leftover instances
  • old subnets
  • old security groups
  • old VPC + cruft

CGW info

• Type: ipsec.1
• IP address: 63.245.214.82
• BGP ASN: 65026

Attaching via UI only allows /dev/sdf and higher;

aws ec2 attach-volume --region us-west-1 --volume-id vol-b9a4eaed  --instance-id i-d44e2c17 --device /dev/sda

seemed to work, though

Actually, UI just recommends /dev/sdf and higher; type what you want. /dev/sda1 worked (/dev/sda doesn't - PV uses partitions, not drives)