►
From YouTube: Tutorial: Build Your Own Heroku With Cloud... - Muvaffak Onus, & Sidarta Oliveira, Grupo Boticário
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe 2023 in Amsterdam, The Netherlands from April 17-21. Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Tutorial: Build Your Own Heroku With Cloud Native Stack - Muvaffak Onus, Upbound & Sidarta Aguiar de Oliveira, Grupo Boticário
Speakers: Muvaffak Onus, Sidarta Aguiar de Oliveira
Heroku has led the transformational PaaS experience we're all used to today and we still see companies building a variant of that experience in their specific niche. However, while the opinionated nature of Heroku made it a really sound choice for general use cases, everyone knows that they will outgrow it at one point. What if you could build your own Heroku and tailor it to your needs as you grow? With the help of the cloud native stack, we will build a Heroku experience that is fully customizable for your ever changing use cases. By combining Backstage, Crossplane and several other cloud native tools, we will build our platform that can give the Heroku experience to your users consistently while your organization’s needs grow and you accommodate the changes.
A
A
A
So
what
you
don't
get
from
Heroku
and
one
of
the
some
of
the
reasons
that
you
would
not
continuously
get
is
that
they
don't
deploy
stuff
in
your
own
internal
Network
because,
like
you
know
it's
all
in
the
in
their
accounts
and
like
they're,
essentially
a
hosting
service
right,
a
cloud
service
some
extent
and
they
don't
allow
you
to
use
their
own
cloud
accounts
and
complex
applications
developed
by
multiple
teams.
For
example.
A
If
you
want
to
have
like
lots
of
microservices
some
like
Auto
scaling
with
AWS
like
Advanced
scenarios,
essentially
with
more
than
like
you
know,
a
few
Dyno
Dino,
they
call
and
also
like
in
your
own
galleries.
Right.
It's
it's
just
like
the
opinions
of
heroku's
design
are
good,
but
they
don't
work
for
everyone,
especially
the
big
companies
right.
So
what
we
want
to
have
is
a
heroically
that
you
can
customize
more
and
you
can
have
like
you
know
when
you're,
you
cannot
feel
it
under
full
control.
A
So
I'm
gonna
go
through
like
a
few
tools
that
we're
going
to
use
the
first
one
is
cross,
play
right,
so
cross
plane
is
this
tool
that
allows
you
to
build.
Your
own
internal
Cloud
platform
to
provision
Cloud
resources
essentially
and
you
can
interact
with
it,
to
IAC
tools
like
terraform
or
kubernetes
applications
or
CI
CD
pipeline
through
githubs,
because
it's
essential
built-in
kubernetes
API
it
gives
you
it
installs
cids
and
you
can
interact
with
them
with
that.
A
Just
like
all
other
cncf
tools
and
backstage
is
another
cncf
tool
that
allows
you
to
have
a
service
catalog
in
your
company,
and
on
top
of
that
they
allow
you
to
have
a
software
template
concept
where
you
can
click
and
create
a
new
application
like
git
repo,
with
some
of
the
like,
you
know,
presets
and,
like
you
know,
you
can
see
I
see
the
actions
if
you
want
to,
and
then
also
they
have.
This,
like,
you
know
view
of
hey
who
is
owning
this
service.
Where
is
it
located?
A
And
in
a
very
high
level,
this
is
like
a
really
basic
diagram,
but
I.
Think,
like
you
know
the
more
we
go
like
you're
gonna
understand
the
details,
backstage
what
what
we,
how
we
are
going
to
do.
It
is,
like
you
know,
backstage
we'll
have
a
set
of
software
templates.
When
you
request
a
new
service,
it's
going
to
create
a
git
repo
with
all
the
CI
CD
and
then
Argo
CD
will
take
over
to
deploy
and
what
it
deploys
is
both
application
and
infrastructure
and
then
cross
plane
is
going
to
talk
to
cloud
provider.
A
And
yeah
without
further
we
can.
We
can
just
start.
The
tutorial
do
go
to
that
page,
because
there
are
places
where
that
I'll
just
like
copy
and
paste
the
ammo,
because
it's
just
too
long
so
that
you
can,
like
you
know,
keep
an
open
Tab
and
you
can
just
copy
and
paste
the
same
thing
and
also
like
you
know
later,
you
can,
you
can
follow
it.
A
A
A
A
Nice
and
now
I'm
going
to
get
push
your
cool
man
cool,
so
one
experience
that
we're
actually
not
going
to
be
able
to
give
is
this,
like
you
know,
git
log,
because
we're
gonna
use
GitHub.
It
doesn't
allow
you
to
edit
this
will
remote
logging.
It
just
builds
right
when
you
do
the
push
and
deploys
it
we're
going
to
use
GitHub
actions
to
do
to
do
that,
operation
cool.
A
So
if
you
refresh
open
up
yeah
and
now
we're
seeing
the
hello
world,
so
whenever
we
make
a
change,
the
same
thing
happens,
get
push
and
builds
it
and
it
deploys
it.
So,
that's
kind
of
like
you
know
the
Heroku
experience
that
I'm
going
to
like
you
know,
try
to
get
to,
and
additionally
there
is
this
add-ons
concept.
A
Okay,
for
example,
yeah
so
add-ons
is
like
you
know
how
you
add
infrastructure
to
your
heroic
application,
but
for
example,
if
you
want
to
add
a
bucket,
you
can
use
this
bucket
here
and
it
would
like,
you
know,
make
an
environment
variable
available
for
you,
like
bucket
name
and
credentials
to
be
able
to
use
it.
We're
not
going
to
do
that
for
now,
but
yeah.
Now
we
are
going
to
start
to
install
our
tooling
to
our
cluster
I'm.
Just
gonna
copy,
a
bunch
of
code
here
and
it's
going
to
be
a
kind
cluster.
A
And
so
the
the
this
cluster
is
going
to
host
backstage
cross,
plane
and
also
Argo
CD
and
I've.
Just
set
the
namespace,
so
I'm
gonna
I'm
gonna
create
a
backstage
app.
So
backstage
is
a
little
bit
different
than
the
other
two
in
that
it's
actually
a
bunch
of
like
you
know,
libraries
that
allows
you
to
build
your
own
UI
right,
so
it's
essentially
a
typescript
Library
set.
A
A
A
A
A
A
Cool,
so
we
got
that
right,
and
that
is
we
need
to
check
if
it's
so
there's
this
app
config
you've
got
app
config,
local
and
production,
and
this
is
like
you
know
the
core
app
config,
depending
on
the
environment,
these
override
the
main
core,
app
config
one.
For
example,
when
I
run
riyan
Dev
it
uses
this
empty
file,
I'm
going
to
build
an
image
and
deploy
to
kubernetes
Cluster.
It's
going
to
use
this
production
one.
A
So
what
it
does
is
like
in
three
steps
is
like
kind
of
the
base
you
give
it
a
directory
for
scaffolding.
Hey,
like
you
know,
these
are
the
like.
You
know
starting
point
for
my
repo
and
it's
got
some
good
templates
that
it
can
fill
with
users
input
right
now.
We
just
give
like
either
hey.
I
am
the
owner.
This
is
the
repo
address,
but
we
can
explain,
extend
that
and
then
it
publishes
to
GitHub
repository
and
then
it
registers
it
back
to
to
this
instance.
A
A
It's
what
we
confirmed
so
we're
going
to
deploy
this
to
our
kind
cluster.
There's
a
bunch
of
options
here,
but
we're
just
going
to
use
in-memory
DB
and
on
top
of
the
standard,
we're
going
to
add
this
template
option.
Normally
it
doesn't
allow
you
to
add
templates
in
the
UI.
It
has
to
be,
like
you
know,
compiled
in
with
your
application,
but
we're
just
going
to
enable
that
and
add
it
through
the
UI,
so
I'm
going
to
production.
A
And
there's
the
next
step,
we
are
going
to
create
a
secret
that
has
the
GitHub
token
that
we
created
in
the
earlier
step
page.
We
don't
have
to
wait.
Okay,
GitHub
token
is
created.
Okay
image
is
loaded,
so
we're
gonna,
deploy
with
a
like
very
simple,
manifest
it's
going
to
have
like
deployment
one
replica
using
our
image
and
a
service
that
exposes
through
Port
80
and
the
service
account,
which
will
be
useful
later
on
so
I'm
going
to
copy
this
manifest.
A
A
A
A
A
A
A
A
Cool
that's
created,
and
it's
also
need
to
have
the
secret
I
already
have
this
environment
variable
available
for
my
service
account
in
gcp,
I
mean
I,
hope
I
do
but
yeah
cool,
so
the
installation
part
is
done.
I
think
I
hope
so
we're
gonna
have
a
like
simple
hello
world
template
just
like
the
similar.
Just
like
you
know
the
existing
template,
but
with
actual
like
you
know,
some
code
in
it
and
like
from
our
own
template,
GitHub
repo.
A
Git
clone,
so
this
is
going
to
sort
of
like,
for
example,
in
a
company.
This
Reaper
would
be
maintained
by
a
platform
team
because
they
would
kind
of,
like
you
know,
set
the
compositions
like
you
know
what
you
can
do
and,
like
you
know,
the
best
practices
of
languages.
In
this
case
we're
gonna
go
with
node.js
and
let's
initialize
the
repo.
A
So
a
template,
a
scout
like
in
order
to
prepare
a
scaffolding
for
backstage,
you
need
to
First,
create
a
template.
Yaml
that
will
tell
it
like
you
know,
hey,
go
and
take
the
for
example.
In
this
case,
you've
got
some
properties
like
that.
We
will
ask
to
users:
hey:
what's
the
service
name,
who
is
the
owner
of
it
and
then
choose
a
location?
They're
gonna,
like
you
know,
we're
gonna
choose
a
repo
and
then
there
are
steps.
So
these
steps
are
very
familiar.
A
A
B
A
A
Package
Json
and
then
we've
got
our
basic,
simple
hello
world.
So
one
thing
to
to
to
see
here,
like
you
know,
I
I
have
templates
in
actual
code
as
well
like,
for
example,
when
I
create
a
repo
I
expect
this
to
be
replaced
with
service
name
and
owner,
which
is
like
you
know
something
that
we're
going
to
use
in
in
Coral,
Spring
part
of
the
side,
part
of
the
code
as
well.
A
So
I'm
so
I'm
going
to
take
the
URL
of
that
template
yaml
to
import
it
to
Backstage
it's.
It
has
a
really
nice
integration
with
GitHub
that
is
able
to
figure
out
like
you
know
how
to
fetch
anything
from
fromagita
people
and
we
imported
it
and
we
got
it
and
create,
and
you
see
Hello
World
on
kubernetes
our
own.
Our
own
templates
keep
going,
and
you
see
like
you
know
how
many
times
I
had
to
try
so
move
off.
A
A
And,
let's
see
foreign
okay,
of
course
it's
not
https
cool,
so
I,
just
like
you
know,
went
through
like
very
small
cycle.
Very
simple
app,
like
you
know:
hey
I'm,
a
developer
I
just
want
a
hello
world
on
this
specific
language
and
I
created
it
through
templates.
So
this
is
like
you
know,
mostly
just
just
backstage
and
and
backstaging
GitHub
Magic.
A
A
A
A
A
A
The
one
thing
to
notice
here
is
that
this,
like
you
know
notation
without
this,
like
you
know
the
helmet
backstage
would
like
you
know
it
would
Clash
essentially,
for
example,
if
you,
if
you
don't
have
it
here,
then
this
dot
values
but
backstage
would
try
to
interpret
that
and
it
would
fail
because
there's
no,
like
you,
know,
image
attack
in
the
user
input
right.
So
you
put
this
raw
and
Android
at
the
beginning
and
end
of
the
part
where
you
don't
want
backstage
to
touch
it.
A
A
And
yeah
and
our
GitHub
actions
will
will
essentially
be
hey,
like
you
know,
check
out
repo
Docker
build
see.
This
is,
for
example,
this
builds
like
multi-platform
images
right.
You
don't
want
your
developer
to
deal
with
that
at
all
right,
so
we
are
able
to
just
take
that
load
from
them
by
having
it
just
in
the
scale
folder.
A
A
A
A
A
A
A
But
there
is
no
nothing
like
you
know:
hey,
go,
create
a
deployment
or
go
create
anything
and
on
the
cluster,
so
we
I
have
written
this.
Like
you
know,
it's
it's
a
very
simple,
but
I
don't
want
to
go
into
details,
but
this
will.
Let
us
have
the
custom
action
that
will
create
an
Argo
CD
application
as
part
of
the
scaffolding
and
the
reason
that
we
did.
We
don't
do
this
as
part
of
GitHub
action.
Is
that
I
don't
want
GitHub
repo
to
have
access
to
my
cluster,
because
my
cluster
is
kind
clustered.
A
A
A
So
I'm
going
to
packages
and
backhand
here
you
have
the
source
plugins,
and
then
you
got
the
scaffolder.
That's
what
we're
concerned
with
mostly,
and
now
it
doesn't
do
anything
it
just
like
create
router
with
defaults
and
I'm,
going
to
change
it
to
essentially
initially
initialize
the
built-in
actions
and
add
two
actions
from
my
package.
A
So
there's
an
endpoint
called
create
where
we
can
go
and
actually
create
actions
cool.
So
this
is
like
the
list
of
actions
that
are
registered
in
this
backstage
instance,
and
let
me
go
to
the
bottom
yeah.
Our
actions
are
here,
so
we're
cool
all
good
and
in
addition,
our
backstage
service
account
needs
to
have
permissions
to
create
these
ago
CD
applications.
It
doesn't
have
them
by
default.
A
A
And
if
we
push
like
you,
know
different
tag,
then,
like
you
know,
something
has
to
go.
Tell
Argo
CD,
Hey
There.
Is
this
new
version
or
digest?
Let's
change
it
right!
So
there's
a
small
project
called
Argo
CD
image
updater,
but
it
doesn't
quite
work
with
Google
GitHub
container
registry
for
some
reason.
A
A
A
A
A
A
7
create
cool.
Now
we
we
see
our
actions
there
and
while
it's
doing
its
job,
let's
go
to
the
next
step
cross
plane,
which
is
the
part
that
I'm
mostly
excited
about,
and
in
this
part,
we're
going
to
first
without
templates
as
a
platform
team,
we're
going
to
Define
an
API
for
buckets
right
and
it's
going
to
be.
Like
you
know,
it's
going
to
have
only
one
parameter
location
and
we're
going
to
include
it.
A
A
Code,
okay,
so
I
am
going
to
create
a
yaml
for
let's
say
platform.yaml.
This
is
not
going
to
be
interpreted
by
backstage
at
all.
It's
just
I'm
going
to
like
you
know,
keep
still
apply,
but
it
could
be
like
you
can
have
it
in
the
like
single
repo,
keep
going
templates
repo,
but
it
doesn't
have
to
be.
A
Cool
so
so,
as
I
said,
like
I
have
to
apply
them
like
independent
of
any
templating
or
backstage,
or
anything
so
that
environment
Gets,
Ready
in
production,
I
can
use
this
in
depth.
I
can
use
like
Min
IO
composition
right
so
that
hey
I'm,
gonna
I'm
gonna
create
a
crib
hey.
This
is
like
demo
environment,
so
you're
going
to
get
to
a
bucket
with
container,
but
in
production
I
want
you
to
have,
like
you
know,
encrypted
bucket.
A
A
So
we're
creating,
like
you,
know,
Argo
CD
application
targeting
this
chart
that
we
publish,
but
the
chart
had
a
had
the
wrong
version
for
some
reason.
So
we're
going
to
fix
this
in
GitHub,
CI
yeah
there
it
is
I-
was
trying
something
and
I
shouldn't
have
tried
it.
Okay,
so
this
is
also
fixed.
We
got
the
image
chart.
I'll
go
see
the
application.
Our
platform
is
ready.
A
Yeah-
and
this
is
all
my
developer-
needs
to
know
right,
just
a
very
simple
API
with
that
single
parameter
event,
location,
us
and
then
they
are
able
to
give
like
you
know:
hey
publish
your
credentials
to
this
specific
secret
and
what
I'm
going
to
do
is,
like
you
know,
Mount
the
secret
to
my
service,
so
that
when
the
whole
thing
deploys
first
bucket
is
created,
and
then
my
application
comes
up
with
that
credentials
and
it
works
with
the
bucket.
So
this
is
like
you
know:
I
didn't
have
to
give
gcp
credentials.
A
A
And
cool,
so
our
hello
world
application
is
going
to
have
to
change
because,
like
you
know,
we
need
to
interact
with
Google
gcp
bucket.
So
this
is
a
very
small,
so
this
may
be
like
a
really
bad
type
script
code,
because
I'm
not
a
type
script
developer
and
honestly
I
kind
of
hate
it
with
this
yarn
and
npm,
but
just
bear
with
me:
okay.
So
what
it
does
is
essentially
every
30
seconds
it
generates
a
file
uploads
it
and
lists
lists
the
files
all
the
files
from
the
bucket.
A
A
A
The
one
of
the
nice
things
about
crossband
composition
is
that
I
don't
have
to
know
the
composition
to
know
the
secret
like
Keys.
It
is
defined
as
part
of
the
API,
so
we
don't
Define
only
the
parameters
and
Fields,
but
also
connection
secret
keys
that
we
can
use
so
that
we
know
what
to
mount
and
composition
is
responsible
to
populate
those
fields
in
the
in
the
connection
details
so
I'm
going
to
add
here.
A
Register
it
analyze,
cool,
okay,
so
I
think
we're
getting
closer
to
like
you
know
the
like
production
like
platform
right
now.
This
is
like
node.js
application
with
bucket
and
you're
gonna
have
like
go
application
with
something
else
or
in
case
of
like,
for
example,
group
of
folks
have,
like
you
know,
one
application
and
input
as
like
hey.
Do
you
want
RDS
instance?
Do
you
want
bucket?
It's
like
a
really
rich
UI,
keep
going
na6.
A
Yeah,
so,
while
it's
doing
its
job,
this
is
like
kind
of
the
last
step
that
we
showed
the
integration
next
steps
for,
like
you
know
like
where,
where
you
can
take
this
angle
right,
it's
mostly
like
you
can,
for
example,
you
can
make
different
choices
like
githubs
in
githubs
most
of
people.
They
have
a
different
repo
for
deployment
right.
So,
instead
of,
like
you,
know,
Argo
CD
picking
up
from
the
actual
code
repo,
you
can
have
the
GitHub
actions
to
open
a
PR.
A
There
go
through
some
checks
and
then
it
would
update
the
Argo
CD
application
from
the
repo
that
is
used
for
deployment
right.
So
because,
like
you
know
we're
just,
we
just
have
all
these
like
standardized
Frameworks
and
applications
on
kubernetes.
We
can
just
like
you
know,
edit
all
all
parts
of
the
architecture,
and
you
can
use
Argo
CD
image
updater,
which
uses
like
summer
updates
and
everything
which
I
think
is
pretty
cool
project.
Just
didn't
work
for
GitHub
containers
yesterday
and
you
can,
like
you
know,
add
more
input
parameters
right.
A
A
A
A
A
A
It's
got
20
events,
okay,
so
it
has
created.
First,
a
service
account
service
account
key
crypto,
key
and
queuing.
So
the
reason
that
these
are
created
before
the
bucket
is
that
they
are
required
for
bucket
creation,
like
we
have
to
give
the
KMS
key
name
so
they're
going
to
reconcile
and,
like
you
know,
get
up
to
speed
drill
to
apply.
Let
me
see:
what's
the
error
here,
container
Port
required
value.
A
A
A
A
B
A
A
Can
cross-plane
import
existing
infrastructure?
Yes,
the
Crosman
resources
have
a
notion
called
external
name,
which
is
the
way
how
it
identifies
a
resource
in
the
external
API
which
is
like
you
know,
AWS
API,
let's
say
so.
If
you
use
like,
if
you
create
the
ammo
with
external
name
annotation,
and
give
the
VPC
ID
when
you
create
that
it's
going
to
come
up
and
it's
like
it's
going
to
adopt
the
resource
as
if
it
was
the
one
who
created
it.
A
So,
yes,
it
would
be
possible-
and
you
can
do
this
in
scaffolding
as
well
in
composition.
You
can
say:
okay,
like
I'm,
going
to
ask
an
optional
parameter
from
user.
If
they
want
to
use
the
existing
cluster
right
or
existing
RDS
instance
and
in
composition,
they
can
patch
that
external
name
with
that
input
parameter
from
user.
So
when
they
create
a
new
application,
they
can
just
point
to
something
that
that
already
exists.
A
A
A
B
It
working
cool.
We
are
going
to
share
a
little
bit
how
group
about
Chicago
Implement
those
tools
use
the
same
ideas
to
make
our
developer
day-to-day
easier,
with
removing
all
the
complex
that
they
have
to
create
this
CI
CD
and
the
infrastructure
and
the
cloud
resource.
So
first,
who
is
gurupa
bocikaru
is
a
Brazilian
beauty.
Company
with
45
years
of
foundation
is
not
Duty
in
the
cloud
we
have
44
in
Thousand
employees,
we
have
more
than
4
000
stores.
We
have
two
factors
and
eight
distribution
centers.
We
are
a
multi-national
company.
B
B
You
can
go
to
this
care
code
and
have
a
15
discount
on
your
first
purchase,
using
the
cube
15
code
and
our
Market
team
will
be
happy
so
why
you
decide
to
create
our
internal
developer
platform
in
2019.
We
start
a
digital
journey
and
a
lot
of
say,
digital
transformation,
and
we
can
summarize
that
transformation
into
four
pillars.
B
B
We
are
even
moving
how
those
micro
Services
Co
integrate
moving
from
IBM
bus
to
Kafka
and
APG,
and
we
are
moving
from
a
proprietary
stack
to
more
open
source
language
and
because
we
are
moving
to
the
cloud
and
create
a
bunch
of
micro
Services.
We
need
to
give
to
the
developers
the
autonomy
they
need.
So
that's
why
we
start
our
internal
developer
portal
and
basically,
the
main
idea
is
to
make
our
developers
day-to-day
easier.
B
B
B
B
So
basically,
you
already
saw
the
the
backstage
interface,
so
I'm
not
going
to
deepen
the
technical
I
would
say,
show
basically
the
developers
workflow,
so
they
want
to
create
a
new
component.
We
have
a
bunch
of
templates
the
golden
paths
that
are
all
Beauty,
So,
Fast,
Five,
serverless,
coating
jungle.
B
B
B
B
B
B
And
again
we
try
to
get
as
minimal
information
required.
You
see,
there's
no
VPC
ID
nurse,
no
even
Security
Group
anything,
so
they
choose
the
engine
type.
So,
let's
say
I
want
to
say:
I
create
a
postgres
and
the
version
and
I
can
use
adding
more
resources
so
suppose
that
I
want
acid
rebooked
again
I
can
put
a
name.
B
B
It
should
work
yes,
so
after
I
select
the
template
and
choose
the
risk
Cloud
resource
that
I
need,
I
can
create,
and
that
will
take
around
10
minutes
to
scaffolding,
the
repository
and
provisioning,
the
infrastructure,
as
we
don't
have
that
10
units
to
wait
for
I
just
have
another
Repository,
our
red
provision
and
created
so
for
our
developers.
They
go
to
the
backstage
catalog
and
they
see
all
the
information
from
their
their
application,
their
repository
and
we
go
there
in
a
minute.
B
There
I
go
CD,
so
they
can
see
the
state,
the
New
Relic
information,
the
sonar
Cube
and
even
the
CI
steps
that
we
in
your
case
we
are
using
GitHub
actions.
So
if
you
go
to
the
Repository
I
know
if
it's
too
small,
we
have
in
the
same
repository
the
infrastructure
and
the
application,
Helm
values
basic.
So
you
can
see
the
application
information.
B
And
the
infrastructure,
basically,
we
scaffold
the
infrastructure
and
we
we
populate
all
the
parameters.
One
thing
that
our
fine
Ops
team
is
happy
because
we
put
all
the
taglings
to
keep
the
cost
and
we
are
using
GitHub
CI
to
to
do
the
CI
and
and
triggers
the
action
in
the
Argo
CD
and
we
can
go
to
Diago
City
and
we
have
the
basically
kubernetes
resource
for
the
application
and
we
can
see
as
well
the
resources
the
quality
resources
created
by
cross-plane.
So
you
can
see
that's
the
RDS.
B
B
So
we
can
see
the
database
created
and
we
integrate
the
tooling
that
our
developers
need
we
integrated.
So
we
go.
They
don't
need
to
worry
about
integrated
to
neurality,
to
configure
in
their
logs
to
get
the
credentials
for
the
database.
We
inject
those
conditions
for
them,
so
that's
basically
the
workflow
of
our
developers
and
what
are
the
benefits
we
are
seeing
with
this
approach.
B
So.
Currently,
we
are
using
our
internal
platform
by
our
teams.
We
have
100
AWS
accounts,
managed
by
this
platform.
We
have
more
than
109
applications,
Beauty
user
platform.
We
have
at
the
moment
13
templates
and
we
have
195
resource
that
could
be
a
bucket,
a
database,
a
dynamodb
and
what
are
benefits.
We
give
the
developers
the
autonomy
they
need.
They
don't
have
to
talk
to
the
infrastructure
team
to
ask
anyone.
They
can
go
to
the
portal
and
provisioning
whatever
they
need.
B
B
We
we
can
ensure
our
security
and
monitoring
standard.
So
we
put
this
image
scanning
code
scanning
all
in
the
pipeline.
We
keep
in
the
same
repository,
the
product
will
life
and
the
the
infrastructure
information
in
the
same
repository,
and
because
we
are
working
in
the
same
structure
is
a
bunch
of
standard.
We
can
have
the
teams
collaborating
better,
so
it
is
a
pretty
nice
Journey
and
basically
that's
it.
Thank
you
guys
feel
free
to
reach
me.
B
A
With
all
the
yellow
screen
and
everything
I
think
it's
finally
come
up:
okay,
yeah
just
similar
to
The
Argosy
disciplines
that
startup
showed,
which
were
like
way
more
advanced,
but
here
we've
got
like
our
application
deployment
and
then
bucket,
and
it
provisioned
like
in
all
this
bunch
of
infrastructure.
Crypto
Etc
service
accounts.
Finally,
it
publishes
its
own
secret.