I need to move my entire AWS Windows Infrastructure over to a separate root account. What are the steps?

Question

I tried copying files over per other guides that I found, but this did not work for me.

Is there a simple way to just create an image of my current infrastructure port it to a new account? Below I have provided the error that my web app receives, as well as AWS's response to the issue.

This occurs when my point DNS to the "new" server.

1) On checking the instance (i-028c4caedaae3ca1e), i can see, it is passing all the status checks and is in running state.Also, i don't see any traffic block on Security group, NACL or route table.

2) On investigating further and checking for similar issues on Third party websites and Microsoft support blogs or articles. I found something related to the following errors :

**[DBNETLIB][ConnectionOpen (SECCreateCredentials()).]SSL Security error.
or
[DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error.**

-> Since, we at AWS Premium Support does not have any visibility on the OS level of instance due to the security policies and also does not have much insight about any running any third party application, this is something that falls outside of our scope of support and Shared Responsibility Model. However, I would still like to share my suggestions to help you in the best effort basis.

re:Post Agent · Answer

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:

1. 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.

2. Prepare the AWS environment: In your new account, set up the necessary Virtual Private Cloud (VPC) and networking configurations.

3. 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.

4. 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.

5. Migrate other services: Follow specific migration procedures for other AWS services you're using, such as RDS, ElastiCache, or Lambda.

6. Configure and test: Set up your applications and services in the new account, ensuring all connections and dependencies are properly configured.

7. Validate the migration: Thoroughly test your migrated workload to ensure it functions as expected and meets all security and compliance requirements.

8. Optimize: After migration, optimize your workload by resizing instances, configuring auto-scaling, and implementing cost-saving strategies.

9. 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](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-microsoft-workloads-aws/migrating-windows-server-workloads.html)  
[Resource replication or migration between AWS accounts - AWS Prescriptive Guidance](https://docs.aws.amazon.com/prescriptive-guidance/latest/transitioning-to-multiple-aws-accounts/resource-migration.html)

Edwin · Answer

Hello,

Can an AWS Expert suggest a solution here for me?

I need to move my entire AWS Windows Infrastructure over to a separate root account. What are the steps?

Contenus pertinents