From the course: AWS DevOps: Continuous Docker Deployment to AWS Fargate from GitLab

What you should know

From the course: AWS DevOps: Continuous Docker Deployment to AWS Fargate from GitLab

Start my 1-month free trial

What you should know

“

- [Instructor] There's a few things that you'll need to follow along with this course. An AWS account with root or administrator privileges. Now if you're installing GitLab onto an on premise server with Ubuntu already installed, you can adapt most of these instructions to suit your needs, but you will need to already know how you are going to point your domain at your local server, since this can involve dynamic IP addresses, opening up ports on your firewall or router, and a bunch of other scenarios specific to your local network. So you would need a little web hosting knowledge on setting up and running your own server. You'll also need administrative access to a domain name that you can use. I will be using the sample domain, simpleemailservice.org, for this course, but you will need your own domain name with the ability to add new DNS records to your domain. You will also SMTP outbound mailing credentials if you want GitLab to be able to send emails to your users. You can use Amazon Simple Email service or Mailgun or SendGrid or any number of cloud based outbound email servers. If you are installing GitLab on premise, you can use an SMTP server on your network, but you will need to give GitLab an SMTP server name and login credentials during the configuration video. Okay, great. Now, there's a few things you should know before getting started. Our sample application is a Docker container and we're going to store the Docker image in GitLab using the GitLab container registry. So if you're new to Docker, I would recommend checking out another course in the catalog just to get familiar with the basics of Docker. You can still follow along with this course, but I'm not going to go into a lot of detail about the Docker commands that we'll be using. We will also build a pipeline in GitLab that'll automatically deploy our container to Fargate. If you haven't used Elastic Container Service, I would recommend checking out another video on running containers on AWS. You can still follow along, but if you want to know more about task definitions and ECS services, check out one of those videos that introduces ECS. You will also need to know a few basics about how Git repositories work, but you can still follow along as I type out the commands. And this course assumes that you've already done a first pass of GitLab and you've decided to use it in production with your actual development team. If you're completely new to GitLab and would like a walk through of its features and how to navigate its user interface, I would recommend checking out the other courses that we have that introduce GitLab. We will walk through the entire setup of GitLab, but once it's up and running the other courses will go into more detail about how to actually use GitLab and its various features.

Contents