Skip to main content

Must use VS Code Extensions for anyone working on Cloud

Here are the list of VS Code extensions that anyone working on cloud technologies can use to speed up their development. 

To download any extension, refer to the extension tab on your VS code window:



As we will manage all our cloud resources using Terraform, we will start with Terraform Autocomplete Extension. 

1. Terraform Extensions


Terraform: to manage terraform resources directly from VS Code. 




Terraform Autocomplete: useful when we are creating terraform resources.



2. Docker: To build, manage and deploy docker containers from VS Code.



3. Python: extension that provides python interpreter



4. Prettier-Code formatter:



5. Markdown Preview: 



6. Git:  

Git History:



Git Graph:





Now we can select the below extensions, and click on install. 


AWS VSCode Extensions:

1. AWS Toolkit: To interact with AWS resources directly from VS Code. Helpful in taking a look of AWS resources without having to login into console, provides us with a very cool UI to get a quick overview of our resources.



Upon successful installation, we can find AWS on the left toolbar as shown below:




2. AWS CLI Configure: To use the AWS profiles directly, will be very handy when we want to use multiple AWS accounts and want to manage them separately. Realtime use-case would be when we want to access AWS resources from different environments like PROD environment or DEV environment.



3. AWS boto3: boto3 is a python library that will help us communicate with AWS resources



4. Sort AWS IAM Policy: will be a lot of help when we want to prepare IAM document especially when we are dealing with too many AWS resources in the same document. Unless they are really sorted, IAM policy can quickly become a mess. 



5. AWS Step Functions Constructor: Helps us to visualize the AWS step functions directly on the VSCode, without having to check the document definition on the console. 




Azure VSCode Extensions:


1. Azure Account:



2. Azure Tools:



The above extension is a package installer - will install or download the following Azure extensions as well:

- Azure Functions

- Azure Resources

- Azure CLI Tools

- Azure App Service

- Azure Resource Manager (ARM) tools

- Azure Databases

- Azure Storage

- Azure Pipelines

- Azure Virtual Machines

- ARM Template Viewer



Google Cloud (GCP) Extensions:


1. Cloud Code: 



2. Google Cloud Spanner Driver:



Labels:

Comments

Post a Comment

Popular posts from this blog

AWS Connect: Reporting and Visualizations

Amazon connect offers: - built in reports i.e., historical and real-time reports.  We can customize these reports, schedule them and can integrate with any BI tool of our requirement to query and view the connect data.  Sample solution provided by AWS: 1. Make sure Connect is exporting the CTR data using Kinesis Data Stream 2. Use Kinesis Firehose to deliver the CTR that are in KDS to S3. (CTR's can be delivered as batch of records, so one s3 object might have multiple CTR's). AWS Lambda is used to add a new line character to each record, which makes object easier to parse.  3. s3 Event Notifications are used to send an event to modify the CTR record and saves it in S3. 4. Athena queries the modified CTR's using SQL. Use partitions to restrict the amount of data scanned by each query, improving performance and reducing cost. Lambda function is used to maintain the partitions.  5. Quicksight is used to visualize the modified CTRs.  Solution variations: Convert re...
Post a Comment
Read more

Databricks: Job aborted due to stage failure. Total size of serialized results is bigger that spark driver memory.

  While running a databricks job, especially running a job with large datasets and longer running queries that creates a lot of temp space - we might be facing below issue if we have a minimal configuration set to the cluster.  The simple way to fix this would be changing the spark driver config in the databricks cluster tab spark.driver.maxResultSize = 100G (change the GB based on your cluster size)
Post a Comment
Read more

Terraform lifecycle

 If we are using terraform, terraform state file is the heart of all the infrastructure that we spin up using terraform templates.  There are several ways to deploy the infrastructure using terraform: 1. Using CLI (setup terraform and then run terraform commands) 2. Automated Build (terraform scripts integrated as part of your jenkins pipeline) No matter of the way we chose, we must make sure that we are using the same terraform state file, so that we are having a sync and proper checklists of the resources that we used.  I would like to share the terraform commands that we do on a daily basis: terraform init = the basic/starting command which initializes the terraform (make sure the proper provider is provided. In my case, I use AWS).  terraform workspace select <workspace name > (creates a new workspace, useful in scenarios where we have different terraform modules - database, servers, logs, storage) terraform state list = shows the list of terraform resour...
Post a Comment
Read more