1回答
- 新しい順
- 投票が多い順
- コメントが多い順
0
Check if this applies to you - https://stackoverflow.com/questions/39051477/the-aws-access-key-id-does-not-exist-in-our-records
Check if this applies to you - https://stackoverflow.com/questions/39051477/the-aws-access-key-id-does-not-exist-in-our-records
checked it already it doesnt work for me I cant even connect through cli even if i put new access key and secret key
Have you checked that the user has the necessary permissions to carry out the commands that you tried from the CLI? For example if you tried aws s3 ls command, you need to ensure that the user has the necessary S3 permissions. Otherwise what you are saying does not make much sense. Try creating a Cloud9 and try running the CLI from inside Cloud9 by creating a different user than the one that created the Cloud9 environment and setting this new user's profile in Cloud9.