Create, debug, and deploy Java & Python applications with AWS Toolkit for IntelliJ
The AWS Toolkit for IntelliJ was announced about a year ago at re:Invent and the GA is finally here. Today, we take a look at its features and what you can do with this brand new toolkit.
A year after its initial announcement at re:Invent, the AWS toolkit for IntelliJ is generally available!
According to the official website:
The AWS Toolkit for IntelliJ is an open source plug-in for the IntelliJ IDEA that makes it easier to create, debug, and deploy Java and Python applications on Amazon Web Services.
Among others, the toolkit provides an integrated experience for developing serverless applications, including assistance for getting started, step-through debugging, building, and deploying from the IDE.
Let’s have a look at its features.
What can you do with AWS toolkit for IntelliJ?
Build a serverless application easily – You can set breakpoints and debug serverless applications locally. When building serverless applications with IntelliJ, the default application is composed of a single Lambda function that you can call via HTTP using Amazon API Gateway and it comes with unit tests that make it easy to build high-quality applications.
Run functions locally – When running a function locally, you can edit the configuration to choose the AWS credentials you want to use, the Region (for AWS services used by the function), and the input event to provide. What’s more, you can customize the HTTP request using the syntax described here as well as pass environment variables to customize the behavior of the function.
Debug a function locally – Sometimes it happens that you are not really sure how the location, part of the output message, is computed by an application. Now, you can select the option to debug locally and use the IntelliJ debugger to get a better understanding of my function.
Deploy a serverless application – You can deploy the serverless application in the AWS Region of your choice. Create an S3 bucket to host the deployment packages that the build process creates and this new bucket is automatically created in the AWS Region I selected before. You can reuse the bucket for multiple deployments. If your build process depends on the actual Lambda execution environment, you can choose to run it inside a container to provide the necessary emulation.
Run a function remotely – You can invoke a Lambda function remotely or jump to the source code of the function.
Invoke the HTTP endpoint – To invoke the API via HTTP, you need to know the API endpoint. For example, you can get it from the output of the AWS CloudFormation stack using the AWS CLI.
SEE ALSO: AWS launches Open Distro for Elasticsearch, an Apache 2.0-licensed distribution of Elasticsearch
If you are looking to get started with this tool, you can find all the information you need, from installation guides and prerequisites to the features the AWS Toolkit for JetBrains offers by programming language, head over to the official ‘getting started‘ guide.