Eddie Knight

@mcleo-d, getting input from the FINOS members should be the first item picked up by the relevant working group outlined in #272

:wave: :shipit:

- Part of #254 - Relates to #271 in that we need to adjust how we're doing out releases to avoid this type of issue being repetetive - Relates to...

👋 :shipit:

I suspect @maoo can help us find the info we need to plan this out

RFC @maoo It looks like we just need these three elements to prepare an infrastructure for the legend deployment... could you take a look to see if we missed anything...

Thanks @maoo! @thinkl33t @AdrianHammond @ml4 For the development purposes, it looks like we'll just need to finalize EKS and set up a Mongo child module. For dev/test purposes we'll follow...

@thinkl33t could you link any associated RI WG issues to this epic?

FYI, you can nowview the CLOMonitor stats for this project on the UI: https://clomonitor.io/projects/cncf/cloud-provider-aws#cloud-provider-aws_security

Created a parent / epic to keep track of this #298