Pulumi AWS Native, currently at version 1.61.0, is a Python package for defining and managing AWS resources using the AWS Cloud Control API. It provides same-day access to new AWS resources and properties as they become available in Cloud Control. The library maintains a rapid release cadence, often with multiple updates per month, reflecting its close alignment with AWS Cloud Control API updates.
pip install pulumi-aws-nativeVerified import paths — ran on the pinned version, not inferred.
This quickstart program provisions a new S3 bucket using the `pulumi-aws-native` provider. It demonstrates how to import the provider and create a basic AWS resource, then exports the bucket's name. Remember to configure your AWS credentials and region before running `pulumi up`.
Be aware of the name change when consulting documentation or community resources; search for 'AWS Cloud Control Provider' if 'Pulumi AWS Native' doesn't yield results.
Evaluate your project's needs. If a resource is well-supported in `pulumi_aws`, prefer it. Use `pulumi-aws-native` when you need a resource that is very new, only available through Cloud Control, or requires specific behaviors exposed by Cloud Control.
Manually inspect `pulumi preview` output carefully after a `refresh`. If unintended resource replacements are planned due to attribute defaults, you might need to manually edit the Pulumi state file or explicitly define the attribute in your code to match the default, preventing a perceived drift.
Ensure your AWS SSO session is active and that environment variables (like `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, `AWS_SESSION_TOKEN`) are correctly exported and refreshed in the shell where `pulumi` commands are run. This can sometimes be a more sensitive area for `aws-native` due to underlying provider differences.
Set the Pulumi stack configuration `aws:skipMetadataApiCheck` to `false` (`pulumi config set aws:skipMetadataApiCheck false`) or export the environment variable `export AWS_SKIP_METADATA_API_CHECK=false` to ensure credential detection.
Re-authenticate your AWS SSO session using your preferred method (e.g., `aws sso login` or your SSO tool) to refresh credentials and ensure they are active and correctly exported as environment variables (`AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, `AWS_SESSION_TOKEN`).
Examine the `pulumi preview` output carefully to identify the specific attribute causing the replacement. If the default value is acceptable, explicitly set that attribute in your Pulumi code. If not, manual state editing might be required, or open an issue with Pulumi for specific resource behavior.