Well, thanks to the incredible popularity of VMware, the concept of a V neck is certainly familiar
to us and I'm kind of borrowing that terminology here for RWC, so we know exactly what we're talking
about, but elastic IP is you might never have heard of.
So we're going to be prepping those for FMC environment in this video.
So let's take care of the network interface that our FMC virtualized appliance is going to be utilizing.
So where am I going?
Let me think of the best place.
Yeah, the probably the easiest way to get where we need to go to create our network interface is to
go to the EC2 dashboard and then let's go into the network in security area there and choose network
interface.
So I'm going to create a network interface.
I will call this FMC in a WAC underscore interface.
I will then select a subnet.
This is obviously going to be a key, key consideration here that we get this right notice thanks to
our naming, I can see there's a management subnet for my FMC.
By the way, those other subnets I created were for the future, right?
Those additional data subnets, those I created at that time, we're not going to need them for just
the management interface of the FMC, but it's great to have those created for, you know, obviously
what's going to come later on where you would want to connect the FMC to your actual data passing devices
like your firewall threat events systems.
Okay.
So private IP address, notice this.
I am not going to have a U.S. auto assign a private IP address.
No way.
We want to make this very deterministic.
And why don't we do ten .0.0. ten and we will do the slash 24 bit mask.
Of course, that is in the management subnet and we'll make this the dot ten node.
We don't need any fancy fabric adapter capabilities.
And notice that we are going to be attaching the security group to this network interface that we created
earlier in the previous video.
I'll go ahead and add a tag.
Of course, you know what it's going to be.
We have a tag of use and this is our FMC in a WAC.
And it is I think I said FMC underscore in underscore eight of us.
There we go.
We are going to create this network interface hopefully up.
It just wants the IP address.
It does not care about the mask.
All right, let's create the network interface.
And I should have known that it doesn't care about the mask because it knows the mask for the underlying
subnet configuration.
All right.
We forgot the name tag.
No problem.
Notice I can give the name tag right here.
This is FMC and AWG underscore network card or something like that.
So there's our network card.
Beautiful.
This is going to be much appreciated by the FMC virtualized appliance.
And now to wrap up this brief, straightforward video, we want to talk to you about an elastic IP.
What's going to happen is this FMC is going to be deployed in a WAC and the default settings that we're
going to enact would be to auto assign it a public IP address, but you might not want that public IP
address to change, right.
That would be a pain.
So, you know, you have your putty all set up to go to this public IP and it keeps changing on you.
So if you want a static public IP address, if you will, one that you control, that's what an elastic
IP address is all about.
So this is a very important capability.
I don't necessarily need one in this practice lab, to be honest with you.
I really don't care if my FMC management IP address that I can use to access it changes.
But I'm really going to show you this even though I don't need it, because a lot of times you would
want this, you would absolutely have to have it.
So the IP address does not change.
It's not like it's very expensive.
In fact, the IP address is free while your EC2 instances turned on.
If you terminate the instance in the NIC shuts down and the IP address is just sitting there, that's
when AWG gets aggravated and.
Starts charging you, but even then it's not expensive.
So notice that I am assigning or allocating a new elastic IP address here, and that's fine to have
it pulled out of Amazon's pool of available public IP addresses.
I want to go ahead and add a custom tag of use, and this is FMC in a WAC.
Let me get that right, actually.
There we go.
And we will allocate this address that couldn't be much simpler.
I actually will give a name tag and I'll do that right here.
I keep forgetting we'll call this elastic up.
Whoops.
I've been kind of doing FMC in IWC up front and then IP for elastic IP.
So there is our elastic IP address.
Now notice that it has already gotten the allocated IPv4 out of the pool.
So that's cool.
So we have this address.
54.2 26.1 86.1 36.
Boom, we can write it down.
It's not going to change.
And that's how we're going to be able to get to our FMC.
Notice that we've allocated the address, but now we're going to associate the elastic IP address and
I can go and say, I want that elastic IP address associated with this network card or network interface
that we created earlier.
Love it.
And then I could allow this to be resuscitated if I wanted.
Maybe I'm sharing them between devices or something fancy like that.
We're not doing anything that fancy.
So I'm just going to say go ahead and bind that nice static public IP to that network interface card
that we created moments ago.
Well, guess what?
Congratulations.
You've reached that point at which we are now ready to deploy the Firepower Management Center virtualized
device.
I know this was a lot of steps.
I know we built a lot in AWP, but let's face it, it was all super easy.
So now let's deploy the FMC in our next video to this awesome VPC that we've constructed.