Using PaaS resources in Azure brings convenience to developers such as saving times, concentrating on coding, and etc. However, there is a paradox which convenience and secure might never on the same direction.
Your customers might challenging you by exposing the inter-connection among resources under public networks. For example, You builded a Function App for tracking customers’ information and storing them in to a Blob container (from a Storage Account). Meanwhile, connections invoked by that function uses public domain name to the container, which means those requests might have a great opportunity routing outside.
For security purpose such as ISO/IEC 27001, you may want your resources to co-op privately, however, detail network settings among PaaS services are extreamly hard to find (at least for me, a pure newbie). So this article is my research for connecting PaaS devices such as Azure Function App to a Blob container under private network (and cross region).
Here is the outline, I will inreoduce 2 methods: Service Endpoints and Private Endpoints, help you to protect your connection.
I started to study blockchain recently and try to figure out concepts about the keys, addresses which related to the bitcoin wallet. Meanwhile, I also collect some methods to easily export/import the existing key pairs among different wallets and platforms. I want to share my experiences with you. And please leave me some comments if you have any question or have found some misleading information via this post 🙂
This is the TOC and I only translate some of them since all the others are not essential part of this topic. And, forgive my weakness translation as usual…..
Exporting the private/public address pairs from wallet
Verifying address pairs to understand the calculation flow to the keys
Creating the customized private/public address pairs
Importing the customized private/public address pairs into wallet