[jboss-jira] [JBoss JIRA] (SWSQE-567) OCP 4.0 provisioning on AWS
Matt Mahoney (Jira)
issues at jboss.org
Fri Jan 25 10:59:00 EST 2019
[ https://issues.jboss.org/browse/SWSQE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687718#comment-13687718 ]
Matt Mahoney commented on SWSQE-567:
------------------------------------
Helpful nodes:
1) confirm that your API key / value is correctly specified in ~/.aws/credentials. It should look something like this:
[openshift-qe]
aws_access_key_id = AKIAXXXXXXXXXXXXX
aws_secret_access_key = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Run something on the command line to confirm that:
sudo dnf install awscli
aws --profile=openshift-qe --region=us-east-2 ec2 describe-vpcs
You'll either see a big list of info (good) or a permission denied error. If you get an error, then double check that your credentials file looks similar to the above. Sometimes people accidentally leave off characters or add extra ones.
2) If that fails, you can provision yourself a new API key ID / secret pair. Log into the console and visit:
Services --> IAM --> Users --> [your username] --> Security Credentials tab, and you'll see a place to generate a new API key / secret. Once you've done that, place it into your ~/.aws/credentials file, and remove the old API key (because you can only have a maximum of 2).
> OCP 4.0 provisioning on AWS
> ---------------------------
>
> Key: SWSQE-567
> URL: https://issues.jboss.org/browse/SWSQE-567
> Project: Kiali QE
> Issue Type: Sub-task
> Reporter: Matt Mahoney
> Assignee: Matt Mahoney
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
More information about the jboss-jira
mailing list