Before You Begin
Before you get started using Pulumi, let’s run through a few quick steps to ensure your environment is set up correctly.
Install Pulumi
Install Pulumi on macOS through Homebrew:
$ brew install pulumiInstall Pulumi on Linux by running the installation script:
$ curl -fsSL https://get.pulumi.com | shInstall Pulumi on Windows using elevated permissions through the Chocolatey package manager:
> choco install pulumiFor alternative installation instructions (e.g. script-based installation, binaries, etc.) or troubleshooting, see Download and Install.
Next, install the required language runtime, if you have not already.
Install Language Runtime
Choose Your Language
Install Node.js.
If you're having trouble setting up Node.js up on your machine, see Installing Node.js via Package Manager for alternative installation options.
Install Python version 3.6 or later. To reduce potential issues with setting up your Python environment on Windows or macOS, you should install Python through the official Python installer.
pip is required to install dependencies. If you installed Python from source, with an installer
from python.org, or via
Homebrew you should already have pip.
If Python is installed using your OS package manager, you may have to install pip separately,
see
Installing pip/setuptools/wheel with Linux Package Managers. For example, on Debian/Ubuntu you must run
sudo apt install python3-venv python3-pip.
If you're having trouble setting up Python on your machine, see Python 3 Installation & Setup Guide for detailed installation instructions on various operating systems and distributions.
Install Go.
Install .NET Core 3.1 SDK or later.
Pulumi will need the dotnet executable in order to build and run your Pulumi .NET
application. Ensure that the dotnet executable can be found on your path after
installation.
Finally, configure Pulumi with AWS.
Configure Pulumi to access your AWS account
Pulumi requires cloud credentials to manage and provision resources. You must use an IAM user account that has Programmatic access with rights to deploy and manage resources handled through Pulumi. In this guide, your IAM user must have the s3:CreateBucket IAM policy action granted.
If you have previously installed and configured the AWS CLI, Pulumi will respect and use your configuration settings.
If you do not have the AWS CLI installed or plan on using Pulumi from within a CI/CD pipeline, retrieve your access key ID and secret access key and then set the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables on your workstation.
$ export AWS_ACCESS_KEY_ID=<YOUR_ACCESS_KEY_ID>
$ export AWS_SECRET_ACCESS_KEY=<YOUR_SECRET_ACCESS_KEY>
$ export AWS_ACCESS_KEY_ID=<YOUR_ACCESS_KEY_ID>
$ export AWS_SECRET_ACCESS_KEY=<YOUR_SECRET_ACCESS_KEY>
> $env:AWS_ACCESS_KEY_ID = "<YOUR_ACCESS_KEY_ID>"
> $env:AWS_SECRET_ACCESS_KEY = "<YOUR_SECRET_ACCESS_KEY>"
For additional information on setting and using AWS credentials, see AWS Setup.
Next, you’ll create a new project.
Thank you for your feedback!
If you have a specific, answerable question about how to use Pulumi, ask it in our Community Slack.
Open an issue on GitHub to report a problem or suggest an improvement.
