AWS
Auto Added by WPeMatico
Auto Added by WPeMatico
Amazon’s web services AWS continue to be the highlight of the company’s balance sheet, once again showing the kind of growth Amazon is looking for in a new business for the second quarter — especially one that has dramatically better margins than its core retail business.
Despite now running a grocery chain, the company’s AWS division — which has an operating margin over 25 percent compared to its tiny margins on retail — grew 49 percent year-over-year in the quarter compared to last year’s second quarter. It’s also up 49 percent year-over-year when comparing the most recent six months to the same period last year. AWS is now on a run rate well north of $10 billion annually, generating more than $6 billion in revenue in the second quarter this year. Meanwhile, Amazon’s retail operations generated nearly $47 billion with a net income of just over $1.3 billion (unaudited). Amazon’s AWS generated $1.6 billion in operating income on its $6.1 billion in revenue.
So, in short, Amazon’s dramatically more efficient AWS business is its biggest contributor to its actual net income. The company reported earnings of $5.07 per share, compared to analyst estimates of around $2.50 per share, on revenue of $52.9 billion. That revenue number fell under what investors were looking for, so the stock isn’t really doing anything in after-hours, and Amazon still remains in the race to become a company with a market cap of $1 trillion alongside Google, Apple and Microsoft.

This isn’t extremely surprising, as Amazon was one of the original harbingers of the move to a cloud computing-focused world, and, as a result, Microsoft and Google are now chasing it to capture up as much share as possible. While Microsoft doesn’t break out Azure, the company says it’s one of its fastest-growing businesses, and Google’s “other revenue” segment that includes Google Cloud Platform also continues to be one of its fastest-growing divisions. Running a bunch of servers with access to on-demand compute, it turns out, is a pretty efficient business that can account for the very slim margins that Amazon has on the rest of its core business.
Powered by WPeMatico
Microsoft is capping off a rather impressive year without any major missteps in its final report for its performance in its 2018 fiscal year, posting a quarter that seems to have been largely non-offensive to Wall Street.
In the past year, Microsoft’s stock has gone up more than 40 percent. In the past two years, it’s nearly doubled. All of this came after something around a decade of that price not really doing anything as Microsoft initially missed major trends like the shift to mobile and the cloud. But since then, new CEO Satya Nadella has turned that around and increased the company’s focused on both, and Azure is now one of the company’s biggest highlights. Microsoft is now an $800 billion company, which, while still considerably behind Apple, Amazon and Google, is a considerable high considering the past decade.
In addition, Microsoft passed $100 billion in revenue for a fiscal year. So, as you might expect, the stock didn’t really do anything, given that nothing seemed to be too wrong with what was going on. For a company that’s at around $800 billion, that it’s not doing anything bad at this point is likely a good thing. That Microsoft is even in the discussion of being one of the companies chasing a $1 trillion market cap is likely something we wouldn’t have been talking about just three or four years ago.
The company said it generated $30.1 billion in revenue, up 17 percent year-over-year, and adjusted earnings of $1.13 per share. Analysts were looking for earnings of $1.08 per share on revenue of $29.23 billion.

So, under Nadella, this is more or less a tale of two Microsofts — one squarely pointed at a future of productivity software with an affinity toward cloud and mobile tools (though Windows is obviously still a part of this), and one that was centered around the home PC. Here are a couple of highlights from the report:
Powered by WPeMatico
When Amazon introduced AWS Lambda in 2015, the notion of serverless computing was relatively unknown. It enables developers to deliver software without having to manage a server to do it. Instead, Amazon manages it all and the underlying infrastructure only comes into play when an event triggers a requirement. Today, the company released an app in the iOS App Store called AWS IoT 1-Click to bring that notion a step further.
The 1-click part of the name may be a bit optimistic, but the app is designed to give developers even quicker access to Lambda event triggers. These are designed specifically for simple single-purpose devices like a badge reader or a button. When you press the button, you could be connected to customer service or maintenance or whatever makes sense for the given scenario.
One particularly good example from Amazon is the Dash Button. These are simple buttons that users push to reorder goods like laundry detergent or toilet paper. Pushing the button connects to the device to the internet via the home or business’s WiFi and sends a signal to the vendor to order the product in the pre-configured amount. AWS IoT 1-Click extends this capability to any developers, so long as it is on a supported device.
To use the new feature, you need to enter your existing account information. You configure your WiFi and you can choose from a pre-configured list of devices and Lambda functions for the given device. Supported devices in this early release include AWS IoT Enterprise Button, a commercialized version of the Dash button and the AT&T LTE-M Button.

