►
From YouTube: BDotNet-Bangalor.Net - AWS Cloud for .NET Developers
Description
Amit Jha, Sr. Developer Advocate - AWS - AWS Cloud for .NET Developers This session is targeted for .Net developers/architects/development leads who are exploring/building .NET applications on AWS. Learn .NET on AWS tools and .NET integration story for several AWS Services (Lambda, EC2, Containers etc.). Understand typical .NET Apps migration & modernization journey on AWS and learn about the DevSecOps tools/services. Lastly learn about how other customers are innovating further by leveraging AWS Platform features & Services in their .NET Applications.
Amit works as Developer Advocate with Amazon Web Services (AWS) and has 18+ years of Industry experience. In his current role, Amit focuses on architecting on AWS, optimizing AWS environments and helping customers & partners with cloud adoption with special focus on Microsoft/.NET workloads. Prior to his current role, he served numerous roles at Microsoft for 11+ years helping large enterprises with Cloud/Software architecture and development consulting.
A
Hey,
I
believe
we
are
live,
hey
good
evening
guys,
thank
you
so
much
for
joining
in
for
the.net
user
group
meet
on
march.
So
before
we
start
with
the
event,
I
would
like
to
give
a
brief
introduction
about
myself
and
the
group,
and
then
we
will
jump
into
the
event
right.
So
my
name
is
swami.
I
work
as
an
architect
at
musk
and
I
am
on
microsoft,
mvp
under
developer
technologies.
A
I
do
write
technical
blogs,
occasionally
at
my
blog,
which
is
swaminativity.in,
and
if
you
want
to
follow
me
on
twitter,
that's
my
twitter
handle
all
right
and-
and
this
group
is
called
b.n,
which
is
nothing
but
bangalore.net
user
group.
So
this
is
one
of
the
oldest
user
groups
in
bangalore
since
2005's
time
and
we've
been
evolving
as
and
when
the
technology
evolved
and
now
we
are
having
our
live
events
and
virtual
meetups
all
right.
A
So
if
you,
if
you
want
to
be
part
of
our
meetup,
so
you
can
join
at
meetup.comg
or
if
you
are
more
active
on
facebook,
you
can
join
the
groups
there
and
we
also
have
presence
on
twitter
and
video
10..
I
n
is
our
basic
website
about
the
about
the
community
and
the
events.
What
we
you
know
contact,
we
kind
of
share
it
there
and
we
also
recently
started
our
youtube
channel.
So
that's
the
link
for
it
and
they're
also
on
discard
to
have
more
close
collaboration
with
the
with
them.
A
You
know
the
tech
community,
so
that's
our
discord.
Handle
too.
I
will
share
these
links
as
well
in
the
in
the
show
notes,
so
that
you
can,
you
know,
join,
join
us
and
yeah,
so
thanks
to
sponsors.
So
this
is
this.
Meetup
is
sponsored
by
dotnet
foundation
and
we
also
have
microsoft
and
jetbrains
as
other
sponsors
yeah,
and
I
want
to
give
a
brief
about
dotnet
foundation.
If
in
case
you
are
not
completely
aware
about
that
right,
so
dotnet
foundation
is,
is
a
is
an
open
source
consortium
right.
A
A
That's
also
you
know
available
and,
of
course,
like
like
the
marketing
communication
about
the
events
right
like
what
we
are
doing
currently.
This
is
also
hosted
by
darton
foundation's
virtual
meetup
group
right,
so
you
can
also
you
know,
get
that
out
of
the
foundation
and
about
the
support
we
also
get
some
sort
of
hosting
and
the
code
signing
and
in
azure
devops
you
get
get
good
good
support
to.
You
know,
set
up
your
devops
pipelines
for
your
open
source
projects,
etc.
So
anything
to
do
with
with
opensourcein.net.
A
So
you
can
go.
Look
at
the
other
dotnet
foundation
sponsored
meetups
at
meetup.comproslash.net,
and
if
you
are
running
a
meetup
which
is
not
part
of
the
foundation
yet
you
could
also
do
that
and
there's
also
a
newsletter
which
you
could
sign
up
for
and,
as
I
said,
the
projects,
if
you
want
to
get
your
projects
as
part
of
the
foundation
umbrella,
you
could
very
well
do
that
too,
and
for
any
other
things
you
can
contact
the
foundation
all
right
that
the
next
thing
is
about
the
speaker,
so
we've
got
amit
today.
A
I
think
he's
here
he's
here
with
me,
so
he
is
and
senior
developer
advocate
at
aws
and
he's
joining
us
from
from
the
u.s.
I
believe
it's
in
new
york
so
I'll
leave
his
introduction
during
his
session.
So
I'm
not
going
to
talk
too
much
about
him,
but
thank
you
so
much
amit
for
taking
time
and
sharing
the
knowledge
with
our
community
and
moving
on.
So
this
is
a
this
is
a
pretty
sleek
agenda
today.
So
this
is
the
introduction
session.
A
A
We
would
have
feedback
on
the
raffle
right,
so
there
is
a
quiz
which
will
unveil
at
the
end
of
the
session.
So
you
stand
a
chance
to
win
five.
Five
people
can
win
azure.
Sorry,
not
as
your
quest,
I'm
sorry
aws
credits
and
just
the
bit
of
even
etiquette,
so
q
a
will
be
handled
at
the
end
of
the
session
right.
A
Okay.
So
if
if
in
case,
there
are
a
few
audience
so
I
would
like
you
to
have
a
bit
of
a
poll.
So
if
you
can
open
your
mobile
or
in
website,
you
can
just
go
in
your
your
desktop.
You
can
go
to
www.menti.com
and
use
this
code
and
it
will
be
good
if
you
could.
You
know,
fill
up
this
poll
so
that
we'll
get
and
get
the
idea
about
what
your
experience
and
your
background
about
the
wwsup.net
all
right.
A
A
So
you
guys,
please
fair
openmenti.com
in
your
mobile
or
in
the
browser
and
then
just
use
the
code.
This
is
more
since
it's
more
of
a
virtual
event
right,
so
we
wanted
to
make
it
more
interactive.
So
this
is
one
of
the
ways
of
you
know
interacting
with
the
with
the
audience.
So
we
would
like
to
get
your
you
know
inputs.
So
as
in
when
any
of
you
start
feeling
feeling
the
pull
we
we
keep
getting
the
answers,
I
think
yeah
somebody
has
that's
good
yeah.
We
are
getting
the
responses
now.
A
A
A
A
B
Cool
wonderful.
Thank
you.
Thanks
for
that
wonderful
introduction,
swami
team,
my
name
is
amit.
I
work
as
developer
advocate
at
aws
and
today
in
next
hour
hour
and
a
half,
my
plan
is
to
give
you
run
through
of
all
things.net
on
aws
okay.
I've
been
with
aws
little
over
five
years
and
and
been
in
the
industry
for
a
little
over
16
years:
development
architecture,
cloud,
end-to-end,
ci,
cd,
devops
security,
that's
where
I
I'm
more
comfortable.
B
I
live
in
new
jersey.
I
work
out
of
new
york,
so
I
have
good
amount
of
financial
services.
Customers
that
I
work
with
so
I'll
be
bringing
those
use
cases
as
the
discussion
goes
along
for
today.
I
understand
there
are
many
people
who
are
new
to
aws,
so
I'll
quickly,
give
aws
primer
very
short
and
then
move
into
the
topic
of
the
day,
which
is
aws
tools
for
net
developers.
B
Show
you
different
tool
sets
that
we
have
and
then
understand
what
are
the
different
migrations
and
modernizations
path
for
a.net
application
on
aws,
along
with
that,
obviously,
when
you
bring
an
application,
it's
also
productionizing.
How
do
you
trace?
How
do
you
monitor?
How
do
you
do
authentication
authorization
so
we'll
touch
upon
those
those
topics
as
well?
As
you
can
see,
I
have
good
amount
of
agenda
to
to
pack
it
in
in
within
one
and
a
half
hour.
B
So
just
put
your
questions
as
you
get
and
I'll
make
sure
that
we
keep
some
time
at
the
end
and
touch
those
questions
also,
okay,
so,
before
anything
check,
the
first
thing
is:
what's
the
business
goal
right,
the
driver
behind
moving
to
the
cloud,
it
could
be
revenue
streams,
it
could
be
cost
savings,
it
could
be
lowering
the
business
risk.
Different
enterprises
have
different
goals
right
with
coved.
Digital
transformation
has
become
pretty
significant.
Many
customers
are
looking
to
jump
the
hoop
and
get
more
cloud
native,
a
speed
with
which
things
are
being
built.
B
The
innovation
speed
many
enterprise
customers
want
to
actually
get
that
nimbleness
of
a
startup
and
get
that
ci
cd
pipeline
going
so
that
they
can
actually
produce
valuable
outcome
for
their
customers
right
sometimes
it
starts
with
just
simple
cost
savings:
hey.
I
have
significant
amount
of
cost
in
my
data
centers
I
may
want
to
consolidate
them.
That's
a
very
valid
reason.
B
Sometimes,
basically
on-prem,
you
do
not
have
the
services
that
are
available
in
the
cloud,
many
of
the
higher
level
like
ai
ml,
analytic
services,
so
essentially
many
customers
bring
those
data
onto
cloud
and
then
actually
enrich
harness
the
power
of
aiml
and
get
more
value
out
of
their
data.
So
there
are
many
different
business
drivers.
So
it's
very
important
to
get
that
clarity.
What's
the
business
driver
to
go
into
the
cloud
and
then
looking
at
the
use
cases
that
you
map,
because
sometimes
it
can
go
into
many
different
directions?
B
What
is
aws
very
top
level?
It
basically
has
set
off
regions.
Each
region
is
put
offset
of
availability
zone.
Each
availability
zone
has
multiple
data
centers
each
data
center
underlying
you
have
the
actual
compute
instances
right.
That's
I
like
to
see
the
mapping
of
it.
The
key
distinction
you
have
to
understand
is
between
the
availability
zones.
So
you
got
the
region
which
is
different
locations
around
the
world.
Availability
zones
are
one
or
more
discrete
data
centers,
each
with
redundant
power,
networking
and
connectivity
housed
in
separate
facilities.
B
When
I
say
separate
facilities,
they
are
basically
miles
apart
right.
So
that's
the
key
distinction.
You
have
to
keep
in
mind
when
you
are
actually
building
your
application
architectures.
You
may
do
a
multi-ac
based
design
or
multi-region
based
design.
Having
that
clarity
of
how
how
much
distance
is
there?
What's
the
latency
between
the
two
will
help
you
actually
design
your
application
architecture
better?
B
B
What?
What
do
we
mean
when
we
actually
bring
a
workload
onto
aws
or
a
cloud?
It
always
starts
with
a
shared
responsibility
model
right.
The
key
word
I
look
for
is
off
and
in
so
we
are
responsible
for
anything
off
the
cloud
so
think
of
it
like
hypervisor
down
power,
cooling,
everything
in
the
data
center,
that's
on
us
anything
you
bring
into
the
cloud.
You
have
the
responsibility.
B
We
give
you
tools
like.
If
you
bring
in
data,
we
give
you
tools
to
encrypt
decrypt.
We
give
you
tools
to
authenticate
and
authorize
so
essentially,
whatever
you
bring
in
using
the
tools
and
services,
you
have
the
responsibility
for
the
securing
those
data
and
applications
right,
and
we
give
you
tons
of
services
right.
B
These
are
different
pillars
across
identity
detection,
infrastructure
protection,
data
protection
incident
response
compliance-
one
thing
I
would
want
to
highlight
is
traditionally
it
has
been
very
hard
to
actually
have
automated
security,
whereas
in
the
cloud
it
becomes
much
easier
because
every
resource
when
it
changes,
you
have
an
ability
to
actually
have
some
kind
of
trigger
or
a
hook
which
can
check
whether
you
want
that
change
to
happen
or
not,
or
you
can
actually
track
whether
in
real
time
who
who
made
those
changes.
So
it's
much
easier.
You
can
have
automated
security
along
with
that.
B
Obviously,
there
are
many
services.
The
two
areas
that
I
want
to
highlight
is
the
ml
stack,
ai
ml
stack
and
we
will
probably
be
seeing
couple
of
demos
today
and
the
second
is
data
analytics.
Once
you
bring
in
the
data,
there
is
so
much
value
that
can
be
produced
out
of
it
and
we
provide
many
services
to
do.
B
Etl
and
doing
dashboarding
visualization
on
top
of
that
data,
we
have
our
services,
but
we
have
many
aws
partners
who
are
building
on
top
of
aws
and
enhancing
and
building
on
top
of
aws,
and
we
also
have
many
other
products
in
our
aws
marketplace
that
enhances
the
aws
offering
okay.
So
that
was
very
quick
primer.
If
I
have
to
summarize
it
remember,
regions,
availability
zones,
mapping,
understand
the
application,
architecture,
multi-ac
and
multi-region
understand
the
services
and
capabilities,
and
also
look
for
different
level
of
abstractions.
B
B
Here
is
very
quick
summary
on
the
left.
You
see
the
ide
integration,
the
visual
studio,
I
mean
any
dotnet
developer.
The
first
thing
they
want
to
look
at
is:
what
do
you
support
or
provide
inside
visual
studio
right?
We
have
the
toolkit
for
visual
studio.
We
have
toolkit
for
visual
studio
code
and
we
also
support
toolkit
for
jetbrain
slider
right.
So
that's
that's.
On
the
id
integration
front.
The
second
is
the
sdk
right.
B
Whenever
a
dartmouth
developer
comes
in
he's
like
I
want
to
manipulate
this
service,
I
want
to
use
this
service
what's
the
way.
What's
the
sdk,
how
do
I
use
it?
So
we
provide
both.net
framework
and
dot
net
core
based
sdk,
which
you
can
use
and
manipulate
aws
services
right
beyond
that.
We
also
have
command
line.
Powershell
ci
cd
devops
integrations
with
aws
code
suite
services,
as
well
as
our
partners
like
jenkins,
shipable,
atlassian,
bitbucket,
azure
devops.
We
integrate
with
those
two
okay.
B
B
If
I
go
to
the
extension
in
this
case,
I
have
2019,
and
I
search
for
aws
here
is
the
aws
toolkit
for
visual
studio.
I
have
already
installed
this
toolkit
once
you
install
this
toolkit.
The
first
thing
that
you
will
notice
is
something
called
aws
explorer,
so
aws
explorer
is
ability
to
see
aws
services
right
inside
visual
studio
for
the
folks
who
are
very
new
to
aws.
B
The
first
thing
you
may
do
is
creating
an
iam
account
or
you
may
have
a
federation-based
integration
once
you
create
the
im
account,
you
link
your
visual
studio
with
the
the
same
so
here.
If
you
see
here,
if
I
want
to
specify
new
account
profile,
I
can
say,
and
I
can
specify
the
account
number
with
which
this
will
connect.
So
basically,
if
I
see
here,
I
see
these
buckets
I
go
in
here.
Let's
go
to
the
s3
service
right.
B
And
hopefully
the
demo
guards
are
happy
here
you
go
so
you
can
see.
I
see
the
same
set
of
buckets
here
too
same
buckets
are
being
listed,
so
the
idea
behind
providing
you
the
aws
explorer
is
basically
you
do
not
have
to
go
outside
of
visual
studio.
You
are
able
to
see
all
the
resources
right
inside
visual
studio
and
not
just
c.
You
can
actually
do
operations.
Also,
like
here
are
my
instances
right.
I
can
actually
connect.
B
I
can
do
operations,
I
can
do
rdp
session
so
making
it
more
meaningful
and
rich
right
inside
visual
studio.
That's
the
first
thing.
We
provide
you
after
that,
right
and
depending
on
the
application
type,
you
would
see
different
set
of
deployment
wizards
that
we
expose.
So
here
is
a
web
application.
Let
me
quickly
show
you
this.
B
Okay,
this
is
a
typical
asp.net
application,
I'm
using
d3
to
do
client-side,
sorting,
filtering
right.
This
is
a
typical
web-based
application.
We
actually
expose
right
inside
visual
studio
because
of
the
toolkit
deployment
wizards
right
from
visual
studio.
So
if
you
see
I'm
here,
I'm
looking
to
publish
to
bing
stock,
this
is
another
one
of
our
past
like
service,
so
I
actually
have
published
this
application
off
the
bat.
So
if
I
go
here
and
see
the
bin
stock
link
here
is
the
same
application
deployed
to
beanstalk
right.
B
So
the
idea
here
is
once
you
have
installed
the
toolkit.
You
are
able
to
connect
the
explorer
to
your
account
and
you're,
able
to
see
resources
right
inside
database
explorer
inside
visual
studio,
and
we
also
expose
the
deployment
wizards.
Obviously
you
may
actually
do
the
right
click
deployment
just
for
testing
purposes,
but
it
actually
gives
you
a
pretty
neat
fast
way
of
iterating
like
deploy,
see,
check,
come
back
fix,
deploy
in
your
own
dev
test
account,
so
that
way
it
the
iteration
becomes
much
faster.
B
B
As
you
can
see,
we
are
dotnet
five
ready,
so
we
have
both
net
five
container
base
support,
as
well
as
dot
net
five
custom
run
time
base
support,
so
I
can
choose,
it
can
create
a
default
code.
Based
is,
let's
choose
one
and
quickly
show
you
what
I
mean
by
the
boilerplate
functions,
and
hopefully
the
demo
gods
are
happy
right.
So
here
you
go
as
you
can
see,
this
is
the
image
label.
So
any
time
an
object
is
being
uploaded
to
s3,
which
is
over
scalable
object.
Storage.
B
The
lambda
function
will
come
in
and
execute
and
do
some
kind
of
recognition
to
see
the
attributes
inside
that
image
that
got
uploaded
right
here
you
go,
you
can
see.
This
is
the
actual
lambda
handler
and
as
soon
as
this
comes
it
may
call
the
recognition
api
detect
the
attributes
inside
that
image.
But
this
is
the
idea
here
is
to
show
you
templated
project
templates
and
boilerplate
code
that
gets
generated
right
right
click
deployment.
B
B
Okay,
and
if
you
have
to
see
here,
I
have
configured
the
connected
this
command
line
and
I
can
list
down
all
the
basically
you
install
the
aws
cli,
you
configure
the
connectivity
specify
the
access
key
secret
access
key
or
you
could
do
a
federation
based
also
where
right
and
then
once
you're
connected
you
can
start
using
command
line.
Similarly,
powershell
you
could
you
could
do
the
same
thing
here
you
go.
This
is
again
connected.
I
can
use
powershell
command,
let's
and
and
do
different
operations,
so
cli
power,
shell
inside
widget
studio.
B
B
B
B
B
And
then
you
can
see
we
pretty
much
expose
for
each
services.
We
have
a
sdk
offering
all
right,
azeeb
sdk.
Once
you
refer,
there
is
a
typical
pattern
which
is
amazon.servicename
amazon.servicename.model.
So
that's
a
typical
model,
any
service,
you're
manipulating
you
would
do
the
same.
Ec2
ec2,
dot
portal,
dynamodb
dynamodb
model,
so
you
get
that
pattern
right
for
each
service
so
to
make
it
simple
right
and
create
the
client
and
call
the
object.
So
your
developers,
let
me
do
this.
B
What
I'll
do
is
I'll
do
a
quick
debug
here,
so
this
is
checking
for
required
fields.
Let's
see
here
in
this
case.
What's
the
profile
in
this
case,
I
have
specified
aws
profile
limits,
meetup
foundation,
as
you
can
see,
on
the
left.
The
explorer
can
connect
to
multiple
profiles.
So,
as
a
developer,
you
may
work
on
one
account.
You
may
work
on
multiple
accounts,
so
you
can
create
different
profiles
right
in
this
case,
I
am
connecting
to
the
same
account.
B
Let's
go
in,
I
created
the
s3
client
object
and,
let's
just
see
what
that
client
object
is
right.
It's
a
scalable,
object,
storage.
What
do
you
think
it
will
have
copy?
It'll
have
delete
right
and
it
gives
you
exposes
both
sync
async,
so
synchronous
based
calls
or
asynchronous
based
call
right.
So
we
we
exposed
those
let's
go
in,
and
here
I
am
iterating
through
the
buckets
actually,
let's
step
into
it
and
see
the
details
of
it.
Here
you
go
so
it's
called
the
list
bucket.
B
It
gave
me
a
response
and
then
I'm
iterating
through
each
bucket,
so
you
get
a
neat
typed
object,
bucket
name
and
other
set
of
properties,
and
then
I'm
just
in
this
case,
iterating
through
it
and
listing
down
the
same
set
of
bucket
that
we
saw
here
as
well
as
on
the
console
right.
So
again,
I
repeat
what
what
did
I
do
here?
It's
basically,
I
took
the
dependency
and
each
of
them
are
published
by
nougat
packages.
So
you
you
choose
the
aws
sdk
dot.
In
this
case
I
chose
the
s3
right
once
you
have
it.
B
You,
import
s3
as
three
dot
model
typical
pattern
for
any
services
create
the
client
of
it.
Once
you
create
the
client
of
it,
you
have
the
ability
to
iterate
through
and
call
different
functions
and
depending
on
the
service
type,
you
will
have
different
set
of
methods
and
that's
what
is
the
learning
as
we
go
along
we'll
see
some
other
use
cases
of
the
same
okay.
So
that's
a
very
quick
demo
on
the
sdk
side
right.
One
key
thing
here
is,
you
would
say:
aws
has
apis
and
this
sdk
has
called
those
apis.
B
I
didn't
get
to
know
the
underpinnings
like
does
the
api
call
need
json-based
utilization,
xml-based
serialization?
How
did
the
marshalling
go
through
all
that
is
abstracted
from
you?
So
that's
the
beauty
of
sdk.
It
makes
it
much
a
seamless
right
and,
as
I
showed
you,
the
typical
pattern,
it's
a
consistent
sdk
coding
pattern
using
service
name,
service,
name,
dot,
model,
create
the
client
so
the
same
client,
and
then
you
call
the
operations.
B
B
Okay,
so
that
was
a
very
quick
demo
on
on
how
to
use
aws,
sdk4.net
and
manipulate
a
different
aws
services.
Now
you
showed
me
amid
so
many
different
services.
How
do
I
decide
and
and
how
to
explore
that?
So
I
always
look
at
like
don't
boil
the
ocean,
you
do
not
have
to
know
all
the
aws
services
depending
on
which
application
you
are
working.
You
would
look
to
map
the
type
of
services
that
you're
interested.
B
In
take
an
example,
let's
take
a
web
application
you're
working
in
that
case,
you
are
looking
for
compute,
where
you
can
have
a
either
hosting
or
if
you're
looking
to
modernize
them
go
to
a
higher
higher
level
of
abstraction.
At
a
very
high
level,
there
is
vm
based
container
based
and
serverless
based
right,
vm
based
essentially
ec2
container
based.
We
have
ecs,
which
uses
our
own
orchestration
eks,
which
uses
kubernetes,
orchestration
and
serverless
paste.
We
have
lambda
step
functions
right
and
there
are
serverless
containers
called
fargate.
B
These
are
the
services
at
the
compute
level,
storage
level.
You
may
say:
scalable
object,
storage,
s3.
You
want
to
use
some
kind
of
caching.
We
have
elastic
cache.
You
want
to
use
database,
we
have
rds
managed
and
it
supports
many
different
underlying
database
engine
like
sql
oracle,
mariadb
mysql
dynamodb,
our
nosql,
offering
right
so
understanding
the
list
of
services
for
your
application
is
the
first
thing
that
I
look
to
start
typical
applications
journey.
How
let's
say
on
prem
to
aws
works
like
this.
Is
your
classic
typical,
three-tier
based
architecture.
B
You
can
see
web
tier
api,
tier
and
data
tier
once
you
get
it
on
to
aws.
We
may
just
map
it
to,
let's
say,
as
is,
I
am
getting
it
so
in
this
case
I
am
not
actually
looking
to
go
more
container
or
serverless,
I'm
just
looking
to
replicate
what
I
have
on
prem
onto
aws.
So
what
you
look
for
is
basically
the
configurations
of
your
on-prem
machines.
B
Look
for
the
right
instance,
types
that
would
map
and
then
replicate,
so
you
could
do
a
snapshot
and
and
get
a
export
import
kind
of
way
of
exporting
it
or
you
create
a
ec2
instance
and
deploy
your
applications
via
some
kind
of
ci
cd
pipeline.
So,
as
you
can
see,
this
is
a
typical
pattern.
Where
customers
start,
we
call
it
lift
and
shift
move
and
tune,
but
this
is
this
is
the
first
level
we
don't
stop
here.
So
basically,
now
you
start
looking
at
hey.
B
I
have
good
amount
of
operations
work,
because
the
more
vms
are
the
more
operations
work
will
be
there
because
upgrades
patching
is
on
you.
So
then
you
look
for
like
what
are.
What
are
all
areas
can
be
moved
into?
Maybe
managed
services
or
maybe
serverless
services,
where
all
I
care
about
is
my
own
code
and
the
serverless
services
take
care,
takes
care
of
auto
scaling,
depending
on
my
request
pattern.
So
this
is
one
example
of
how
I
am
actually
taking
that
same
application.
This
is
primarily
serverless
stack.
B
Don't
worry
if
you
are
not
familiar
with
the
service
names,
but
the
idea
here
is
think
of
this
as
a
service
gate,
so
any
api
service,
I'm
exposing
via
api
gateway
and
then
the
actual
compute
is
lambda
the
serverless
and
then
I
actually
introduce
sqs
and
sns
think
of
it
like
queuing
and
pub
sub
model.
Just
from
a
decoupling
point
of
view,
so
request
came
in
api
gateway,
gave
it
to
lambda
lambda,
put
it
into
q
automatically
from
queue.
B
There
is
a
processing
by
another
lambda
and
via
sns
it
notified
that
hey,
it's
done
so
the
idea
here
is,
I
move
towards
more
serverless.
Why?
Because
I
do
not
want
to
do
the
operations
work.
I
want
to
rather
focus
on
my
application
and
add
newer
use
cases.
Similarly,
on
the
data
tier,
I
moved
from
having
let's
say,
sql
server
on
ec2
to
our
an
rds
or
or
other
offerings
right.
So
typically,
that's
that's
where
the
conversation
starts.
B
When
we
go
for
like
application
portfolio
analysis,
hey
this
application
needs
to
move
to
aws,
or
should
we
move
it
as
is?
Should
we
refactor
this
application?
This
is
in
dot
net
framework.
What
would
it
take
to
go
to
dot
net
core
right?
So
that's
that's
the
conversation
we
have
and
the
three
compute
engine
discussions
are
around
ec2,
lambda
and
containers.
Right
ec2
is
your
typical
vm
lambda
is
the
serverless
offering
and
containers?
B
This
is
quick
mapping
of
if
you
have
an
application,
dot
net
framework
based
versus
dot,
net
core
or
dot
net
5
based
so
net
framework.
The
offerings
are
ec2
bean
stock,
light,
sale,
elastic
container
service
and
elastic
kubernetes
service.
This
is
where
the
dotnet
framework
based
applications
can
be
deployed
to
so
underlying
containers
is
basically
windows,
container
dot,
net
core
has
more
wider
choice
and
that's
where
the
fargate,
the
serverless
container
or
lambda,
comes
in
right.
One
quick
thing:
let
me
quickly
show
you
the
bean
stock
where
customers
start.
B
B
B
And
it
gives
you
pretty
neat
dashboard
for
health
monitoring.
I
can
set
up
alarms.
I
can
check
in
terms
of
what's
the
request
pattern
out
of
the
box,
like
all
you
did
was
right,
click
deploy,
or
maybe
you
called
the
same
right-
click
deploy
by
command
line
or
integrated
in
your
ci
cd
pipeline
right.
That's
it
beyond
that.
We
created
the
underlying
environment,
so
created
the
underlying
ec2
deployed
the
application
configured,
the
auto
scaling
and
configured
the
alarms
configured
the
logging
monitoring
right.
So
this
is
by
default.
B
This
is
why
I
say
like
when
you
have
a
web
application,
api
websites
and
you're,
not
very
sure
like
where
to
start
just
map
it
to
elastic
bean
stock.
That's
probably
the
best
way
to
start
get
going.
It
gives
you
a
pretty
neat
integration,
end-to-end
with
logging,
health
monitoring
ability
to
manage
updates
right.
So
those
are
all
out
of
the
box
that
that
you
get.
You
can
customize
it
like.
B
B
B
Seconds:
okay,
I'll
update
that
later
and
once
you
get
that
by
default,
docker-based
support.
Now
I
have
ability
to
actually
containerize
it
and
then
deploy
it
onto
ecs
or
eks.
Do
we
provide
some
tools
for
the
same?
We
have
couple
of
tools.
If
you
have
an
application,
let's
say
if
you
have
a
legacy.net
framework
based
application
and
you
you're
looking
to
get
them
to
net
core.
B
You
can
also
see
the
api
level
details
and
it
can
go
up
to
the
level
of
source
code
which
apis
are
being
called
inside,
which
cs
files
right
so
porting
assistant
for
dotnet
is
a
pretty
neat
tool
to
help
you
analyze
your
existing
dotnet
framework
based
application.
Like
typically,
you
want
to
understand
the
level
of
effort,
that's
needed
to
port
that
application
from
dotnet
framework
to
dotnet
core.
In
my
experiences
working
with
different
set
of
customers,
api
based
applications
are
easier
to
port
to
net
core.
B
If
you
have
like
a
thick
client
based
applications
like
winforms
wpf,
those
are
more
harder
wcf,
depending
on
like
windows.
Communication
foundation
sometimes
had
has
more
configurations,
so
I
call
it
windows
configuration
service
sometimes,
but
if
it
is
just
a
standard,
crud
based
operations,
those
are
easier
to
port
asp.net,
mvc,
sprout
and
web
api
are.
B
If,
unless
there
is
significant
dependencies,
they
are
they're
easier
to
pour
to.net
core
again,
you
want
to
understand
the
list
of
effort,
that's
needed
and
based
on
that,
take
the
call
right,
because
you
have
to
understand
incompatibilities,
understand
the
changes
that
you
may
have
to
do
and
then
move
towards
net
core.
Okay.
So
let's
go
in
okay.net
5
support.
I
showed
you
the
net
container
image
by
default
boilerplate.
We
have
it
for
the
blueprints
for
lambda
functions.
B
We
have
the
command
line,
based
templates
that
I
was
saying
right.
Click
deploy
same
thing
is
available
via
the.net
cli
extensions.
We
give
you
ec
to
linux
armyfor.net5
right,
you
can
just
filter
it
down.
That's
that's
available,
and
this
is
where
you
come
in
like
and
start
discussing.
In
terms
of.
Where
do
I
run
my
code?
Is
it
easy
to
instances?
Is
it
containers
or
is
it
lambda
or
serverless
right?
Typically,
you
want
to
port
as
as
much
as
when
it
is
possible.
B
You
must
have
heard
or
seen
many
conversations
around
moving
from
a
traditional
monolithic,
single
stack
based
application
to
more
modern
micro
services.
Decoupled
services,
like
each
service,
has
its
own
api.
It
has
its
own
data
store
and
they
all
communicate
via
public
kind
of
https
right.
So
that's
that's.
A
typical
pattern
of
refactoring.
B
The
second
yes
supporting
assistant
also
provides
you
a
dependency
graph
where
you
can
actually
learn
more
about.
Sometimes,
actually
we
go
to
many
customers
and
say
we
don't
know
actually,
which
one
calls
which
one
we
don't
have
understanding
of
the
whole,
because
I
mean
it's
been
ages
years
that
it
has
been
built
so
porting
assistant
helps.
You
actually
understand
those
dependencies.
Also,
pretty
pretty
right
neatly
showed
you
quickly.
The
another
tool
is
basically
the
app
to
container.
B
If
you
want
to
package
dotnet
framework
application
into
containers-
and
you
do
not
want
to
actually
work
with
the
underpinnings
of
hey
docker
docker
file
creation,
how
do
you
manage
the
containers
so
app
to
container
actually
gives
you
a
pretty
neat
tool
that
will
actually
go
through
your
let's
say
you
deployed
on
your
iis
web
server.
It
will
actually
go
through
and
find
out
all
the
applications
that
are
there
and
then
actually
give
you
ability
to
to
artif
containerize
them
in
a
wizard
fashion.
B
You
so
you
are
actually
you
do
not
have
to
know
the
underpinnings
of.
How
do
I
create
ecs
service
ecs
task?
How
do
I
map
the
application
to
it?
So
this
is
another
application
like
if
you
have
a
legacy
framework
based
application,
and
you
just
want
to
containerize
them
app
to
container
is
definitely
you
want
to
explore
and
see.
If
that
can
that
can
help.
You
app2container
also
does
auto
containerization
for
java
based
apps,
also
right,
other
dot
net
modernization.
B
So
when
you
bring
in
dotnet
based
application,
traditional
applications
may
have
some
kind
of
caching
tier
right.
One
example
is:
maybe
you
want
to
evaluate
if
reddish
velocity
cache
can
help
you,
we
give
you
direct
configuration
based
ability
to
change
right
yeah
just
here.
I
can
change
this
as
an
instruction
straight
provider
just
by
changing
the
end
point
to
radish
and
from
there
onwards
your
session
starts
getting
stored
into
the
registration
state
provider.
That's
one
example
of
modernizing
when
you're
bringing
the
applications.
B
You
also
want
to
understand
how
the
call
flows
are
when
the
api
calls
are
being
made,
how
much
time
is
spent
in
each
layer,
and
that's
where
the
our
aws
x-ray
support
comes
in
once
you
have
x-ray
integrated
in
your
application.
You'll
be
able
to
see
the
whole
call
stack
so
think
of
it.
Like
a
web
call
k
main
from
there,
it's
called
service
from
there.
It
called
data
tier.
You
can
actually
see
the
actual
call
stack
and
it
is
very
useful
for,
like
a
performance,
troubleshooting
use
cases
right.
B
All
you
do.
Is
you
specify
the
x-ray
recorder,
the
services
that
you
want
to
capture
and
it
will
start
giving
you
that
service
map?
Another
neat
integration
that
we
have
is
for
typical
applications
will
have
list
of
services
right,
I
may
have
compute
may
have.
Databases
may
have
other
set
of
services,
so
the
app
insights
gives
you
ability
to
actually
group
them
and
create
a
dashboard
and
get
insights
and
summary
of
how
that
that
has
been
used
very
useful
for
again
performance,
troubleshooting
and
t2
based
stacks
right.
B
So
we
looked
at
tool
sets
of
aws
for
dot-net
developers.
Remember
aws
toolkit
for
visual
studio.
We
looked
at
sdk
support
both
for
net
framework
as
well
as
dotnetcore.net
5..
We
understood
different
abstraction
tier
right,
understood
in
terms
of
hey.
I
can
actually
bring
that
application
into
vm.
In
that
case,
I
have
to
take
care
of
the
infrastructure-oriented
work
like
patching
upgrade.
All
that
is
on
me.
I
can
go
to
more,
let's
say
elastic
bean
stock,
where
it
abstracts
a
lot
of
things
for
me
and
does
those
things
on
my
behalf.
B
We
can
go
to
containers
or
serverless
again
if
you
are
able
to
port
your
application
to
net
core.
In
that
case,
definitely
you
would
want
to
explore
going
to
serverless.
You
say
this
is
great.
We
got
that,
but
usually
I
have
a
ci
cd
pipeline
in
my
organization
right.
I
have
a
devsecops
pipeline.
How
do
I
integrate
with
those
and
aws
actually
has
its
own
code
sweet
services,
but
it
also
integrates
with
most
of
the
widely
used
cicd
providers
so
at
the
top
left
you
see
here.
These
are
the
aws
code.
B
Suite
services
right
code,
build
code
command
code,
deploy
code
pipeline
code
pipeline.
Is
the
orchestrator,
so
basically
go
get
the
code.
Do
the
code
build
and
do
the
code
deployment,
so
it
gives
you
ability
to
do
different
kind
of
events.
Also,
while
you
are
doing
ci
cd-
and
it
does
not
mean
that
you
have
to
use
aws
code
services
only-
you
could
very
well
integrate
aws
code
pipeline
with
other
like
jenkins,
atlassian
products
right,
and
we
also
integrate
with
azure
devops.
B
So
you
can
keep
the
source
code
in
azure
devops,
give
us
the
binary
and
we
do
the
hosting
or
you
could
give
us
the
code
and
we
do
the
build
and
then
deploy
it
onto
the
compute
services,
both
the
ways
we
integrate
right.
We
are
today
looking
at
primarily.net,
but
we
have
many
other
sdks
on
different
languages
that
we
support.
We
looked
at
integration
with
visual
studio,
but
we
have
many
other
ids
that
we
integrate
with
right.
B
These
are
some
of
the
cicd
partners
that
we
integrate.
If
nothing
else
you
can
have
a
hook
and
based
on
that,
you
can
integrate
via
the
same
also
and
now
I'll
quickly.
Move
on
to
another
area
like
modernization
does
not
mean
that
you
move
from
easy
vm
base
to
container
to
serverless.
Modernization
can
mean
a
lot
of
other
things
right.
B
One
of
the
area
where
I'm
seeing
many
customers
actually
look
at
their
existing
application
and
see
are
there
use
cases
that
can
be
added
in
that
application,
leveraging
maybe
higher
level
auto
auto
trade
ai
services
right?
This
is
a
good
eye
chart
of
all
the
aiml
services.
Think
of
it
like
the
three
different
personas
at
the
bottom
tier
and
the
ml
framework
and
infrastructure
caters
to
kind
of
the
machine.
B
Learning
scientist
right,
who
wants
to
have
the
complete
control
on
the
infrastructure
and
the
second
tier
is
basically
the
the
the
machine
learning
people
who
are
actually
creating
model
training
them
against
different
data.
So
it's
a
cycle
like
you,
have
an
algorithm
you're
training
against
different
set
of
data.
The
third,
which
is
the
everyday
developer,
who
wants
to
actually
use
auto
trained
ai
services
right,
would
not
have
the
amount
of
time
to
actually
create
and
train
a
model.
So
this
is
where
most
of
the
dot
net
based
application
integration.
B
B
Okay,
this
is
I'm
integrating
with
one
of
our
service
aws
comprehend.
Think
of
it
like
a
sentiment
analysis
right,
given
a
text,
it
can
understand
and
do
a
sentiment
analysis.
So
this
is
a
text
here.
I
just
wanted
to
find
some
really
cool
new
places.
I
have
never
visited
before
and
it
has
some
actual
suggestions
and
also
some
sentiments,
so
you
can
see
just
terrible.
So
what
I'm
gonna
do
is
I'm
quickly
gonna
call
the
comprehend
api.
So
remember
the
drill
of
referral,
I'm
referring
the
asws
sdk.comprehend
right.
B
B
Okay,
so
that's
the
text
file
that
you
saw.
That's
the
input,
the
same
thing.
Okay,
so
that's
the
one
and
it
does
have
sentiment.
It
has
some
entities
it
has.
This
is
in
english,
so
let's
go
in
and
the
comprehend
api
has
different
set
of
functions
to
detect
different
values.
So
in
this
case
I'm
calling
find
out
the
language
find
out
the
different
entities
find
out
the
key
phrases
find
out
the
sentiment
inside
this
okay.
I
call
those
apis.
B
B
B
Okay,
so
it
should
have
generated
a
file.
Comprehend
here
is
the
output.
It
found
the
language
code
en
it
found
the
entities.
2021
type
is
date,
and
it
gives
you
a
score
so,
based
on
the
score,
you
can
have
a
percentage
of
score
on
which
you
want
to
take.
The
values
here
are
some
of
the
key
phrases
that
it
detected.
B
No
luck,
these
top
score,
and
last
it
actually
found
the
sentiment
negative.
Remember
we
saw
the
word
terrible
so
that
that
shows
a
kind
of
sentiment
right
so
very
quickly.
What
we
did
here
is
we
used
one
of
the
ai
service
right
comprehend
to
do
sentiment,
analysis
that
reused
the
aws.net
sdk
and
call
the
different
methods
on
the
comprehend
to
get
language
entities
different
key
phrases
and
also
sentiments
right.
We
can
do
similar
exercise
for
different
set
of
operations
right
here
you
go.
B
This
is
translate
same
thing
right
and
take
the
language
in
english
and
do
the
translations
in
different
set
of
files
right.
I
could
transcribe
same
drill,
take
a
file
and
then
transcribe
it.
If
you're,
given
a
media
it'll,
do
the
transcription
recognition
again
give
a
image.
It
will
be
able
to
find
out
faces
it
can
find
out
attributes,
and
after
that
you
can
have
your
own
additional
use
cases
right.
That
was
a
very
quick
example
of
ai
integration
inside
your
application.
B
Typical
pattern,
if
you
see
here
the
same
thing,
the
the
amazon
and
instead
of
translate,
you
can
say
comprehend,
client,
instead
of
so
that
it's
the
same
thing,
give
the
input,
what
input
it
would
need
in
this
case
it
needs
to
text
and
then
call
the
corresponding
functions
right,
so
that
that
brings
me
to
the
to
the
summary
of
the
discussions.
Today
we
started
with
a
toolkit.
Let
me
quickly
repeat
the
things
that
we
have
seen.
We
started
with
extensions
right,
remember:
aws
toolkit!
B
B
Once
you
have
connected
you're
able
to
see
your
resources
and
you're
able
to
manipulate
those
resources
right
inside
visual
studio,
once
you've
installed,
the
toolkit
you're
able
to
see
a
different
set
of
deployment,
wizards
pop
up
right
right
click
based
deployment
right
that
that
comes
up
here.
You
also
see
boilerplate
templates
for
aws
platform
right
here
you
go,
you
can
see
the
serverless
application
and
I
may
actually
have
a
serverless
application
here.
You
go
this
one.
I
created
quickly
very
simple
api,
hello
meetup.
So
if
we
give
you
a
mock
tool,
also.
B
So
here
is
the
mocking
tool.
I
can
execute
it,
and
here
is
the
so
I
can.
I
can
actually
do
a
quick,
debugging
and
client
side
for
serverless
application.
Once
I
am
done,
I
can
do
a
right
click
and
do
a
publish
right
choose
the
region
where
you
want
to
deploy
and
publish
the
application
right.
So
we
give
you
that
right,
click
publish
is
also
available
via
dotnet
cli
extensions.
B
So,
let's
say:
if
you
have
a
ci
cd
pipeline,
you
can
call
those
to
simulate
the
same
right
click
deploy
in
your
devsecops
pipeline
right.
We
saw
that
there
are
three
different
abstraction
tiers
for
compute
on
aws,
ec2
containers
and
and
serverless
lambda
functions.
We
saw
that
typically,
if
you
have
a
dotnet
framework
based
application,
you
first
do
an
analysis.
Using
we
gave
you
two
tools.
One
is
supporting
assistantfor.net,
which
analyzes
and
gives
you
detailed
information
on
dependency
graph.
B
It
shows
you
the
nougat
packages
compatible
incompatible
and
also
shows
you
actual
cs
file
where
those
incompatible
apis
are
being
called
right.
Helps.
You
understand
the
level
of
effort
that
it
would
take
to
port
that
dotnet
framework
based
application
to
dotnet
core
or
not
five,
the
sec
tool
that
we
quickly
discussed
was
the
app
to
container.
B
So
if
you
have
a
legacy,
dotnet
framework
based
application,
think
of
it
like
iis
machine
where
you
can
deploy
app
to
container
it,
will
go
through,
find
out
all
the
applications
deployed
on
the
iis
and
can
automatically
auto
containerize
those
application
onto
aws.
You
do
not
have
to
understand
the
underpinnings
of
let's
say:
ecs,
the
elastic
container
service
that
we
have
has
service
tasks
and
underlying
manipulations.
Those
are
all
abstracted
from
you.
B
It
will
give
you
the
endpoint
published
once
the
application
is
deployed
right
and
last
we
looked
at
modernization
does
not
mean
just
going
to
the
different
abstraction
tier.
It
also
means
enriching
your
application.
You
can
keep
your
dot
net
framework
based
application
on
prem
and
add
newer
use
cases
right.
We
discussed
a
simple
thing
like
maybe
I
want
to
use
one
of
the
ai
services
right
and
enrich
those
once
the
application
is
on
aws.
You
can
enrich
more,
like
maybe
the
data
we
can
actually
integrate
with
quicksite
and
get
a
bi
dashboard
created
right.
B
So
you
can
mod
continuously
modernize
the
application
and
add
newer
use
cases
and
enrich
the
application
continuously.
I'll.
Give
you
another
example:
chatbots
right,
I
see
many
customers
actually
adding
chat
bots
in
their
application.
Very
simple,
like
there
are
always
list
of
questions
that
users
will
have
and
you
can
automatically
using
lex
right.
You
could
also
do
a
voice
based
integrations
like
most
of
the
time,
your
click
and
mouse
paste.
You
can
also
integrate
with
voice
based
integration
right.
B
Maybe
there
is
an
alexa
skill
that
calls
the
same
api
for
your
application.
So
there
are
many
many
use
cases
that
you
will
keep
on
thinking
once
you
start
exploring
different
services
offerings
that
are
available.
Okay
with
that,
I
want
to
give
you
resources,
because
I
know
in
in
an
hour
it's
very
hard
to
actually
learn
all
all
the
things.
Right
I
mean
there's.
This
is
just
a
start,
the
first
thing
and
this
I
this
deck
will
be
shared.
B
You
can
you
can
use
this
deck,
and
the
first
thing
I
want
to
share
is
the
you
want
to
bookmark
the
aws.amazon.com
net.
So
if
you
do
this,
that
takes
you
here
same
thing:
developer
language
net.
So
this
is
our
home
page,
all
things.net.
On
aws,
we
have
step
by
step
guides,
we
have
code
samples
and-
and
you
can
start
exploring
the
same
right
once
you
go
in
you'll-
find
different
code
samples
for
different
area
right.
That's
the
first
thing
that
you
want
to
start.
B
B
B
So
we
have
a
very
detailed
youtube:
video
library
for
each
services
with
code
samples,
walkthroughs
right
understanding,
those
this
this
would
be
significant
resource
and
we
keep
publishing
to
the
same
channel
pretty
much
on
on
a
bi-weekly
or
monthly
basis,
and
the
last
is
another
resource
if
you
are
looking
to
go
more
deeper
into
this.net
on
aws,
this
is
an
immersion
day
and
I'll
share
the
link
for
this.
It
goes
through
across
different
tiers,
like
starting
with
the
toolkit.
How
do
you
configure
it
step
by
step?
B
Then
we
give
you
ability
to
deploy
the
application.
We
saw
the
bean
stock
step
by
step.
Then
we
give
you
containers
serverless
right,
so
this
is
basically
think
of
it,
like
a
step
by
step,
help
you
and
different
use
cases
that
can
be
added
on
the
same
right.
So
this
workshop
will
be
helpful
if
you're
looking
to
go
more
deeper
on
all
things
dotnet
on
aws.
B
B
B
Me,
okay,
I
see
a
question
from
karan
kathani.
Could
we
get
some
link
to
sample
project?
Yes,
so
I
I
will
share
the
link.
I
will.
What
I'll
be
doing
is
the
deck
that
I
went
through?
I
am
going
to
share
the
pdf
version
of
the
deck,
which
has
all
the
links
to
the
different
resources
that
I
have
shown,
and
it
also
has
linked
to
the
the
immersion
day,
wherein
you
can
actually
go
through.
B
B
B
B
A
A
A
B
A
B
A
B
B
If
you
can
see
different
metrics
using
cloudwatch,
I
showed
you
app
insights
and
it
creates
a
dashboard.
That's
very
useful,
depending
on
a
specific
use
case.
I
may
be
able
to
help
you
more,
but
starting
with
having
the
x-ray
integration
in
your
application.
Having
the
cloud
watch
app
insights
integration
gets
you
going
like
pretty
easily
to
see
what's
happening
in
the
logs
right.
A
Okay,
so
I
also
had
another
questions:
this
is
more
around
the
ci
cd
right
and
so
what
kind
of
support
do
we
have
on
github
actions?
I
know
you
touched
upon
azure
devops.
Are
there
ready-made
templates
or
the
actions
available
for
anyone
to
consume,
to
deploy
things
into?
Let's
say
I
want
to
deploy
a
lambda
into
aws
lambda
right.
How
do
I
get
started
within
github
action
specifically.
B
So
we
had
a
like
pretty
detailed
list
of
tasks
published
in
the
azure
devops
pipeline,
like
if
you
go
to
the
azure,
dev
ops
and
there.
If
you
see
custom
tasks,
if
we
have
aws
public
once
we
enable
the
aws
extension,
we
give
you
ability
to
integrate
with
either
aws
code
suite
services
or
integrate
with
our
infrastructure
as
a
code
like
a
cloud
formation,
so
we
have
published
good
amount
of
tasks
there
right
and
specifically
talking
about
github
actions.
B
And
I
can
share
some
details
of
that
toolkit.
We
have
a
toolkit
for
azure
devops,
specifically,
which
which
publishes
both
like
a
higher
level.
Also
like.
Let's
take
an
example,
you
have
a
file
in
azure
devops.
You
want
to
upload
to
s3.
We
actually
have
a
s3
upload
task,
so,
instead
of
actually
doing
a
cli
call
or
a
powershell
call
or
a
script,
you
actually
just
use
that
higher
level
task
and
that
abstracts
the
actual
call.
B
A
Yeah
right,
I
was
just
gonna
touch
upon
that
yeah,
so
we
are
gonna
have
we
are
having
a
very
quiz?
Basically
with
five
questions.
I
think
tough
in
it
so
yeah.
If
you
follow
through
the
session
of
amit,
you
could
very
well
easily.
You
know
answer
those
so
I'll
just
bring
that
a
link
and
then
five
winners
of
that
quiz
would
be.
You
know
eligible
to
get
free
credits
right
so
dave.
Do
you?
Okay.
Let
me
share
my
screen
and.
A
Since
it's
virtual,
I
have
to
collect
your
email
id.
So
don't
worry,
it's
not
going
to
go
anywhere
else.
This
is
going
to
be
purely
used
for
communicating
with
you
for
sharing
these
goodies.
Okay,
so
yeah.
So
please,
and
as
this
happens,
you
can
also
please
post
your
questions
and
then
we
would
continue
to
you
know,
answer
them,
because
we
reserved
quite
a
good
amount
of
time
for
the
q
and
d.
So
we
want
to
make
it
more
interactive.
A
B
Okay,
I
see
a
couple
of
questions
on
the
comment
side
pinder,
how
much
time
you
think
it
would
take
to
get
grip
off
aws,
specifically
from
net
developers,
point
of
view.
Okay,
that's
that's
a
little
hard.
One
time
is
subjective
and
everybody
has
their
own
learning
speed
how
they
learn
like
I
learned
by
looking
at
sample
projects
and
understanding
the
code,
but
there
is
definitely
initially
like
you
want
to
understand
the
if
you
are
not
if
you
are
completely
new
to
cloud.
B
Obviously
there
is
a
just
a
mental
model
in
terms
of
on-prem
to
cloud
right.
The
resources
are
being
created
in
the
on-prem
world.
Usually
infrastructure's
code
is
kind
of
missing,
so
that
layer
comes
up
in
aws
so
or
any
cloud
provider,
so
understanding
the
abstraction,
be
it
arm
templates
or
clock
formation,
templates
or
terraform
scripts
right
that
you
have
to
consider
and
depending
on
what
is
the
use
case,
you
are
looking
to
build
if
it
is
a
simple
web
application
web
services.
The
learning
curve
is
much
much
quick
like
pretty
much
your
map.
B
Is
it
serverless?
Okay,
api
gateway,
lambda,
and
there
are
a
few
set
of
services
that
you
want
to
learn
like
application
developer,
oriented
services,
let's
say:
you're,
building
a
data
lake
on
aws.
In
that
case
there
is
other
set
of
services
that
you
have
to
understand.
So,
depending
on
the
use
case,
you
would
have
different
set
of
services
to
understand,
but
in
a
ground
up
we
have
a
pretty
detailed
what
you
call
study
guide
of-
and
I
can
I
can
share
that
with
swami
too.
You
want
to
start.
B
We
have
different
certifications
levels
also,
so
you
start
with
the
practitioner
level
certification,
and
then
we
have
an
associate
basically
developer
as
well
as
a
solution.
Architect,
certification,
if
you
are
looking
to
also
get
certified
so
that's
another
part
best
according
to
me,
is
basically
start
building
something
like
once.
You
start
building
something
you
will
start
exploring.
B
You
will
start
hitting
issues
and
that's
that's
how
you
probably
learned
and
within
I
would
say,
consistent
if
you're,
giving
a
good
amount
of
time
getting
your
serverless
application
onto
aws
will
be
pretty
quick,
but
have
the
roadmap
to
learn
other
services
where
you
can
enrich
your
applications
right.
I
can't
give
you
a
specific
six
months
or
one
year.
Sometimes
it
can
take
more
because
getting
a
mastery,
it's
it's
I
mean
I
myself
go
to
customer.
I
have
many
times.
I
don't
know
I
mean.
B
Obviously
nobody
can
know
so
many
different
services
and
it's
not
about
the
services.
It's
also
the
depth
of
features
inside
those
services.
Right,
sometimes
you
know
the
service
at
the
high
level,
but
then
the
detailed
feature
it
takes
time
to
learn
so
have
a
multi-year
road
map
getting
a
dev,
hands-on,
dirty,
very
quick.
You
should
be
able
to
get
moving
and
then,
depending
on
use
cases
you
want
to
do
aiml
you
want
to
do
data.
Take
you
want
to
do
contact
sector.
You
want
to
do
so.
A
Things
so
the
primary
thing
is,
you
understand
the
cloud
architecture
principle.
So
that's
the
thing
which
is
the
mindset
and
the
cloud
architecture
principles
is
what
we
need
to
learn
first
and
then,
once
you
have
that
grip
of
it,
because
these
offerings
keep
evolving
at
a
very
rapid
pace
right,
whatever
it
was
available
to
today,
would
be
like
it,
it
might
become.
You
know,
obsolete
to
think
of
that
to
call
it
that
way
right.
A
So
it
things
keep
changing
in
a
much
rapid
pace
in
the
offering
perspective,
also
right
so,
but
what
would
remain
is
the
cloud
architecture,
principles
and
on
the
basic
concepts
of
how
the
entire
cloud
infrastructure
everything
works.
Right,
so
get
that
understanding
first
and
then
it
would
be.
You
know
you
can
definitely
build
on
top
of
that
yeah.
B
Yeah
yeah
yeah,
I
would
I
would.
I
would
definitely
second
that
what
he
mentioned,
understanding
that
we
have
something
called
a
well
architected
guideline
and
well
architected
paper.
If
you
search
aws
well
architected
principles,
it's
a
pretty
neat
white
paper
to
understand
best
practices
across
different
pillars:
security,
resiliency
operations,
availability,
so
understanding
going
through.
That
would
give
you
a
good
amount
of
understanding
on
on
the
the
cloud-based
architecture
principles.
B
Right
I
mean
I
think
somebody
mentioned
serverless.
So
let's
say
you
move
to
microservices
completely.
Once
you
move
to
microservices,
there
are
some
sort
of
things
that
you
have
to
think
like
hey
now
that
everybody's
calling
over
network.
What
if
network,
is
down
so
should
I
have
a
kind
of
a
retries
there's
a
principle
called
exponential
back
off
like
try,
wait,
try
wait
double
the
amount
of
time,
then
retry
right
in
cloud.
There
is
something
called
eventually
consistent
and
strongly
consistent.
Remember
on-prem!
You
moved
from
single
thread
to
multi-threaded.
You
were
like.
B
Oh
this
variable.
Did
it
change
or
not
another
thread?
Similarly,
when
you
are
working
with
services
which
are
eventually
consistent
in
that
case,
the
read
may
not
give
you
the
latest
copy
strongly
consistent
will
definitely
give
you
again.
That's
that's.
That's
you
have
to
handle
that
in
in
your
code,
we
are
moving
towards
from
a
single
purpose,
driven
kind
of
a
storage
to
single
storage,
to
a
purpose-driven
storage,
so
understanding
different
use
cases
for
your
micro
services,
mapping
to
the
right
data
tier.
Let's
say
I
have
a
time
stream
data.
B
Should
I
put
that
in
rdbms
and
do
all
kinds
of
complex
correlated
sub
query,
or
should
I
actually
use
a
time
stream
based
database
rights
makes
it
much
simpler.
So,
as
you
see
it,
it'll
keep
on
end.
You
won't
believe,
like
my
home
page
in
browser
is
aws
what's
new,
because
I
don't
know
what
got
launched
last
night.
B
A
B
Oh
yeah,
so
blazer
is
an
interesting
development
like
I
remember
the
days
of
silverlight
and
activex
and
applet
on
the
client
side
and
laser
seems
promising.
I
should
say
that
so
we
have
another
service
called
amplify
for
mobile-based
development
right
if
you
haven't
explored
that
that's
also
another
react
view
and
other
set
of
services.
Currently
we
have
a
different
set
of
server-side
back-end
services
that
you
would
integrate
with
laser.
Let's
say
you
want
to
do
authentication
authorization
in
your
bazer
application.
You
can
use
cognito,
which
is
oauth
based,
authentication
provider.
B
You
can
call
our
api
gateway.
You
can
call
our
appsync
based
so
graphql
kind
of
integration,
but
we
are
looking
to
actually
integrate
more
natively
in
on
blazer,
so
there
might
be
few
developments
at
this
moment.
I
see
on
on
either
a
mobile
applications
via
amplify
or
xamarin
based
applications
and
classic
html
javascript
based
application
connecting
to
api
gateway,
appsync
and
and
using
cognito
and
other
api
services
for
the
back-end
based
operations.
A
A
You
can
save
your
application
right
if
you're,
building
and
blaze,
your
washing
based
application,
but
if
in
case
you're
building
a
blazer,
asp.net
core
hosted
application,
then
obviously,
like
whatever
the
hosting
service
you
have
on
aws,
you
need
to
host
and
say
that
and
then
your
app
will
be
served
right.
So
it
depends
on
the
workload.
But
serverless
is
not
really
really.
I
wouldn't
say
it's
not
really
for
this,
but
for
an
blazer
application.
A
That's
if
you
want
to
you
know,
be
part
part
of
the
jetbrains
raffle
right.
Otherwise
also,
I
was
just
thinking
to
you
know,
have
a
bit
of
an
interactive
user.
So
if
can
can
you
please
log
in
or
open
your
browser
and
then
go
to
www.mentee.com
and
use
this
code
and
you'll
be
given
this
question
about
tell
us
your
feedback
about
the
event
in
single
word
right.
Can
you
please
start
adding?
A
I
mean
providing
your
feedback
as
I
collate
the
results
and
then
I'll
I'll
publish
the
winner
soon,
yeah,
so
good,
bad
ugly.
Whatever
be
it
please
open
up,
and
then
it's
it's.
We
want
to
hear.
How
can
it
feedback
about
the
event
right
and
if
you
have
any
detailed
feedback,
please
go
ahead
and
fill
in
the
feedback
form
and
then
yeah.
We
would
use
that
to
improvise
in
the
next
time
right.
B
Yeah
with
that,
I
want
to
take
a
moment
and
thank
everyone
for
joining
today,
and
thanks
swami
and
team.net
foundation
for
hosting
me
today
definitely
enjoyed
presenting
and
look
forward
to
depending
on
the
feedback
like
hey.
Maybe
we
want
to
do
a
workshop.
Maybe
we
want
to
do
a
one
use
case,
end-to-end
deep
dive.
I
may
look
to
come
back
with
swami
and
and
present
more
sessions.
A
Yeah
absolutely
amit.
Thank
you
so
much.
It
was
really
very
informative
and
I
know
a
lot
of
questions
would
be
there
and
we
can't
definitely,
you
know,
fill
in
the
entire
list
of
dotnet
developers
in
one
hour
and
half
hours
yeah.
So
we
would
definitely
get
the
feedback
from
the
audience
and
then,
whatever
the
you
know,
further
topics
of
interest
are
that
we
will.
We
will
should
you
leave
for
for
the
sessions
yeah.
B
B
The
question
is:
if
you
use
cognito
and
security
groups
in
azure
ad,
come
across
using
saml,
is
there
still
a
limitation
on
the
size?
Our
security
group
in
azure
80
is
too
large
for
cognito,
using
saml,
okay.
So
for
the
folks
who
may
be
new
to
this,
space,
authentication
has
two
flavors
right.
There's
a
federation
and
there
is
oauth
saml-
is
used
mostly
for
the
enterprise
kind
of
use
cases
where
active
directory
or
azure
id
or
other
kind
of
a
saml
based
provider.
B
So
in
that
case,
once
the
authentication
is
done,
it
generates
what
is
called
saml
assertion.
It's
a
xml
based
representation
right
and
that
assertion
will
have
information
about
the
authenticated
user.
So
in
this
case
dns
use
case
she
wants
to
bring
in
the
security
group
information
into
that
assertion.
So
assertion
can
get
bigger
depending
on
the
amount
of
security
groups.
The
user
is
member
or
part
of
right,
so
there
is
a
size
limit
that
that
probably
is
being
hit
so
deanna.
B
B
Either
you
do
a
security
group
based
or
you
do
a
user
attributes
based
mapping.
If
it
is
pretty
large,
I
don't
know
5000
or
is
there
a
character
limit?
In
that
case,
you
may
look
to
either
see
if
you
can
get
that
information
in
a
club
manner
right.
Can
there
be
a
bit
representation
for
each
of
the
information
with
specific
to
cognito?
I
have
to
see
the
limit,
so
I'm
not
very
sure
on
what
that
limit
is
so
I'll.
Come
back
on
that
with
you
saw
me.
A
A
B
A
A
A
Okay,
so
it
was
pretty
straightforward
and
it's
mahadev
shivraj
jotapa.
So
congratulations!
So
I
will
share
you
and
jetbrains
toolbox
license,
so
that
will
I'll
also
share
with
you,
the
you
know
the
steps
to
redeem
the
particular
license
and
then
yeah
you
could
use
that
yeah.
Okay,
all
right!
Thank
you!
So
much
guys.
Thank
you
so
much
for
taking
time
on
a
week
week
day,
some
of
you
maybe
have
joined
before
the
office.
Some
of
you
have
joined
after
your
office.