Open VS Code and open the command palette as we did in the earlier step. Now that we successfully have setup our credentials profile, we can go ahead and connect to our AWS environment. Paste the access key here and hit Enter:įinally, enter the AWS Secret Key and press Enter to create the Credential profile: In the next step, we need to provide the AWS Access Key that we have created in the previous step. In the command palette, search for AWS and select AWS: Create Credentials Profile: Inside VS Code, open the command palette using the View -> Command Palette. Let us now go ahead and create the shared credential and config files in the VS Code. aws” directory and are named config and credentials, respectively. Byĭefault, these files can be found under the “. The shared AWS config file and the shared AWS credentials file are the ones in which we can store the credential information that we received. Using the shared AWS files that is provided by AWS. We would now need to setup the credentials that we obtained from AWS in the toolkit in VS Code. You can also see that the Access Key ID has been added to the summary and is Active at the moment:įigure 7 – Access Key Added Setting up the AWS credentials in Visual Studio Code Secret Access Key to a secure location and click on Close. Once you click on Create access key, a new popup window will open up in which you will get toĭownload the CSV file containing the credentials. Navigate to the Security Credentials page and select Create access key: On the Users page, click on the username to see the details: Navigate to the IAM section on the AWS Management Console at and choose Users: Let us go ahead and generate these credentials from the AWS Console. It consists of two parts – the Access Key ID and the Access Key Secret. The AWS Access Key is a specific type of credential that allows us to programmatically access the AWS Two-step process, in which first we obtain AWS Access Keys from the AWS console and then set up the credentials in VSĬode. Using an external credential process (not supported by amazon) – This process can be used if you have a process that generates or lookup the credentials not directly supported by Amazonįor the sake of this tutorial, we will go ahead with the AWS Supported Credentials.Using the AWS supported credentials – These can be provided by Amazon directly using a shared AWS credential file or a shared AWS config file.There are two process in which we can obtain the credentials and use it with VS Code. Now that we have installed the AWS Toolkit extension for VS Code, the next step here is to setup the credentials toĬonnect to the AWS. Obtaining the credentials for AWS Toolkit Next is to connect to our AWS account using specific credentials, which I be explaining in the later section of this YouĬan use it to access all the resources available under your AWS account. Once the toolkit is installed on your machine, you can see a new icon will appear on the sidebar on the left. Select it andįigure 2 – Install AWS Toolkit for Visual Studio Code The very first item on the list will be the AWS Toolkit extension. On the search box, search for “ AWS Toolkit”Īnd hit Enter. Installed on your machine, open it, and click on the Extensions icon available in the left pane ofįigure 1 – Extensions for Visual Studio Code Let us now go ahead and install the AWS Toolkit for Visual Studio Code. Docker – This is also not mandatory for the toolkit, but if you want to test your serverless application locally using the SAM CLI, then it is necessary to have docker installed.Although it is not mandatory for the toolkit, but still it is recommended to install it on the local machine AWS SAM CLI – This is a command line utility from Amazon that enables us to develop and test our serverless applications locally.Code Development SDK – You need to install the relevant SDK that you are going to use to code your application. VS Code is available for Windows, Linux, and Mac Visual Studio Code – You need to download and install Visual Studio Code in your machine. Navigate to to get started with Amazon Web Services
0 Comments
Leave a Reply. |