AWS Shared Responsibility

While AWS is great for quickly provisioning servers and networks without worrying about the back end hardware, there are a few caveats to be aware of. A big one is who's responsible for what in Amazon's Cloud environment? Not really meant to be loaded question, it's important to understand that Amazon can not be held liable for your everything in your custom cloud architecture.

Below are some items you are responsible for within their infrastructure:

• Network access to and from your AWS instances
• Logging
• Patching
• Backups
• Virus Protection of instances

Amazon is responsible for items such as:

• Physical security
• Physical servers, storage, and networking components
• Disk destruction
• Security audites
• DDOS protection (Free Kindle AWS White Paper Below) 

Neither list above is comprehensive but does give you an idea on what you the customer will need to protect on your own. Even something such as login access to your instances is your responsibility. If you happen to loose your private key to an instance, there's not much Amazon can do for you as an example (easy to resolve that problem I know). For the most part if it's anything that's physical or layer 2, you can probably bet that Amazon handles that portion of the cloud.

Hopes this helps, anything else I should add to the list above? Let me know in the comment section below!

Initial Strides with Amazon Web Services (AWS)

I've finished my work provided LMS video series last week and now I'm powering through CBT Nuggets at a fairly fast clip. I estimate that within two weeks I'll be complete with the Nuggets training as well. What's great about learning Cloud is how quick you can ramp up a lab environment as mentioned in my last post. It's really supercharging the time it usually takes to pick up a new technical skill.


To be honest, I'm most excited about the Udemy course as I hear it's very hands on and closely relates to the exam itself. That's also the main reason that I'm saving that piece for last. But using books on Safari always allows me to deep dive into the technology at hand which is why it's included in my study plan.

This is all perfect timing as I'm getting thrown into a few interesting AWS projects. One is how to get around some of the AWS networking limitations. We're needing to communicate between potentially dozens if not hundreds of VPC's due to our engineering testing. How do we accomplish this at scale? How do we limit the time for deployment? How can we make it simple to implement along with using our own proprietary instances? There's a lot of questions to be solved for and this isn't including business aspect of things such as cost (of course) and personnel resource requirements.

VPC Example:

I would love to hear other opinions on rather you think the "Cloud" is hear to stay? If you think so, what are you doing to prepare for it? Talk to you all soon

Beginning AWS Studies

As our company begins to swiftly move services to the cloud, specifically AWS I'm now in a great position to pick up this technology. This will require a paradigm shift on my part, not just on learning the tech but also how I learn and study this info as well.

Before with traditional networking, you could pick up a book or 3, setup a small scale lab if necessary, and be on your way. Since Cloud technology moves so quickly, reading books that are only 2 years old can be out of date already! Not only that but there's so much to cloud services you need a very good grasp on what tools are available to you. The best way is to of course setup your own account with the cloud service and play around with everything available. This is a nice change as in the past with labs, it took dozens of hours planning, purchasing, and setting up hardware before you could even begin labbing.

My AWS study plans will focus on the AWS Certified Solutions Architect - Associate cert. This seems to be the initial starting point everyone recommends. I'm not sure how deep I need to go yet with this material but it's for sure a mile wide the material that I need to learn. Once this cert is completed, I'm most likely going to take a look at the AWS Certified Advanced Networking specialty exam as it makes the most sense to me. For the first exam I plan on using the current studying plan in this order:

• Internal company LMS (Learning Management System) web learning for the AWS course: This will provide me with a very high level overview, I'll begin basic labs as well
• CBTNuggets AWS Associate videos: I'll begin taking notes at this point before moving on. Still debating on older 2013 videos that they have, may be very outdated at this point.
• Safari Books - AWS Certified Solutions Architect Official Study Guide: Associate Exam: This will perform as my deep dive (hopefully) into the AWS material. I will continue note taking along as implementing flashcards using Anki at this point
• Udemy (CloudGuru) course: I'll then prep for the exam itself by going through this course if affordable and available to finish up any lingering topics. I'll also deep dive into labs during this time.

Looking into the future...Cloud

For the past year our family have experienced a lot of new things, challenges, and overall growth. We have a new addition and now we're a family of three! You really do learn to survive on less hours of sleep, very rarely do I sleep for my than 6 hours a day now, less for my wife unfortunately.  Even with that considered we wouldn't have it any other way.

I'm still at it here and there with Python scripting but my big focus for the last year was completing the Cisco Certified Design Professional (CCDP). This exam was absolutely tough and I barely squeaked by but I made it through. Even though I'm not playing much with Cisco at the moment, the concepts hold true for many other vendors as well. The most difficult topics were new tech that I just don't get to play with along with security. Be sure you understand Cisco ACI at a high level and Cisco security IDS best practice designs at a low level.

