Bug 1896919

Summary:	start creating new-style Secrets for AWS
Product:	OpenShift Container Platform	Reporter:	Joel Diaz <jdiaz>
Component:	Cloud Credential Operator	Assignee:	Joel Diaz <jdiaz>
Status:	CLOSED ERRATA	QA Contact:	wang lin <lwan>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.6.z	CC:	dgoodwin, lwan
Target Milestone:	---	Keywords:	UpcomingSprint
Target Release:	4.6.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1896918	Environment:
Last Closed:	2021-02-08 13:50:51 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1896918
Bug Blocks:

Description Joel Diaz 2020-11-11 20:47:30 UTC

+++ This bug was initially created as a clone of Bug #1896918 +++

Description of problem:
Going forward, CCO needs to create Secrets containing AWS credentials/configuration into a new 'credentials' field in the Secret.
It must continue to populate the legacy aws_access_key_id and aws_secret_access_key, but it will now build a valid AWS configuration file with the same credentials information:

[default]
aws_access_key_id = ACCESSKEY
aws_secret_access_key = secretkey

Comment 6 errata-xmlrpc 2021-02-08 13:50:51 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 4.6.16 security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:0308