Mit Sammlungen den Überblick behalten
Sie können Inhalte basierend auf Ihren Einstellungen speichern und kategorisieren.
Last reviewed 2023-05-19 UTC
Google Cloud bietet Tools, Produkte, Anleitungen und professionelle Dienste für die Migration von Arbeitslasten, Daten und Prozessen von Amazon Web Services (AWS) zu Google Cloud. In diesem Dokument wird erläutert, wie Sie einen Plan für die Migration von AWS zu Google Cloud entwerfen, implementieren und validieren.
Die Diskussion richtet sich an Cloud-Administratoren, die Details zum Planen und Implementieren eines Migrationsprozesses wünschen. Sie ist auch für Entscheidungsträger gedacht, die die Möglichkeit zur Migration bewerten und erfahren möchten, wie die Migration aussieht.
Dieses Dokument ist Teil einer mehrteiligen Reihe zur Migration von AWS zu Google Cloud, die folgende Dokumente enthält:
Die Migration Ihrer Arbeitslasten, Daten und Prozesse von AWS zu Google Cloud kann je nach Umfang und Größe der Migration eine Herausforderung sein und Tage, Wochen oder Monate dauern. Daher empfehlen wir Ihnen, die Migration sorgfältig zu planen und auszuführen.
AWS- und Google Cloud-Produkte, die auf ähnliche Anwendungsfälle ausgerichtet sind, verhalten sich möglicherweise ähnlich hinsichtlich der Bereitstellung, Konfiguration und Verwendung der von ihnen bereitgestellten Ressourcen. Trotz dieser Ähnlichkeiten können diese Ressourcen jedoch erheblich in ihrer Funktionsweise und ihren Anforderungen abweichen. Daher empfehlen wir Ihnen, die Funktionsweise ähnlicher AWS- und Google Cloud-Ressourcen zu prüfen, bevor Sie Ihre Migration planen.
In dieser Reihe finden Sie Anleitungen zu den folgenden Migrationspfaden:
[[["Leicht verständlich","easyToUnderstand","thumb-up"],["Mein Problem wurde gelöst","solvedMyProblem","thumb-up"],["Sonstiges","otherUp","thumb-up"]],[["Schwer verständlich","hardToUnderstand","thumb-down"],["Informationen oder Beispielcode falsch","incorrectInformationOrSampleCode","thumb-down"],["Benötigte Informationen/Beispiele nicht gefunden","missingTheInformationSamplesINeed","thumb-down"],["Problem mit der Übersetzung","translationIssue","thumb-down"],["Sonstiges","otherDown","thumb-down"]],["Zuletzt aktualisiert: 2023-05-19 (UTC)."],[[["\u003cp\u003eGoogle Cloud offers comprehensive resources, including tools, products, guidance, and professional services, to facilitate the migration of workloads, data, and processes from Amazon Web Services (AWS).\u003c/p\u003e\n"],["\u003cp\u003eThis document serves as an introductory guide for cloud administrators and decision-makers on planning, implementing, and validating a migration strategy from AWS to Google Cloud.\u003c/p\u003e\n"],["\u003cp\u003eThe migration process from AWS to Google Cloud can be complex and time-consuming, necessitating careful planning and execution to ensure success.\u003c/p\u003e\n"],["\u003cp\u003eThis guide is part of a series detailing specific migration paths from AWS to Google Cloud, covering compute, data storage, database, and data analytics services, such as migrating from Amazon EC2 to Compute Engine or Amazon S3 to Cloud Storage.\u003c/p\u003e\n"],["\u003cp\u003eAlthough AWS and Google Cloud products may appear similar, they often have distinct operational differences and requirements, making it crucial to assess these differences before commencing the migration.\u003c/p\u003e\n"]]],[],null,["# Migrate from AWS to Google Cloud: Get started\n\nGoogle Cloud provides tools, products, guidance, and professional\nservices to help you migrate workloads, data, and processes from Amazon Web\nServices (AWS) to Google Cloud. This document introduces a discussion\nabout how to design, implement, and validate a plan to migrate from\nAWS to Google Cloud.\n\nThe discussion is intended for cloud administrators who want details about\nhow to plan and implement a migration process. It's also intended for\ndecision-makers who are evaluating the opportunity to migrate and who want\nto explore what migration looks like.\n\nThis document is part of a multi-part series about migrating from AWS to\nGoogle Cloud that includes the following documents:\n\n- Get started (this document)\n- [Migrate from Amazon EC2 to Compute Engine](/architecture/migrate-amazon-ec2-to-compute-engine)\n- [Migrate from Amazon S3 to Cloud Storage](/architecture/migrate-amazon-s3-to-cloud-storage)\n- [Migrate from Amazon EKS to Google Kubernetes Engine](/architecture/migrate-amazon-eks-to-gke)\n- [Migrate from Amazon RDS and Amazon Aurora for MySQL to Cloud SQL for MySQL](/architecture/migrate-aws-rds-to-sql-mysql)\n- [Migrate from Amazon RDS and Amazon Aurora for PostgreSQL to Cloud SQL for PostgreSQL and AlloyDB for PostgreSQL](/architecture/migrate-aws-rds-aurora-to-postgresql)\n- [Migrate from Amazon RDS for SQL Server to Cloud SQL for SQL Server](/architecture/migrate-aws-rds-to-cloudsql-for-sqlserver)\n- [Migrate from AWS Lambda to Cloud Run](/architecture/migrate-aws-lambda-to-cloudrun)\n\nMigrating your workloads, data, and processes from AWS to Google Cloud\ncan be a challenging task and can take days, weeks, or months to complete,\ndepending on the scope and size of the migration. Therefore, we recommend that\nyou plan and execute your migration carefully.\n\nAWS and Google Cloud products that target similar use cases might seem\nsimilar in the way you provision, configure, and use the resources that they\nprovide. However, despite similarities, these resources might differ\nsignificantly in the way they work and in their requirements. We therefore\nrecommend that you assess the ways in which similar AWS and Google Cloud\nresources work before you plan your migration.\n\nThis series provides guidance about the following migration journeys:\n\n- **From AWS compute services to Google Cloud**\n - [Migrate from Amazon EC2 to Compute Engine](/architecture/migrate-amazon-ec2-to-compute-engine)\n - [Migrate VMware VMs to your Google Cloud VMware Engine private cloud](/vmware-engine/docs/workloads/howto-migrate-workloads)\n - [Migrate from Amazon Elastic Kubernetes Service (Amazon EKS) to Google Kubernetes Engine](/architecture/migrate-amazon-eks-to-gke)\n - [Migrate from AWS Lambda to Cloud Run](/architecture/migrate-aws-lambda-to-cloudrun)\n- **From AWS data storage services to Google Cloud**\n - [Migrate from Amazon S3 to Cloud Storage](/architecture/migrate-amazon-s3-to-cloud-storage)\n- **From AWS database services to Google Cloud**\n - [Migrate from Amazon RDS and Amazon Aurora for MySQL to Cloud SQL for MySQL](/architecture/migrate-aws-rds-to-sql-mysql)\n - [Migrate from Amazon RDS and Amazon Aurora for PostgreSQL to Cloud SQL for PostgreSQL and AlloyDB for PostgreSQL](/architecture/migrate-aws-rds-aurora-to-postgresql)\n - [Migrate from Amazon RDS for SQL Server to Cloud SQL for SQL Server](/architecture/migrate-aws-rds-to-cloudsql-for-sqlserver)\n- **From AWS data analytics services to Google Cloud**\n - [Amazon Redshift to BigQuery migration](/bigquery/docs/migration/redshift-overview)\n\nWhat's next\n-----------\n\n- Read about [other AWS to Google Cloud migration journeys](/architecture/migration-from-aws-get-started).\n- Learn how to [compare AWS and Azure services to Google Cloud](/free/docs/aws-azure-gcp-service-comparison).\n- Learn when to [find help for your migrations](/architecture/migration-to-gcp-getting-started#finding_help).\n- For more reference architectures, diagrams, and best practices, explore the [Cloud Architecture Center](/architecture).\n\nContributors\n------------\n\nAuthor: [Marco Ferrari](https://www.linkedin.com/in/ferrarimark) \\| Cloud Solutions Architect"]]
