►
Description
Ryan Niksch (AWS) and Thatcher Hubbard (Red Hat) explore how customers are further modernizing their application workloads on OpenShift by complimenting them with native AWS services. See how the Amazon Controller for Kubernetes can be integrated with Red Hat OpenShift service on AWS (ROSA) to help shift to the left.
Learn more at: https://go.aws/3z0R84L
Subscribe:
More AWS videos - http://bit.ly/2O3zS75
More AWS events videos - http://bit.ly/316g9t4
ABOUT AWS
Amazon Web Services (AWS) is the world’s most comprehensive and broadly adopted cloud platform, offering over 200 fully featured services from data centers globally. Millions of customers — including the fastest-growing startups, largest enterprises, and leading government agencies — are using AWS to lower costs, become more agile, and innovate faster.
#redhat #openshift #redhatopenshiftserviceonaws #rosa #AWS #AmazonWebServices #CloudComputing
A
B
A
Cloud
right,
you
see
Legacy,
so
that
ties
in
very
nice
neatly
with
my
problem
today.
For
the
last
eight
years,
I've
been
talking
to
customers,
everybody
has
this
desire
for
greater
agility
to
move
faster
than
modernizing
their
businesses.
One
piece
of
that
modernization
is
moving
towards
adopting
a
container
solution,
changing
their
development
strategy,
and
then
they
move
their
workloads
into
that
environment.
It's
typically
open
shift.
A
Nowadays,
it's
modernizing
to
a
more
managed
approach,
so
managed
openshift
on
AWS,
it's
the
red
hat
openshift
service
on
AWS
called
Rosa,
but
then
customers
come
to
me
and
they
they
take
that
next
step
of
evolution
right.
How
do
I
take
native
AWS
services,
so
the
AWS
services
that
are
built
from
the
ground
up
to
be
scalable,
resilient,
secure
and
managed
for
me
and
and
how
do
I
take
advantage
of
those
to
complement
the
workloads
I
already
have
in
openshift
and
automatically
I'm
thinking
things
like
databases,
queuing
mechanisms,
no
SQL
environments,.
A
A
A
That
they
see
they're,
typically
interacting
with
either
kubernetes
directly
or
they're,
using
some
sort
of
manifest
file
that
they
are
pushing
into
that
openshift
environment.
What
one
way
to
do
this
would
have
this
person
go
into
an
AWS
console
stand
up
an
AWS
service.
Rds
is
an
example,
then
come
back
to
openshift
and
create
services
and
bindings,
and
it's
a
very
clunky
and.
B
A
B
Installing
it
no
it's
more
of
a
Gateway
that
allows
you
to
interact
with
the
AWS
API,
but
using
sort
of
this
kubernetes
native
yaml
that
you
are
already
used
to
so
you
know,
most
people
who
use
ocpe
or
kubernetes
are
familiar
with
a
deployment
capital
D
after
installing
ack.
The
correct
controller
is,
you
could
refer
to
a
bucket
capital
B,
that's
an
S3
bucket
or
a
table
capital
T,
which
is
Dyno
ODB
table.
B
B
B
Right
so
you
know
as
an
example,
let's
use
RDS
very
common.
You
would
post
a
chunk
of
yaml
that
defined
a
DB
instance
object
to
the
kubernetes
API.
The
API
itself
would
validate
that
request
and
then
it
would
hand
it
to
the
controller
that's
running
and
it's
the
controller's
job
to
translate
that
into
calls
to
the
AWS
API
so
native.
B
When
that,
assuming
that
that
succeeds,
that
the
you
know
the
correct
permissions,
are
there
and
we'll
talk
about
that
in
a
minute
here.
The
controller
will
then
inject
a
secret
back
into
the
requesting
namespace
that
contains
the
connection
string.
So
you
know
hostname,
endpoint
and
credentials
to
talk
to
that
RDS
instance
and
allowing
you
then,
to
consume
that
that
information
in
other
pieces
of
the
solution
that
you've
built
so
whether
it's
a
deployment
or
a
service
connect
those
up.
A
So
there's
a
couple
of
things
that
you
mentioned
over
there
inside
openshift
there's
a
few
constructs.
There
are
the
built-in
Secrets
inside
openshift
we're
going
to
take
the
information
and
if
you
talk
about
RDS,
we're
talking
about
the
RDS
database,
end
point
that
would
be
one
piece
of
information.
The
IAM
credentials
needed
to
authenticate
to
that,
so
those
would
be
stored
inside
openshift
as
secrets
and
by
applications
would
be
able
to
is
binding.
The
correct
word.
A
A
We
also
have
this
context
of
a
kubernetes
service
or
an
open
shift
service.
I
typically
use
them,
for
you
know,
user
accounts
or
credentials
that
I'm
linking
to
my
applications.
So
if
my
app
needed
to
interact
the
RDS
I
may
create
a
service
for
that,
and
these
are
internal
to
open
shift,
whether
it's
managed
or
self-managed.
A
Dv
table
and
these
objects
exist
in
the
AWS
account.
They
don't
exist
inside
openshift
we're
connecting
from
my
application
workload
on
openshift
to
those
systems
there.
That
has
an
interesting
benefit
if
I
look
at
it.
What
we've
done
is
we've
now
taken
all
of
the
storage
that
used
to
be
assistant,
storage,.
B
A
A
Sts
capabilities
on
YouTube,
so
the
ack
operator
for
RDS
now
gets
a
policy
specific
to
that
again
least
privilege,
and
we
get
that
credential
rotation
really
taking
the
benefit
of
what
managed
openshift
has
had
for
a
little
while
now
and
bringing
that
into
these.
Each
of
these
operators
and
I
think,
as
we
see
more
and
more
operators
being
created,
whether
for
AWS
services
or
for
other
components
of
openshift.
We're
going
to
continue
to
see
that
least
privilege
that
temporary
so.
B
B
B
B
A
But
what
AWS
and
red
hat
are
doing
is
that
are
gradually
adding
in
more
and
more
surface
support
and
as
it
manifests
in
ack,
these
are
appearing
inside
openshift
inside
the
operator
Hub,
as
a
growing
list
of
AWS
services
to
complement
your
workloads
right
Thatcher
is
always
fantastic.
Having
you
here,
fun
discussions
great
to
be
here
with
you.
Thank
you.
Thank
you
all
for
watching.