Alot of ebs volumes got created when I was testing out my stack. So I looked into delete policies. https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-deletionpolicy.html
Adding resources to stack after the fact
change sets
CloudFormation things to know
https://stackoverflow.com/questions/49198657/add-resources-to-existing-cloudformation-stack Add Resources to existing CloudFormation stack
Joining bash arguments as string
https://unix.stackexchange.com/questions/197792/joining-bash-arguments-into-single-string-with-spaces arg $1 is suppose to be “@werm-fw/cloud” and $2 “@werm-fw/set-up” but after I want to pass both args as a single string you would think that if i do this im good, but actually I have to do execute the code below for it to work
npm stopped being able to publish and pull package
for some reason npm stop being able to publish and pull package then it worked
All of sudden, npm install stopped working on the instance level
I was doing some testing then all of a sudden I stopped being able to pull packages. So I ran these two commands again and it worked.
Upload to s3 from client using aws sdk
https://github.com/Sam-Meech-Ward/s3-direct-upload Ran into cors issue https://stackoverflow.com/questions/28568794/amazon-s3-javascript-no-access-control-allow-origin-header-is-present-on-the
extract.w cheat sheet
Has to have a boolean value or no value at all. “wow” will be equal to “true” and “hey” will be placed in the “${leftover[@]}” array and set as “$1” arg “wow” will be equal to false because false is a boolean because –wow- ends with “-“, “wow” must have[…]
authorize-security-group-ingressauthorize-security-group-ingress and modify-instance-attribute
On a newly created security group, port 22 is not open. before applying it to a instance, add port 22 to the security group.