Cloud Identity and Atlassian Access: User lifecycle management across your organization

User lifecycle management—the ability to automatically add and remove users to applications—is one of the key features of Cloud Identity, Google Cloud’s identity, access, and device management solution, which is available as a standalone solution and also to our G Suite Enterprise customers. Many of our G Suite customers use a variety of additional SaaS and on-premises applications, including Atlassian products like Jira, Confluence, Bitbucket, and more. Today, we’re pleased to announce that we’re partnering with Atlassian to enable user lifecycle management for these products.This partnership will allow you to provision and de-provision Atlassian users directly from the Cloud Identity or G Suite admin console,meaning admins will automatically have the right accounts created for all of their Atlassian apps. This saves your IT department from the headache of constantly updating user accounts and permissions across apps—now, when you add, modify, or delete a user in the admin console, changes are automatically reflected in your Atlassian apps, making it easier to manage access as employees change roles, join or leave the company. This update will also make life easier for your end users, enabling them to easily move from working in G Suite to their Atlassian apps.We do this by integrating with Atlassian Access, which provides enterprise-wide cloud governance and security across multiple Atlassian cloud products.Enabling SSO for Atlassian is required to set up user provisioningEnabling user provisioning for Atlassian in the admin consoleUnderpinning this partnership is SCIM 2.0, an industry-standard protocol for user lifecycle management that Cloud Identity has supported since 2016. In addition to Atlassian, Google Cloud partners with dozens of other apps and service providers for automated user provisioning and deprovisioning from within Cloud Identity and G Suite, including with Box, Dropbox, Salesforce, Slack, Zendesk, and more. See the full list of supported apps here and sign up today for a free trial to try it out yourself.
Quelle: Google Cloud Platform

5 reasons your legacy data warehouse won’t cut it

As we engage with enterprises across the globe, one thing is becoming clear: Today’s businesses are solving complex business problems that are data-intensive. But often, their data platform infrastructure is holding them back. Data platform architectures that were designed in the 1990s are not ready to solve business problems for 2020. We don’t have to tell you about the explosive data growth that’s going on for businesses around the world. If you’re managing data infrastructure today, you already know plenty about that data growth. Ever faster and larger data streams, global business needs, and tech-savvy users are all putting the pressure on IT teams to move faster, with more agility.Despite all these changes, it is often the legacy, traditional data warehouse where most of the data analytics tasks take place, and they’re underprepared for those demands. When we talk to people working in IT today, we hear a lot about the constraints that come with operating legacy technology while trying to build a modern data strategy. Those legacy data warehouses likely aren’t cutting it anymore. Here’s why—and here’s what you can do about it.  1. Business agility is hard to achieve with legacy tools. Business agility is the main goal as organizations move toward completely digital operations. Think of online banking, or retailers staying ahead of always-on e-commerce needs in a competitive environment. All these great, cutting-edge innovations reflect cultural and technical change, where flexibility is essential. A business has to be able to manage and analyze data quickly to understand how to better serve customers, and allow its internal teams to do their best work with the best data available.We hear that lots of data warehouses running today are operating at 95% or 100%, maxing out what they can provide to the business. Whether it’s on-premises or an existing data warehouse infrastructure moved wholesale to cloud, those warehouses aren’t keeping up with all the data requests users have. Managing and preventing these issues can take up a lot of IT time, and the problems often compound over time. Hitting capacity limits slows down users and ties up database administrators too.From a data infrastructure perspective, separating the compute and storage layers is essential to achieve business agility. When a data warehouse can handle your scalability needs and self-manage performance, that’s when you can really start being proactive. 2. Legacy data warehouses require a disproportionate degree of management. Most of the reports and queries your business runs are probably time-sensitive, and that sense of urgency is only increasing as users and teams see the possibilities of data analytics. In our engagements with customers, we often observe that they are spending a majority of the time on systems engineering, so that only about 15% of the time is spent analyzing data. That’s a lot of time spent on maintenance work. Because legacy infrastructure is complex, we often hear that businesses continue to invest in hiring people to manage those outdated systems, even though they’re not advancing data strategy or agility.To cut time on managing a data warehouse, it helps to automate the system engineering work away from the analytics work, like BigQuery enables. Once those functions are separated, the analytics work can take center stage and let users become less dependent on administrators. BigQuery also helps remove the user access issues that are common with legacy data warehouses. Once that happens, users can focus on building reports, exploring datasets, and sharing trusted results easily. 3. Legacy data warehouse costs make it harder to invest in strategy. Like other on-prem systems, data warehouses adhere to the old-school model of paying for technology, with the associated hardware and licensing costs and ongoing systems engineering. This kind of inefficient architecture drives more inefficiency. When the business is moving toward becoming data-driven, they’ll continue to ask your team for more data. But responding to those needs means you’ll run out of money pretty quickly. Cloud offers much more cost flexibility, meaning you’re not paying for, or managing, the entire underlying infrastructure stack. Of course, it’s possible to simply port an inefficient legacy architecture into the public cloud. To avoid that, we like to talk about total cost of ownership (TCO) for data warehouses, because it captures the full picture of how legacy technology costs and business agility aren’t matching up. Moving to BigQuery isn’t just moving to cloud—it’s moving to a new cost model, where you’re cutting out that underlying infrastructure and systems engineering. You can get more detail on cloud data warehouse TCO comparisons from ESG.4. A legacy data warehouse can’t flexibly meet business needs. While overnight data operations used to be the norm, the global opportunities for businesses mean that a data warehouse now has to load streaming and batch data while also supporting simultaneous queries. Hardware is the main constraint for legacy systems as they struggle to keep up.Moving your existing architecture into the cloud usually means moving your existing issues into the cloud, and we hear from businesses that doing so still doesn’t allow for real-time streaming. That’s a key component for data analysts and users. Using a platform like BigQuery means you’re essentially moving your computational capabilities into the data warehouse itself, so it scales as more and more users are accessing analytics. Unlimited compute is a pretty good way to help your business become digital. Instead of playing catch-up with user requests, you can focus on developing new features. Cloud brings added security, too, with cloud data warehouses able to do things like automatically replicate, restore and back up data, and offer ways to classify and redact sensitive data. 5. Legacy data warehouses lack built-in, mature predictive analytics solutions. Legacy data warehouses are usually struggling to keep up with daily data needs, like providing reports to departments like finance or sales. It can be hard to imagine having the time and resources to start doing predictive analytics when provisioning and compute limits are holding your teams back.We hear from customers that many of them are tasked with simplifying infrastructure and adding modern capabilities like AI, ML and self-service analytics for business users. The best stories about digital transformation are those where the technology changes and business or cultural changes happen at the same time. One customer told us that because BigQuery uses a familiar SQL interface, they were actually able to shift the work of data analytics away from a small, overworked group of data scientists into the hands of many more workers. Doing so also eliminated a lot of the siloed data lakes that had sprung up as data scientists extracted data one project at a time into various repositories to train ML models.These large-scale computational possibilities save time and overhead, but also let businesses explore new avenues of growth. AI and ML are already changing the face of industries like retail, where predictive analytics can provide forecasting and other tasks to help the business make better decisions. BigQuery lets you take on sophisticated machine learning tasks without moving data or using a third-party tool. We designed BigQuery so that our engineers deploy the resources needed for you to scale. It means your focus can change entirely toward meeting the needs the business has put forth, and bringing a lot more flexibility. BigQuery is fully serverless and runs on underlying Google infrastructure, so it integrates with our ecosystem of data and analytics partner tools. This architecture means you’re continually getting the most up-to-date software stack—analytics that scale, real-time insights, and cutting-edge functionality that includes geospatial and machine learning right from the SQL interface. Streamline your path to data warehouse modernization with BigQuery by learning about Google Cloud’s proven migration methodology and get started with your data warehouse by applying for our migration offer.
Quelle: Google Cloud Platform

