Was just curious if anyone has tested bunny with Amazon's new MQ service that supports AMQP specifically.
We tried our existing implementation on top of bunny and it through this message:
Using TLS but peer hostname verification is disabled. This is convenient for local development but prone to man-in-the-middle attacks. Please set verify_peer: true in production!
Using TLS but no client certificate is provided! If RabbitMQ is configured to verify peer certificate, connection upgrade will fail!
{"message":"Must be one of [:method, :headers, :body, :heartbeat] {"message":"Must be one of [:method, :headers, :body, :heartbeat]\n[\"/home/rails/rails_app/current/vendor/bundle/ruby/2.2.0/gems/amq-protocol-2.3.0/lib/amq/protocol/frame.rb:64:in `decode_header'\", \"/home/rails/rails_app/current/vendor/bundle/ruby/2.2.0/gems/bunny-2.9.1/lib/bunny/transport.rb:237:in `read_next_frame'\", \"/home/rails/rails_app/current/vendor/bundle/ruby/2.2.0/gems/bunny-2.9.1/lib/bunny/session.rb:1127:in `init_connection'\", ................. etc }