Cloud Architecture: interconnection and concrete case


The advent of Clouds has greatly changed the IT landscape in the last few years. Public, private and a lot more. There are numerous types, each having its specific advantages. And thanks to cloud architects, it is now possible to build a hybrid, secure and flexible infrastructure that perfectly meets the requirements of organizations.


Today we are going to talk about just what is cloud hybrid ization in practice?


We can not deal with the subject of Cloud architecture without mentioning the interconnection that is vital. An interconnection allows data to be transferred from one environment to another in a hybrid architecture. An e-commerce site sends validated orders to the Cloud hosting the CRM so that the data is entered there to cite just one example, it is through it that a Cloud hosting.

Before continuing, let us pause for a moment on this word, “interconnection”. We no longer speak of “connection”, a term connoting a unilateral descent of information, but of interconnection, involving exchanges and putting all of the elements linked to each other on the same amount of importance. It really is a positive development, really representative o f the thought of cloud architectures, and of what is becoming for the IT landscape in general.

This trend accentuates the overall need for securing information systems. Indeed, it may be better to gather information during its transfer rather than compromise the environments by which it’s saved. The interconnections, therefore, present a chance for hackers and needs to be entirely safe. Along with that, they must be as efficient as the surroundings they link in order not to ever slow down the functioning that is overall of information system. So take both of these elements into consideration when choosing your provider.


In a hybrid cloud, the environments and their interconnections must, therefore, form a homogeneous whole; this is one of the reasons why a cloud architect is necessary for any hybridization project. These experts know good practices and can above all identify the technologies that are right surroundings adapted to each need.

Indeed, we frequently speak about connecting the public cloud (for flexibility) and private cloud (for data security), but this is only one example of what a hybrid architecture can be. We talk about hybridization from the moment an interconnection exists between two environments: thus, the best solutions are chosen to meet each specific need.

We could, consequently, imagine an architecture linking different neighborhood networks of the subsidiaries of an organization via an MPLS, or conversely the interconnection of two public Clouds to profit from two various technologies or simply just redundancy … The main limit, aside from technical constraints, here is the imagination of architects!


Just take the exemplory case of the fictitious The Email Shop, evolving in the B2B sector, that is undergoing digital restructuring. It hosted its internal information system itself, which included, among other things, a system that is messaging several business tools making use of Microsoft technology. The company’s website and associated information system depend on Linux. The Email Shop, therefore, chooses to turn to a UK colocation architecture that is hybrid.

One other cheap colocation associated with internal information system, contained in the HRIS, the CRM, etc. are however considered critical by The Email Shop Company. In the interests of colocation UK sovereignty to have them hosted on a se cure private cloud, located on British soil.

It stays to choose the absolute most effective solution for hosting its website. The website is linked to CRM but does not use any of its data considered to be critical. It can, therefore, be hosted on a public cloud supporting Linux infrastructures.

We now have thus identified at the very least four different environments for the information system associated with the e-mail Shop business: two public that is different, a private Cloud, and another private Cloud in the form of a PaaS (Platform as a Service) for Office 365. In order to manage the interconnection between these environments, supports the outsourcing of the system in general. The latter also ensures information protection and the overall protection of the IS against attacks.

Many companies now provide automated interconnection portals. They guarantee both good data transfer speed, and UK server colocation integrity and security. For more information, contact our Cloud architects who will be thrilled to reply to your concerns!

How exactly to think about protection in the AWS cloud?

Currently, a major change is taking place in companies. Digital transformation is a very broad subject, but with a typical thread: IT security. Information protection is now better and better, however, stays an issue for several, especially with regard to clouds that are public such as for instance AWS. Nevertheless, migration for this cloud usually improves the safety of its information systems.

Protected infrastructure: Security is JOB ZERO

The cloud is attractive, but frightening at the time that is same organizations could find it hard to consider having their information kept on gear that they don’t get a handle on. But, the security with this equipment is guaranteed by AWS, for whom safety is “Job Zero”, to phrase it differently, the supplier’s first concern.

The amenities of Amazon internet Services, therefore, have actually a tremendously level that is high of. The infrastructures have been designed to meet the strong security needs of military organizations and sometimes even banks: this will be “security by design” put ahead by the GDPR. In addition, the AWS secur ity group, constantly available, is continually learning and thanks that are improving the feedback from their an incredible number of clients.

The guarantee of this security is a number that is large of with which AWS is in compliance. And this is where a received idea began to appear: “My information system migrated to AWS benefits from their accreditations”: this is false! However, if you want to have your environments certified, this will be possible, because the base on which they are installed is in compliance with said certification.

And also this is in which the nuance is very important: AWS provides cloud safety (the building blocks, the foundations of the architecture), and you offer security within the cloud (the operational system). This dimension, the security policy, remains the re sponsibility of the company, which controls and it is accountable for it.

Adopt good practices and safety tools

Nevertheless, AWS isn’t only a safe infrastructure on that you simply must find a way to set up a protected system. Migrating to the AWS cloud means building your environments on a solid foundation, and accelerating the utilization of security procedures, benefiting from this modification to implement best practices.

For example, Amazon Web Services strongly encourages integrating and paying attention to identity and access management, an essential component of the security of an information system or a website. And to support you, the AWS cloud provides you with a very wide range of native tools to greatly help secure your environments.

Privilege isolated infrastructures with Amazon Virtual Private Cloud, and discover about cryptography tools (Amazon CloudHSM, etc.), access monitoring and logging solutions (Cloud Trail, etc.), interior action tracking (CloudWatch), etc.

Another point that is strong of is that this cloud gives great freedom of automation. By using more and more automation, the risk of human error is reduced, which improves security. Amazon Web Services itself has intends to cut manual operations by 80% per year!

AWS, therefore, poses as a guide towards securing your systems, but above all, do not grow the various tools without worldwide reasoning! Protection is a process that must definitely be regarded as an entire, whether your environments are on a cloud or on-premise.

Think about migration to AWS because of the best security

Once you understand the safety of AWS, you realize you are building on a strong foundation. You also know that you have to create and manage your own security policy, specially as a result of the equipment and services made available from the cloud provid er.

To implement this safety policy, concentrate on your challenges. This is certainly a necessary step, as indicated in our article “how to consider migration on AWS? »: Just take the time to include the safety aspect in your thinking. To limit the risks to your data, create a criticality matrix. This will allow you to determine the level of sensitivity of your data, and whether it can be migrated to the cloud that is public maybe not, sufficient reason for just what amount of protection.

This mapping done, everything is a question of access control, code quality … in short, compliance with good security practices! 100% security does not exist, the important thing is to understand important computer data and applications well, to determine the risks involved as well as the procedure to check out to correct or get a handle on them.

How to get into AWS safety, in accordance with AWS Transformation teams day:

• Understand AWS security

• Build on strongly compliant, strong fundamentals

• Integrate identification and access management

• Allow detection checks

• Establish data localization and system protection

• Implement data protection

• Optimizing change management

• Automate security functions