►
From YouTube: GitLab Runner and AWS Fargate Driver: Speed Run
Description
In this video I show how to setup GitLab Runner and the GitLab AWS Fargate driver for executing CI jobs on AWS Fargate.
https://docs.gitlab.com/runner/configuration/runner_autoscale_aws_fargate/index.html
A
A
Yes,
specifically
installed
to
get
that
runner
when
AWS
ec2
instance,
configuring
and
running
the
editors
Fargo
driver
and
start
the
AWS
pocket
driving
for
the
custom
executor
create
ECS
task
definition,
which
will
mean
obviously
for
running
or
containers
on
foggy
and
then
finally
wrap
up
with
a
quick
demonstration
of
a
test
pipeline,
one
that
will
be
executing
online
container.
That
was
created
at
one
time,
a
tabular
small-game,
the
auto
scaling,
FM
CI
solution
or
even
respond.
A
Give
me
actually
least
that
in
May
12
at
1,
0
release
and
their
ashes
and
enhancements
coming
as
well
and
feature
releases.
So
thought
was
of
the
temptress
to
a
quick
speedrunner
Kenobi,
don't
quick
overview
of
the
setup
and
processes
and
this
I
get
put
into
in
terms
of
how
it
works.
As
you
can
see
in
this
diagram
here,
no
documentation
for
MPC
implementation
of
this
solution.
A
We
are
using
an
ec2
instance
on
AWS
to
host
get
that
better,
the
actual
binary
and
we
needed,
if
that
were
a
fun
gate
driver
and
then
that
solution
is
what
I'm,
using
a
double
spawn
gate
for
creating
containers
and
to
executing
your
CI
jobs
in
the
future.
Is
your
ratio
of
this
video
will
probably
cover
using
a
doubly
respond
gate
to
also
host
a
runner
as
I'm?
An
offender
is
going
to
be
an
interesting
link
here.
A
What
about
poster
was
put
together
that
I
wasn't
that
colors
that
deployment
parents
will
probably
cover
the
next
speedrun'
I'm
sure
the
documentation
that
steps
that
we
will
be
going
through
today,
actually
cover
it
in
our
auto-scaling
at
Pepsi
and
in
a
bit
fun
get
dance
which
is
spawned
here
and
our
webinar
on
dark
science.
It
ducks
ok
club
that
calms,
that's
runner,
I
mean
go
to
configure
and
then
you'll
see
the
link
here.
A
A
So
the
first
thing
that
we
need
to
do
is
run
this
command
and
all
the
commands
in
the
morning
here
are
again
covered
in
detail
in
the
configuration
Docs.
You
can
see
one
here.
There
depends
so
many
the
set
of
commands
you're
running
to
go
ahead
and
get
the
AWS
they'll
get
that
minute
driver
the
gift
everyone
configured
along
with
a
driver
on
it
or
maybe
a
of
us.
So
that's
the
first
step,
given
your
I
just
created,
and
then
the
next
step
we're
gonna
to
go
ahead
and
fill
in
the
packages
that
we
need.
A
A
I'm,
brilliant
so
once
that's
complete
the
next
step,
as
any
Canadian
announces
that
we
will
register
to
get
that
runner
and
if
you'll
recall
the
registration
status.
What
connects
the
get
that
runner
all
that
that
you
set
up
at
two
installs
with
agate
lab
project
in
your
own
get
live
instance.
So,
in
this
case,
I'm
connected
to
a
project
library,
have
cell
phone
get
lab,
calm
and
so
I'm
gonna
run
the
gift
that
run
a
register
command.
A
A
Guess
it's
good
enough
times,
I
think
I
just
say
no
js'
for
now.
Let's
leave
it
at
that,
and
the
next
step
here
is
in
the
final
step
is
asking
for
the
executor.
We
want
to
use
custom
because
we'll
be
configuring,
the
gift
that
wanted
to
use
the
customers
that
gets
drunk
right.
So
now
that
successfully
done
you
move
on
to
the
next
step,
which
we
just
want
to
need.
A
quick
edit
of
the
clip
that
gonna
complete
that
tunnel
file.
A
A
A
A
Another
thing
that
you
need
to
enter
here
is
your
farm,
a
cluster,
so
in
my
example,
I'm
just
going
to
put
the
top
over,
so
you
can
have
up.
You
can
see
it
visually.
It's
great
and
easy
us
I'm
going
to
be
using
this
foggy
question.
Just
calling
a
testify
mate.
So
I'm
gonna
tell
the
farm
gate
driver,
that's
the
cluster
I'll
be
using
on
ACS.
In
my
case,
it's
you
as
the
s2
and
you'd
also
want
to
enter
your
subnet.
A
Your
sudden
idea,
stacks
definitions
and
so
on,
in
this
case,
I'm
just
going
to
change
the
task
definition
just
for
the
example,
because
I
actually
want
to
set
up
and
the
easiest
a
definition.
So
let's
call
this:
that's
genius,
I!
Guess
it's
a
little
bit
ago,
I
wouldn't
even
have
already
has
said
and.
A
So
this
stage
the
foggy
driver
is
ready
to
go.
The
other
thing,
I'm
listening
to
quickly
do
a
pop
over
and
over
and
ECS
and
stability
create
a
task
definition
so
who's.
The
went
through
a
very
simple
example
here
in
terms
of
creating
a
task
definition,
so
you
can
get
a
feel
for
how
simple
is
and,
of
course
all
of
these
definitely
spun
on
AWS.
You
can
certainly
automate
I'm
the
focus
of
this
video
we're
just
kind
of
doing
it
manually.
So
you
can.
A
A
We
have
a
role
that
I
have
in
mind
every
step
down:
east,
yes!
Well,
the
south
side
is
really
up
to
you
in
terms
of
you
know,
kind
of
how
much
compute
and
men
you
think
you
need
for
the
patinas.
There
will
be
executing
your
senior
jobs
on
on
on
AWS
one
day,
I'm
consistently
around
these
settings
and
see
which
or
the
performance
impacts
are.
A
A
So
the
continuing
that
who
wouldn't
let
me
need
to
use-
and
this
is
expected
by
the
finally
drivers-
cement
coordinator
here
and
say
what
do
you
things
are
between
two
to
allow
SSH
relations
and
and
then
the
last
step
that
didn't
want
to
put
in
here
is
the
Reaper
fully
in
the
repository
for
for
your
container
I
happen.
I,
don't
I'm,
not
mistaken.
I
have
a
copy
of.
A
A
You
know
it
create
any
other
task.
Definition
is
done
so
now.
At
this
point,
you
have
the
basic
building
blocks
to
use
this
configuration
that
we
have
described
here,
which
is
an
ec2
instance,
this
hosting
the
fun
runner,
along
with
the
family
driver,
and
then
it's
able
to
use
a
diverse
farm
gate
to
spin
up
a
bill
container
really
fast.
A
Okay.
So
at
this
point
itself,
so
with
those
couple
of
very
straightforward
steps,
you
have
not
able
to
experiment
with
and
use
a
diverse
farm
gate
to
to
learn
and
execute
your
C
on
jobs
and
get
that
I
also
have
a
quick
look
at
how
that
works.
Red
looks
like
a
reality,
so
I'm
gonna
go
back
to
Ava
dress.
A
So
look
at
the
questions
you
know:
I
have
a
clusters
where
you
go
and
you
look
at
distance
so
like
on
this
either
in
my
learner's
test
form
a
cluster
I'm
there
in
the
running
time,
everything's
mentioned
on
what
I'm
gonna
do
on
this
side
was
just
basically
keep
up
a
pipeline.
This
particular
projects
only
been
configured
to
use
in
run
and
that's
cryptogram
on
AWS,
but
I'll
go
to
file
new
driver.
So
just
gonna
learn
that
pipeline
and
we'll
see
what's
happening.
It's
a
pipelines
run
and
let's
keep
refreshing
the
screen
over
here.
A
It's
already
kicked
up
the
time
so
here
in
the
Long's,
the
active
bombs
you're,
seeing
it
to
be
clearing
the
customer
tickets
driver
I'm
over
here
being
abused
in
the
cluster
the
times
definition
that
we
have
prepared
previously,
it's
it's,
no
launching
that
task
or
that
containment,
and
so
obviously,
with
this
manner.
But
definitely
this
model
is
that
you
only
be
using
resources
on
a
diverse
farm
gate
when
you
initiate
a
CI,
build
a
CI
job,
and
so
there's
a
little
bit
of
a
slang.
A
few
seconds
I
would
have
noticed
a
few
seconds.
A
Obviously,
in
terms
of
that
tasks
that
I
take
is
spinning
up
and
then
once
that
going
when
that
gets
going
and
then
the
the
CI
Bojan
is
running.
So
you
can
see
here
that
now
things
are
executing
with
from
the
container
the
continuum
as
you
look
over
here,
AWS
DCs,
fine,
attach
the
running,
is
active
and
over
here
and
get
the
magnets
running
some
very
basic
tests
and
a
very
simple
test.
Job.
A
And
once
this
drum
is
running,
obviously
to
continue
or
the
tasks
in
need
of
a
responding,
it
will
continue
to
be
active
as
well
doctor
no
over
here.
My
left
concern.
You
can
see
that
as
Jeb
succeeded
and
all
the
way
here
inform
you
that,
given
a
moment-
and
it's
go
back
to
the
password-
it's
already-
it's
officially
decommissioned
that
particular
task.
So
now
the
task
that
was
spun
up
to
execute
your
C
on
job,
that's
asked,
there's
no
more
active
and
final
gate.