Is anyone here using AWS? I have been playing around with their CloudFormation service and using ec2.py to automate Ansible playbook. It is pretty awesome.
I purchased a couple different certification courses from that $10 Udemy sale but have yet to use them or AWS. It's on my list of things to at least play with and understand.
Nice idea, but would you want sensitive documents there?
I'm torn on the idea of some of these cloud places. But having been through several interviews lately, it's on the radars of a lot of companies. My current companies CTO mentioned recently that we were already using it. :wtf: We're so big I had no idea.
Yes, I am using amazon aws EC2 service, it is totally free for one year.
It's totally amazing!!!
High Internet Speed!!!
We're using it.
I'll be honest and say I don't know enough about it that I'd like to. When we get issues I've relied on my knowledge as a network engineer (such as how VRF works, how load balencers work and simple routing) but it's more too it than that.
I have a CBT nuggets subscription and will be picking up AWS vids there. My Sys. Admin just completed the solutions architect associate level. I'm going to be pursuing this at some stage.
I started using Glacier last week for my Synology backups. A little overwhelming at first but thanks to blogs I got it all going.
Quote from: zarawatsonn on April 28, 2016, 12:58:53 AM
Yes, I am using amazon aws EC2 service, it is totally free for one year.
It's totally amazing!!!
Do you mean the free tier service? It is very easy to go over the free tier usage limit.
Just had some deep dive sessions with some of our colleagues who've been struggling with NFV and third party appliances (FWs, LBs etc.) in AWS.
Suffice to say there's enough caveats to make your head spin - you just cannot do anything about the standard AWS networking paradigms e.g. how all subnets are automatically attached to the default gateway on the VPC router, how you cannot put a host (i.e. your virtual FW or LB) in line between the IGW and the VPC router, etc. The takeaway is that its way too hard, not scalable (any working solution invariably involves injection of static and/or host routes and bidir NAT, or running routing protocols within AWS itself between hosts directly, or tunnels), most solutions break integration into AWS services like S3 since those services rely on default routing behaviour - if your requirements at a networking level cannot be accomodated by standard AWS networking components (security groups, the standard VPG, the standard IGW, the standard WAF etc.) then just do not deploy in AWS - don't think that you can put in your own NFV appliances like in a vmware or kvm environment. In fact is far more restrictive than say Openstack.