Next up for me is most likely Sec+ but I've also been taking a hard look at cloud infrastrucure. Our enterprise is heavily focused on moving as much as we can to cloud or at the very least, a hybrid infrastructure. Not much as landed in our Networking team's laps but it's coming down the line fast. Most likely I'll dive into AWS to get a good sense on what it's all about. Because I'll be honest physically racking less equipment is not anything I'll ever complain about!

Stay tuned for further updates and don't forget to check out my Github to the right -->

2016 Recap

A lot has happened this year, including a employer change, new family addition, and new certifications. The employer I work for now has a huge Juniper presense which allowed me to grow my CLI skills with a different vendor besides just Cisco. In order to take full advantage of this change, I went ahead and knocked out a few of Juniper's lower level certifications. I took and passed both the JNCIA and JNCIS-ENT this past summer to help vet my new learned skillset.

Book I used for the JNCIA and JNCIS-ENT Exam:

Along with Juniper we're also rolling out our own NGFW's that rivals many competitors such as Palo Alto. Not only have I had an opportunity to get more hands on experience with our firewalls, I have the chance to administer Juniper SRX's and Palo Alto's which has been very challenging but engaging.

In my past roles I never had much of a chance to deal with network load balancers which always bugged me. While I played around with Cisco ACE's (now extinct) I didn't find them very intuitive with a weird learning curve. This year I've had the chance to deploy and implement virtual F5's using their LTM and GSLB modules. I only touched the GSLB (DNS Load Balancing) very lightly but I did get some great experience with LTM (De-facto Server Load Balancing).

To end the year off, our first little one arrived, which meant that I didn't want to dig to deep into the certification world right now. Instead I'm now diving into Python so that I can script some of the repeatable stuff I do on a daily, weekly, or monthly basis. I'm very noobish but with a help of a fellow colleague, we're starting to make some useful stuff.

Check out my github link to the right ---> I'll be keeping this updated as time goes on and my skill level increases. Hope everyone has a happy holidays, I'm excited for what the next year will bring!

Digging into IP Packets

For the next 6 to 12 months I'm going to take a departure from focusing solely on certifications. I want to gain a better understanding of the underlying protocols that encompass my career daily. This will mean deep diving into the TCP/IP protocol suite. Not only do I want to understand what a general IPv4/IPv6 looks like, I want to learn how to correlate trends based on the IP packets that traverse my network.

Alcantel-lucent Ocean Fiber Cable Run

This will help immensely in troubleshooting security and general network connectivity issues. Not only that, but it can be used to stop certain teams from automatically blaming particular incidents on the network. Through the use of packet capture tools that show exactly what's happening between two hosts. There can be no if, and, or buts about whose fault it is for a particular problem using concrete logs.

Not that a packet capture will be used for every incident but it's good to have "big guns" that you can pull out of your arsenal every now and again. With that said, pulling out a "big gun" is no use if you have no clue on how to operate the weapon. Hence why I've been culling over multiple WireShark and huge TCP/IP books to help get me started. Having a strong foundation is important for just about any goal in life. We all know fundamental learning can become boring and repetitive quickly because typically it's not the cool bleeding edge stuff but it's VERY important. Mastery comes from making tasks second nature which requires constant repetition.

Just like a race car driver has to learn how to drive a fast car slow first, the same can be said with networking. We must learn how to configure and design small elements of a particular portion of a network first before moving on to deploying networks that can properly scale along with become resilient.

My Packet Capture read list:

Practical Packet Analysis

Wireshark Network Analysis (Second Edition)

Routing TCP/IP, Volume 1 (2nd Edition)

Cisco CCDA Passed!

I just left the test center with a passing score for the Cisco CCDA exam. Overall the exam was a lot more fair than what was described on the many internet forums I attend. There were a handful of questions that def. wasn't mentioned in the FLG\OCG.

I think part of the reason is that the FLG\OCG books are a little long in the tooth. For example Cisco NAC is mentioned all over the CCDA books, but nothing is mentioned about Cisco ISE. The same thing for the Cisco SONA framework, good stuff to know; at least at a high-level.

I'm taking a break from certs for a while. I want to do some independent research on the TCP/IP stack and deep dive into packet inspection. After that I'll most likely read through some CCIE material for a refresher on all of those routing protocols.

CCDA 200-310 Official Cert Guide