How to add access keys for aws configuration

Cloud AWS
#1

I’m unable to configure the AWS in VScode . Please provide any resolution

#2

Hi @NikhilSai2407

Which step are you stuck on?
Are you having trouble generating access keys or configuring them on your local machine?

To generate access keys (not recommended for production, but okay for demo or learning purposes):

  1. Go to: https://aws.amazon.com/
  2. Sign up and create a new account (you can use the free 1-year trial).
  3. Go to your AWS Console: https://console.aws.amazon.com/
  4. Click your account name in the top-right corner.
  5. Select Security Credentials from the menu.
  6. Create and download your Access Key (Access Key ID and Secret Access Key).

After you get the access keys, you can use them with tools like AWS CLI or Terraform.
If you need help with configuring them, please let me know which tool you are using.

#3

My aws account is not working, that’swhy i subscribed the kodekloud account with pro subscription.
i am using terraform only ,to create instances and clusters for that i need access keys. so could you please help me resolving the issue

#4

You create access keys exactly the same way in playground.
Log into the playground console following playground instructions and follow Raymond’s instructions from step 4

#5

Screenshot (84)
Screenshot (84)1920×1080 251 KB

after aws configuration also showing the error and i have taken code from

git clone GitHub - hashicorp-education/learn-terraform-modules-create

#6

And for every three hours accout is expiring automatically for that i need to continous with same key for until terraform learn can you please provide any solution

#7

That’s how the playgrounds work – you get a most 3 hours before things are taken down and reset. If you need key pairs that live longer than 3 hours, you can’t use a playground for that. You’d need to resolve whatever issue you have with your personal AWS account to not have that limitation.

#8

If you are running the terraform from your own PC using access keys, you just start a new playground and let the terraform you have written so far redeploy everything which will only take a few minutes. Then you can spend the next 3 hours improving it.

Clearly if you have started a new lab, you will need to delete the state file and change the access keys. Keep the state file local, not in S3 - because you do have to re-do the build.
with each lab.

I created the terraform for the EKS build - and as I’ve described is exactly how I did it because it took me much longer than 3 hours to get right!