Introducing Cloud Run Button: Click-to-deploy your git repos to Google Cloud

As developers, we love that Cloud Run allows you to deploy containerized serverless applications without having to worry about operations, scalability and security. You can package your app in a container, deploy to Cloud Run, and get a fully managed HTTPS endpoint.Today, we are introducing the Cloud Run Button, an image and link you can add to the README of your source code repositories to allow others to deploy your application to Google Cloud Platform using Cloud Run. Check out a demo:Cloud Run Button works with any repository that has a Dockerfile, or that can be built using Cloud Native Buildpacks. When you click the Cloud Run Button to deploy an application, it packages the application source code as a container image, pushes it to Google Container Registry, and deploys it on Cloud Run.For example, you can deploy our cloud-run-hello sample application (which has a Dockerfile) to Cloud Run on your GCP project by clicking this button:Once deployed, this application is hosted in your GCP project, and with Cloud Run’s pay-per-use model, you are only charged when the application handles requests.You can also make your Git repositories easily deployable to Cloud Run by following the instructions on the Cloud Run Button repository. Give it a try and let us know what you think!
Quelle: Google Cloud Platform

Amazon Chime fügt Anrufliste für Sprach- und Videoanrufe hinzu

Amazon Chime zeigt nun eine Liste der letzten eingehenden, ausgehenden und verpassten Anrufe an, damit Sie schnell neu wählen, mit einer Nachricht antworten oder zurückrufen können. Sie können Ihre 1:1-Sprach- und Videoanrufe in der Anrufverlaufliste sehen. Wenn Sie Chime Business Calling aktiviert haben, können Sie auch Anrufe zu und von Ihrer Geschäftstelefonnummer sehen. Bei jedem Anruf sehen Sie den Namen oder die Telefonnummer der anderen Person, das Datum und die Gesprächsdauer. Der Anrufverlauf wird auf allen Ihren Geräten mit Chime synchronisiert, sodass Sie immer den aktuellen Anrufverlauf verfügbar haben.
Quelle: aws.amazon.com

Amazon ECS unterstützt jetzt auch Parameter für Auslagerungsspeicher pro Container

Wenn Sie Amazon ECS mit dem EC2-Start-Typ unter Linux verwenden, können Sie nun die Verwendung von Auslagerungsspeicher auf Containerbasis steuern. Auslagerungsspeicher wird von Betriebssystemen wie Linux verwendet, um Prozessen zu ermöglichen, mehr Speicherplatz zu nutzen, als physisch auf dem Host verfügbar ist; der Betriebssystemkern wird physischen Speicher bei Bedarf auf die Festplatte "auslagern", um die Anforderungen der auf dem Host laufenden Software zu erfüllen. Auslagerungsspeicher ermöglicht es Anwendungen, mehr Speicherplatz zu nutzen, als sie normalerweise nutzen könnten, und zwar auf Kosten einer höheren Latenz und eines geringeren Durchsatzes dieses Speicherzugriffs. Anwendungen, wie beispielsweise Anwendungen mit stark variierendem Speicherbedarf, aber geringerer Empfindlichkeit gegenüber Latenzzeiten, können von der Verwendung von Auslagerungsspeicher profitieren. 
Quelle: aws.amazon.com