►
From YouTube: Expose Lambda functions without an AWS API Gateway
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
So
we
have
a
way
to
expose
these
Lambda
functions
directly
through
our
glue
platform
Gateway
and
bypassing
the
AWS
Gateway
or
AWS
API
Gateway.
If
you
use
eks,
you
don't
really
need
to
do
what
I'm
going
to
do
right
now,
which
is
deploying
this
Amazon
pod
identity
web
hook,
but
here
I'm,
basically
using
kind
clusters,
so
I
need
to
add
this
component
insert
manager
and
so
on,
so
that
I
can
allow
some
of
my
pods
to
talk
to
these
Lambda
functions.
A
So
you
can
see
here
there
will
be
the
platform
team
that
will
be
normally
responsible
for
click,
creating
a
cloud
provider
in
the
management
cluster
and
telling
you
which
account
ID.
That
needs
to
be
exposed
to
the
application
teams
which
region
and
if
also
they
want
to
enable
Discovery,
for
example.
A
So
you
can
create
what
we
call
Cloud
resources
manually
so
that
you
can
Define
the
functions
that
people
are
able
to
use
or
you
can
just
enable
discovery
which
is
essentially
what
we
are
doing
at
this
moment
now,
if
I
enable
Discovery,
then
I
need
to
allow
this
management
server
in
the
management
cluster
to
also
talk
to
the
AWS
API.
To
get
information
about
available
functions
in
Lambda
or
Lambda
functions
so
I'm
doing
this
here
and
if
I
go
ahead
and
wait
for
a
few
seconds.
A
So
now,
if
I
want
to
Route
some
traffic
over
to
one
of
these
Lambda
functions,
it
becomes
very
easy
and
I
can
just
as
a
user
as
an
application
owner
I
can
create
a
route
table
and
say:
if
there's
traffic
sent
to
this
slash,
Lambda
prefix,
then
I
want
to
not
send
traffic
to
a
pod
in
my
cluster,
but
instead
I
want
to
forward
this
traffic
to
this
Lambda
function,
which
is
called
Workshop
Echo
I.
Don't
want
to
do
any
transformation,
so
I
just
want
to
get
the
whole
output
from
the
Lambda
function.
A
A
What
is
happening
is
that
you
don't
really
want
to
return
the
raw
payload
from
the
functions,
because
what
is
happening
is
you
normally
get
this
whole
payload
and
the
AWS
API
Gateway
is
using
it
to
extract
the
header
from
the
payload
that
needs
to
be
returned
to
the
end
user,
on
the
body
or
of
the
body.
So
here
so
there
is
some
transformation
that
is
actually
done
by
the
AWS
API
Gateway.
A
And
if
you
want
to
replace
the
AWS
API
Gateway,
then
you
need
to
make
sure
the
same
Transformations
are
done
by
the
gloop
platform
Gateway.
So
what
we
need
to
do
in
that
case
and
what
we're
going
to
show
in
the
second
example
is
we
are
going
to
use
a
node.js
Lambda
function
that
returns
this
response
with
the
status
code,
these
headers
and
some
data
in
the
body
in
the
format
that
is
expected
by
the
AWS
API
Gateway.
A
Then
we're
going
to
update
our
route
table
to
send
the
traffic
to
this
function.
But
If
You,
observe
here
we
want
to
have
the
default
response
transformation,
which
means
we
want
to
transform
the
response
in
the
same
manner
that
the
AWS
API
Gateway
is
doing
it.
So
now,
if
I
send
my
request
here,
I
can
see
that
I
just
get
this
body
instead
of
getting
the
raw
response.
A
A
The
that
has
returned
this
different
data
in
this
Json
payload.
So
we've
extracted
this
data
from
this
payload
and
effectively
transformed
it
in
the
same
way
that
the
AWS
API
Gateway
would
transform
it.
You
can
even
apply
some
extra
transformation
and
so
forth,
but
the
key
idea
here
is
to
show
you
that
you
can
easily
replace
the
AWS
API
Gateway
by
using
our
Gateway
without
having
to
change
anything
for
the
end
user.