I don't know what else is needed, but at least I'm missing a preconfigured subnet that I could use under aws-copr user in both us-west-1 and us-west-2. At the same time, I don't have permissions to pre-configure myself.
aws-copr
Metadata Update from @mizdebsk: - Issue tagged with: aws
Please check again. I made a vpc in each of those regions. If you can't see them, then we likely have a permissions issue going on. ;(
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review)
Any news here? Does this look to be working now?
Sorry for delay. I tried 'N. California' now and I still miss "subnet" options on 'Step 3' when creating x86_64. the same problem in Oregon (with both x86_64/aarch64).
Subnets created. :) Please test again.
Nice! Looks like it is working fine now.
Metadata Update from @praiskup: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.