►
Description
Updated version of this getting started video: https://youtu.be/kGZyAEVioWg - Kong Gateway with Kong Manager GUI
In this video, Kong Developer Advocate, Kevin Chen, will walk you through adding a Service, adding a Route to the Service and adding Plugins, such as key-auth.
Install Kong: https://konghq.com/install/
Join the Kong Community: https://konghq.com/community/
Read the full written guide with screenshots on our blog: https://konghq.com/blog/set-up-kong-gateway/
View the complete Kong Gateway documentation: https://docs.konghq.com/
A
A
A
A
Second,
you
want
to
make
sure
you've
started,
calling,
after
installing
in
to
check
I'm
gonna,
make
a
quick
request
to
the
port
8000,
a
1
which,
by
default,
is
where
the
Kong
admin
API
sets.
You
can
see.
The
response
status
code
is
200
telling
us
that
Kong
is
indeed
up
or
running
with
that
we're
ready
to
start
the
guide
in
this
QuickStart
guide.
You'll
be
adding
an
API
to
Kong.
In
order
to
do
this,
you'll
first
thing
to
add
a
service.
That
is
the
name
Kong
uses
to
refer
to
the
upstream
api's
and
micro
services.
A
A
A
A
A
As
we
stated
earlier.
Having
a
service
is
not
enough.
You
also
need
a
route
for
that
service,
so
let's
go
ahead
and
now
create
a
new
route
for
our
service.
Once
again,
we're
gonna
make
a
post
request
to
the
admin
API
to
create
a
new
route.
We're
gonna
be
hitting
the
example
service,
which
we
created
earlier
right
here
and
then
we're
gonna
hit
the
routes
endpoint.
For
that
example,
service.
A
We're
also
going
to
specify
the
host
headers
of
example.com
and
if
we
press
create
response
status
code
of
201
again,
which
is
great,
was
created
and
a
bunch
of
information
here
now
that
we
have
a
route
and
a
service
we're
ready
to
proxy
a
request
through
column.
So,
let's
issue
a
curl
command,
but
this
time
we're
gonna
be
using
the
port.
8000
note
that
by
default
called
handle
proxy
request
on
port
8000
8000.
One
is
just
for
the
admin
API
to
configure
in
the
Gateway.
A
Awesome
we
see
in
a
successful
response,
which
means
Kong
is
now
forwarding
request
made
to
localhost
port
8000
to
the
URL
we
configured
back
in
step,
one
which
is
the
Mokpo
api.
If
we
make
the
same
request
again
and
this
time
we
just
strip
out
the
header
you'll
see
that
we
have
a
static
code
of
200,
which
means
success,
successful
request
its
proxy
via
column
1.3.
So
you
can
see
the
version,
and
you
can
also
see
how
much
latency
the
column
proxy
is
adding
to
a
request.
A
We
have
to
issue
the
following:
curl
request:
once
again:
we're
going
to
be
utilizing
the
admin
API
to
create
a
plug-in,
and
this
time
we're
just
going
to
be
hitting
the
service
of
example,
service,
which
we
created
and
the
plugins
route
and
saying
that
we
wanted
add
a
plug-in
called
key
off.
So
we
go
ahead
and
make
that
request.
A
So
now
that
you've
configured
key
our
plug-in,
you
can
see
how
quickly
you
can
secure
any
services
that
you
might
have
sitting
in
your
behind
your
call
gateway
the
power
of
this.
Is
you
don't?
You
cannot
specify
the
plug-in
to
one
service
or
you
can
specify
to
a
whole
route
we're
going
to
specify
for
an
entire
gateway.
This
gives
you
that
granularity
of
choosing,
which
plugins
go
we're
giving
you
more
control
over
your
micro
services
for
our
next
step.
We're
gonna,
configure
the
key
off
plug-in
and
learn
how
you
can
add
consumer
to
your
service.
A
So
now
we
can
continue
to
proxy
requests
through
Kong.
So
let's
go
ahead
and
create
a
consumer.
Do
the
restful
api
once
again
utilizing
the
admin
API
we're
gonna,
be
hitting
the
consumers
endpoint
this
time
and
adding
consumer
named
Jason.
So
we
go
ahead
and
we
see
a
2
a
1
created
Jason
is
created
with
an
ID.
This
idea
will
be
important
later,
so
the
next
step
is
to
provision
key
credentials
for
a
consumer
and
to
do
that.
A
As
you
guessed
we're
going
to
be
using
the
admin
once
again
and
this
time
we're
gonna
be
making
it
a
poster
class
through
the
consumer
to
Sasha
Jason
Saskia
end
point-
and
here
you
see
that
in
the
data
it
says
four
key
in
the
entry
key
here.
This
is
where
you
enter
the
ID
that
you
see
in
Jason's
response
code
response:
Jason,
sorry!
So
if
we
go
ahead,
do
that
you'll
see
that
it
was
created
successfully.
That
means
Jason
now
has
the
the
credentials
necessary
to
make
the
request.
A
So
if
we
go
back
and
make
the
request
to
port
8000
one,
we
still
keep
the
host
header,
which
example.com,
but
now
we
have
to
add
additional
field,
which
is
the
API
key.
So
we
take
the
key
for
Jason
and
we
plug
it
in
right
here
now
you
see
the
request
starts
to
work
again.
We
can
strip
the
body
and
just
look
at
the
header
and
we
get
eggs
response
of
200
just
like
that.
A
Thank
you
for
tuning
into
our
five
minute
QuickStart.
You
can
find
a
lot
more
information
on
our
kong
documentation
page
here.
It
is
docs
kong,
HQ
comm.
If
you
have
any
additional
questions
that
our
documentation
doesn't
answer
or
you
just
want
to
talk
with
the
community,
please
do
not
hesitate
to
check
out
our
kong
nation
page.
It
can
be
found
here
at
discuss,
call
HQ
comm.
Here
you
can
ask
questions
or
answer
questions.