Description of problem:
While creating an EC2 Computer Resource (CR), you can download the SSH keys, but not afterwards.
Asking users to search the database is not user friendly.
Version-Release number of selected component (if applicable):
Sat6.7 Snap 9
[root@dell-r330-12 ~]# rpm -q satellite
Steps to Reproduce:
1. start the config procedure set up as per guide 
2. Before you "Click Submit to save the Amazon EC2 connection", notice SSH keys are downloadable
3. After you "Click Submit to save the Amazon EC2 connection", notice SSH keys are no longer downloadable
SSH keys are no longer downloadable after EC2 CR creation
SSH keys are still downloadable after EC2 CR creation
Created attachment 1654028 [details]
Two SSH keys showing on the SSH tab for EC2 CR
How did you manage to create two keys?
(In reply to Stephen Wadeley from comment #2)
> Created attachment 1654028 [details]
> Two SSH keys showing on the SSH tab for EC2 CR
> Hello Melanie
> How did you manage to create two keys?
Perhaps another bug for you, Stephen.
When you delete the CR and recreate using the same AWS keys, the old SSH appear within the second CR, but I suspect that might be because the keys are the same. I have no idea if there is any value to keeping this stored in memory after the CR is deleted. I suspect not. It seems like sub-optimal behaviour.
Re comment 2 and comment 3
Given that behaviour, raising priority
In addition to my comment 11, I have observed the same behaviour on sat 6.6 and probably it may exists on sat 6.5 as well.
That's why I don't think it is regression/blocker.
There is one more BZ around this - https://bugzilla.redhat.com/show_bug.cgi?id=1757656.
I agree that issue exists and requires a fix to make user interface better.
But as key-pair resource is part of all other CRs, I request to reconsider the priority of this BZ to next version.
Removed regression & triage keywords.