In the middle of the seven days of the AWS re-invent 2018 meeting, 34 new actions were undertaken and many other new features were added to existing organizations. For example, AWS changed another course of database action called Amazon Timestream and a database of records called Amazon QLDB.

Designers now have six meetings data warehouses to analyze the sub-selections within the family of social databases (eg Aurora, MySQL, etc.). In my association earlier, he was responsible for setting up large companies, and one of the essential elements I began to help tackle the problems of the past was “horses for courses.” We’ve all seen how advances can be made into sleds and all the game’s plans and problems can look like nails.

We saw this in a more detectable way with the social database, which has become a bit of all the stores, but not at all. How many users tried to use a social database for application use cases? Terrible The best courses of action are those that are crafted with advancements that meet the expressed needs.

Databases in memory to save, NoSQL to sets of key aspects and the resume continues until the end of time. Give your group better access to the devices ready for action should be a requirement for any affiliación.

In any case, there is a test that will see each company struggling to win the AWS cloud and begin to reveal the choice and decision of organizations in a cloud. Occasionally, AWS allocation in enterprises has its beginning outside of the IT relationship together (with or without IT), routinely by the need to complete other modernized capability quickly in the light of the security and peace of mind offered by the cloud.

Regardless, as the AWS impression creates, tensions around security and commitment end up being prominent and IT is being asked (or forced) to control the leading group of cloud environments from AWS. It is in the middle of that period that IT, through the mantle of security and exercises, faces a guardian attitude.

I’m not saying this is something horrible. At AWS, safety is zero duty. In any case when it becomes the main concern as it can cause disintegration when the need is less hostile to the flat cloud granulación.La which develops what I see is what I call the Guardians at the gate.

Suppose you have gone to your improvement store, anyway, before you walk, someone stops and asks what you need. You reveal to them that you are there to get a kind of entrance, screws and wood without wires, anyway, they are not allowed in the store. They will get things for you.

Surprisingly more awful, they say their claim is being rejected because of the way the wireless infiltrator is not compatible with the use and is not “insured”.

It disintegrates, in the light of the way they also discover it, it will take several weeks to fulfill your request as there are twenty people before you and these requests are being examined and confirmed for use. As annoying and silly as it sounds, it is tragically a reality for some progress meetings. On the other hand, I have seen that, using the above image, there is no one in the store who keeps an eye on the records and has no security.

People come and get things without paying for them (while the association still pays and does not understand who took it). Or, on the other hand, the most terribly terrible thing is that unapproved people walk into the store and get something vindictive.

Somewhere close to these two endings, there is an experience that saves the nature of the organization and agreement AWS offers, and security organization and all key company needs. It is finding the right agreement between the two.

In a sense, the output of the night is the equivalent of any unusual understanding in the store. There must be someone to help answer where to find what you are looking for, provide capacity for things, and help with funding and support. At AWS, we convey the direction we call Governance @ Scale.