►
Description
Kong Konnect provides developers and API owners a powerful way to secure and manage their API products powered by Kong Gateway (the world's fastest API gateway).
Leverage Konnect to manage Kong Gateway data planes operating on-prem and in the public cloud – either as a centralized APIOps platform or federated experience across business units.
Ultimately, Konnect enables customers to reduce their operational costs by using our hosted runtime manager, service catalog, developer portal and analytics platform.
A
And
so,
thanks
to
all
of
you
who
are
joining
us
today,
my
name
is
dalia
espacer
and
I'm
part
of
the
developer
marketing
team.
Here
at
kong
and
I'd
like
to
welcome
you
all
to
our
august
user
call.
Today
we
have
a
special
presentation
for
you,
coming
from
smriti
and
samantha
as
they're
going
to
talk
about
simplifying
production
scale,
api
management
with
conconnect,
let's
reserve
all
the
questions
at
the
end
of
the
presentation.
Please
put
them
in
the
q,
a
function
at
the
bottom
that
you
see
and
we'll
answer
them
at
the
end.
A
If
you
wish
you'll
be
able
to
mute
yourself
and
ask
the
question,
if
you
want
that
way
and
with
that
before
we
begin,
I
actually
have
a
few
things.
I
would
like
to
mention
I'm
sure
that
most
of
you
have
seen
or
already
on
social
media,
but
we
have
our
yearly
event.
Kong
summit
coming
up
in
september
on
september,
27,
28
and
29
in
san
francisco.
It's
gonna
be
an
in-person
event.
What
I
would
like
to
mention
is
very
cool.
A
This
year
we
have
four
free
training
courses,
so
we
have
kong
gateway,
foundations,
mesh
foundations
for
kubernetes
foundations,
and
then
we
also
have
connect
training
and
next
to
that
this
year,
we're
also
doing
a
virtual
hackathon
and
it's
opening
up
on
september
1st,
if
you'd
like
to
participate,
please
go,
you
can
see
the
link
here,
konghq.com
summit,
slash,
hackathon
and
register
there,
the
five,
the
top
five
contributions
will
earn
prizes
and,
of
course,
everyone
will
earn
a
unique
t-shirt
that
be
designed
specifically
for
the
hackathon,
but
please
check
out
the
webpage
for
more
information
how
to
participate.
A
B
Hi
everyone.
Thank
you
so
much
for
joining
us.
I
am
just
going
to
share
my
screen
here
in
the
thank
you
for
joining
us
for
the
august.
2022
connect
user
call
with
smriti
jagi
and
myself.
B
I'm
a
group
product
manager
here
at
kong
and
smithy,
is
a
product
manager
overseeing
the
runtime
manager,
we're
going
to
be
jumping
into
a
connect
overview
today
and
doing
an
end-to-end
journey
as
well
as
actually
demoing.
Some
of
our
newest
features.
B
Con
connect,
sas
api
management
platform
makes
this
transition
seamless
by
providing
those
out-of-the-box
api
capabilities
which
ultimately
improves
developer
communication
and
knowledge
sharing
and
ensures
the
reliability
for
both
cloud
native
and
legacy.
Workloads,
one
of
our
core
capabilities
is
runtime
management,
which
offers
a
sas
delivered
control
plane
for
kong
gateway
data
planes,
so
instead
of
every
business
unit
or
team
needing
to
deploy
a
database,
a
gateway,
admin,
api
and
a
kong
manager,
users
can
simply
make
an
api
call,
with
the
click
of
a
button
to
launch
a
control
plane
through
connect's
integrated
management
interface.
B
So
what
you're
going
to
see
here
is
that
data
planes
which
process
your
customer
traffic
run
entirely
in
your
network.
So
you
never
actually
have
to
worry
about
the
data
leaving
your
control
and,
on
top
of
the
world's
fastest
gateway
and
streamline
runtime
management.
We
also
offer
a
set
of
sas
apps
that
provide
additional
value
to
your
organization.
So
take
you
on
a
quick
overview
of
what
those
are
and
that's,
where
you're
going
to
see
here
in
the
global
management
plan,
so
quickly.
B
B
Your
runtime
manager
is
part
of
the
control
plane
that
allows
you
to
see
the
various
locations
your
kong
gateways
are
deployed.
We
actually
call
these
your
runtimes
and
then
enable
you
to
group
those
runtimes
according
to
internal
business
units
such
as
billing
or
procurement,
or
you
can
group
them
by
different
environments,
maybe
like
production
or
staging.
B
B
We've
got
vitals,
also
known
as
analytics,
and
these
are
your
macro
and
micro
insights
to
some
of
the
golden
signals
of
your
api
business,
which
include
throughput
and
error
rate
visible
at
both
the
service
and
runtime
level.
We've
also
baked
in
some
custom
reporting
functionality
that
enables
our
users
to
gain
further
insights
around
those
services.
C
Thank
you
so
much
sam
hello,
everyone,
my
name
is
pretty
and
let's
talk
a
little
bit
about
what
you
know
with
a
real
life
example.
What
is
it
that
we
that
an
end-to-end
user
journey
would
look
like
within
connect?
So
for
our
example,
today
we
are
looking
at
a
pet
store
which
has
an
online
presence,
so
it
has
grooming
services
where
you
could
book
and
look
for
appointments.
It
has
different
products
that
you
could
purchase
for
your
pets
and
that's
kind
of
what
we
are
going
to
reference.
C
So
there
are
four
key
personas
or
teams
that
we
are
going
to
talk
about
in
today's
call.
So
the
first
one
is
a
platform
team
which
is
typically
your
centralized
it
teams,
and
they
you
know
they
will
set
up
your
runtime
environments.
They
define
the
initial
internal
deployment
policies,
they
create
runtime
instances
within
the
runtime
group.
They
leverage
connect
teams
and
permissions
to
ensure
that
everyone
has
the
right
access,
be
it
an
individual
person
on
an
individual
team.
We,
when
everyone
has
received
their
proper
access.
C
We
are
looking
at
some
micro
services
teams,
such
as
your
groomings
appointment
booking
services
or
your
pet
supply
services
that
will
register
all
of
these
services
onto
the
connect
platform
and
create
implementations
for
this
within
service
hub.
These
implementations
will
define
how
their
services
can
be
mapped
to
a
gateway
to
process
traffic.
C
All
of
the
platform
team
can
have
visibility
to
these
services
and
all
of
the
traffic
that's
flowing
through
connect
through
our
vitals
portal
or
our
analytics
portal,
and
so,
with
this
connect
platform,
actually
realizes
two
pillars
of
the
con
product
portfolio,
which
is
running
and
governing
apis.
C
So
I
think,
with
this
sam,
let's
dive
right
into
our
demo
and
walk
everyone
through.
You
know,
through
the
connect
platform.
As
I
share
my
screen
here,
I
would
urge
everyone
to
try
out.
You
know
the
connect
platform
with
us
and
kind
of
take
advantage
of
all
the
features
that
it
provides.
B
Here
and
while
smarties
pulling
that
up
I'll
just
highlight
that
you
can
access
your
free
connect
user
account
by
going
to
konghq
dot
com
and
signing
up
for
that
account.
B
We've
got
some
great
docs
that
go
along
with
it,
as
well
as
an
awesome
community
online
that
can
answer
any
questions
and
then,
of
course,
this
user
call
is
being
recorded.
So
if
you
want
to
come
back
and
reference
anything
that
we
go
over,
you
can
certainly
do
that.
C
Perfect,
so
let's
go
and
see
what
our
registration
looks
like.
So
you
can
access
this
page
on
dot
com,
slash
we're
going
to
put
this
link
in
the
chat
as
well,
and
it's
a
simple
registration
form.
All
you
need
is
you
know
a
couple
of
details,
I'm
going
to
sign
up
through
kong
and
add
my
details
here
and
just
generate
a
password
agree
to
the
the
legal
requirements
of
the
privacy
policy.
C
There
you
go
once
you
confirm
your
email,
you
will
have
access
to
your
connect
account,
and
so
let's
I'm
gonna
go
to
an
account
that
I
already
have
access
to.
So
I
can
show
some
cool
features
within
connect.
C
So
let's
start
talking
a
little
bit
about
the
login
itself.
So
for
the
login
experience
we
have
two
options.
So
I'm
going
to
go
into
my
identity
management
either
I
could
use
a
octa-based
sign-in
to
my
oitc
or
I
could
sign
in
using
connect's.
You
know
username
password,
so
just
to
show
you
what
that
looks.
Like
I've
set
up
octa
on
my
organization,
I
can
simply
say
login
through
sso
using
the
octa.
You
know
credentials
that
I
have
stored
in
the
in
my
octa
profile.
C
C
Let's
talk
a
little
bit
about
the
organization
itself.
Connect
provides
certain
default
themes
that
people
can
take
act.
You
know
advantage
of
so
you
have
the
org
admin
portal,
admin,
portal,
viewers,
etc.
These
are
teams
that
have
predefined
access.
So,
let's
you
know
go
into
one
of
these
groups.
We
have
a
runtime
admin.
I
can
see
that
they
have
predefined
roles
for
creating
editing
and
deleting
runtime
groups
in
the
runtime
manager.
We
cannot
modify
the
permissions
for
these
or
groups
because
these
are
provided
by
default.
C
But
if
there
are
you
know
requirements
for
you
to
have
a
more
custom
based
permission
rules,
we
do
have
an
option
to
create
teams,
so
I
can
add
a
new
team.
I
can
enter
a
name
and
description,
so
let
me
say
if
this
is
a
test
team,
I
can
create
the
team
and
then
I
can
add
members
to
this
team.
I
can
add:
what
kind
of
services
do
I
want
to
give
roles
to
or
what
kind
of
runtime
groups
to
give?
You
know
the
roles
to
this
team?
C
So
let
me
walk
you
through
an
actual
example
for
this.
I
have
a
custom
team
here
that
talks
that
is
called
bookings.
It
is
responsible
for
managing
the
grooming
bookings
for
our
pet
store,
so
they
would
need
you
know
they
would
need
to
get
information
from
our
groomers
about
what
kind
of
availability
they
have
and
then
provide
different
ways
for
our
users
to
actually
book
those
appointments.
C
So
what
I
have
done
here
is
given
them
the
the
access
to
a
groomings
appointments.
C
You
know
service
where
they
can
check
for
what
is
the
available
appointments,
but
I
have
not
provided
them
access
to
our
groomers
data
itself,
because
that
is
an
hr
related
data
that
does
not
need
to
be
present
with
this
bookings
team
that
will
provide
the
the
separation
that
is
needed
where
the
team
can
function
with
the
data,
but
they
don't
have
access
to.
C
You
know
even
accidentally
modify
that
information,
and
so
I
can
add
members
here
if
you're
using
octa,
you
can
do
that
through
your
idp
directly
and
add
members
if
you
are
using
connects
internal
login
systems.
You
can
just
add
your
team
members
here.
You
can
invite
users,
you
know
through
through
your
users
tab.
You
can
simply
say
invite
user,
their
name,
email
address
and
what
kind
of
team
you
want
to
invite
them
to.
C
There
is
also
a
way
for
us
to
leverage
something
that's
called
a
personal
access
token,
so
this
is
mostly
to
use
for
when,
when
you're
building
any
kind
of
automation
or
using
apis
or
deck,
which
is
our
declarative
platform
for
accessing
connect,
you
could
simply
use
a
token
rather
than
using
your
username
and
password
it's
pretty
simple.
You
can
generate
a
token
here.
I'm
going
to
call
this
part
two.
I
can
select
what
kind
of
expiration
I
need
for
this
and
simply
generate
it.
C
There's
going
to
be
a
token
that's
present
here
and
that
I
can
then
leverage
to
all
of
my
you
know
all
of
my
automation
and
api
based
access.
C
I
also
want
to
highlight
one
more
feature,
which
is
the
fact
that
we
have
deployments
in
multiple
regions.
So
we
have
us
and
europe
that
is
available
right
now,
and
so
what
we
have
with
these
regions
is
all
of
the
services
and
runtime
groups
are
restricted
around
a
region
that
they
are
defined
in.
So
if
I
define
a
service
in
north
america,
they
will
not
be
visible
when
I
go
to
europe
and
vice
versa.
The
advantage
for
this
is
we
hit
two
points.
C
One
is
the
data
residency
requirement,
so
this
ensures
that
all
of
your
data
that
needs
to
be
within
a
region-
you
can
define
it
in
that
region
itself
and
it's
not
visible
in
other
regions,
so
there's
a
huge
compliance
benefit
to
it.
The
other
is,
of
course,
on
latency,
so
the
control
plane
is
deployed
in
the
region
itself,
so
it
helps
with
minimizing
the
latency.
So
your
calls
are
not
made
all
across
the
world
just
to
access
data.
C
B
Sweetie
so
hopping
in
to
we're
gonna
hop
into
service
hub,
so
you've
seen
just
to
recap,
you
saw
a
custom
team
being
made
for
a
oh
excuse
me
for
a
booking
service
and.
B
Now,
I'm
going
to
continue
on
that
specific
example
and
let's
say
that
that
team
now
we're
in
service
hub.
So
let's
say,
for
example,
I'm
on
the
services
team
for
grooming
grooming
booking
and
I'm
doing
an
api
first
development,
where
perhaps
I
don't
have
an
available
developer,
but
my
roles
determine
what
we
need
to
build
and
how
we'll
do
it.
B
I
can
always
choose
to
publish
this
to
our
portal,
which
we're
going
to
hop
into
in
just
a
second
and
what
we're
looking
at
here
is
really
a
high-level
view
of
the
service,
the
service,
and
I
can
see
a
total
number
of
requests
count
and
the
failed
requests
that
have
come
in
and
how
many
versions
of
the
service
that
we
have.
So
this
version
might
be
version.
One
might
be
the
one.
That's,
let's
say
in
staging,
for
example,
so
I
can
hop
into
that
version.
I
can
see
my
upstream
url.
B
I
can
see
all
of
the
the
plugins
that
I've
applied.
I've
applied
a
rate
limiting
plug
and
I've
applied
a
key
authentication
plug-in
which
currently
is
disabled,
but
this
is
related
to
the
developer
portal.
I
do
want
to
highlight
here
that
connect
has
a
ton
of
available
out
of
the
box
plugins
that
you
can
apply
to
your
existing
services.
B
Those
are
also
available
on
our
website,
as
well
as
the
ability
to
hit,
add
plugin
and
select
and
choose
from
our
entire
kind
of
portfolio
of
plugins
and
by
digging
in
a
little
deeper
you're
going
to
see
the
yaml
file.
That's
been
uploaded
for
that
api
spec
itself,
as
well
as
version
specific
analytics
that
you're
going
to
see
here
and
as
sweetie
pointed
out
this
service
right
here
is,
you
know.
B
B
Oh
excuse
me:
I'm
com.
Excuse
me,
I'm
just
gonna
change
the
change
the
topic
there,
but
I
am
in
north
america
and
I'm
seeing
my
services
that
are
running
on
my
cloud
environment,
that's
associated
with
my
region
and
that's
going
to
support
the
compliance
through
data
residency
as
well
as
improve
latency.
So
that's
what
I
did
want
to
highlight
there
around
north
america,
I'm
going
to
hop
in
to
dev
portal
here
and
just
take
you
on
a
little
bit
of
a
tour.
B
I
can
see
my
published
services,
so
we
already
did
point
out
that
in
the
grooming
appointments
that
that
service
is
published
to
the
developer
portal,
the
developer
portal
allows
for
full
customization.
So
I
can
see
all
you
know
at
a
glance
the
background
colors,
the
text
colors,
etc.
We
also
have
some
very
exciting
things
coming
down
the
pipeline
for
additional
customization
for
dev
portal,
but
some
new
things
I
do
want
to
highlight
here:
we've
simplified,
creating
and
generating
a
custom
portal
url.
B
B
I'm
actually
going
to
hop
into
the
portal
itself
and
show
you
a
little
bit
about
the
portal
in
action,
and
I'd
also
want
to
highlight
that
we've
not
only
applied
the
single
sign-on
to
connect
itself,
but
we've
also
done
that
at
the
portal
level.
So
we
can
log
in
here
with
sso
and
I'm
going
to
go
ahead
and
do
that.
B
B
B
So
I've
gone
ahead
and
set
up
a
custom
report
for
everyone,
but
I'm
going
to
go
ahead
and
hit
edit
and
so
that
we
can
see
kind
of
what
that
looks.
Like
I
can
name
my
report.
I
can
adjust
my
time
frame
of
my
report
and
I
can
select
from
a
variety
of
metric
selections,
I've
chosen
to
understand
total
traffic
by
status
code
because
I
specifically
want
to
understand
what
type
of
400
errors
are
coming
in.
B
So
if
I
go
and
hop
into
this
report
itself,
I
can
now
see
that
I'm
getting
quite
a
bit
of
149
errors.
Now
this
is
related
to
that
rate,
limiting
plug-in
that
I've
applied
to
this.
I
applied
it
to
not
only
my
grooming
appointments,
but
in
this
particular
scenario
I
am
looking
at
my
pet
purchase
service,
so
pet
supply
purchase
service.
B
So
what
that
means
is
that
perhaps
on
my
pet
store,
I
have
a
bunch
of
supplies
that
people
can
shop
for
directly
on
the
site
and
there
might
be
other
websites
that
go
ahead
and
scrape
that
information
well
to
protect
my
website
and
to
ensure
that
my
service
can
always
be
available
for
those
who
are
coming
to
my
local
website.
B
I've
applied
that
rate
limiting
plug-in
to
minimize
the
number
of
calls
those
other
third-party
websites
can
do
to
my
site,
and
you
can
see
that
that
rate
limiting
plugin
is
working,
and
that
is
our
analytics.
It's
a
quick
overview
for
there.
So
on
that
note,
I'm
going
to
actually
go
ahead
and
pass
it
on
back
to
sweetie
to
overview
our
run
time
and
deck.
C
Perfect,
thank
you
so
much
sam.
I
am
going
to
share
my
screen
one
more
time
and
let's
talk
about
the
runtime
manager.
Now
people
generally
think
about
with
our
you
know,
on-prem
kong,
to
have
you
know
in
order
to
separate
their
different
environments,
they've
usually
gone
on
the
path
of
installing
standalone
instances
of
kong
on-prem.
C
What
we
did
here
as
sam
mentioned
during
during
the
introduction
is
we've
provided
a
way
for
customers
to
have
that
logical
separation
between
environments
or
even
between
business
units
within
the
runtime
manager
itself
would
which
minimizes
the
need
for
our
customers
to
set
up.
C
You
know
standalone
instances
of
the
database,
have
people
look
into
the
admin
apis,
have
new
instances
of
cog
manager
for
each
individual
environment
and
instead
leverage
runtime
manager
itself,
where
I
can
create
a
new
runtime
group
with
just
a
click
of
the
button
I
can
add
in
whatever
name
I
want
so.
Let's
say
I
want
to
have
it
for
a
whole
different.
C
You
know
business
unit
such
as
my
pet
supplies
unit,
so
I
can
say
that
it's
a
pet
supplies
is
the
name
of
my
runtime
group
and
I
want
to
say
this
is
for
the
pet
supplies
team
and
I
can
simply
create
my
runtime
group.
I
have
a
limit
of
three:
that's
because
I'm
in
an
enterprise
based,
you
know
tier
for
kong,
kong
connect,
and
so
I
have
a
limit
of
three
runtime
groups
at
this
point.
C
But
this
is
just
how
simple
it
is
for
me
to
add
new
runtimes.
Now
I
have
set
up
my
runtime
groups
in
terms
of
my
environment,
so
I
have
a
default
one.
I
have
a
dev
and
a
prod,
and
with
each
of
these
runtime
groups
I
can,
you
know,
add
in
you
know
what
services
I
need
for
this.
What
kind
of
routes
going
for
for
my
group?
C
We
can
also
see
that
this
meters,
when
I
see
the
routes
it
mirrors,
what
we
have
set
up
in
the
service
hub
itself.
So
this
is
another
way
for
me
to
configure
my
services
and
in
the
runtime
group
itself,
where
I
can
add
a
route
and
associate
that
to
my
service
using
the
gateway
services.
C
So
with
that,
I'm
going
to
hop
in
a
little
bit
into
deck,
which
is
you
know,
which
is
the
declarative
way
for
me
to
access
access,
connect,
I'm
going
to
start
off
with
a
simple
ping
of
deck,
and
there
is
great
documentation
that
we
will.
We
can,
of
course,
reference
to
to
give
you
a
little
bit
more
details
about
each
of
these
commands,
but
with
this,
what
I
want
to
show
is:
how
do
we
even
leverage
our
cli
for
even
connecting
to
to
to
my
connect?
C
So
what
I
have
done
here
is
I'm
just
simply
pinging
deck
to
a
runtime
group,
and
I
I
have
saved
the
value
of
the
default
runtime
group
here
and
I'm
using
my
credentials
to
ping
it,
and
then
we
will
see
that
it
has
successfully
pinged
it
now.
As
you
remember,
we
had
two
regions
available
within
our
connect
platform.
One
was
an
eu
region.
C
C
We've
made
that
distinction
by
adding
a
new
flag
called
connect
addr,
wherein
I
can
send
in
the
send
in
the
api
address
it
is
by
default
for
the
us
api
with
the
flag.
I
can
change
it
to
any
other
region
that
I
want,
and
you
can
see
that
I
have
successfully
connected
as
pretty
even
to
my
eu
region.
C
C
So
let
me
get
my
my
command
here
and
then
to
a
deck
dump
of
the
runtime
group.
Through
my
credentials
it
is
saving
it
in
the
in
a
file
called
kong.yaml.
So
I'm
going
to
move
that
to
my.
Let
me
just
open
that
kong.camel
here
and
what
you
can
see
here
is.
C
C
I
can
see
all
of
the
different
configurations
for
it.
I
can
also
see
my
rate
limiting
plug-in
and
then
I
can
see
that
it
is
enabled
for
true.
I
have
set
a
a
threshold
of
900
requests
per
minute
and
I'm
limiting
that
by
ip
address.
So
all
of
this
good
information
is
available
within
this.
It
has
a
tag
to
which
service
it
is
connected
to.
C
So
we
are
connected
to
the
grooming
appointment
service,
which
is
where
we
are
making
sure
that
we
have,
you
know,
rate
limits
available,
so
it
is
available
not
just
in
grooming
service,
but
also
in
our
pet
services,
but
I
can
modify
all
of
the
plugins
as
I
need.
It
shows
me
what
path
is
available.
You
know
where
I
am
accessing
my
my
route,
so
it
has
all
of
this
good
information
now.
C
One
thing
that
that
is
really
cool
here
is
that
I
can
make
modifications
to
my
yaml
file.
Do
a
deck
sync
command
and
it
will
automatically
sync
it
in
the
ui
itself.
So
let
me
go
ahead
and
make
that
make
make
those
adjustments
in
my
file.
So
let
me
move
the
kong.yaml
to
my
desktop,
so
I
have
easy
access
to
it.
A
C
Hang
on,
while
I
get
my
screens
in
order,
please,
okay,
I
am
going
to
bring
this
down
so
that
you
guys
can
see
what
I
see.
So
this
is
the
yaml
file
that
I
have.
I
am
going
to
make
a
modification
and
let's
say
I'm
going
to
put
the
rate
limiting
enabled
to
false
I'm
going
to
save
that,
and
then
let's
do
a
deck
sync
command
for
for
this,
and
I
should
be
able
to
see
that
reflected
on
on
the
ui
itself.
C
C
In
a
different
version,
so
I
have
that
in
the
v1
version,
and
you
will
see
that
my
rate
limiting
plug-in
has
now
been
disabled.
So
that's
a
very
cool
way
for
us
to
make
modifications
to
our
to
our
connect
configuration
directly
through
the
cli
command.
C
With
that,
I
want
to
urge
everyone
to
you
know
sign
up
today
for
free
at
kong.cloud.com
hq
dot
com,
slash
register.
You
will
start
off
with
a
free
trial
for
two
weeks
and
you
will
be
able
to
take
advantage
of
all
the
cool
features
that
we
have
there
and
play
around
with
connect,
and
you
know
with
that.
I
want
to
open
up
the
floor
for
any
questions
that
you
guys
may
have
for
us
today.
A
C
Perfect,
I'm
going
to
read
john's
questions
out
question
out
aloud,
so
his
question
is:
what
is
the
expansion
plans
in
india
region
for
the
control
plane?
A
lot
of
clients
are
asking
about
the
data
going
out
of
region,
since
I
believe
currently
it
only
supports
us.
So
that
is
true
that
currently
our
control
plane
is
in
us.
C
We
have
just
added
a
new
region
for
eu
and
we
are
evaluating
what
are
other
regions
that
we
want
to
most
our
control
plane
in,
and
you
know
india
definitely
is
one
of
those
candidates
and
we
can
we.
We
will
be
evaluating
based
on
a
number
of
customers.
What
is
the
next
region
that
we
target.
A
B
Yeah,
I
think
that
absolutely
depends
on
kind
of
what
your
organization
is
in
need
of,
and
that's
one
of
the
neat
things
about
vitals
is
that
you
do
have
that
customization,
but
what
we
call
our
golden
signals
are
throughput,
as
well
as
error
rate
and,
what's
coming
in
our
roadmap
in
the
next
few
months,
is
you're
going
to
start
to
see
latency
as
well,
and
a
bunch
of
other
neat
custom
dashboards,
so
you'll
start
to
see
this
vitals
component
grow
and
that
customization
for
what
the
needs
of
your
organization
are
will
be
available.
B
A
C
So
armored
for
kong
as
an
api
gateway,
you
have
two
options.
You
could
either
do
the
on-prem
for
kong,
which
is
you
know,
getting
the
license
for
calling
api,
sorry
for
the
api
gateway
and
then
implementing
that
on-prem
with
within
your
within
your
infrastruc
infrastructure.
So
what
that
would
need
is
for
you
to
set
up
a
database,
a
postgres
database,
some
admin
apis,
as
well
as
an
instance
of
kong
manager
to
have
that
ui
to
manage
the
api
gateway.
C
That
is
also
a
way
for
you
to
use
deck
and
then
install
your
api
gateway
and
and
kind
of
configure
it
based
on
your
environment.
The
other
way
for
you
is
to
use
kong
connect
to
get
access
to
the
api
gateway,
so
con
connect
leverages
the
enterprise
version
of
the
api,
the
kong
api
gateway
in
as
it's
as
its
data
plane.
So
you
could
register
at
the
cloud.com
hq
dot
com,
slash
register
and
pla
set
up
a
control
plane.
C
So
with
that,
the
data
plane
that
you
would
need
for
the
gateway
will
still
be
in
your
environment.
But
then
you
could
have
a
cloud
hosted:
control
plane
to
configure
configure
your
your
gateways.
B
And
the
mirror
all
of
that
is
also
like
in
our
supporting
docs
as
well.
So
I
definitely
encourage
you
to
reference
that.
So,
after
you
kind
of
let's
say
you
go
the
direction
of
connect
which
you
know
smoothie
and
I
might
be
a
little
biased
towards
connect
because
it's
the
product
we
work
on
99
of
our
time
specifically.
B
But
after
after
you
go
ahead
and
get
that
set
up,
you
know
you'll,
go
and
like
she
said,
install
kong
gateway
onto
your
control,
plane
doing
that
in
runtime
manager,
and
then
you
can
set
up
your
gateway
services
through
runtime
manager.
Or
if
you
want
to
do
that,
api
first
design,
you
can
always
start
at
service
hub
as
a
way
to
kind
of
set
up
that
service
catalog
and
then
set
up
the
gateway
as
service
implementation.
Through
there.
A
All
right,
thank
you,
so
much
smitty
samantha,
thanks
ross
for
being
here
thanks,
everyone
who
joined
today,
we
hope
to
see
you
at
our
next
user
call.
Yeah
have
a
great
evening
great
day,
see
you
soon
bye.