I endorse this request. I think probably "pyai.fedorainfracloud.org" is okay for experimenting, but assuming this experiment goes well, I'd love to have it more official as "pyai.fedoraproject.org".

@bstinson "As soon as reasonable" might mean different things to different people. As I understand it, there are people ready and itching to go on this project...

So, to clarify, you want a aws group for this?

Does the group need only web console, or do you need cli access as well?

Do you need just ec2? or other services?

The "download location" you just need dns pointed to your resource/instance? Or do you also need space and such?
If you aren't running that part of it, we could just make you a dl.fedoraproject.org/pub/alt/<groupname> space? (that would also be mirrored by any sites that mirror alt)

Web console, and cli access.

We plan on deploying some http shares on ec2 + block storage to serve python package indexes directly and eventually deploying https://devpi.net

ok. EBS is kinda of difficult with our permission model... it requires making the volume and adding it to your policy.

Is 'pyai' an ok name for this? if so, then the group would be 'aws-pyai'.

I will need a freeze break it turns out because I have to add the SAML2 mapping to our auth server thats frozen. I'll put in for that now with the 'aws-pyai' name...

https://pagure.io/fedora-infra/ansible/pull-request/1967

aws-pyai looks perfect

:thumbsup:

ok, sorry for the delay here.

I have created the aws-pyai group, you are in it and a manager of it.
You should be able to reach the console via the saml2 link in https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/aws-access/

The cli/user access is in a file in your homedir on batcave01 called 'pyai'

Please let us know if you need anything further on it...

Do make sure to tag any instances with 'FedoraGroup' 'pyai'