Actually, I'd prefer we not expand use of that second "community-cloud" account, Dusty. Especially since we seem to be in an uncertain state for it pretty much constantly as our friends at AWS try to work out how to get it into their community umbrella.Instead, Adam should make use of the existing Fedora AWS account where we can delegate access via IAM and using roles. Check in with the infra team -- they can follow an SOP to make roles, but you'll still need to work with them to tag some resources and set up a policy so you can play in the right sandbox._______________________________________________On Fri, Sep 13, 2019 at 4:56 PM Dusty Mabe <firstname.lastname@example.org> wrote:
On 9/13/19 4:51 PM, Adam Williamson wrote:
> On Fri, 2019-09-13 at 16:25 -0400, Dusty Mabe wrote:
>> On 9/13/19 3:44 PM, Adam Williamson wrote:
>>> Hi folks! We're currently still discussing adjusting the release
>>> criteria to explicitly require Fedora releases to boot in EC2. Someone
>>> pointed out that if we're going to require that, it would be good if we
>>> had an account allowing EC2 access for testing, so individual Fedora
>>> testers don't have to potentially pay out-of-pocket just to test Fedora
>>> works in EC2. Does anyone know if we have an existing arrangement with
>>> Amazon for this? Thanks!
>> cc Paul Frields
>> I have access to an account I think we use explicitly for testing Fedora in AWS.
>> Adam, if Paul doesn't point out any reason not to I can hand you some credentials.
> It'd be better for it to be something more robust and 'team-accessible'
> than just people emailing each other passwords, ideally :)
Encrypted of course :-P
It would be better to have it be something more managed but I don't have anything
more robust that I can offer right now. Maybe fedora infra does.
cloud mailing list -- email@example.com
To unsubscribe send an email to firstname.lastname@example.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://email@example.com