59장. GitLab CI에서 AWS로 배포하는 방법

 

 

## CLI 이용시 - Jar 파일 곧바로 Elastic Beanstalk 업로드 불가 (S3 활용 필요)

 

 

=================================

 

Now, we have mainly deployed a job application and it's running into a w cloud infrastructure, but

our goal of automation is to avoid any manual interaction.

So we need to figure out a way how we can deploy our job application in the cloud directly from catalepsy.

In order to do that, we have to follow a few steps, and the first thing that we need to understand

is that all the services, all this cloud services that we are trying to use in this case with the offer

tools that enable automation.

So Awista provides tools that allow you to interact with the services directly from your console.

One of these tools is the IWC ally.

So as the name implies, it doesn't have a graphical interface.

You can only use it by, of course, using the CLIA command line interface.

So this is what will use Enghelab.

Additionally, as we are creating an artifact.

It's not possible directly to upload this artifact to a W.S. when it comes to the service Elastic Bienstock

one that we have to use another AAUW service, a WASC three, which stands for simple storage service.

You can think of it like Dropbox for the cloud.

And actually as a fun fact, Dropbox actually uses a W.S. S3 in order to store your files if you're

using it.

So what we need to do is the following, using the eight Seelie, we need to upload the artifact, the

jar file to S3, the storage service from Awassa, and now we're using the IWC alive.

We're going to instruct Elastic Bienstock to take the artifact that we have just uploaded to S3 and

to deployed in our production environment.