sparse-intern-71089
03/28/2019, 4:49 PMfierce-dinner-20116
03/28/2019, 4:50 PMdamp-book-35965
03/28/2019, 4:52 PMdamp-book-35965
03/28/2019, 4:52 PMfierce-dinner-20116
03/28/2019, 4:52 PMdamp-book-35965
03/28/2019, 4:53 PMdamp-book-35965
03/28/2019, 4:53 PMfierce-dinner-20116
03/28/2019, 4:54 PMdamp-book-35965
03/28/2019, 4:54 PMfierce-dinner-20116
03/28/2019, 4:54 PMfierce-dinner-20116
03/28/2019, 4:55 PMdamp-book-35965
03/28/2019, 4:55 PMfierce-dinner-20116
03/28/2019, 4:55 PMdamp-book-35965
03/28/2019, 4:56 PMfierce-dinner-20116
03/28/2019, 4:58 PMfierce-dinner-20116
03/28/2019, 4:58 PMfierce-dinner-20116
03/28/2019, 4:58 PMdamp-book-35965
03/28/2019, 4:59 PMbreezy-hamburger-69619
03/28/2019, 4:59 PMdamp-book-35965
03/28/2019, 4:59 PMwhite-balloon-205
nodeAmiId
explicitly. For production installations, you most likely will want to do this so that you are in full control of the timing of new AMI rollouts to nodes.damp-book-35965
03/28/2019, 5:17 PMfierce-dinner-20116
03/28/2019, 5:44 PMnodeAmiId
a mandatory field and moving the existing logic to an optional helper function would help prevent people from accidentally shooting themselves in the footfierce-dinner-20116
03/28/2019, 5:46 PMawsx.eks
package that has this behavior (since the theme of that package is “better defaults”)white-balloon-205
breezy-hamburger-69619
03/28/2019, 6:46 PMfierce-dinner-20116
03/28/2019, 6:59 PMbreezy-hamburger-69619
03/28/2019, 7:00 PMbusy-pizza-73563
03/28/2019, 7:14 PMami-032ed5525d4df2de3
.damp-book-35965
03/28/2019, 7:14 PMdamp-book-35965
03/28/2019, 7:15 PM