Skip to main content

Azure Networking Options - Core Cloud Services



I have done a lot of AWS things on here. Time to give Azure some attention. After all, since employers don't think Cisco or COMPTIA certifications are important, maybe Microsoft ones are?

First, let's really think about why these are the two biggest cloud services providers in the world:

They've been doing internet things for a long time. Amazon launched in 1995, a virtual bookstore.
Microsoft, well, you know. 

They've lived, breathed, and frankly, created, infrastructure that we use today, that they're selling to us today. Of course the Store of Everything and the Company of Everything would encourage us to put everything in their hands.

Also: Azure has a lot less silly names for modules. Important. I appreciate straightforwardness.


I said 'a lot less', not '100% sensible names'


Microsoft has a clear set of Azure Fundamentals that anyone can interact with. Let's talk about networking basics, basically to say, again, "Hi, employers, I have an interest in this and will ask questions to better my knowledge."

  • Virtual Networking
  • Azure Load Balancer
  • Traffic Manager



 Virtual Networking is almost how we use it on our individual machines - It's a logically isolated network that can be subnetted. Users interact directly with the web tier - the interface we see in a browser.

CREATE A VIRTUAL MACHINE

You can manage a group of load balanced VMs with Scale Sets - When you need more VMs, they're automatically made, and deleted in response to demand.

Azure Spot Instances offers unused resources at a discounted rate. All of these things are explained if you mouse over the Information toggle on the appropriate pages.



Not the greatest idea, but we can leave it up for testing. In a production enviroment, use the Advanced controls in the Networking tab to create rule limits.

Speaking of which:





I picked Azure Load Balancer for now, as it supports multiple traffic types and instances (Port forwarding, internal Azure traffic, ect). Just HTTP traffic can be used with Application Gateway.

 Load Balancing is essentially, backups under the same IP address. A cloud version of HSRP (Hot Standby Routing Protocol) with Cisco routers.

If there are 3 Azure VMs, and one goes down, the others pick up the slack. If there's a sudden influx of traffic, the load is distributed evenly among all three. The user does not care if VM A, B, or C is processing their request.

You can also set up extensions to install after the VM is set up. Less fiddling around with apt-get commands.


Because I'm in the Sandbox option of Azure Fundamentals Learning,  I can't push it to production. The module is supposed to be pushing a Wordpress app, but I take the time to explore instead, as I did that yesterday!

Traffic Manager means "We don't want things to go slowly!", which high availability doesn't really solve. It works in conjunction with regions, directing traffic to the region closest to the user, to avoid slowdown.

(Okay, this is probably the last post of the year. Expect more Azure)

EMPLOYERS: Hooray for the Cloud. Don't forget to visit the standalone page on LinkedIn to keep up to date!

Comments

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.