Once you select a device, you define the project to trigger a Lambda function, or send an SMS or email, as you prefer. Choose Lambda for an event trigger, then touch Next to move to the configuration screen where you configure the trigger action. For instance, if pushing the button triggers a call to IT from the conference room, the trigger would send a page to IT that there was a call for help in the given conference room.
Finally, choose the appropriate Lambda function, which should work correctly based on your configuration information.
All of this obviously requires more than one click and probably involves some testing and reconfiguring to make sure you’ve entered everything correctly, but the idea of having an app to create simple Lambda functions could help people with non-programming background configure buttons with simple functions with some training on the configuration process.
It’s worth noting that the service is still in Preview, so you can download the app today, but you have to apply to participate at this time.
Powered by WPeMatico
At its re:Invent developer conference, AWS made so many announcements that even some of the company’s biggest launches only got a small amount of attention. While the company’s long-awaited Elastic Container Service for Kubernetes got quite a bit of press, the launch of the far more novel Fargate container service stayed under the radar.
When I talked to him earlier this week, AWS VP and Amazon CTO (and EDM enthusiast) Werner Vogels admitted as much. “I think some of the Fargate stuff got a bit lost in all the other announcements that there were,” he told me. “I think it is a major step forward in making containers more cloud native and we see quite a few of our customers jumping on board with Fargate.”
Fargate, if you haven’t followed along, is a technology for AWS’ Elastic Container Service (ECS) and Kubernetes Service (EKS) that abstracts all of the underlying infrastructure for running containers away. You pick your container orchestration engine and the service does the rest. There’s no need for managing individual servers or clusters. Instead, you simply tells ECS or EKS that you want to launch a container with Fargate, define the CPU and memory requirements of your application and let the service handle the rest.

To Vogels, who also published a longer blog post on Fargate today, the service is part of the company’s mission to help developers focus on their applications — and not the infrastructure. “I always compare it a bit to the early days of cloud,” said Vogels. “Before we had AWS, there were only virtual machines. And many companies build successful businesses around it. But when you run virtual machines, you still have to manage the hardware. […] One of the things that happened when we introduced EC2 [the core AWS cloud computing service] in the early days, was sort of that it decoupled things from the hardware. […] I think that tremendously improved developer productivity.”
But even with the early containers tools, if you wanted to run them directly on AWS or even in ECS, you still had to do a lot of work that had little to do with actually running the containers. “Basically, it’s the same story,” Vogels said. “VMs became the hardware for the containers. And a significant amount of work for developers went into that orchestration piece.”
What Amazon’s customers wanted, however, was being able to focus on running their containers — not what Vogels called the “hands-on hardware-type of management.” “That was so pre-cloud,” he added and in his blog post today, he also notes that “container orchestration has always seemed to me to be very not cloud native.”

In Vogels’ view, it seems, if you are still worried about infrastructure, you’re not really cloud native. He also noted that the original promise of AWS was that AWS would worry about running the infrastructure while developers got to focus on what mattered for their businesses. It’s services like Fargate and maybe also Lambda that take this overall philosophy the furthest.
Even with a container service like ECS or EKS, though, the clusters still don’t run completely automatically and you still end up provisioning capacity that you don’t need all the time. The promise of Fargate is that it will auto-scale for you and that you only pay for the capacity you actually need.
“Our customers, they just want to build software, they just want to build their applications. They don’t want to be bothered with how to exactly map this container down to that particular virtual machine — which is what they had to do,” Vogels said. “With Fargate, you select the type of CPUs you want to use for a particular task and it will autoscale this for you. Meaning that you actually only have to pay for the capacity you use.”

