I provisioned a Redis Enterprise Cloud add-on for my app on Heroku which is designed to only connect to a TLS version of Redis in production. But the URL provided by Heroku in my config vars doesn't contain the TLS version.
How can I get the TLS URL?
Related
I try to do GRPC client --> GCP external LB with HTTPS --> GKE with pod GRPC server
The external LB uses a google managed certificate.
The documentation states:
If you are using HTTPS or HTTP/2 from the load balancer to the backends, you must install SSL certificates on each VM instance. To install SSL certificates on a VM instance, use the instructions in your application documentation. These certificates can be self-signed.
So I developped the grpc server with a self-signed certificate.
My question is how the backend service (part of the LB) can call the GRPC server without the server.crt, i.e. the public key of the cert used in the GRPC server?
Is there a way to pass this server.crt to the backend service?
I don't see how to fulfill the documentation requirement.
Please help :)
I have built a backend server application without a frontend to it. Can I still deploy it to heroku ?
Sure. Heroku only hosts apps.
As long as your backend server application listens on a specified port, and is able to receive and respond to HTTP requests, you can host it on Heroku.
We are trying to enable tls to the Consul so that our Rest service(which is using self-signed certificate) will be able to register to Consul in Https mode, For enabling TLS I am following Consul documentation as well as below links
https://www.digitalocean.com/community/tutorials/how-to-secure-consul-with-tls-encryption-on-ubuntu-14-04
http://russellsimpkins.blogspot.in/2015/10/consul-adding-tls-using-self-signed.html
Note: I am using centos 7.2
now my service try to register to the consul but in Consul dashboard its down and on the console I am getting below error:
x509: certificate signed by unknown authority
we found the solution. we have to add the CA cert to TLS trust store instead JVM trust store for centos it is "/etc/pki/tls/certs/ca-bundle.crt"
just by appending CA certificate to this file solved our issue
I've set up a starter account on Heroku with a Bonsai elasticsearch add-on. I'm trying to connect to it via a Java application, but can't seem to connect via either Transport Client or the NodeBuilder options that are explained on the elasticsearch documentation pages.
I can run the following CURL to post data:
curl -XPOST http://banyan-7086980.us-east-1.bonsai.io/med/test/hello3 -d '{"title":"Hello world2"}'
My current line of thought is this:
Client client = new TransportClient()
.addTransportAddress(new InetSocketTransportAddress("http://banyan-7086980.us-east-1.bonsai.io", 9300));
But this is not working. What am I missing?
Most services that offer hosted Elasticsearch on Heroku does not support any other transport than HTTP. The canonical way of interfacing with Elasticsearch from Java is using either the Transport client or the Node client, both of which you've tried connecting to HTTP-endpoints.
The transport and node clients use a custom-built binary protocol which is not compatible with HTTP.
Additionally, this binary protocol by default does not support some core features you should expect in a production setup: authentication and encryption.
If your requirements include running on Heroku and using the official Java clients, have a look at Found Elasticsearch on Heroku, which provides support for the transport client using a custom transport module: https://github.com/foundit/elasticsearch-transport-module
Disclosure: I'm one of the developers at Found
Bonsai is a hosted service for elasticsearch, and if you are using the heroku addon, there are internals of both ES and Heroku that are abstracted.
For instance, the URL that you are hitting is at port 80 (http), whereas you are attempting to connect to 9300 (which is the default Elasticsearch port). This tells me that there is a proxy layer in between that is hiding ports 9200 and 9300 from the outside world, for security reasons.
What to do?
You could try connecting your Java client to port 80.
Client client = new TransportClient() .addTransportAddress(new InetSocketTransportAddress("http://banyan-7086980.us-east-1.bonsai.io", 80));
If you are using Heroku to host your application, follow the instructions of the Bonsai addon, use the ENV variables to setup the connection.
If you just want to have a hosted instance, you can use alternatives such as qbox for found
I prefer using Elasticsearch on Openshift.
So my question is heroku support rabbitmq currently? It was addon 'rabbitmq' but currently it looks like it disabled. If heroku do not support rabbitmq, then maybe it support other broker which could work via amqp protocol?
You can search the Heroku add-ons catalog for RabbitMQ add-ons. There are two:
CloudAMQP
RabbitMQ Bigwig