►
From YouTube: Cloud Custodian Community Meeting 20211026
Description
Our community meeting is public and we encourage users and contributors of Cloud Custodian to attend! You can find the notes for this meeting on our github repo: https://github.com/cloud-custodian/community/discussions
To get an invite to the meeting join the google group and you'll receive one via email: https://groups.google.com/g/cloud-custodian
A
Here
we
go
hello,
everyone,
it
is
october,
26
2021,
and
this
is
the
cloud
custodian
community
meeting
I'll,
be
your
host
today,
george
castro,
just
a
reminder
that
this
meeting
is
under
the
cncf
code
of
conduct.
So
please
be
excellent
to
each
other
and
just
a
reminder
that
we
do
record
these
meetings
and
they
will
be
available
on
youtube
along
with
all
the
notes
after
we
are
done.
So
it's
been
a
while.
A
We
took
a
break
there
for
kubecon
cloud
data
governance's
code
day,
so
we
almost
have
a
in
a
month.
So
we've
got
a
an
agenda
with
a
lot
of
good
stuff
here
to
talk
about
both
kapila
and
mayor's.
Send
their
regards
are
not
a
temple
able
to
attend
today,
but
we'll
be
here
next
time.
So
we
like
to
have
introductions
and
things
like
that.
So
if
it's
your
first
meeting
or
you
want
to
say
hello,
this
is
the
time
where
we
do
that.
B
C
A
A
I
don't
know
if
aj
was
reaching
for
the
mute
button
or
not.
Look
like
you
were
all
right.
Let's
get
started
all
right,
so
I
tossed
the
notes
url.
In
the
side
we
like
to
take
notes
of
everything
that
we
have
and
then
we
check
these
into
github
and
then
I
always
publish
these
notes
on
the
google
group
for
cloud
custodian,
which
you
can
find
a
link
to
on
the
website,
and
things
like
that.
A
So
if
you
could
scroll
down
a
little
bit
liz
to
like
the
agenda
items,
so
we
finished
the
intros
like
we
said,
welcome
back
and
we
have
some
agenda
items
first,
I
want
to
cover
governance's
code
day.
This
happened
last
week
on
tuesday
was
it
last
week,
two
weeks
ago,
two
weeks
ago,
time
flies
as
part
of
cubecon
cloud
nativecon.
A
We
had
incredible
turnout
over
2500
people
representing
over
50
countries.
Many
thanks
to
our
speakers
and
attendees.
I
know
a
lot
of
people
from
our
community
submitted
talks
and
we
were
able
to
get
some
fantastic
content
and
we're
luck
because
we
recorded
everything,
and
so,
if
you
weren't
able
to
attend,
there's
a
link
there
to
the
youtube
playlist
that
has
all
of
the
talks.
A
You
know
you
could
just
link
to
each
one
and
then
here
in
the
notes
I
put
umer,
did
like
a
blog
write-up
of
the
of
the
events.
If
you
want
to
look
for
like
the
summary-
and
he
has
a
link
to
all
the
individual
talks
there
as
well,
so
definitely
check
those
out
something
I
like
to
do
after
large
conferences,
you
can't
ever
watch
enough
because
there's
so
much
content
in
multiple
tracks,
a
pro
tip.
A
If
on
youtube,
you
can
set
your
playback
speed
to
1.25
and
you
can
get
through
a
lot
more
technical
content
quickly.
So
that's
how
I've
been
kind
of
trying
to
make
my
way
through
that
monster
playlist
so
definitely
check
that
out
and
semi-related
state
of
the
custodial.
One
of
those
talks
was
kapila
and
I
kind
of
doing
a
state
of
the
custodian.
A
So
if
you
are
using
custodian-
or
maybe
you
haven't
kept
up
with
development,
what
we
tried
to
do
the
mantra
for
this
talk
was:
let's
try
to
summarize
the
development
that's
been
happening
over
the
past
year.
So,
if
you're
interested
in
maybe
underdeveloped
features
that
you
know
you're
kind
of
wondering
where
they're
happening
or
what
the
state
is
of
azure,
google
kubernetes
all
that
kind
of
sort
of
stuff.
That
is
the
one
talk
I
would
recommend.
If
you
only
watch
one
talk,
that's
probably
the
one
to
watch.
A
So
that
has
a
lot
of
bunch
of
interesting
stuff
and
I
added
it
to
do
there.
I
still
need
to
export
the
slides
to
make
sure
that
we
put
that
there.
I
want
to
put
that
on
the
readme
list,
or
maybe
the
website.
I
don't
know
we
can
think
about
ideas
where
it
makes
sense.
Anybody
have
any
questions
or
comments
about
that
before
we
move
on.
B
A
A
B
A
Follow
along
so
this
is.
This
is
one
where
we
were
in
the
middle
of
getting
a
bunch
of
feedback
here,
and
I
think
I
just
need
to
accept
your
successes,
changes
and
merge
or
accept
your
suggested
changes
and
then
send
it
to
kapil
for
review.
I
think,
is
what
I
meant
to
say.
So
that
is
in
progress
and
for
those
of
you
who
are
not
aware,
we
do
every
friday
liz
and
I
kind
of
spend
an
hour.
A
We
grab
a
thing
that
we
think
is
annoying
in
in
the
documentation
or
maybe
there's
a
bug
report
and
a
user
says
something
is
confusing,
and
then
we
just
do
a
pr
on
the
spot
and
we
try
to
fix
it
documenting
service
drive.
Filters
has
taken
us
quite
a
long
time
because
we
had
to
go
unravel
it's
like
one
of
those
things.
A
B
D
All
right,
I
think
my
main
thing
on
it
was
that
it's
kind
of
like
what
you're
saying
we
just
need
to
get
something
posted
out
there
and
keep
because
there's
a
it's
such
a
big
thing
and
it's
so
easy
to
become
unclear
that
there's
a
pull
to
just
keep
revising
the
heck
out
of
it
and
yeah
yeah.
Let's
just
get
it
up
there,
but
if
anybody
here
has
feedback,
if
anyone's
using
it
for
sure
have
look.
A
Yeah,
I'm
also
really
interested.
I
know
this
is
weird.
I've
never
done
a
git
commit
with
like
a
co-authored
field
and
I'm
really
interested
in
seeing
like
how
that
looks
like
on
like
the
github,
charts
and
stuff.
I
don't
know,
but
we're
figuring
it
out,
it's
great
all
right
anything
else.
Before
we
get
on
to
events.
A
A
So
these
we
normally
do
on
the
regular
monthly
they've
been
on
pause
because
we're
preparing
for
kubecon
and
those
will
definitely
be
starting
up
here
again
in
november.
So
between
now
and
reinvent
and
the
holidays,
we
are
hoping
to
have
at
least
one
more,
but
we
don't
have
a
solid
date
yet,
but
in
the
notes
there
I
have
the
link
and
that's
when
we're
ready
to
do
that.
E
Yep
all
right,
so
I
may
go
to
re-invent,
I'm
still
working
with
my
manager
at
this
time
to
approve
all
the
funds
and
stuff.
My
thing
was,
you
know
I
was
wondering
if
you
can
have
a
workshop
at
the
arraignment.
You
know
how
to
use
the
other
scripts,
you
know
and
then
mailer
or
c7
trail
creator.
You
know
whatever
we
have.
Can
we
hit
those
workshops?
You
know
because
I
have
already
said
before.
E
A
C
C
So
we
cover
like
log
exporters,
c7n,
org,
mailer,
c7n,
trail
creator,
some
stuff,
like
that,
it's
more
at
a
high
level,
but
we
kind
of
show
some
use
cases
what
you
might
use
them
for,
so
that
might
be
a
good
place
to
get
started.
If
you
haven't
seen
that
video,
but
yeah
workshop
would
be
great
to
get
some
people's
hands
on.
E
A
B
So
we
are
actually
in
the
middle
of
planning
like
in
a
dance
class.
That's
going
to
be
covering
c7
and
org
like
more,
not
like
not
hands-on.
Like
a
workshop,
it's
like
a
class
about
it,
we'll
go
through
what
that
configuration
looks
like
and
how
to
use
it,
so
that
will
be
coming
up
in
november
and
in
november
2
right
now.
The
tentative
plan
is
to
roll
those
community
workshops
into
like
re
invent,
so
we
might
be
like
broadcasting.
A
Yeah
well,
and
if
you
are
going
to
be
at
re,
invent
physically,
of
course,
we'll
just
sit
down
and
give
you
a
peel
and
then
we'll
record
it
and
then
we'll
just
put
that
on
youtube.
Maybe
that'll
be
the
way
to
do
it,
but
yeah.
This
is
the
kind
of
feedback
that
that
I've
been
looking
for.
So
now
that
I
know
that
at
least
one
person
would
show
up
to
it.
A
B
D
E
A
All
right
good
to
know
that
kind
of
handles
the
the
formal
agenda,
there's
a
few
more
things
that
that
we
did
want
to
tackle
that
are
in
github,
but
unfortunately,
since
kapil
can't
attend,
he
wanted
to
ensure
that
he
had
a
look
at
those
items.
So
we're
gonna
have
to
pump
those,
but
we
do
have
one
from
jameson
that
is
aws
subnet
resource
add
modify
subnet
action
that
he
wanted
some
feedback
from
the
community
on
and
liz.
C
Yeah,
if
you
could
scroll
down
a
little
bit
there,
we
go
so
this
proposal
for
feature
request
is
to
add
an
action
to
the
aws
subnet
resource
and
that
action
would
be
a
modify.
Subnet
action
which
relates
to
the
ec2
client,
modify,
subnet,
attribute,
block,
203
call
and
the
use
case
around
this
would
be
if
you
have
subnets
throughout
your
accounts,
where
maybe
they
didn't
get
set
up
correctly
or
what
not.
When
they're
you
know
set
to
map
public
ips
on
launch.
C
So
by
adding
the
modify
subnet
action
you'd
be
able
to
do
a
policy
similar
to
this
sample.
One
in
here
where
you
could
scan
all
subnets
find
ones
that
have
the
setting
of
map
public
ip
on
launch
set
to
true,
and
then
it
could
take
an
action
to
modify
those
identified
subnets
to
switch
the
map
public
ip
on
launch
to
false.
C
Therefore,
so
any
new
instances
and
stuff
launched
in
that
subject
would
not
automatically
be
assigned
public
ip
and
therefore
that
by
doing
that,
run
that
policy
that
would
help
secure
some
of
the
infrastructure
a
little
bit
by
default.
Instead
of
having
to
remediate
when
you
see
a
public
ip
pop
up
having
to
shut
it
down
or
remove
it
after
the
fact
just
prevents
it
from
automatically
launching
it
with
those
in
the
first
place.
C
A
B
C
C
D
C
Yeah
but
you
can
you'd
be
able
to
adjust.
You
know:
assigning
ipv6
addresses
on
creation
map
public
ips,
on
launch
the
map,
customer
owned
ip
on
launch
and
then
modify
the
customer
owned,
ipv4
pool
as
well.
So
a
few
different
things
you
can
use
it
for
not
just
for
the
map
public
ip
on
launch,
but
ipv4
and
ipv6
stuff.
C
B
B
This
could
be
really
fun
for
me
to
take
because
it
sounds
like
it's
adding
and
I
know
in
the
contributor
docs.
I
think
that
there's
a
section
on
adding
stuff
like
this,
so
this
would
actually
be
kind
of
fun
and
go
back
to
the
thing
I
have
on
the
backlog
about
the
contributor
docs.
This
could
be
an
opportunity
for
me
to
walk
through
that
doing
that
going
through
the
stocks
and,
like
you
know,
going
through
it
and
seeing
where
we
can
improve
that
documentation
and
it
doesn't
seem
like
it's.
B
D
A
Process
might
just
be
what
kapil
did?
Is
you
put
kind,
slash
enhancement
on
the
label
and
we
call
it
a
day,
and
then
you
know
when
we
need
something
more
complicated,
we'll
do
something
more
complicated,
so
that
might
that
might
be
the
solution,
all
right,
that
pretty
much
wraps
it
up
for
things.
Does
anybody
have
anything
they'd
like
to
add
the
agenda
or
a
question
or
concern
or
anything
before
we
get
give
you
some
time
back.
D
I
would
have
a
quick
call
and
not
even
a
call
to
action,
a
call
to
thought.
I
guess
only
because
of
some
things
that
I've
been
noticing
recently.
I
I
just
came
across
a
an
action
and
james.
I
think
it
was
when
you-
and
I
were
talking
about
like
for
as
three
buckets
when
you
can
set
set
logging,
there's
a
there's,
a
parameter
where
it'll
it's
kind
of
smart,
about
pulling
in
a
bucket
region
and
doing
doing
the
right
thing,
and
there
was
no
example
policy
in
the
docs
that
included
that
option.
D
I
feel
like
that's
a
really
handy
pr,
to
make
an
example
clearer
or
to
add
a
useful
example.
That's
not
obvious,
so
whether
you
bring
it
up
in
getter,
make
a
vr
or
something
it
seems
like
a
really
nice
way.
If
you
just,
you
want
to
contribute
something
and
you're
not
where
to
go,
and
you
don't
know
where
to
go.
A
D
B
D
A
Yeah,
if
you
know
there's
an
example,
you
want
to
fix
and
you
don't
know,
and
you
reach
out
to
us
I'll,
we'll
figure
out
a
time
and
come
to
you
if
you're
right
here,
you
know
if
you're
willing
to
do
the
work.
We
will
come
to
you
on
that
one
but
yeah.
That
is.
That
is
a
great
idea,
call
for
thought.
We
are
using
that
from
now
on.
That
must
that
that
might
be
a
good
section
to
have
there
as
a
regular.
You
know
things
to
think
about
over
the
next
week.
Anything
else.