I have two amazon aws account's and i want to move all SQS EC2 RDS S3 CLOUDFRONT SECURITY GROUP'S to the new account .
And i have EC2 account id and account secret key in the AMI IMAGE for AWS CLI after moving to the new account how can i change all EC2 account id and account secret key to new account?
What is the best and fast way to do so?
Thank You
Some of what you've mentioned is configuration. Some is content. Let's unroll it and go through each one. Generally, the answer is "no".
Create a new SQS queue and point code/configuration at it. Alternatively, you can enable cross-account delegation (though this doesn't change ownership).
Running instances cannot be moved. Either create new instances and reprovision them (with, say, ansible/salt/puppet/chef) or create an AMI of the EC2, share the ami, and relaunch.
Buckets cannot be moved between accounts. You can copy data into a new bucket or enable cross-account delegation (though this doesn't change ownership).
Cloudfront cannot be moved. Creating this in a new account is very easy, though, since it's basically stateless (you don't need to worry about anything beyond setting it up).
Security groups cannot be moved.
And i have EC2 account id and account secret key in the AMI IMAGE for AWS CLI after moving to the new account how can i change all EC2 account id and account secret key to new account?
Use AWS IAM to generate correct user(s) with security keys. This involves using a new ID and key. If you are using IDs and keys you should be comfortable rotating them to reduce security risk.
The alternative is to use IAM roles, which means you don't need to store or use explicit keys.
Ultimately, you should be keeping most of this information in configuration management. This is almost trivial to do with CloudFormation, which describes an entire stack (EC2, cloudfront, security groups, databases) and can create them in a single command.
If you have built your entire infrastructure with CloudFormation you could more easily replicate it, even in another account.
You still need to deal with data migration, which will be different depending on your deployment setup.
If you use configuration management most if not all of your OS can be replicated in your other account too.
While AWS does have a method of reverse engineering a CloudFormation template based on your current environment I've never tried it, sounds like you should give it a go.
The aws cli has commands to move s3 data "aws s3 sync s3://from s3://to". You may need to export or otherwise share other data like RDS and SNS.
SQS
Create a new SQS queue and point code/configuration at it. Alternatively, you can enable cross-account delegation (though this doesn't change ownership). EC2
Running instances cannot be moved. Either create new instances and reprovision them (with, say, ansible/salt/puppet/chef) or create an AMI of the EC2, share the ami, and relaunch. RDS
RDS instances can't be copied. You will need to extract the data and transfer it to a new database instance. S3
Buckets cannot be moved between accounts. You can copy data into a new bucket or enable cross-account delegation (though this doesn't change ownership).
I would just use AWS Organizations to roll up your child account into the parent one, rather than trying to move everything by hand.