When it comes to abstracting away infrastructure, though, Fargate does this for containers, but it’s worth noting that a serverless product like AWS Lambda takes it even further. For Vogels, this is a continuum and driven by customer demand. While AWS is clearly placing big bets on containers, he is also quite realistic about the fact that many companies will continue to use containers for the foreseeable future. “VMs won’t go away,” he said.
With a serverless product like Lambda, you don’t even think about the infrastructure at all anymore, not even containers — you get to fully focus on the code and only pay for the execution of that code. And while Vogels sees the landscape of VMs, containers and serverless as a continuum, where customers move from one to the next, he also noted that AWS is seeing enterprises that are skipping over the container step and going all in on serverless right away.
Powered by WPeMatico
Since the dawn of the internet, the titans of this industry have fought to win the “starting point” — the place that users start their online experiences. In other words, the place where they begin “browsing.” The advent of the dial-up era had America Online mailing a CD to every home in America, which passed the baton to Yahoo’s categorical listings, which was swallowed by Google’s indexing of the world’s information — winning the “starting point” was everything.
As the mobile revolution continues to explode across the world, the battle for the starting point has intensified. For a period of time, people believed it would be the hardware, then it became clear that the software mattered most. Then conversation shifted to a debate between operating systems (Android or iOS) and moved on to social properties and messaging apps, where people were spending most of their time. Today, my belief is we’re hovering somewhere between apps and operating systems. That being said, the interface layer will always be evolving.
The starting point, just like a rocket’s launchpad, is only important because of what comes after. The battle to win that coveted position, although often disguised as many other things, is really a battle to become the starting point of commerce.
Google’s philosophy includes a commitment to get users “off their page” as quickly as possible…to get that user to form a habit and come back to their starting point. The real (yet somewhat veiled) goal, in my opinion, is to get users to search and find the things they want to buy.
Of course, Google “does no evil” while aggregating the world’s information, but they pay their bills by sending purchases to Priceline, Expedia, Amazon and the rest of the digital economy.
Facebook, on the other hand, has become a starting point through its monopolization of users’ time, attention and data. Through this effort, it’s developed an advertising business that shatters records quarter after quarter.
Google and Facebook, this famed duopoly, represent 89 percent of new advertising spending in 2017. Their dominance is unrivaled… for now.
Change is urgently being demanded by market forces — shifts in consumer habits, intolerable rising costs to advertisers and through a nearly universal dissatisfaction with the advertising models that have dominated (plagued) the U.S. digital economy. All of which is being accelerated by mobile. Terrible experiences for users still persist in our online experiences, deliver low efficacy for advertisers and fraud is rampant. The march away from the glut of advertising excess may be most symbolically seen in the explosion of ad blockers. Further evidence of the “need for a correction of this broken industry” is Oracle’s willingness to pay $850 million for a company that polices ads (probably the best entrepreneurs I know ran this company, so no surprise).
As an entrepreneur, my job is to predict the future. When reflecting on what I’ve learned thus far in my journey, it’s become clear that two truths can guide us in making smarter decisions about our digital future:
Every day, retailers, advertisers, brands and marketers get smarter. This means that every day, they will push the platforms, their partners and the places they rely on for users to be more “performance driven.” More transactional.
Paying for views, bots (Russian or otherwise) or anything other than “dollars” will become less and less popular over time. It’s no secret that Amazon, the world’s most powerful company (imho), relies so heavily on its Associates Program (its home-built partnership and affiliate platform). This channel is the highest performing form of paid acquisition that retailers have, and in fact, it’s rumored that the success of Amazon’s affiliate program led to the development of AWS due to large spikes in partner traffic.
Chinese flag overlooking The Bund, Shanghai, China (Photo: Rolf Bruderer/Getty Images)
When thinking about our digital future, look down and look east. Look down and admire your phone — this will serve as your portal to the digital world for the next decade, and our dependence will only continue to grow. The explosive adoption of this form factor is continuing to outpace any technological trend in history.
Now, look east and recognize that what happens in China will happen here, in the West, eventually. The Chinese market skipped the PC-driven digital revolution — and adopted the digital era via the smartphone. Some really smart investors have built strategies around this thesis and have quietly been reaping rewards due to their clairvoyance.
China has historically been categorized as a market full of knock-offs and copycats — but times have changed. Some of the world’s largest and most innovative companies have come out of China over the past decade. The entrepreneurial work ethic in China (as praised recently by arguably the world’s greatest investor, Michael Moritz), the speed of innovation and the ability to quickly scale and reach meaningful populations have caused Chinese companies to leapfrog the market cap of many of their U.S. counterparts.
The most interesting component of the Chinese digital economy’s growth is that it is fundamentally more “pure” than the U.S. market’s. I say this because the Chinese market is inherently “transactional.” As Andreessen Horowitz writes, WeChat, China’s most valuable company, has become the “starting point” and hub for all user actions. Their revenue diversity is much more “Amazon” than “Google” or “Facebook” — it’s much more pure. They make money off the transactions driven from their platform, and advertising is far less important in their strategy.
The obsession with replicating WeChat took the tech industry by storm two years ago — and for some misplaced reason, everyone thought we needed to build messaging bots to compete.
What shouldn’t be lost is our obsession with the purity and power of the business models being created in China. The fabric that binds the Chinese digital economy and has fostered its seemingly boundless growth is the magic combination of commerce and mobile. Singles Day, the Chinese version of Black Friday, drove $25 billion in sales on Alibaba — 90 percent of which were on mobile.
The lesson we’ve learned thus far in both the U.S. and in China is that “consumers spending money” creates the most durable consumer businesses. Google, putting aside all its moonshots and heroic mission statements, is a “starting point” powered by a shopping engine. If you disagree, look at where their revenue comes from…
Google’s recent announcement of Shopping Actions and their movement to a “pay per transaction model” signals a turning point that could forever change the landscape of the digital economy.
Google’s multi-front battle against Apple, Facebook and Amazon is weighted. Amazon is the most threatening. It’s the most durable business of the four — and its model is unbounded on two fronts that almost everyone I know would bet their future on, 1) people buying more online, where Amazon makes a disproportionate amount of every dollar spent, and 2) companies needing more cloud computing power (more servers), where Amazon makes a disproportionate amount of every dollar spent.
To add insult to injury, Amazon is threatening Google by becoming a starting point itself — 55 percent of product searches now originate at Amazon, up from 30 percent just a year ago.
Google, recognizing consumer behavior was changing in mobile (less searching) and the inferiority of their model when compared to the durability and growth prospects of Amazon, needed to respond. Google needed a model that supported boundless growth and one that created a “win-win” for its advertising partners — one that resembled Amazon’s relationship with its merchants — not one that continued to increase costs to retailers while capitalizing on their monopolization of search traffic.
Google knows that with its position as the starting point — with Google.com, Google Apps and Android — it has to become a part of the transaction to prevail in the long term. With users in mobile demanding fewer ads and more utility (demanding experiences that look and feel a lot more like what has prevailed in China), Google has every reason in the world to look down and to look east — to become a part of the transaction — to take its piece.
A collision course for Google and the retailers it relies upon for revenue was on the horizon. Search activity per user was declining in mobile and user acquisition costs were growing quarter over quarter. Businesses are repeatedly failing to compete with Amazon, and unless Google could create an economically viable growth model for retailers, no one would stand a chance against the commerce juggernaut — not the retailers nor Google itself.
As I’ve believed for a long time, becoming a part of the transaction is the most favorable business model for all parties; sources of traffic make money when retailers sell things, and, most importantly, this only happens when users find the things they want.
Shopping Actions is Google’s first ambitious step to satisfy all three parties — businesses and business models all over the world will feel this impact.
Good work, Sundar.
Powered by WPeMatico
AWS’ S3 storage service today launched a cheaper option for keeping data in the cloud — as long as developers are willing to give up a few 9s of availability in return for saving up to 20 percent compared to the standard S3 price for applications that need infrequent access. The name for this new S3 tier: S3 One Zone-Infrequent Access.
S3 was among the first services AWS offered. Over the years, the company added a few additional tiers to the standard storage service. There’s the S3 Standard tier with the promise of 99.999999999 percent durability and 99.99 percent availability and S3 Standard-Infrequent Access with the same durability promise and 99.9 percent availability. There’s also Glacier for cold storage.

