Krypto: Nutzer verklagen Coinbase wegen Scam
2021 fielen zahlreiche Coinbase-Nutzer auf einen Scam herein, der sie um ihr Kryptogeld brachte. Coinbase soll nicht gut genug reagiert haben. (Kryptowährung, Wirtschaft)
Quelle: Golem
Free New Course Coming Soon: Create Your Site With WordPress.com
Are you building a website for the first time? Returning to WordPress after a break? Just looking to get caught up on the newest Gutenberg features?
You’re in the right place.
We’re excited to announce a brand new free course called Create Your Site.
If you’re searching for a solid foundation for making a WordPress.com website, look no further. This is the perfect introduction for anyone with an idea: bloggers, business owners, or creators in any medium.
Join our waitlist today, and you’ll be first in line to find out when the course officially launches in just a few weeks.
Join the waitlist
This course includes:
A clear roadmap for building a WordPress.com site
Hands-on exercises broken down into step-by-step instructions
A self-paced environment so you can learn at a rate that works best for you
A private community to discuss, collaborate, and engage with other students to network and swap feedback
Additional tips, resources, ideas, and feedback provided by WordPress experts
By the end of this course, you’ll know which specific actions to take to build your site with WordPress.com, as well as your next steps after that. After all, launching your site is only the beginning of your journey.
What you’ll learn:
With a combination of short videos, step-by-step instructions, and detailed explanations (when necessary), we cover:
Themes
Pages
Content
Block Editor
Site Editor
Templates
Menus
You can move through the course as quickly as you like, or take your time to dig deeper. You can also repeat the course as many times as you like. Start with a practice site, build your very first site, or use it to build many more sites. The choice is yours!
The best part? At the risk of repeating ourselves: It’s free!
Join our waitlist for Create Your Site with WordPress.com, so you don’t miss the announcement when it opens for enrollment.
Join the waitlist
Quelle: RedHat Stack
EVO2CLOUD – Vodafone’s SAP migration from on-prem to Google Cloud
Editor’s note: Vodafone is migrating its SAP system, the backbone for its financial, procurement and HR services, to Google Cloud. Vodafone’s SAP system has been running on-prem for 15 years, during which time it has significantly grown in size, making this one of the largest and one of the most complex SAP migrations in EMEA. By integrating its cloud-hosted SAP system to its data ocean running on Google Cloud, Vodafone aims to introduce operational efficiency and drive innovation.Vodafone: from telco to tech-coVodafone, a leading telecommunications company in Europe and Africa, is accelerating its digital transformation from a telco to a tech-co that provides connectivity and digital services such as 5G services, IoT, TV and hosting platforms. Vodafone is partnering with Google Cloud to enable various elements of this transformation — from building one of the industry’s largest data oceans on Google Cloud to driving value from data insights and deploying AI/ML models. One of Vodafone’s core initiatives is ‘EVO2CLOUD’, a strategic program to migrate its SAP workloads to Google Cloud. Vodafone uses SAP for its financial, procurement and HR services; it’s the backbone of its internal and external operations. High availability and reliability are fundamental requirements to ensure smooth operation with minimal downtime. Moreover, hosting SAP on Google Cloud is a foundation for digital innovation and maintaining cybersecurity.EVO2CLOUD: enabling SAP on Google CloudWhen complete, EVO2CLOUD will have been one of the largest SAP to Google Cloud migrations. Over the course of two to three years, EVO2CLOUD will enable the transformation of a broad SAP ecosystem composed of more than 100 applications that have been running on-prem for the past 15 years, to a leaner, more agile and scalable deployment that is cloud-first and data-led. With EVO2CLOUD, Vodafone aims to improve operational efficiency, increase its NPS score and maximize business value by incorporating SAP into its cloud and data ecosystem, introducing data analytics capabilities to the organization and enabling future innovations. As such, EVO2CLOUD is providing standardized SAP solutions and facilitating the transition to a data-centric model that leverages real-time, reliable data to drive data-based corporate decision making. SAP’s operating model on Google CloudVodafone foresees a step change in its operating model, where it can leverage an on-demand, highly performant, and memory-optimized M1 and M2 infrastructure at a low cost. Thanks to infrastructure as code, this improved operating model will provide increased capacity, high availability, flexibility and consistent enforcement of security rules. Vodafone is also reshaping its security architecture and leveraging the latest technologies to ensure privacy, data protection, and resilient threat detection mechanisms. Furthermore, it expects to increase its release-cycle frequency from bi-annual rollouts to weekly release cycles, increasing agility and introducing features faster. In short, Vodafone wants to build agility and flexibility in all that it does — from design all the way to delivery and operations, and DevSecOps will need to be an integral part of its operating model.Leveraging data to drive innovationBefore migrating to Google Cloud, it was difficult for Vodafone to extract and make use of its SAP data. Now with the transition to the cloud and with Google Cloud tools, it can expand how it uses its data for analytics and process mining. This includes operations and monitoring opportunities to map data with other external sources, e.g., combining HR data from SAP with other non-SAP data, resulting in data enrichment and additional business value. Vodafone is continuing to explore opportunities with Google Cloud to identify even more ways to leverage their data.Why Google Cloud and what’s NextIn fact, Vodafone is not only building its system on Google Cloud, but rather sees this project as the first step in a three-phase transformation: Redesigning the SAP environment and migrating to Google Cloud to make it ready for integration with Vodafone’s data ocean.Integrating SAP with Vodafone’s data ocean that sits on Google BigQuery. Leveraging cloud-based data analytics tools to optimize data usage, processes, and how Vodafone operates its business. Moving to Google Cloud is in line with Vodafone’s data-centric strategy, which aims to introduce enhanced features in data analytics and artificial intelligence, and effectively serves Vodafone’s employees and customers in more real-time. Transformation and change managementThe migration to Google Cloud is underway with Vodafone, Google Cloud, SAP and Accenture working together as one team to make this transformation a success. “An innovative and strategic initiative, co-shaped with a truly integrated partnership. A daily collaboration among four parties, Vodafone, Google, SAP and Accenture are executing the cloud transformation of a complex SAP estate within a compressed timeframe, for rapid benefits realization and accelerated innovations in the cloud.” – Antonio Leomanni, EVO2CLOUD program lead, AccentureVodafone recently celebrated the pilot’s go-live, an important milestone in this program. Change management has been fundamental to this transformation, incorporating learning and enablement, financial governance, lifecycle management, security, architecture reviews and innovation. By focusing on these disciplines, Vodafone and Google Cloud are ensuring the success of this transformation and strengthening their partnership.ConclusionIn conclusion, the SAP migration aligns with Vodafone’s data strategy by enabling a step change towards operational efficiency and innovation, by integrating SAP to Vodafone’s data ocean. The key to the success of this ongoing migration is:Clear migration requirements and objectives – infrastructure availability, security and resilience. Strong change managementApplication of the right technologies and toolsTo learn more about how Google Cloud is advancing the telecommunications industry visit us here.Related ArticleDelivering data-driven IT and networks, Google Cloud expands its analytics partner ecosystem for telecommunicationsCommunication Service Providers are becoming data driven and leveraging Google Cloud and their partners to solve tough problems.Read Article
Quelle: Google Cloud Platform
Fortress Vault on Google Cloud: Bringing private data to NFTs
Over the past two years, the general population has become more acquainted with cryptocurrencies and the first iterations of NFTs, which were among the earliest use cases for blockchain technology. This public awareness and participation has led to a growing interest in, and demand for, Web3 technology at the enterprise level. But building trust in a new wave of technology, especially in large organizations, doesn’t happen overnight. That is why it’s critical for Web3 technologists to bring the broader benefits, use cases, and core capabilities of blockchain to the forefront of the conversation. If businesses don’t understand how this new technology can help them, how can they prioritize it among competing tech plans and resources? And without baseline protocols that account for privacy, confidential data, and IP, how can they future-proof a business? Answering these questions and delivering trustworthy infrastructure is exactly why Scott Purcell and I founded Fortress Web3 Technologies — to bring about the next wave of Web3 utility. The company’s goal is to provide infrastructure that eliminates barriers to Web3 adoption with RESTful APIs and widgetized services that enable businesses to quickly launch and scale their Web3 initiatives. Our tools include embeddable wallets for NFTs and fungible rewards tokens; NFT minting engines; and core financial services . These include payments, compliance, and crypto liquidity via our wholly-owned financial institution, Fortress Trust. Being overseen by a chartered, regulated entity ensures privacy, compliance and business continuity.Fortress chose Google Cloud to help usher in this new-wave technology because no other cloud provider is better suited to helping regulated industries get up to scale on our Web3 infrastructure and blockchain technology. I’ll get into more specifics below, but at the highest level: IPFS (the current standard distributed storage) is going to face major resistance when it comes to industries that are heavily regulated or deal in ownership rights. By leveraging Google Cloud, which has critical certifications such as HIPPA, Department of Defense, ISO, and Motion Picture, we’re striking the appropriate balance between decentralization and centralization, using the best of both technologies. The Fortress Vault on Google Cloud is a huge and necessary step forward as the first ever NFT-database solution to protect intellectual property, confidential documents, and other electronic records. It represents the first technology that marries privately stored content with the accessibility, privacy, portability, and provenance that blockchain provides. Understanding Non-Fungible Tokens (NFTs)An NFT is not an expensive jpeg. From a technical point of view, an NFT is a unique key stored in a distributed and trustless ledger we call a blockchain. This blockchain token is uniquely identifiable from any other token and acts as a digital key to authenticate ownership and unlock data held in a database. While different blockchains have adopted different standards, Ethereum standards are a good proxy to represent overall concepts. Going back to the primitives, if you read the EIP 721 proposal, metadata is explicitly optional. While today’s NFT hype has indeed leveraged that technology to monetize and distribute digital art, the potential of blockchain is in the ability to digitally represent ownership of a wide variety of different asset classes on a decentralized ledger. Unique, non-fungible tokens are not a new concept. We use them every day in technical systems for things like authentication, database keys, idempotency, and much more. Now, thanks to blockchain technology, you can take those out of their walled gardens and into an open platform that can lead to transformational utility and applications. Take real estate, for example. Instead of a paper-based title documenting you as the owner of your home, imagine that the title is tokenized with an NFT on a blockchain. Any platform could cryptographically verify the authenticity of that form of title along with its provenance in real time and confirm that you’re the rightful owner of that property. But, perhaps you don’t want the title of your property visible to others, nor the associated permits, tax documents, architectural drawings, contractor lists, and other documents. Maybe you just want banks, insurance companies, and others to be able to confirm that you are indeed the owner without revealing the details of those records. The NFT metadata records immutable public-facing provenance, while the underlying data remains private and protected using Fortress Vault on Google Cloud. Apply that same utility to other sensitive information such as medical records, intellectual property, estate documents, corporate contracts, and other confidential information and it’s easy to see how enterprises are just now exploring how to hold traditional assets as NFTs.Fortress Vault: Intellectual Property, Confidential Documents, and Other Electronic RecordsWhat NFTs and Web3 have been lacking is the ability to make the tokenized data accessible exclusively by the owner — and only the owner. NFTs are a digital key to unlock everything ranging from music and event tickets, to real estate deeds and healthcare records, to estate documents, and to everything in the world that’s digital.This is why we created the Fortress Vault. When building it, we had to make a fundamental decision: Either go with a distributed and permissionless storage protocol like IPFS, filecoin, or other blockchain-based database offerings, or work with an industry-leading cloud platform that understands data integrity and is establishing itself as the leader in the space. Ultimately, we chose Google Cloud for its industry-leading object storage, professional management, fault tolerance, and myriad of certifications for architecture and data integrity.Some of the challenges faced when vaulting a vast variety and quantity of digital content at scale include:Balancing data availability versus cost of storageData redundancyLong term archival needsBusiness continuityFlexibility to meet current and future needs of the rapidly evolving Web3 industry. Google Cloud is the clear leader across all of these pain points. The object lifecycle management of Google Cloud Storage enables efficient transition between storage classes when either the data matures to a certain point or it’s updated with newer files. Content in the Fortress Vault can range from on-demand data to long-term uses, such as estate planning documents that won’t be accessed for 30 years. When storing NFT data, robust disaster recovery is table stakes. We quickly gravitated to the automatic redundancy options and multi-region storage buckets that let us customize where we store our data without massive devops and management overhead. By leveraging Google Cloud, we can offer industry leading retention, redundancy, and integrity for our customers’ NFT content.Working with a leader in data storage was key to making this a reality. Additionally, Google Cloud shares our vision of bringing every industry forward into the world of Web3. We are both focused on building the critical infrastructure that allows everyone from Web3 native companies to Fortune 500 brands navigate the strategic shift to blockchain technology.Why Web3 Matters“Web3” is shorthand for the “third wave” of the internet and the technological innovation that brought us here. Web 1 — the earliest internet — democratized reading and access to information, opening the doors to mass communication. Web 2 expanded on that with the ability to read and “write.” It democratized publishing by letting people directly engage in producing information through blogs, social media, gaming, and contributions to collective knowledge. Web 3 expands our technological capabilities even more with the ability to read, write, and “own.” With blockchain, we can now establish clear provenance with visibility into the origination of ownership of any tokenized asset, and we can see the chain of ownership. We can rely on this next-generation technology to track, authenticate, protect, and keep a ledger of our assets. With the Fortress Vault on Google Cloud, we have the capability to ensure the integrity of non-public data while making it accessible via NFTs. This is a game changer for Web3 adoption, particularly in industries like music, event ticketing, gaming, finance, transportation, real estate, and healthcare. Every industry can benefit from the ability to tokenize assets on blockchain technology without leaving the trusted safety of Google Cloud data storage. The market for NFTs is everyone. And the Fortress Vault on Google Cloud is the technology evolution that makes it possible for Web3 innovators to confidently build, launch, and scale their initiatives across every industry imaginable.Related ArticleWhat’s new in Google Cloud databases: More unified. More open. More intelligent.Google Cloud databases deliver an integrated experience, support legacy migrations, leverage AI and ML and provide developers world class…Read Article
Quelle: Google Cloud Platform
Reliable peering to access Google Cloud
Peering is often seen as a complex and nuanced topic, particularly for some of our Cloud customers. Today we’d like to demystify peering’s inner workings and share how a peering policy update that requires local redundancy helps improve reliability for our users and customers. Redundancy is a well understood and documented concept to improve reliability. We have talked previously about how our significant investments in infrastructure and peering enables our internet content to reach users and how we are making our peering more secure. Google Cloud on the internetEvery day Google Cloud customers collaborate with colleagues using Workspace, leverage Google Cloud CDN to serve content to users worldwide or choose to deploy a Global Cloud Load Balancer to leverage our anycast IPs. Each use case has the same thing in common: these and many other Google products rely on peering to connect Google’s global network to ISPs worldwide to reach their destination, users like you and me. Peering delivers internet trafficPeering is the physical fiber interconnection between networks such as Google and your Internet Service Provider (ISP), or between Google and cloud customers, which occurs at various facilities all around the world. Its purpose is to exchange public internet traffic between networks to optimize for cost and performance. Google has built our network to over 100 facilities worldwide to peer with networks both large and small. This is how Google provides a great experience for all of our users, reduces costs for ISPs, and is one of several ways our cloud customers can connect to the Google network. One of the other common ways enterprises connect to Google Cloud that is often confused with peering is Dedicated Interconnect, which offers private connectivity between your on-premise environment and Google Cloud. Think of peering like part of a city water system where the pipes are the fiber optic cables and the water is the bits of data coming to your phone, computer, or data center. Just as your city’s water system needs to interconnect to your house plumbing, Google’s global network needs to interconnect to your neighborhood ISP to deliver all types of Google traffic. The water flowing out of your sink faucet is analogous to being able to use Google services on your home Wi-Fi. Peering infrastructureThousands of networks including Google are peering with each other all over the world every day. Networks who peer mutually agree on the locations and capacity to address traffic demand, cost, and performance. Since there are so many networks worldwide it is not practical for every network to peer with each other so most networks retain some type of IP transit that allows users to reach the entirety of the internet. Essentially, IP transit is a paid service offered to networks to ‘transit’ another well connected network to reach the entirety of the internet. This transit also acts as a failover path for when a peering connection is unavailable, and plays an important role in ensuring the universal reachability of every endpoint on the Internet. One potential downside to transit is that traffic may traverse an indirect and costly path to reach an end user which therefore can decrease performance compared to peering. Google’s preference is to deliver all traffic on the most optimal peering paths to maximize performance.When peering goes downWith any type of physical infrastructure, components can malfunction or need to be taken out of service for maintenance. The same is true for the infrastructure that supports peering. Downtime can sometimes last days or weeks depending upon the cause and time to repair. During downtime, internet traffic to and from Google gets rerouted to failover paths. Sometimes these paths are another peering location in the same city, sometimes they are rerouted hundreds or thousands of miles away to peering in a different city or even country, and in some cases to an IP transit connection if no other peering connection is available. Much of this depends upon how and where a network is peered with Google. The further the traffic is physically rerouted from the intended peering connection, and if any IP transit connections are in the traffic path, the higher the likelihood of increased latency, packet loss, or jitter, all of which can translate into a frustrating or poor user experience. A deep and diverse peering footprintOver many years we have built our peering with ISPs and cloud customers to be both physically redundant and locationally diverse to ensure an optimal user experience for all Google services. This translates to a deep and diverse peering interconnection footprint with networks and customers around the world. As Google Cloud services like Premium Network Tier, Cloud VPN, and Workspace use peering to reach their end users, this type of planning helps to avoid user experience issues mentioned above. A more stable and predictable peering interconnectTo help achieve our goal of a reliable experience for all Google users we have recently updated our peering policy to require physical redundancy on all Google private peering connections within the same metropolitan area. This update will allow Google and ISPs to continue to exchange traffic locally during peering infrastructure outages and maintenance under most circumstances. For our customers and users this means more predictable traffic flows, consistent and stable latency, and a higher effective availability of peering that provides an overall more predictable experience with Google services, while still offering cost savings to ISPs. There are a multitude of factors that can influence performance of an application on the internet, however this change is designed so that outages and maintenance on our peering infrastructure will be a less noticeable and impacting experience. You can read more details about the change on our peering page.Fig A – Two examples of metropolitan area peering redundancy. A redundant peering link (green) in the same metropolitan area helps keep traffic local during peering infrastructure maintenance or outages.Working with our peering partners and customersWe are working closely with our existing and new Google Cloud customers and ISP peers to ensure we build out locally redundant peering interconnects. We also know that many networks have challenges to build this configuration so we are identifying ways to work with them. We encourage Google Cloud customers and any ISPs who are interested to review their redundancy topology with Google to contact us, and to also review our best peering practices. To learn more about peering and to request peering with Google please visit our Peering websiteRelated Article20+ Cloud Networking innovations unveiled at Google Cloud NextUpdates to the Google Cloud Networking portfolio center on content delivery, migrations, security, and observability, to name a few.Read Article
Quelle: Google Cloud Platform
Manage storage costs by automatically deleting expired data using Firestore Time-To-Live (TTL)
We are thrilled to announce that we have added time-to-live (TTL) support for both Firestore Native and Datastore mode!Use Firestore TTL policies to remove out-of-date data from the database. You can think of it as a managed deletion mechanism built-into Firestore. Once documents or entities are considered expired, they will be eligible for deletion. Similar to direct DELETE operations, it will also notify all external services (ex: Function Triggers, etc.), upon a deletion event.Common use casesGarbage collection. TTL can be handy if you have data that has a well-defined lifecycle for a document.Support time relevant features natively. You can rely on TTLs if you want to build features relying on ephemeral data.Security and privacy compliance. There are some regulations that require data retention for no longer than a certain time. You will have the flexibility to configure different expiration at the document level, which can help you meet the requirements from varying sources.Example walkthroughSounds like a good candidate for your application? Let’s walk through an example to see how it works from end to end. The example below uses documents and collections, but it works similarly for entities and kinds.Assume you have a database that saves lots of documents in collection Chats and some of them will be useless at some point in the future.First of all, you need to decide on a field to use as the TTL field, and that field must contain a timestamp value. For example, you can choose to designate the expireAt field as a TTL field, even if your documents don’t contain values for this field yet. There are two ways of configuring TTL policies:Use the gcloud CLI. You can find some sample commands to view and modify TTL policies. Use the Google Cloud Console. You can navigate to the Firestore Time-to-live configuration page to configure a new policy.Now that you have configured TTL policies, the documents should be updated with the TTL field if not already. In this case it is expireAt that serves as TTL field.That’s everything you need to do. Once a document expires, it’s eligible for deletion, and Firestore will perform the deletion on your behalf.Want to learn more? Check out the documentation and happy databasing.Special thanks to Minh Nguyen, Lead Product Manager for Firestore, and Joseph Batchik, Software Engineer for Firestore, for contributing to this post.Related ArticleAll you need to know about Firestore: A cheatsheetBuilding applications is a heavy lift due to the technical complexity, which includes the complexity of backend services that are used to…Read Article
Quelle: Google Cloud Platform
Best kept security secrets: How Cloud EKM can help resolve the cloud trust paradox
Whether driven by government policy, industry regulation, or geo-political considerations, the evolution of cloud computing has led organizations to want even more control over their data and more transparency from their cloud services. At Google Cloud, one of the best tools for achieving that level of control and transparency is a bit of technological magic we call Cloud External Key Manager (EKM). Cloud EKM can help you protect your cloud data at rest with encryption keys which are stored and managed in a third-party key management system that’s outside Google Cloud’s infrastructure, and ultimately outside Google’s control. This can help you achieve full separation between your encryption keys and your data stored in the cloud. Cloud EKM works with symmetric and asymmetric encryption keys, and offers organization policies that allow for fine-grained control over what types of keys are used. Via Key Access Justification (KAJ) it also offers the way for clients to control each key use.At their core, many cloud security and cloud computing discussions are about the kinds of trust that Cloud EKM specifically and encryption more broadly can help create. While the concept of digital trust is much bigger than cybersecurity and its tripartite components of security, privacy, and compliance, one of the most crucial themes of cloud computing is the cloud trust paradox. In order to trust the cloud more, you must be able to trust it less, and external control of keys and their use can help reduce concerns over unauthorized access to sensitive data.How it worksFrom our Cloud EKM documentation, you can use keys that you manage within a supported external key management partner to protect data within Google Cloud. You can protect data at rest in services that support CMEK, or by calling the Cloud Key Management Service API directly.Cloud EKM provides several benefits:Key provenance: You control the location and distribution of your externally-managed keys. Externally-managed keys are never cached or stored within Google Cloud. Google cannot see them. Instead, Cloud EKM communicates directly with the external key management device for each request.Access control: You manage access to your externally-managed keys. Before you can use an externally-managed key to encrypt or decrypt data in Google Cloud, you must grant the Google Cloud project access to use the key. You can revoke this access at any time.Centralized key management: You can manage your keys and access policies from a single location and user interface, whether the data they protect resides in the cloud or on your premises. The system that managed the keys is entirely outside Google control.In all cases, the key resides on the external system, and is never sent to Google. Here’s how it works:Create or use an existing key in a supported external key management partner system. This key has a unique URI.Grant your Google Cloud project access to use the key, in the external key management partner system.Create a Cloud EKM key in your Google Cloud project, using the URI for the externally-managed key.The Cloud EKM key and the external key management partner key work together to protect your data. The external key is never exposed to Google and cannot be accessed by Google employees. Furthermore, Cloud EKM can be combined with Key Access Justifications (KAJ) to establish cryptographic control over data access. KAJ with Cloud EKM can give customers the ability to deny Google Cloud administrators access to their data at rest for any reason, even in situations typically exempted from customer control, such as outages or responses to third-party data requests. KAJ does this by providing customers a clear reason why data is being decrypted, which they can use to programmatically decide whether to permit decryption and thus allow access to their data. Previously, we’ve discussed three patterns where keeping the keys off the cloud may in fact be truly necessary or outweighs the benefits of cloud-based key management. Here’s a brief summary of those three scenarios where Cloud EKM can help solve these Hold Your Own Key dilemmas.Scenario 1: The last data to go to the cloudAs organizations complete their digital transformations by migrating data processing workloads to the cloud, there is often a pool of data that can not be moved to the cloud. Perhaps it’s the most sensitive data, the most regulated data, or the data with the toughest internal security control requirements.Finance, healthcare, manufacturing and other heavily-regulated organizations face myriad risk, compliance, and policy reasons that may make it challenging to send some of their data to a public cloud provider. However, the organization may be willing to migrate this data set to the cloud as long as it is encrypted and they have sole possession of the encryption keys. Scenario 2: Regional regulations and concernsRegional requirements are playing a larger role in how organizations migrate to and operate workloads in the public cloud. Some organizations are already facing situations where they are based in one country and want to use a cloud provider based in a different country, but they aren’t comfortable with or legally allowed to give the provider access to encryption keys for their stored data. Here the situations are more varied, and can include an organization’s desire to stay ahead of evolving regulatory demands or industry-specific mandates. Ultimately, this scenario allows organizations to utilize Google Cloud while keeping their encryption keys in the location of their choice, and under their physical and administrative control.Scenario 3: Centralized encryption key controlThe focus here is on operational efficiency. Keeping all the keys within one system to cover multiple cloud and on-premise environments can help reduce overhead and attack surface, thus helping to improve security. As Gartner researchers concluded in their report, “Develop an Enterprisewide Encryption Key Management Strategy or Lose the Data1,” organizations are motivated to reduce the number of key management tools. “By minimizing the number of third-party encryption solutions being deployed within an environment, organizations can focus on establishing a cryptographic center of excellence,” Gartner researchers saidGiven that few organizations are 100% cloud-based today for workloads that require encryption, keeping keys on-prem can streamline key management. Centralizing key management can give the cloud user a central location to enforce policies around access to keys and access to data-at-rest, while a single set of keys can help reduce management complexity. A properly implemented system with adequate security and redundancy outweighs the need to have multiple systems.Do I need Cloud EKM?Whether protecting highly sensitive data, retaining key control to address geopolitical and regional concerns, or supporting hybrid and multi-cloud architectures, Cloud EKM is best suited for those Google Cloud customers who must keep their encryption keys off of the cloud and always under their full control. To learn more about Cloud EKM, please review these resources:Our research explaining why Google Cloud users can benefit from Cloud EKMThe most recent updates to Cloud EKMTake a deeper dive into the cloud trust paradox1. Gartner, Develop an Enterprisewide Encryption Key Management Strategy or Lose the Data, David Mahdi, Brian Lowans, March 2022.Related ArticleBest Kept Security Secrets: Tap into the power of Organization Policy ServiceOrganization Policy Service is a powerful tool for creating broad security guardrails in the cloud. Learn more about how this Best Kept S…Read Article
Quelle: Google Cloud Platform
Schnelleres Datenbank-Failover mit Amazon Web Services JDBC-Treiber für PostgreSQL
Der AWS JDBC-Treiber für PostgreSQL ist jetzt allgemein für die Verwendung mit Ihren Amazon RDS- oder Amazon Aurora PostgreSQL-kompatiblen Datenbankclustern verfügbar. Dieser Wrapper-Treiber wurde entwickelt, um mit dem PostgreSQL Community-Traiber zusammenzuarbeiten und eine verbesserte Failover-Behandlung für geclusterte Datenbanken wie Aurora PostgreSQL zu bieten. Der AWS JDBC-Treiber für PostgreSQL ist per Drop-In mit Ihren bestehenden Anwendungen kompatibel, da er neben dem Community-Treiber auch Failover-Funktionen bietet, so dass Sie weniger Anwendungsänderungen vornehmen müssen. Diese Version ersetzt den eigenständigen AWS JDBC-Treiber für PostgreSQL, der zuvor als Vorversion veröffentlicht wurde.
Quelle: aws.amazon.com
Amazon Chime gibt neue mobile Apps bekannt, deren Funktionen Ihre Meetingerfahrung verbessern
Neue Versionen der mobilen iOS- und Android-Apps von Amazon Chime werden mit einer neuen Erfahrung eingeführt, die Ihre Amazon Chime Meetings auf mobilen Geräten verbessern soll. Dieses Update führt Funktionen ein, mit denen Sie leichter an Meetings teilnehmen können, wenn Sie unterwegs und nicht am Arbeitsplatz sind. Das Update umfasst einen neuen Anzeigebildschirm, eine neue Meetingbeitrittserfahrung, neue Meetingsteuerungselemente, Leistungsverbesserungen und mehr.
Quelle: aws.amazon.com
AWS Neuron fügt Unterstützung für Amazon-EC2-Trn1-Instances hinzu, um leistungsstarkes, kostengünstiges Deep-Learning-Training im großen Maßstab freizuschalten
AWS Neuron fügt Unterstützung für von AWS Trainium betriebene Amazon-EC2-Trn1-Instances hinzu, um leistungsstarkes, kostengünstiges Deep-Learning-Training im großen Maßstab freizuschalten. Das Neuron SDK umfasst einen Compiler, Laufzeitbibliotheken und Profiling-Tools, die in beliebte ML-Frameworks wie PyTorch und Tensorflow integriert werden. Mit diesem ersten Release von Neuron 2.x können Entwickler jetzt Deep-Learning-Training-Workloads auf Trn1-Instances ausführen und bis zu 50 % Trainingskosten gegenüber vergleichbaren GPU-basierten EC2-Instances sparen und dabei die beste Trainingsleistung in der AWS Cloud für beliebte NLP-Modelle erhalten.
Quelle: aws.amazon.com
