I can reproduce this with an enhanced acceptance test:

% make testacc TESTARGS='-run=TestAccSSMParameter_updateValue' PKG=ssm
make: Verifying source code with gofmt...
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go1.22.2 test ./internal/service/ssm/... -v -count 1 -parallel 20  -run=TestAccSSMParameter_updateValue -timeout 360m
=== RUN   TestAccSSMParameter_updateValue
=== PAUSE TestAccSSMParameter_updateValue
=== CONT  TestAccSSMParameter_updateValue
    parameter_test.go:98: Step 5/5 error running import: exit status 1
        
        Error: Cannot import non-existent remote object
        
        While attempting to import an existing object to "aws_ssm_parameter.test",
        the provider detected that no object exists with the given id. Only
        pre-existing objects can be imported; check that the id is correct and that
        it is associated with the provider's configured region or endpoint, or use
        "terraform apply" to create a new remote object for this resource.
        
--- FAIL: TestAccSSMParameter_updateValue (40.39s)
FAIL
FAIL	github.com/hashicorp/terraform-provider-aws/internal/service/ssm	45.366s
FAIL
make: *** [testacc] Error 1

Relates #37481.

from terraform-provider-aws.

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

from terraform-provider-aws.

I was comparing log files on TRACE level for the provider versions 5.49.0 and 5.52.0 (the issue exists in provider versions >= 5.50.0).

There was one difference in the requests send to AWS:

• in v5.49.0 the array of ParameterFilters looks like

  {"ParameterFilters":[{"Key":"Name","Option":"Equals","Values":["<name of the SSM parameter>"]}]}

• in v5.50.0 the array changes to

   {"ParameterFilters":[{"Key":"Name","Option":"Equals","Values":["<name of the SSM parameter>:<version>"]}]}

  So the version of the parameter is appended to the name of the parameter. In the original description of the issue this can be found as http.request.body="{"ParameterFilters":[{"Key":"Name","Option":"Equals","Values":["my-test-param:1"]}]}

I did try out the impact of that difference using AWS CLI:

• Returns parameter details as expected

  aws ssm describe-parameters --parameter-filters "Key=Name, Option=Equals,Values=<name of the SSM parameter>"

• Returns empty array

  aws ssm describe-parameters --parameter-filters "Key=Name, Option=Equals,Values=<name of the SSM parameter>:<version>"

Maybe this helps to find the cause of the issue.

from terraform-provider-aws.

from terraform-provider-aws.

This functionality has been released in v5.53.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

from terraform-provider-aws.