Data stored in the Standard and Standard-Infrequent access tiers is replicated across three or more availability zones. As the name implies, the main difference between those and the One Zone-Infrequent Access tier is that with this cheaper option, all the data sits in only one availability zone. It’s still replicated across different machines, but if that zone goes down (or is destroyed), you can’t access your data.
Because of this, AWS only promises 99.5 percent availability and only offers a 99 percent SLA. In terms of features and durability, though, there’s no difference between this tier and the other S3 tiers.
As Amazon CTO Werner Vogels noted in a keynote at the AWS Summit in San Francisco today, it’s the replication across availability zones that defines the storage cost. In his view, this new service should be used for data that is infrequently accessed but can be replicated.
An availability of 99.5 percent does mean that you should expect to experience a day or two per year where you can’t access your data, though. For some applications, that’s perfectly acceptable, and Vogels noted that he expects AWS customers to use this for secondary backup copies or for storing media files that can be replicated.

Powered by WPeMatico
A couple of years ago, Dropbox shocked a lot of people when it decided to mostly drop the public cloud, and built its own datacenters. More recently, Atlassian did the opposite, closing most of its datacenters and moving to the cloud. Companies make these choices for a variety of reasons. When Atlassian CTO Sri Viswanath came on board in 2016, he made the decision to move the company’s biggest applications to AWS.
In part, this is a story of technical debt — that’s the concept that over time your applications become encumbered by layers of crusty code, making it harder to update and ever harder to maintain. For Atlassian, which was founded in 2002, that bill came due in 2016 when Viswanath came to work for the company.
Atlassian already knew they needed to update the code to move into the future. One of the reasons they brought Viswanath on board was to lead that charge, but the thinking was already in place even before he got there. A small team was formed back in 2015 to work out the vision and the architecture for the new cloud-based approach, but they wanted to have their first CTO in place to carry it through to fruition.
He put the plan into motion, giving it the internal code name Vertigo — maybe because the thought of moving most of their software stack to the public cloud made the engineering team dizzy to even consider. The goal of the project was to rearchitect the software, starting with their biggest products Jira and Confluence, in a such a way that it would lay the foundation for the company for the next decade — no pressure or anything.
Photo: WILLIAM WEST/AFP/Getty Images
They spent a good part of 2016 rewriting the software and getting it set up on AWS. They concentrated on turning their 15-year old code into microservices, which in the end resulted in a smaller code base. He said the technical debt issues were very real, but they had to be careful not to reinvent the wheel, just change what needed to be changed whenever possible.
“The code base was pretty large and we had to go in and do two things. We wanted to build it for multi-tenant architecture and we wanted to create microservices,” he said. “If there was a service that could be pulled out and made self-contained we did that, but we also created new services as part of the process.”
Last year was the migration year, and it was indeed a full year-long project to migrate every last customer over to the new system. It started in January and ended in December and involved moving tens of thousands of customers.
Photo: KTSDesign/Science Photo Library
First of all, they automated whatever they could and they also were very deliberate in terms of the migration order, being conscious of migrations that might be more difficult. “We were thoughtful in what order to migrate. We didn’t want to do easiest first and hardest at the end. We didn’t want to do just the harder ones and not make progress. We had to blend [our approaches] to fix bugs and issues throughout the project,” he said.
Viswanath stated that the overarching goal was to move the customers without a major incident. “If you talk to anyone who does migration, that’s a big thing. Everyone has scars doing migrations. We were conscious to do this pretty carefully.” Surprisingly, although it wasn’t perfect, they did manage to complete the entire exercise without a major outage, a point of which the team is justifiably proud. That doesn’t mean that it was always smooth or easy.
“It sounds super easy: ‘we were thoughtful and we migrated,’ but there was warfare every day. When you migrate, you hit a wall and react. It was a daily thing for us throughout the year,” he explained. It took a total team effort involving engineering, product and support. That included having a customer support person involved in the daily scrum meetings so they could get a feel for any issues customers were having and fix them as quickly as possible.
As in any cloud project, there are some general benefits to moving an application to the cloud around flexibility, agility and resource elasticity, but there was more than that when it came to this specific project.
Photo: Ade Akinrujomu/Getty Images
First of all it has allowed faster deployment with multiple deployments at the same time, due in large part to the copious use of microservices. That means they can add new features much faster. During the migration year, they held off on new features for the most part because they wanted to keep things as static as possible for the shift over, but with the new system in place they can move much more quickly to add new features.
They get much better performance and if they hit a performance bottleneck, they can just add more resources because it’s the cloud. What’s more, they were able to have a local presence in the EU and that improves performance by having the applications closer to the end users located there.
Finally, they actually found the cloud to be a more economical option, something that not every company that moves to the cloud finds. By closing the datacenters and reducing the capital costs associated with buying hardware and hiring IT personnel to maintain it, they were able to reduce costs.
It was a long drawn out project, and as such, they really needed to think about the human aspect of it too. They would swap people in and out to make sure the engineers stayed fresh and didn’t burn out helping with the transition.
One thing that helped was the company culture in general, which Viswanath candidly describes as one with open communication and a general “no bullshit” policy. “We maintained open communication, even when things weren’t going well. People would raise their hand if they couldn’t keep up and we would get them help,” he said.
He admitted that there was some anxiety within the company and for him personally implementing a project of this scale, but they knew they needed to do it for the future of the organization. “There was definitely nervousness on what if this project doesn’t go well. It seemed the obvious right direction and we had to do it. The risk was what if we screwed up in execution and we didn’t realize benefits we set out to do.”
In the end, it was a lot of work, but it worked out just fine and they have the system in place for the future. “Now we are set up for the next 10 years,” he said.
Powered by WPeMatico
It really is Go Time for GoDaddy . Amazon’s cloud services provider AWS and GoDaddy, the domain registration and management giant, may have competed in the past when it comes to working with small businesses to provide them with web services, but today the two took a step closer together. AWS said that GoDaddy is now migrating “the majority” of its infrastructure to AWS in a multi-year deal that will also see AWS becoming a partner in selling on some products of GoDaddy’s — namely Managed WordPress and GoCentral for managing domains and building and running websites.
The deal — financial terms of which are not being disclosed — is wide-ranging, but it will not include taking on domain management for GoDaddy’s 75 million domains currently under management, a spokesperson for the company confirmed to me.
“GoDaddy is not migrating the domains it manages to AWS,” said Dan Race, GoDaddy’s VP of communications. “GoDaddy will continue to manage all customer domains. Domain management is obviously a core business for GoDaddy.”
The move underscores Amazon’s continuing expansion as a powerhouse in cloud hosting and related services, providing a one-stop shop for customers who come for one product and stay for everything else (not unlike its retail strategy in that regard). Also, it is a reminder of how the economies of scale in the cloud business make it financially challenging to compete if you are not already one of the big players, or lack deep pockets to sustain your business as you look to grow. GoDaddy has been a direct victim of those economics: just last summer, GoDaddy killed off Cloud Servers, its AWS-style business for building, testing and scaling cloud services on GoDaddy infrastructure. It also already was hosting some services on AWS prior to this: its enterprise-grade Managed WordPress service was already being hosted there, for example.
The AWS deal also highlights how GoDaddy is trimming operational costs to improve its overall balance sheet under Scott Wagner, the COO who took over as CEO from Blake Irving at the beginning of this year.
“As a technology provider with more than 17 million customers, it was very important for GoDaddy to select a cloud provider with deep experience in delivering a highly reliable global infrastructure, as well as an unmatched track record of technology innovation, to support our rapidly expanding business,” said Charles Beadnall, CTO at GoDaddy, in a statement.
“AWS provides a superior global footprint and set of cloud capabilities which is why we selected them to meet our needs today and into the future. By operating on AWS, we’ll be able to innovate at the speed and scale we need to deliver powerful new tools that will help our customers run their own ventures and be successful online,” he continued.
AWS said that GoDaddy will be using AWS’s Elastic Container Service for Kubernetes and Elastic Compute Cloud P3 instances, as well as machine learning, analytics, and other database-related and container technology. Race told TechCrunch that the infrastructure components that the company is migrating to AWS currently run at GoDaddy but will be gradually moved away as part of its multi-year migration.
“As a large, high-growth business, GoDaddy will be able to leverage AWS to innovate for its customers around the world,” said Mike Clayville, VP, worldwide commercial sales at AWS, in a statement. “Our industry-leading services will enable GoDaddy to leverage emerging technologies like machine learning, quickly test ideas, and deliver new tools and solutions to their customers with greater frequency. We look forward to collaborating with GoDaddy as they build anew in the cloud and innovate new solutions to help people turn their ideas into reality online.”
Powered by WPeMatico
AWS had a successful year by any measure. The company continued to behave like a startup with the kind of energy and momentum to invest in new areas not usually seen in an incumbent with a significant marketshare lead. How good a year was it? According to numbers from Synergy Research, the company remains the category leader by far with around 35 percent marketshare. Microsoft sits well behind… Read More
Powered by WPeMatico
Steve Jobs used to famously end his keynotes with “there is one more thing…” AWS decided to wait a week after their re:Invent conference ended to announce their more thing when they quietly released a single sign on product for the AWS cloud yesterday.
While the announcement was pretty thin on details, it appears to be focused on providing single sign on for the AWS family of… Read More
Powered by WPeMatico