You would think it would be easy to find this information, but none of the Github or Gandi documentation is clear so I have recorded the required steps here.
Create the following A records:
@ 1800 IN A 185.199.108.153
@ 1800 IN A 185.199.109.153
@ 1800 IN A 185.199.110.153
| a4b.amazonaws.com | |
| access-analyzer.amazonaws.com | |
| account.amazonaws.com | |
| acm-pca.amazonaws.com | |
| acm.amazonaws.com | |
| airflow-env.amazonaws.com | |
| airflow.amazonaws.com | |
| alexa-appkit.amazon.com | |
| alexa-connectedhome.amazon.com | |
| amazonmq.amazonaws.com |
Currently, there is an explosion of tools that aim to manage secrets for automated, cloud native infrastructure management. Daniel Somerfield did some work classifying the various approaches, but (as far as I know) no one has made a recent effort to summarize the various tools.
This is an attempt to give a quick overview of what can be found out there. The list is alphabetical. There will be tools that are missing, and some of the facts might be wrong--I welcome your corrections. For the purpose, I can be reached via @maxvt on Twitter, or just leave me a comment here.
There is a companion feature matrix of various tools. Comments are welcome in the same manner.
| input { stdin { } } | |
| output { | |
| stdout { | |
| #codec => rubydebug | |
| codec => dots | |
| } | |
| elasticsearch { | |
| protocol => http |
| logstash agent -e ' | |
| input { | |
| pipe { | |
| type => tshark | |
| # run tshark unprivileged because it's protocol decoders can be buggy. | |
| command => "sudo tcpdump -w - | tshark -i - -lT fieldstshark -lT fields -E separator=, -E quote=d -e ip.src -e ip.dst -e ip.len" | |
| } | |
| } |