►
From YouTube: Overview AWS Quick Start for Cloud Native Hybrid on EKS
Description
Table of Contents:
00:00 - Overview:AWS Quick Start for GitLab Cloud Native Hybrid on EKS
00:05 - Quick Starts are Production Grade IaC
02:32 - GitLab AWS Quick Start Specifics
04:02 - Touring the Quick Start Guide
06:05 - The Quick Start Launch Form
07:24 - Implementation Patterns Deploy Now
08:35 - Resources
08:48 - Contact Information
Resources:
- Explainer Video: Overview of GitLab AWS Implementation Patterns: https://bit.ly/3lpGwpZ
- GitLab AWS Implementation Patterns for GitLab Cloud Native Hybrid: https://bit.ly/3xhyJww
- AWS Quick Start for GitLab Cloud Native Hybrid on EKS: https://bit.ly/3lej9j4
Play Lists:
- Learning to Provision the AWS Quick Start for GitLab on EKS (https://youtube.com/playlist?list=PL05JrBw4t0Koi8VBnoVhmj_MstnbJjGw5)
- GitLab and AWS (https://youtube.com/playlist?list=PL05JrBw4t0Ko30Bkf8bAvR-8E441Fy2G9)
- GitLab Alliances Tech (https://youtube.com/playlist?list=PL05JrBw4t0KqaWCrU4avIY6TQveKTDMso)
- GitLab Reference Architecture, Cloud Native, Performance Testing, Scaling and HA (https://youtube.com/playlist?list=PL05JrBw4t0KqgVugqCld2fUvrBulanchq)
- GitLab and Kubernetes (https://youtube.com/playlist?list=PL05JrBw4t0Kqp16k3nHTMdrWdATrcDZ5C)
- DarwinTheorizes at GitLab (https://youtube.com/playlist?list=PL05JrBw4t0KoH74CcAtP0Ze7JXjX7zT6g)
A
First,
I
want
to
explain
what
quick
starts
are
because
they're
really
cool
gitlab
happens
to
have
a
quick
start,
but
amazon
does
quickstarts
for
all
kinds
of
technology,
and
so
it's
kind
of
a
proven
platform
that
they
use
to
deploy
all
kinds
of
technology,
so
quick
starts,
are
based
on
partner
best
practices.
So,
in
this
case,
gitlab's
the
partner
with
aws
aws,
gets
together
with
a
partner
and
makes
sure
that
whatever
is
being
built,
is
built
to
the
partners
best
practices.
A
They
are
production
grade.
So
they
even
though
they're
called
quick,
starts
they're,
not
meant
to
be
toys,
they're,
actually
tested
in
many
regions.
They
result
in
a
working
version
of
whatever
the
partner
software
is
and
whenever
upgrades
are
made
to
the
automation,
there's
a
very
full-featured
ci
cd
that
tests
the
deployment
in
multiple
regions
again
before
it's
allowed
to
be
released
to
production
and
replace
the
existing
quick
start.
They
have
to
be
highly
available.
A
A
lot
of
software
can
be
implemented
in
amazon
in
ways
that
are
highly
available
or
not
and
get
labs
the
same
way
to
be
a
quick
start.
The
partner
software
has
to
be
implemented
as
highly
available.
They
meet
aws
well
architected
guidelines
automatically
because
that's
a
requirement
of
being
a
quick
start.
If
you
had
say
a
single
instance
as
a
particular
feature,
it
would
have
to
be
in
an
asg
that
would
auto
spawn
a
replacement
if
that
was
to
terminate
for
any
reason,
so
they
have
to
follow
well
architected
principles.
A
There
is
a
dependency
library
out
there,
so,
for
instance,
the
gitlab
one
depends
on
the
aws
eks
quickstart,
which
has
already
had
a
fairly
rich
and
mature
history
and
has
a
lot
of
cool
functionality
in
it.
One
of
the
examples
in
that
case
is
the
bastion
host
that's
built
in
for
doing
your
eks
administration.
So
you
don't
have
to
open
up
a
public
endpoint,
that's
built
right
into
that
quickstart,
so
we
inherit
that
same
capability
inside
of
gitlab
and
they
result
in
a
working
application.
A
So
the
intent
is
that
when
it's
done
running,
there's
not
a
whole
bunch
of
manual
wire
up.
That
remains
to
be
done.
For
the
gitlab
side,
some
of
the
get
lab
things
that
we've
kind
of
contributed
to
the
mix
here.
We've
made
sure
that
this
is
a
reference
architecture
compliant
so
amazon's
the
one
who
seeded
this
automation
to
start
with
and
when
they
came
to
us,
we
had
to
do
some
work
to
make
sure
that
it
was
reference
architecture
compliant
at
the
time
we
started
with
this.
A
We
have
started
with
the
implementation
patterns
for
aws,
so
that
complementary
kind
of
documentation
orientation
that
gives
you
easy
to
plug
in
numbers
for
the
quick
starts
implemented
as
git
lab
highly
available.
They
are
performance
tested.
So,
from
the
gitlab
side,
we
are
performance
testing
any
of
the
implementation
patterns
that
we
promote
to
be
used
as
input
to
the
quick
start,
have
ongoing
documentation
and
enablement
support
through
videos
how
to's
and
that
kind
of
stuff.
A
So
this
really
works
really
well
together.
It's
a
well
proven
model
from
the
amazon
side.
If
you
go
to
the
quick
starts
website,
you
will
see
hundreds
of
titles
for
enterprise
grade
software
and
when
you
deploy
with
a
quick
start,
you
have
a
working
application
version
that
you
know
meets
the
best
practices
and
well
architected
principles
of
both
amazon
and
the
partner
company,
and
then
of
course,
as
I
mentioned,
we
have
the
implementation
patterns,
specifically
the
bill
of
materials
that
can
be
pumped
right
into
the
into
the
quick
start.
A
A
The
quick
start
guides
have
a
certain
format
of
this
page.
So
it
goes
through
a
lot
of
information
about
the
quick
start
before
you
get
down
to
brass
tacks.
As
far
as
deploying
it
so
it
here
we
talked
about,
and
I
helped
with
this
documentation,
but
we
spend
some
time
helping
folks
understand
that
you
can
use
this
as
a
service.
Catalog
item
also
control
tower
reuses
cloud
formations
that
can
potentially
be
reused
there
as
well.
A
It
talks
a
little
bit
about
the
open
source
community
talks
about
how
gitlab
on
aws
should
be
done
and
as
we
go
through
here,
we
find
the
architecture
diagram.
So
if
you're
wondering
how
this
is
architected,
this
diagram
gives
you
a
sense
of
what
is
going
on
in
the
background
and
we're
going
to
zoom
down
here
a
lot
of
background
information
on
data
encryption.
That's
inside
of
this
quick
start
database
information,
repository
storage.
A
We
also
have
information
about
the
gitlab,
telemetry
and
monitoring.
So
cloudwatch
is
fully
enabled
in
this,
including
container
insights,
which
means
that
performance
markers
from
containers
as
well
as
gitlab
logs,
are
collected
so
that
you
can
so
you
don't
lose
any
of
your
gitlab
logging
if
you're
trying
to
do
troubleshooting,
even
though
you're
using
containers
a
little
more
information
about
console
outputs
and
then
planning
the
deployment.
A
So
some
of
the
things
to
think
about,
as
you
sit
down
and
try
to
go
to,
deploy
this
and
then,
as
we
come
down,
it
tells
you
the
resources
that
are
required.
So
if
you're,
a
fresh
amazon
account,
then
you're
going
to
be
fine,
but
if
you're
in
an
account
that's
being
used,
there
are
certain
quota
usages
that
this
will
use
up.
A
A
A
This
and
we'll
see
if
I'm
logged
in
already
I
am
logged
in.
If
I
wasn't,
I
would
have
been
prompted
to
log
in
and
then
I
would
have
hit
this
screen
if
you're
familiar
with
cloudformation.
This
is
a
quick
create
screen.
So
there's
only
one
screen,
not
the
normal
three
of
cloud
formation.
When
you
load
your
own
template
within
here,
you
go
in
and
fill
in
all
of
the
information
I'm
going
to
have
a
completely
different
video
that
actually
steps
through
this.
A
I
want
to
point
out
one
more
thing
that
we
skipped
over
here.
Inside
of
the
implementation
patterns.
We
have
a
section
called
deploy
now
and
what
we've
done
is
simply
primed
the
values
with
what's
in
this
particular
pattern
below
so
I
mentioned
that
you
have
to
pick
your
own
values
when
you
launch
this.
Let
me
right
here,
so
you
have
to
tell
it
that
says
t3
large
right
now,
but
if
I
click
this
link
here
instead.
A
Instead
of
saying
t3
large,
it's
going
to
prime
it
with
whatever
is
in
the
below
list,
so
this
doesn't
set
all
the
parameters
you
still
have
to
go
through
and
verify
the
other
parameters.
Besides
the
number
of
availability
zones,
the
instance
types
and
the
number
of
instance
types.
So
if
we
go
down
here,
we
now
have
c5
4x
large
and
we
want
nine
of
them.
A
Some
value,
we're
trying
to
add
here,
is
simply
priming
all
the
numbers
from
this
bill
of
materials
below.
So
you
have
literally
one
click,
fill
in
the
details
that
don't
have
to
do
with
instances
and
numbers
of
instances
and
click
go
and
launch
it
and
we'll
be
doing
that
on
a
separate
video,
so
just
quickly
some
resources
that
will
also
be
posted
to
the
youtube
description,
so
you
can
click
them
directly.
These
are
also
just
pages
that
we've
been
going
through
already
and
then.