Welcome to the project Cloudstreet with TerraForm is the name of this project.
And yes, state, not automation, yes, of course, we automated cloud set up Viterra Farm, but it's
more about maintaining the state of your cloud infrastructure.
All right, so let's say you have a cloud management team and they are in charge of deploying, set
up and managing the infrastructure on the cloud and also very heavy usage of cloud services.
Now, of course, then there will be regular provisioning requests and regular changes, regular deployments.
So if you have the heavy usage of cloud services and a very regular usage, then you should also get
into some problems.
When we talk about infrastructure, there are so many things in setting up an entire infrastructure
is a complex process, this network to security, these operating systems, the storage load balancers,
et cetera, et cetera, one time infrastructure setup is fine.
But if you want to do it multiple times, doing the same thing is not repeatable.
And maybe similar infrastructure for dev staging productions and also multiple projects.
So manually, if you're doing that, it's not repeatable.
Also, it will be very difficult to track like who made the change when the change was made.
You try to make documents of the infrastructure like inventory that's time consuming process.
And that should happen because if the infrastructure state is not centralized.
Also, there'll be chance of making human errors, and these things can lead to non-functional infrastructure
or bugs, errors or even exposed infrastructure in such a huge environment, doing all those things
will take a lot of time.
These are some problems, common problems, there could be more.
That's to get the solution.
You need to have configuration management of the infrastructure.
Like at a centralized place, and you need to have everything automated, of course, so there's less
chance of making human error.
And always, you should be maintaining a centralized state of the infrastructure.
So all the configuration of your infrastructure is maintained at a centralized place and we can automatically
deploy the changes, any change management can be triggered very easily and we can avoid the human errors.
Your infrastructure should be in Feis or in court, so you can control it.
You have infrastructure as a court and you should have repeatable infrastructure as a court.
So you should not hard core values also then it should be reusable across different environments like
WDEF, QE, staging production or even across different projects, should also have a reusable code.
Cloud automation and lots of business value and here are some statistics, 71 percent of the companies
say they have seen 10 percent of revenue growth, 84 percent have lowered their operations cost.
Eighty one percent have become more innovative.
When you automate infrastructure, you save a lot of time.
You can invest that time in learning and adapting new technologies in your projects, which can add
more business value.
And, of course, you become more agile.
34 percent have become more agile quickly.
They can deploy changes as per the requirements.
And I think infrastructure was never so easy.
Infrastructure has really become a code now, and we'll see how we're going to do that.
So we are going to use terraform and eatables cloud computing platform, so we're going to set up a
complete infrastructure on A.W. Cloud, but using terraformed, not only set up, we are going to see
how we are going to maintain its state.
Also, any change, how we can very easily deploy to our infrastructure.
So here are the things.
Steps that we're going to do, we need to set up terraform with back and forth so we have a centralized
state of terraform or of a cloud infrastructure.
Then we are going to set up VPC.
With that gateway Internet Gateway subnet, so we can have a secure and highly available VPC set up
with TerraForm.
Will also provision being environment for terraformed and also the backend services that willing to
use idea's elastic cash and active MQ, and also along with that we have security groups, keepers,
Bastion Hills and few other things that are going to automate and maintain with terraform.
OK, so let's do this, but one thing, keep in mind, it's not about just automation, it's not about
just the speed now.
It's also about maintaining the state, having the state of your infrastructure in a file.
That's pretty awesome.
And obviously, then in your state, you can very easily make changes, the differential changes.
So let's see the architecture of the project.
OK, so this is the architecture we're going to have to reform on our local machine and we're going
to store the state the information about our infrastructure in an empty bucket, which will be obviously
not eatables cloud account, will also configure terraformed with the proper authentication we're going
to use in terraformed to access our cloud services and create a VPC of that is distributed among multiple
zones, say it's subnets distributed among multiple zones.
So will have public subnet distributed among multiple zones connected to an Internet gateway with our
roundtable.
So we're going to set up a round table and out the traffic to the Internet gateway.
We'll also have private subnet again, distributed among multiple zones in our private subnet within
two hours, set up services like Easy to instances, MySQL database or Elastic Geshe.
Of course, this private subnet will be connected to a not gateway through a round table.
And to access the center VPC.
What should I say to access private systems in your private subnet?
We are also going to have a Bastion host, so we even provisioned Bastiaan most from our telephone scrotes.
So once we have our VBC created, then we are going to create our infrastructure on that or should I
say Liautaud stack?
Which we'll see in the next architectural Lytro once we have a VBC set up.
We are going to create a stack the services that we need to set up our stack losing terraform again.
And obviously, we are going to maintain the state in the budget, as you have seen the previous design
as well.
So TerraForm is going to set up ideas, for instance, in private subnet, elastic cash in private subnet,
again, Amazon, MQ again in private subnet in the VPC and Bienstock, where the load balancer, the
Bienstock will be in the public subnet and the instances will be in the private subnets to access our
infrastructure, will also take care of the security group and the rules.
And also and key if we need to log into instances which are part of our Bienstock.
But we don't need to create it in multiple steps as we did it in Ansible project, we did first thing.
The second thing, yes, you could have done all the things together in Ansible as well.
But the complexity is too much there.
So we divide it into multiple phases.
But in TerraForm, it's going to be much easier to automate these things.
Also, it's not just about automation.
It's also about maintaining the state of the infrastructure, as I keep repeating that.
So there are no varieties of tools in the market to automate cloud computing tasks, but I think in
today's market, terraform is one of the best cloud automation tool.
Also, if you have used cloud formation, you know, it will be similar, but confirmation is very specific
for eatables.
But you can use terraformed to do other things as well.
You can use other cloud providers and there are other kinds of automation that it supports.
So let's get started now.