- 最新
- 投票最多
- 评论最多
Hi. We launched TLS support at GA and we are currently moving to a default setting of TLS for our APIs. We will be updating our documentation and making an announcement in the Forums to communicate this change. You can change the default setting and disable TLS at the time of creation by selecting TLS_PLAINTEXT, or PLAINTEXT for the ClientBroker parameter. We expect this default behavior to be rolled out to all regions by 6/25. We will also make it possible to update existing clusters encryption settings at a future date. Learn More: https://docs.aws.amazon.com/msk/latest/developerguide/msk-encryption.html
Thank you for replying!
We launched TLS support at GA and we are currently moving to a default setting of TLS for our APIs. We will be updating our documentation and making an announcement in the Forums to communicate this change.
Right. It's this change in defaults that tripped me quite hard, as it essentially broke the glue scripts we prepare for a disaster recovery scenario and for automating our deployments.
I've now updated my awscli
package, and modified the scripts to set the EncryptionInfo
fields to disable TLS for now.
Are you already aware of any other changes in defaults that are going to happen and that I should prepare for?
Glad you were able to get it working. There are no other planned default changes to the API.
相关内容
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前