mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
39 lines
1.2 KiB
Plaintext
39 lines
1.2 KiB
Plaintext
// Module included in the following assemblies:
|
|
// oadp-features-plugins-known-issues
|
|
// * backup_and_restore/application_backup_and_restore/troubleshooting/oadp-installation-issues.adoc
|
|
//
|
|
:_mod-docs-content-type: PROCEDURE
|
|
|
|
[id="resolving-incorrect-aws-credentials-issue_{context}"]
|
|
= Resolving incorrect {aws-short} credentials
|
|
|
|
[role="_abstract"]
|
|
If the `credentials-velero` file that is used to create the `Secret` object is incorrectly formatted, multiple errors might occur, including the following examples:
|
|
|
|
* The `oadp-aws-registry` pod log displays the following error message:
|
|
+
|
|
[source,text]
|
|
----
|
|
`InvalidAccessKeyId: The AWS Access Key Id you provided does not exist in our records.`
|
|
----
|
|
|
|
* The `Velero` pod log displays the following error message:
|
|
+
|
|
[source,text]
|
|
----
|
|
NoCredentialProviders: no valid providers in chain.
|
|
----
|
|
|
|
|
|
.Procedure
|
|
|
|
* Ensure that the `credentials-velero` file is correctly formatted, as shown in the following example:
|
|
+
|
|
.Example `credentials-velero` file
|
|
----
|
|
[default] <1>
|
|
aws_access_key_id=AKIAIOSFODNN7EXAMPLE <2>
|
|
aws_secret_access_key=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
|
|
----
|
|
<1> {aws-short} default profile.
|
|
<2> Do not enclose the values with quotation marks (`"`, `'`). |