Don't listen to these comments. I urge EVERYONE to save their perm files somewhere. Trust me, the rist of getting compromised is nothing compared to the risk you're exposing yourself to if you don't.
Tips for Getting Started With AWS
41–50 of 56 posts
Re: Tips for Getting Started With AWS
#42Don't listen to these comments. I urge EVERYONE to save their perm files somewhere. Trust me, the rist of getting compromised is nothing compared to the risk you're exposing yourself to if you don't.
Simple! Excellent point thanks for posting.
Re: Tips for Getting Started With AWS
#43Earlier quoted context omitted.
Why are people so thrilled about a slower more error prone way to do what amazon provides already? Just make an ami for each kind of server you want. Now you skip the waiting part, and the "oops, my pile of messy ruby scripts fucked up configuring the server" parts.
How do you create that initial AMI? CMs make answering that question simple. AMIs are nice - but they're merely snapshots of an end product. Being able to get to that end product in a repeatable, idempotant and self-documenting fashion is just as nice. So is being able to create a virtual image on your own machine with the same end product. FWIW, Vagrant lets you specify an AMI in its box description, so you get the…
>How do you create that initial AMI? CMs make answering that question simple.
No, they make it slower and more complex. The idea being that after you have built a config, future clones will be easier. But you already get a better solution just setting up a server and then making an AMI from it. Cfengine and friends offer quite literally zero benefits for this sort of scenario.
Re: Tips for Getting Started With AWS
#44Earlier quoted context omitted.
Why are people so thrilled about a slower more error prone way to do what amazon provides already? Just make an ami for each kind of server you want. Now you skip the waiting part, and the "oops, my pile of messy ruby scripts fucked up configuring the server" parts.
You can use Ansible to create an AMI to get the best of both worlds - fast provisioning, plus the ability to make new AMIs in a repeatable, self-documenting manner. You're arguing configuration management is "error prone", but I've found it a lot less error prone than other methods. If something doesn't install right I can blow away the whole thing rather than trying to un-break a destroyed install. If your Ansible s…
>If your Ansible scripts are in Ruby
The popular options are in ruby. Just because you use a less popular one that is written in python doesn't change the main point.
Re: Tips for Getting Started With AWS
#45Earlier quoted context omitted.
You can use Ansible to create an AMI to get the best of both worlds - fast provisioning, plus the ability to make new AMIs in a repeatable, self-documenting manner. You're arguing configuration management is "error prone", but I've found it a lot less error prone than other methods. If something doesn't install right I can blow away the whole thing rather than trying to un-break a destroyed install. If your Ansible s…
>If your Ansible scripts are in Ruby The popular options are in ruby. Just because you use a less popular one that is written in python doesn't change the main point.
Ansible itself is Python, and the docs all use Python examples. I've yet to come across a Ruby one...
Re: Tips for Getting Started With AWS
#46Earlier quoted context omitted.
>If your Ansible scripts are in Ruby The popular options are in ruby. Just because you use a less popular one that is written in python doesn't change the main point.
Ansible itself is Python, and the docs all use Python examples. I've yet to come across a Ruby one...
Why are you replying if you can't be bothered to read?
Re: Tips for Getting Started With AWS
#47Earlier quoted context omitted.
Ansible itself is Python, and the docs all use Python examples. I've yet to come across a Ruby one...
Why are you replying if you can't be bothered to read?
The post you replied to was about Ansible (which is pretty popular).
If you're intending to bash Puppet/Chef, why are you doing it in response to someone mentioning how handy Ansible is?
Re: Tips for Getting Started With AWS
#48Earlier quoted context omitted.
Why are you replying if you can't be bothered to read?
The post you replied to was about Ansible (which is pretty popular). If you're intending to bash Puppet/Chef, why are you doing it in response to someone mentioning how handy Ansible is?
Re: Tips for Getting Started With AWS
#49A bit disappointed by this. As mentioned by ceejayoz, don't upload your .pem file anywhere! AWS has tons of weird/interesting quirks - I thought this article was going to be about those. Here's my 5 tips for AWS... - SQS: encodes messages by default! plan accordingly if you are going to be sending large bodies (265K max). - ELBs: they need time to warm up if you get a huge traffic spike. ELBs won't start scaling unle…
[deleted]
Re: Tips for Getting Started With AWS
#50Earlier quoted context omitted.
The post you replied to was about Ansible (which is pretty popular). If you're intending to bash Puppet/Chef, why are you doing it in response to someone mentioning how handy Ansible is?
http://www.nizkor.org/features/fallacies/straw-man.html