aws.rds.SnapshotCopy ignores the destination_region parameter

[uyy-hero-security]

Describe what happened

I'm trialling Pulumi for some AWS IaC work using Python.
A part of our stack operations is initiating a snapshot copy from a different region (for this purpose, us-east-1) into the current one, aws.config.region='us-east-2' .
I'm observing that the destination_region parameter in this invocation has no effect, causing the incorrect behavior of a copy inside the source region. (Also, the ergonomics for the source are a bit weird, but I can live with that). I wonder how I can trace the way the Python code is converted into an AWS primitive. I've run the command manually using the AWS console, and AWS does perform inter-region copies when requested to do so.

Sample program

copied_snapshot = aws.rds.SnapshotCopy(f"db-snapshot-copy-{environment_identifier}",
        source_db_snapshot_identifier=db_snapshot_identifier,
        target_db_snapshot_identifier=target_snapshot_name,
        destination_region=aws.config.region,
        kms_key_id=None,  # Use default KMS key
        tags={
            "Name": f"hero-db-snapshot-copy-{environment_identifier}",
            "Environment": environment_identifier,
        },
        opts=pulumi.ResourceOptions(provider=aws_source_region),
    )

Log output

No response

Affected Resource(s)

aws.rds.SnapshotCopy

Output of pulumi about

CLI
Version 3.156.0
Go Version go1.24.1
Go Compiler gc

Plugins
KIND NAME VERSION
resource aws 6.72.0
resource awsx 2.21.1
resource docker 4.6.2
resource docker-build 0.0.10
language python 3.156.0

Host
OS darwin
Version 15.3.2
Arch arm64

///// Prefer not to post user-specific details

Dependencies:
NAME VERSION
pulumi_awsx 2.21.1
setuptools 75.8.0
wheel 0.45.1

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

[t0yv0]

Thank you for reporting this, this is really unexpected behavior. This appears to be caused by the exact same problem in the upstream provider that pulumi-aws is derived from: hashicorp/terraform-provider-aws#39951

Our best bet on fixing the issue is having it fixed upstream and then inheriting the fix in a regular release.

For troubleshooting AWS calls https://www.pulumi.com/docs/iac/support/troubleshooting/#verbose-logging is relevant, note the TF_LOG parameter. Unfortunately debug-level logs can be quite voluminous though.