- Mais recentes
- Mais votos
- Mais comentários
Moving your entire AWS Windows Infrastructure to another master account is a complex process that requires careful planning and execution. Unfortunately, there isn't a simple way to create an image of your current infrastructure and port it directly to a new account. However, you can follow these steps to migrate your Windows workload:
-
Assess and plan: Identify all the applications and workloads you need to migrate. Create a detailed migration plan, estimate costs, and identify the appropriate AWS services for hosting your migrated workloads.
-
Prepare the AWS environment: In your new account, set up the necessary Virtual Private Cloud (VPC) and networking configurations.
-
Choose a migration tool: Select an appropriate migration tool based on your specific needs. AWS Application Migration Service, AWS Migration Hub Orchestrator, or VM Import/Export are recommended options for large-scale infrastructure migrations.
-
Migrate your resources:
- For EC2 instances: Create custom AMIs in your source account, share them with the target account, launch new EC2 instances from the shared AMIs in the target account, and then deregister the shared AMIs.
- For data in S3 buckets: Use S3 cross-account replication or grant access to the S3 bucket from the target account.
- For DynamoDB tables: Use AWS Backup, DynamoDB import/export to Amazon S3, or other available methods.
- For EFS file systems: Use AWS DataSync to transfer data between EFS file systems in different accounts.
-
Migrate other services: Follow specific migration procedures for other AWS services you're using, such as RDS, ElastiCache, or Lambda.
-
Configure and test: Set up your applications and services in the new account, ensuring all connections and dependencies are properly configured.
-
Validate the migration: Thoroughly test your migrated workload to ensure it functions as expected and meets all security and compliance requirements.
-
Optimize: After migration, optimize your workload by resizing instances, configuring auto-scaling, and implementing cost-saving strategies.
-
Monitor and manage: Set up monitoring using Amazon CloudWatch to ensure optimal performance and security of your migrated workload.
Regarding the specific error you're encountering, it appears to be related to SSL security when establishing a database connection. This is likely an application-level issue rather than an AWS infrastructure problem. Since it involves the operating system and potentially third-party applications, it falls outside the scope of AWS Premium Support. You may need to investigate further at the application level, possibly consulting with the application vendor or a Windows system administrator to resolve the SSL security error.
Sources
Migrating Windows Server - AWS Prescriptive Guidance
Resource replication or migration between AWS accounts - AWS Prescriptive Guidance
Conteúdo relevante
- AWS OFICIALAtualizada há um ano
- AWS OFICIALAtualizada há um ano
- AWS OFICIALAtualizada há 9 meses