►
Description
In this Kong Konnect tutorial, you'll learn how to get started with Konnect and manage your API ecosystem from a single, easy-to-use interface. Learn more about Konnect and start a free trial: https://bit.ly/3vDuUBz
We'll cover how to use Konnect Runtime Manager to set up your own Kong Gateway instance in Docker (1:00). Then we'll walk through how you can expose, secure and manage your first service using the Konnect ServiceHub (2:22). Lastly, we'll publish that API to our developer portal and show how you can share that documentation with your users and developers all within Konnect (9:20).
Now your developers can focus on what really matters: building the functionality that powers your business.
Read the full tutorial blog post: https://bit.ly/3yi6PlR
Contact us if you have any questions as you’re getting set up: https://support.konghq.com/support/s/
Once you’ve set up Konnect, you may find these other tutorials helpful:
• Implementing Client Credentials With Kong and Okta: https://bit.ly/3eJd62p
• Getting Started with Kong Mesh and Open Policy Agent: https://bit.ly/3o8Cq4U
• Protect Your APIs With Kong Konnect and Fastly (Signal Sciences): https://bit.ly/3ogiVr1
#APIGateway #APIs #Konnect
A
Hey
everyone:
my
name
is
Adam
Bauman
I'm,
a
Solutions
engineer
at
Kong
and
I'm,
going
to
show
you
how
easy
it
is
to
get
up
and
running
with
the
Kong
connect
manage
control
plane
all
through
a
single
easy
to
use
interface.
What
we're
going
to
do
is
walk
through
how
to
set
up
a
runtime
instance
in
your
local
machine
using
Docker,
we're
going
to
then
create
a
new
service
expose
that
service
secure
it
and
do
some
management
of
it
through
the
con
connect
service
Hub.
A
Finally,
we're
going
to
publish
your
API
to
a
developer
portal,
so
you
can
easily
share
your
documentation
and
allow
developers
to
try
out
your
newly
created
service,
all
right,
let's
get
started
so.
The
first
thing
we
need
to
do
is
set
up
some
runtime
instances
in
our
local
machine
in
order
to
proxy
traffic
for
the
services
and
the
routes
that
we'll
be
setting
up
later
to
get
started,
go
to
the
connect,
UI
and
click
on
the
runtime
manager.
Tab
in
the
left
hand
navigation.
A
A
You'll
see
the
list
of
runtime
instances
we're
just
getting
going
so
there
shouldn't
be
any
runtime
instances
in
here
yet,
but
let's
go
ahead
and
click
the
new
runtime
instance
button
I'm
on
a
Mac
OS
system,
and
so
I'll
just
leave
this
as
Mac,
but
you
can
follow
along
on
Windows
or
Linux,
or
if
you
want
to
start
with
any
of
your
Cloud
providers,
you
can
feel
free
to
click.
One
of
those
I've
got
a
Gateway
instance
here
of
the
latest
version
of
Kong.
A
A
The
next
step
is
to
generate
a
script.
We
come.
We
build
this
pre-configured
for
you
with
some
base,
Kong
configurations
so
that
you
can
have
your
local
instance
connect
to
connect
to
be
able
to
to
manage
configurations
I'm
going
to
go
here
and
run
this
in
my
terminal,
and
it
will
go
in
start
up
the
the
con
Gateway
proxy
and
connect
back
to
the
connect
portal.
As
you
can
see,
there's
a
new
runtime
instance.
A
A
So,
in
order
to
do
that,
we're
going
to
go
to
the
service
Hub
tab
in
the
left
hand,
side,
and
you
can
see
I-
have
some
Services
already
set
up
here,
because
I've
been
working
with
my
organization,
but
you
may
not
have
anything
here.
So,
let's
get
started
by
clicking
the
service
package
button
in
the
upper
right
hand,
corner
I'm
just
going
to
give
this
a
generic
name,
and
you
can
leave
the
description
blank
for
now.
A
It's
not
required
once
clicking
save
you'll
have
the
options
to
create
a
service
version
at
Kong
we
use
semantic
versioning,
so
I'm
just
going
to
create
this
one
as
1.0.0
and
the
runtime
group
is
already
set
to
default.
Again,
you
probably
only
have
the
default
runtime
group,
so
you
can
just
leave
that
as
is
and
click
create.
A
And
we
have
an
upstream
URL
of
swagger
pet
store.
An
upstream
URL
is
really
the
backend
service
that
you're
going
to
be
connecting
to
that
will
serve
the
data
and
it
would
be
your
application
either
internally
or
in
this
case,
we're
using
an
external
URL
I'll
leave
the
rest
of
the
settings
as
default
and
go
on
to
creating
a
route.
A
The
routing
is
really
important
here,
because
this
is
what's
going
to
actually
handle
the
traffic
and
figure
out
what's
coming
in
and
which
service
it
needs
to
connect
to
so
I'm
going
to
do
a
simple
service.
That's
available
in
my
Upstream
I
can
name
this
whatever
I
want
I'm
going
to
leave
the
protocols
HTTP
https,
because
I'm
just
doing
a
restful
call
and
I'm
going
to
set
a
route
of
pet
store.
A
What
this
is
doing,
that
any
requests
that
come
into
our
Gateway
and
hit
pet
store
will
then
be
routed
to
the
Upstream
service
again
leaving
the
rest
of
the
fields
the
default
Fields
as
they
are,
I'll
click
create,
and
now
we've
actually
got
an
implementation
of
our
service.
That's
exposed
now
that
we've
created
and
exposed
our
service
to
the
outside
world.
We
need
to
start
considering
security.
One
common
concern
is
overuse,
whether
it's
either
malicious
or
accidental.
That
could
severely
degrade
the
performance
of
your
Upstream
service.
A
So
in
order
to
prevent
that
we're
going
to
add
a
rate
limited
plugin
from
the
service
version,
let's
go
to
add
plugin
button
and
filter
down
the
selection
of
plugins
that
you
can
get
through
Kong
to
rate
limiting.
There
are
several
options
here:
let's
just
choose
the
base
one,
it's
the
most
simple
to
get
set
up
and
running,
there's
a
few
options
here,
but
let's
stick
to
most
of
the
defaults
but
I'm
going
to
set
a
limit
of
10
calls
per
minute.
A
It's
not
really
a
real
world
example,
but
it's
something
we
can
use
for
testing
purposes
in
this
video
I'm
going
to
save
that
plugin
and
then
go
over
to
my
design,
debug
and
testing
tool
called
insomnia.
You
can
see.
I've
got
a
connection
to
my
local
environment
here
under
that
pet
store
service
and
I'm
going
to
make
a
call.
A
This
is
really
powerful
because
we're
doing
that
at
the
API
Gateway
layer
and
not
at
the
backend
service,
so
you're
removing
the
requirement
for
the
developers
to
implement
this
kind
of
logic,
and
you
could
do
it
at
a
higher
level
through
the
Kong
rate,
limiting
plugin
with
our
surface
protected.
Now
it's
time
to
increase
the
performance.
A
We're
going
to
do
this
by
caching
responses
from
the
Upstream
service
only
in
the
Kong
Gateway,
eliminating
the
back
and
forth
between
the
Gateway
and
the
service,
as
well
as
reducing
load
on
the
Upstream
service.
To
do
this,
we'll
use
our
proxy
cache
plugin
same
way.
We
added
the
rate
limiting
plug-in,
we'll
go
to
the
plugin
hub
and
look
up.
A
Caching
and
we'll
select
the
base
proxy
caching
plugin,
because
it's
easier
to
configure
for
the
most
part
we'll
keep
all
of
the
settings
the
same,
but
we
are
going
to
specify
using
the
caching
strategy
of
memory
we'll
save
this,
and
now
we've
got
caching
enabled
to
show
this
in
action.
We're
going
to
again
go
to
our
insomnia
tool
to
hit
the
endpoint
that
we
have
stored
in
our
local
cache
if
we
hit
send
again
we're
getting
the
200
okay
and
it's
important
to
notice
the
Upstream
latency
here.
A
A
Before
we
expose
our
service
to
the
external
Dev
portal,
we're
going
to
make
sure
it's
secure
by
using
key
Authentication
and
consumers
to
uniquely
identify
who's
accessing
the
API
and
control
the
data.
That's
sent
back
to
them.
We'll
do
this
in
the
same
way,
we
added
the
other
plugins
click,
add
plugin
here
and
search
for
key
Authentication.
A
A
A
And
click
save
now
that
we
have
our
new
consumer,
we
have
to
create
an
API
key
for
them.
You
could
do
this
by
going
to
the
credentials
Tab
Key
authentication
in
this
example,
because
that's
the
plugin
that
we
enabled
we'll
create
a
new
key
credential.
You
can
leave
this
one
blank
because
we
want
to
Auto
generate
this
key,
go
back
to
the
key
authentication
and
we
can
copy
that
key.
A
So
now,
as
you
can
see,
we've
added
Authentication
to
this
endpoint
to
secure
it
and
only
allow
specific
consumers
to
be
able
to
call
it
and
get
data
back
from
our
service
with
our
service
secure.
The
final
step
is
to
publish
our
service
to
our
externally
facing
developer
portal
so
that
other
developers
can
consume
our
newly
created
API.
A
In
order
to
do
this,
you
need
to
have
an
open,
API
specification
file.
I've
created
a
simple
one,
to
match
up
with
the
steps
we've
taken
in
this
article,
and
it
will
include
the
basic
service
information,
the
paths
to
get
to
the
newly
created
routes,
as
well
as
some
API
key
authentication
tags
that
will
allow
you
to
use
those
API
keys
in
your
developer
portal.
A
With
this
created,
we
can
go
back
to
our
connect
manager,
go
down
to
the
service
Hub
tab
on
the
left
hand,
side
and
select
our
my
new
service
that
we
created
earlier
in
the
tutorial.
We
have
our
version
1.0.0
that
is
currently
unpublished
in
this
screen.
You'll
see
a
lot
of
information,
but
what
we're
going
to
do
right
now
is
go
to
the
version
spec
section,
which
is
in
the
bottom
right
and
upload
that
file
that
we've
created
I'm
just
going
to
grab
that
one
here
upload.
A
As
you
can
see
right
away,
you
get
a
brief
preview
of
what
it
will
look
like
from
the
specification
in
the
developer
portal.
Next,
we'll
need
to
actually
change
the
status
of
this
version
to
be
published.
If
you
go
to
the
upper
right
hand,
side
select,
the
actions
drop
down
and
edit
version
status
you'll
see
several
options.
A
Currently,
this
one
is
unpublished
but
we'd
like
to
publish
it.
So,
let's
select
that
option
and
click
save
before
your
new
service
is
available.
Through
the
dev
portal,
you
will
have
to
publish
the
service
to
the
dev
portal
itself.
By
going
to
my
new
service
actions.
In
the
top
right
and
clicking
publish
to
portal,
once
that's
done,
you're
now
published
and
if
you
go
over
to
the
dev
portal
section
in
the
left
hand,
side
you'll
see
the
my
new
service
created
with
one
service
version
1.0.0,
which
is
the
one
we
created.
A
If
you
now
go
to
the
link
for
The
Connect
portal,
URL
you'll
be
taking
into
the
developer
portal
I'm
already
logged
in
here,
but
you
may
have
to
log
in
or
sign
up
with
a
new
account
in
order
to
act
as
a
external
developer.
But
you'll
see
that
my
service
tab
here
is
is
linked
with
the
latest
version
of
1.0.