1. Packages
  2. AWS Native
  3. Installation & Configuration

AWS Native is in preview. AWS Classic is fully supported.

AWS Native v0.97.0 published on Wednesday, Feb 21, 2024 by Pulumi

AWS Native: Installation & Configuration

aws-native logo

AWS Native is in preview. AWS Classic is fully supported.

AWS Native v0.97.0 published on Wednesday, Feb 21, 2024 by Pulumi

    If you do not already have an AWS account, you can create a free AWS account. Most resources in our examples fall within the AWS Free Tier, but we encourage you to follow the cleanup steps at the end of each section to avoid paying for resources you aren't using.

    Installation

    The AWS Native provider is available as a package in all Pulumi languages:

    Credentials

    To provision resources with the Pulumi AWS Native provider, you need to have AWS credentials. To do so:

    1. Create an IAM user in the AWS console with programmatic access and ensure it has sufficient permissions to deploy and manage your Pulumi program’s resources.
    2. Set up AWS credentials for your user.
    If you are using temporary security credentials, you will also have to supply an AWS_SESSION_TOKEN value before you can use Pulumi to create resources on your behalf.

    Your AWS credentials are never sent to pulumi.com. Pulumi uses the AWS SDK and the credentials in your environment to authenticate requests from your computer to AWS.

    Configuration

    There are a few different ways you can configure your AWS credentials to work with Pulumi.

    Authenticating via EC2 instance metadata is not currently supported for the AWS Native provider.

    Set credentials as environment variables

    We recommend using a shared credentials file for most development. However, if you need to temporarily override your credentials file, you can use environment variables. You can do this to quickly switch to a different access key or to configure AWS access from within an environment that might not have an AWS CLI, such as a continuous integration/continuous delivery (CI/CD) system.

    To authenticate using environment variables, set them in your terminal:

    $ 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>"
    

    You may alternatively set the AWS region in your Pulumi.<stack-name>.yaml file:

    $ pulumi config set aws:region <your-region> # e.g.`ap-south-1`
    

    Create a shared credentials file

    A credentials file is a plaintext file on your machine that contains your access keys. The file must be named credentials and is located underneath .aws/ directory in your home directory. We recommend this approach because it supports Amazon’s recommended approach for securely managing multiple roles.

    Option 1: Use the CLI

    To create this file using the CLI, install the AWS CLI. If you’re using Homebrew on macOS, you can use the community-managed awscli via brew install awscli.

    After installing the CLI, configure it with your IAM credentials, typically using the aws configure command. For other configuration options, see the AWS article Configuring the AWS CLI.

    $ aws configure
    AWS Access Key ID [None]: <YOUR_ACCESS_KEY_ID>
    AWS Secret Access Key [None]: <YOUR_SECRET_ACCESS_KEY>
    Default region name [None]:
    Default output format [None]:
    

    Now you’ve created the ~/.aws/credentials file and populated it with the expected settings.

    Option 2: Create by hand

    You can also create the shared credentials file by hand. For example:

    [default]
    aws_access_key_id = <YOUR_ACCESS_KEY_ID>
    aws_secret_access_key = <YOUR_SECRET_ACCESS_KEY>
    

    If you want to specify multiple profiles, those are listed in different sections:

    [default]
    aws_access_key_id = <YOUR_DEFAULT_ACCESS_KEY_ID>
    aws_secret_access_key = <YOUR_DEFAULT_SECRET_ACCESS_KEY>
    
    [test-account]
    aws_access_key_id = <YOUR_TEST_ACCESS_KEY_ID>
    aws_secret_access_key = <YOUR_TEST_SECRET_ACCESS_KEY>
    
    [prod-account]
    aws_access_key_id = <YOUR_PROD_ACCESS_KEY_ID>
    aws_secret_access_key = <YOUR_PROD_SECRET_ACCESS_KEY>
    

    In this case, you will need to set the AWS_PROFILE environment variable to the name of the profile to use.

    Set up multiple profiles

    As an optional step, you can set up multiple profiles.

    Here’s what that looks like in your ~/.aws/credentials file:

    [default]
    aws_access_key_id = <YOUR_DEFAULT_ACCESS_KEY_ID>
    aws_secret_access_key = <YOUR_DEFAULT_SECRET_ACCESS_KEY>
    
    [test-account]
    aws_access_key_id = <YOUR_TEST_ACCESS_KEY_ID>
    aws_secret_access_key = <YOUR_TEST_SECRET_ACCESS_KEY>
    
    [prod-account]
    aws_access_key_id = <YOUR_PROD_ACCESS_KEY_ID>
    aws_secret_access_key = <YOUR_PROD_SECRET_ACCESS_KEY>
    

    You can specify which profile to use with Pulumi through one of the following methods:

    • Set AWS_PROFILE as an environment variable

      $ export AWS_PROFILE=<YOUR_PROFILE_NAME>
      
    • Set aws:profile in your Pulumi.yaml

      pulumi config set aws:profile <profilename>
      

    Dynamically generate credentials

    In addition to configuring the AWS Native provider locally, you also have the option to centralize your configurations using Pulumi ESC (Environments, Secrets, and Configuration). Using this service will enable you to run AWS or Pulumi CLI commands with dynamically generated credentials, removing the need to configure and manage your credentials locally.

    To do this, you will need to complete the following steps:

    Configure OIDC between Pulumi and AWS

    Refer to the Configuring OpenID Connect for AWS Guide for the step-by-step process on how to do this. Note that when adding your configuration to your environment file, you can also define your AWS region in the environmentVariables section:

    values:
      aws:
        login:
          fn::open::aws-login:
            oidc:
              duration: 1h
              roleArn: <your-oidc-iam-role-arn>
              sessionName: pulumi-environments-session
      environmentVariables:
        AWS_ACCESS_KEY_ID: ${aws.login.accessKeyId}
        AWS_SECRET_ACCESS_KEY: ${aws.login.secretAccessKey}
        AWS_SESSION_TOKEN: ${aws.login.sessionToken}
        AWS_REGION: <YOUR_AWS_REGION> # e.g.`ap-south-1`
    

    [Optional] Move Pulumi config to your ESC environment

    It was mentioned earlier in this guide that you can also set your AWS region as a Pulumi configuration value in your project’s stack settings file (Pulumi.<stack-name>.yaml). In addition to this, there may be other values that you have defined in this file, and these values can also be centralized using Pulumi ESC. To expose these values to Pulumi IaC, you will need to add a second-level key called pulumiConfig and nest any desired values underneath it as shown below:

    values:
      aws:
        login:
          fn::open::aws-login:
            oidc:
              duration: 1h
              roleArn: <your-oidc-iam-role-arn>
              sessionName: pulumi-environments-session
      environmentVariables:
        AWS_ACCESS_KEY_ID: ${aws.login.accessKeyId}
        AWS_SECRET_ACCESS_KEY: ${aws.login.secretAccessKey}
        AWS_SESSION_TOKEN: ${aws.login.sessionToken}
        AWS_REGION: <YOUR_AWS_REGION>
      pulumiConfig: # exposes Pulumi config values to the Pulumi CLI
        project:environment: 'dev'
        aws:roleArn: 'arn:aws:iam::058111598222:role/OrganizationAccountAccessRole'
        aws:dynamodbEndpoint: 'dynamodb.us-east-2.amazonaws.com'
    

    If your workflow does not require the exposure of environment variables, you can also define those variables under the pulumiConfig block so that they are scoped only to your pulumi run.

    values:
      aws:
        login:
          fn::open::aws-login:
            oidc:
              duration: 1h
              roleArn: <your-oidc-iam-role-arn>
              sessionName: pulumi-environments-session
      pulumiConfig: 
        aws:region: <YOUR_AWS_REGION>
        aws:accessKey: ${aws.login.accessKeyId}
        aws:secretKey: ${aws.login.secretAccessKey}
        aws:token: ${aws.login.sessionToken}
        project:environment: 'dev'
        aws:roleArn: 'arn:aws:iam::058111598222:role/OrganizationAccountAccessRole'
        aws:dynamodbEndpoint: 'dynamodb.us-east-2.amazonaws.com'
    
    The configuration values under pulumiConfig can also be referenced directly from within your Pulumi program code. This is done using the same method to reference values from your project’s stack settings file. You can see examples of how to do this in the Accessing Configuration from Code section of the Pulumi documentation.

    Import your environment

    The last step is to update your project’s stack settings file (Pulumi.<stack-name>.yaml) to import your ESC environment as shown below:

    environment:
      - <your-environment-name>
    

    Make sure to replace <your-environment-name> with the name of the ESC environment you created in the previous steps.

    You can test that your configuration is working by running the pulumi preview command. This will validate that your AWS resources can be deployed using the dynamically generated credentials in your environment file.

    Make sure that your local environment does not have AWS credentials configured before running this command. You can check by running something like the aws s3 ls command which should return the following:

    ‘Unable to locate credentials. You can configure credentials by running “aws configure”.’

    To learn more about projecting environment variables in Pulumi ESC, refer to the relevant Pulumi ESC documentation.

    Configuration options

    Some configuration options are not supported in AWS Native. You can check on the status of a configuration option you need by visiting our backlog of Github issues; feel free to add your vote to an issue by adding a 👍 reaction.

    Use pulumi config set aws-native:<option> or pass options to the constructor of new aws-native.Provider.

    OptionRequired?Description
    regionRequiredThe region where AWS operations will take place. Examples are us-east-1, us-west-2, etc.
    allowedAccountIds (Not supported yet)OptionalList of allowed AWS account IDs to prevent you from mistakenly using an incorrect one (and potentially end up destroying a live environment). Conflicts with forbiddenAccountIds.
    accessKeyOptionalThe access key for API operations. You can retrieve this from the ‘Security & Credentials’ section of the AWS console.
    assumeRoleOptionalA JSON object representing an IAM role to assume. To set these nested properties, see docs on structured configuration, for example pulumi config set --path aws-native:assumeRole.roleArn arn:aws:iam::058111598222:role/OrganizationAccountAccessRole. The object contains the properties marked with a ↳ below:
    durationSecondsOptionalNumber of seconds to restrict the assume role session duration.
    externalIdOptionalExternal identifier to use when assuming the role.
    policyOptionalIAM Policy JSON describing further restricting permissions for the IAM Role being assumed.
    policyArnsOptionalSet of Amazon Resource Names (ARNs) of IAM Policies describing further restricting permissions for the IAM Role being assumed.
    roleArnOptionalAmazon Resource Name (ARN) of the IAM Role to assume.
    sessionNameOptionalSession name to use when assuming the role.
    tagsOptionalMap of assume role session tags.
    transitiveTagKeysOptionalSet of assume role session tag keys to pass to any subsequent sessions.
    dynamodbEndpointOptionalUse this to override the default endpoint URL constructed from the region. It’s typically used to connect to dynamodb-local.
    endpoints (Not supported yet)OptionalConfiguration block for customizing service endpoints.
    forbiddenAccountIds (Not supported yet)OptionalList of forbidden AWS account IDs to prevent you from mistakenly using the wrong one (and potentially end up destroying a live environment). Conflicts with allowedAccountIds.
    defaultTags (Not supported yet)OptionalA JSON block with resource tag settings to apply across all resources handled by this provider. Additional tags can be added/overridden at a per resource level. The object contains the properties marked with a ↳ below:
    tagsOptionalA key value pair of tags to apply across all resources.
    ignoreTags (Not supported yet)OptionalA JSON block with resource tag settings to ignore across all resources handled by this provider (except any individual service tag resources such as aws.ec2.Tag) for situations where external systems are managing certain resource tags. The object contains the properties marked with a ↳ below:
    keysOptionalA list of exact resource tag keys to ignore across all resources handled by this provider. This configuration prevents Pulumi from returning the tag in any tags properties and displaying any diffs for the tag value. If any resource still has this tag key configured in the tags argument, it will display a perpetual diff until the tag is removed from the argument or ignoreChanges is also used.
    keyPrefixesOptionalA list of resource tag key prefixes to ignore across all resources handled by this provider. This configuration prevents Pulumi from returning the tag in any tags properties and displaying any diffs for the tag value. If any resource still has this tag key configured in the tags argument, it will display a perpetual diff until the tag is removed from the argument or ignoreChanges is also used.
    insecure (Not supported yet)OptionalExplicitly allow the provider to perform “insecure” SSL requests. If omitted, the default value is false.
    kinesisEndpointOptionalUse this to override the default endpoint URL constructed from the region. It’s typically used to connect to kinesalite.
    maxRetries (Not supported yet)OptionalThe maximum number of times an AWS API request is being executed. If the API request still fails, an error is thrown.
    profileOptionalThe profile for API operations. If not set, the default profile created with aws configure will be used.
    s3ForcePathStyle (Not supported yet)OptionalSet 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.
    secretKeyOptionalThe secret key for API operations. You can retrieve this from the ‘Security & Credentials’ section of the AWS console.
    sharedCredentialsFileOptionalThe path to the shared credentials file. If not set this defaults to ~~/.aws/credentials.
    skipCredentialsValidation (Not supported yet)OptionalSkip the credentials validation via STS API. Used for AWS API implementations that do not have STS available/implemented.
    skipGetEc2Platforms (Not supported yet)OptionalSkip getting the supported EC2 platforms. Used by users that don’t have ec2:DescribeAccountAttributes permissions.
    skipMetadataApiCheck (Not supported yet)OptionalSkip the AWS Metadata API check. Useful for AWS API implementations that do not have a metadata API endpoint. Setting to true prevents Pulumi from authenticating via the Metadata API. You may need to use other authentication methods like static credentials, configuration variables, or environment variables.
    skipRegionValidation (Not supported yet)OptionalSkip 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 (Not supported yet)OptionalSkip requesting the account ID. Used for AWS API implementations that do not have IAM/STS API and/or metadata API.
    tokenOptionalUse this to set an MFA token. It can also be sourced from the AWS_SESSION_TOKEN environment variable.
    aws-native logo

    AWS Native is in preview. AWS Classic is fully supported.

    AWS Native v0.97.0 published on Wednesday, Feb 21, 2024 by Pulumi