The Amazon Web Services (AWS) provider for Pulumi can be used to provision any of the cloud resources available in AWS. The AWS provider must be configured with credentials to deploy and update resources in AWS.
See the full API documentation for complete details of the available AWS provider APIs.
The AWS provider supports several options for providing access to AWS credentials. See AWS setup page for details.
The quickest way to get started with AWS is to follow the Get Started guide.
Additionally, there are several tutorials available to follow:
- Containers on ECS “Fargate”: Deploy containers to Amazon
- EC2 Linux WebServer VM: Create an EC2 Linux Web Server virtual machine
- Serverless REST API Gateways using Lambda: Create simple RESTful web server using AWS Lambdas
- Serve a Static Website from S3: Serve a static website out of content in an S3 bucket
- Serverless + Containers + Infrastructure: Deploy a complete application using a combination of buckets, serverless functions and containers.
In addition to the tutorials, several interesting examples are available complete with instructions:
- Ruby on Rails in EC2: Run a Ruby on Rails WebServer using EC2 instances
- SQS-Triggered Lambdas: Post to Slack using a Lambda anytime a SQS message arrives
- Static Website in CloudFront and S3: Create a static website serving content out of S3, fronted by a CloudFront CDN
- Provision an Elastic Kubernetes Service Cluster: Stand up a managed EKS cluster
Introducing Pulumi Crosswalk for AWS
Use Pulumi Crosswalk for AWS to easily use the best of what AWS has to offer, with well-architected best practices, for the entire AWS cloud. Go to production with containers, Kubernetes, and serverless applications.
const aws = require("@pulumi/aws"); const bucket = new aws.s3.Bucket("mybucket");
You can find additional examples of using AWS in the Pulumi examples repo.
The following packages are available in package managers:
The AWS provider is open source and available in the pulumi/pulumi-aws repo.
The AWS provider accepts the following configuration settings. These can be provided to the default AWS provider via
pulumi config set aws:<option>, or passed to the constructor of
new aws.Provider to construct a specific instance of the AWS provider.
region: (Required) The region where AWS operations will take place. Examples are
accessKey: (Optional) The access key for API operations. You can retrieve this from the ‘Security & Credentials’ section of the AWS console.
dynamodbEndpoint: (Optional) Use this to override the default endpoint URL constructed from the
region. It’s typically used to connect to dynamodb-local.
insecure: (Optional) Explicitly allow the provider to perform “insecure” SSL requests. If omitted, the default value is
kinesisEndpoint: (Optional) Use this to override the default endpoint URL constructed from the
region. It’s typically used to connect to kinesalite.
maxRetries: (Optional) The maximum number of times an AWS API request is being executed. If the API request still fails, an error is thrown.
profile: (Optional) The profile for API operations. If not set, the default profile created with
aws configurewill be used.
s3ForcePathStyle: (Optional) Set this to true to force the request to use path-style addressing, i.e.,
http://s3.amazonaws.com/BUCKET/KEY. By default, the S3 client will use virtual hosted bucket addressing when possible (
http://BUCKET.s3.amazonaws.com/KEY). Specific to the Amazon S3 service.
secretKey: (Optional) The secret key for API operations. You can retrieve this from the ‘Security & Credentials’ section of the AWS console.
sharedCredentialsFile: (Optional) The path to the shared credentials file. If not set this defaults to
skipCredentialsValidation: (Optional) Skip the credentials validation via STS API. Used for AWS API implementations that do not have STS available/implemented.
skipGetEc2Platforms: (Optional) Skip getting the supported EC2 platforms. Used by users that don’t have
skipMetadataApiCheck: (Optional) Skip the AWS Metadata API check. Useful for AWS API implementations that do not have a metadata API endpoint. Setting to true prevents Terraform from authenticating via the Metadata API. You may need to use other authentication methods like static credentials, configuration variables, or environment variables.
skipRegionValidation: (Optional) Skip static validation of region name. Used by users of alternative AWS-like APIs or users w/ access to regions that are not public (yet).
skipRequestingAccountId: (Optional) Skip requesting the account ID. Used for AWS API implementations that do not have IAM/STS API and/or metadata API.
token: (Optional) Use this to set an MFA token. It can also be sourced from the