Welcome to 'Back to Basics'. I'm Nelli Lovchikova.
In this episode, we will show you how to deploy your static web page.
Static web pages are great if you want to tell the world about your business,
present an idea about a brand new software as a service startup,
landing page, or even a blog.
Let's talk about what skills you will need to build a web page
and bring it out to the world.
You'll need to have at least a bachelor's degree in Googling.
Also, understanding HTML and CSS would be an advantage.
Some JavaScript,
watching any JavaScript tutorial could be a sufficient start.
So you created your perfect web page
and uploaded it to an S3 bucket with enabled hosting feature.
Then you realize it's not that great.
Then made a change, zipped and uploaded it again,
and again, and again.
This is annoying. Let's automate.
In AWS, it is really easy to set up a deployment pipeline,
this AWS CodePipeline - an orchestration service.
It commands other services what to do.
You may have noticed we also have a test environment.
Let's talk about this beast.
Think about having a place where you can safely deploy,
ensure everything is working as expected,
and it is not your main web page
where actual customers are trying to do their 'customer' activities.
Sounds good, right?
This place is a test environment.
Now, you can definitely have another S3 bucket in the same account.
However, having a separate account significantly improves the security profile
and provides a nice isolation between environments.
Adding more accounts doesn't cost anything,
but the resources with them do.
You may even have a development environment
so you can play with all this cool editable services
as far away as possible from production.
Now you definitely can have another S3 bucket in the same account.
However, having it in a separate account
significantly improve your security profile
and provides a nice isolation between environments.
All these S3 buckets, maybe CloudFront and the pipeline are
constantly evolving and growing.
How do you keep track of that?
How do you keep making sure your environments are the same
so you can play and innovate?
In AWS, you can describe all the resources in a file, deploy quickly,
and have the same resources configured in the same way
in any environment you want.
It's called infrastructure as a code.
There are options for how to do that.
But if you actually manage to complete the JavaScript course,
you can graduate to the Cloud Development Kit - CDK -
which supports not only JavaScript,
but also Python, TypeScript, Java, C-Sharp
and we're adding more languages.
Here is an example for configuring an S3 bucket
with CloudFront distribution.
With those tools, all of your configurations live in a source control
and you have a history of who did what.
Now you can chase people who did that weird thing and ask them why.
In this episode,
we explored how to deliver your static web page,
how to set up an environment for experimentation,
what is infrastructure as a code,
why and how to use it.
Check out the links below. Happy building.