AWS the gp3 volume type throughput parameter is not set on AMI about packer-plugin-amazon HOT 7 CLOSED

Thanks for the notification. It does from the testing I’ve done today seem that Packer 1.6.6 and 1.7.8 are producing rational gp3 configurations. Does seem to solve the issue. -Alan From: Jenna Goldstrich ***@***.***> Sent: Thursday, January 13, 2022 12:45 PM To: hashicorp/packer-plugin-amazon ***@***.***> Cc: Alan Sparks ***@***.***>; Mention ***@***.***> Subject: Re: [hashicorp/packer-plugin-amazon] AWS the gp3 volume type throughput parameter is not set on AMI (#32) Hey all, sorry for the delay in getting back to y'all on this, I tested this on Packer v1.7.8 (amazon plugin v1.0.4 should work the same on newest v1.0.6) with the following JSON buildfile { "_comment" : "Test", "variables": { "aws_access_key": "", "aws_secret_key": "" }, "builders": [ { "type": "amazon-ebs", "access_key": "{{user `aws_access_key`}}", "secret_key": "{{user `aws_secret_key`}}", "region": "us-east-1", "source_ami_filter": { "filters": { "virtualization-type": "hvm", "name": "ubuntu/images/*ubuntu*", "root-device-type": "ebs" }, "owners": [ "099720109477" ], "most_recent": true }, "ami_block_device_mappings": [ { "device_name": "/dev/sda1", "delete_on_termination": "true", "volume_size": 20, "volume_type": "gp3", "throughput": 750, "iops": 3000 } ], "instance_type": "t2.micro", "ssh_username": "ubuntu", "communicator": "ssh", "ami_name": "jenna-test-2-5", "encrypt_boot": true, "tags": { "Team": "myteamtag", "OS_Version": "Centos", "Release": "Latest", "Base_AMI_Name": "jenna-test", "Extra": "latest" } } ] } And I see throughput 750/iops 3000 on the Add Storage step of launching my AMI on EC2. After this @nywilken<https://github.com/nywilken> and I tested this on Packer 1.6.6, with the same .json file, with the same expected correct result. I'm wondering if in the last few months something has changed on the AWS SDK that might have fixed this, since it seems to be working for us on both older, and newer versions of Packer. @webminster<https://github.com/webminster> @begetan<https://github.com/begetan> y'all both experienced this issue recently, can you please let us know if you're still experiencing this? — Reply to this email directly, view it on GitHub<#32 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAWJXBX2ARMXN2IGKD7VTJLUV4TSVANCNFSM4Z7MR7WQ>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>