-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
When calling ssm.put_parameter with Overwrite=True on an existing parameter the event output operation is incorrectly "Create".
{"version":"0","id":"868aaf27-09eb-40bd-a2aa-2a3266a0aa7f","detail-type":"Parameter Store Change","source":"aws.ssm","account":"000000000000","time":"2025-11-24T20:09:40Z","region":"us-east-1","resources":[],"detail":{"name":"/test/parameter","operation":"Create"}}
Expected Behavior
The expected aws event output should be
{"version":"0","id":"80f88d1f-c6fa-bb5c-502c-f4bf41346062","detail-type":"Parameter Store Change","source":"aws.ssm","account":"","time":"2025-11-24T19:36:05Z","region":"us-east-1","resources":["arn:aws:ssm:us-east-1::parameter/test/parameter"],"detail":{"name":"/test/parameter","type":"String","operation":"Update"}}
How are you starting LocalStack?
With a docker-compose file
Steps To Reproduce
How are you starting localstack (e.g., bin/localstack command, arguments, or docker-compose.yml)
docker run localstack/localstack
Client commands (e.g., AWS SDK code snippet, or sequence of "awslocal" commands)
python boto3 client
"boto3==1.26.101",
"botocore==1.29.102"
Following script demonstrates different output when enpoint_url is pointed at localstack vs real aws with aws_account_id correctly set
- Create SNS Topic, Sqs Queue , and initial SSM parameter
- Set sqs policy to accept sns SendMessage & subscribe queue to topic
- Create Event Bridge Rule & Target topic & add event bridge policy to topic
- Update SSM parameter & wait for message to appear in queue
Environment
- OS:Ubuntu 22
- LocalStack: Pro
LocalStack version: 4.10.0
LocalStack Docker image sha: f2229121415abf7acfae288fbc47ccb08490519fa282a38ba7b82cd6a919a79f
LocalStack build date: 2025-10-30
LocalStack build git hash: 51171bd3cAnything else?
No response