Is transaction triggered by web3 secure on the internet?

Question

I'm trying to construct my business architecture using ethereum.

I'll operate public ethereum node and private business server on the AWS.

I'll trigger transaction from the private business server using web3.js to public ethereum node.

Q1 : On this case, Do I have to sign the transaction using private key on the private business server. right?

Q2 : The transaction will go through internet because ethereum node and business server node are physically separated. On this case, Is the transaction(signed data) which triggered by web3 safe through the internet? I'm worry that the signed data packets are captured on the internet and translated by hackers.

Answer 1

On this case, Do I have to sign the transaction using private key on the private business server. right?

That would be the ideal scenario. You could technically restrict your public node's RPC to be only accessible by your business server, and then use the personal APIs to unlock and send transactions from a keystore held on the node server. However, it is easier to secure a setup where a presigned tx is broadcast, as you can avoid unlocking any keys on the server.

The transaction will go through internet because ethereum node and business server node are physically separated. On this case, Is the transaction(signed data) which triggered by web3 safe through the internet? I'm worry that the signed data packets are captured on the internet and translated by hackers.

What do you mean by translated? Anyone intercepting the data in flight could also just as easily read it from the blockchain, or form any node's txpool.

You are protected against tampering, since even if someone were to intercept it and alter the transaction, it would invalidate your signature, making it an invalid transaction.