[Bug]: Resource update error with aws_kinesis_firehose_delivery_stream when using a Snowflake destination over PrivateLink

[briantreff]

Terraform Core Version

1.1.4

AWS Provider Version

5.52.0

Affected Resource(s)

aws_kinesis_firehose_delivery_stream

Expected Behavior

After successfully creating a Firehose delivery stream with a Snowflake destination that uses PrivateLink connectivity, we should be able to update the existing delivery stream (e.g. - modify values for processing_configuration).

Actual Behavior

When attempting to update an existing aws_kinesis_firehose_delivery_stream resource, the resource update fails with the message, "Changing the snowflake private link url is not supported at this time." However, we did not make any changes to the referenced value in our configuration.

Relevant Error/Panic Output Snippet

Error: updating Kinesis Firehose Delivery Stream (edw-connect-agent-snowflake-data-firehose-dev): operation error Firehose: UpdateDestination, https response error StatusCode: 400, RequestID: cfe6f838-226c-0357-913d-3cb177f6b3d3, InvalidArgumentException: Changing the snowflake private link url is not supported at this time.

Terraform Configuration Files

github-issue-submission.zip

Steps to Reproduce

Deploy a new Firehose delivery stream (i.e. - aws_kinesis_firehose_delivery_stream resource) with a Snowflake destination that uses PrivateLink connectivity. Attempt to update the existing delivery stream resource without changing the Snowflake account_url or VPC configuration. For example, modify the BufferSizeInMBs value in the processing_configuration.

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

[github-actions]

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.