CODEWITHSUNDEEP
amazon-web-servicesterraformterraform-provider-aws
Kannaiyan
Kannaiyan

Reputation: 13055

Import current state of my cloud AWS account with terraform

I would like to version control my cloud resources initially before using it to apply through Terraform. Is there anyway I can run a single command and store the current state of my cloud?

I have tried to use Terraform's import command:

terraform import ADR ID

But this takes a long time to identify all the resources and import them.

I have tried terraforming but this also needs a resource type to import:

terraforming s3

Is there any tool that can help in importing all existing resources?

Upvotes: 0

Views: 1236

Answers (2)

ppmag
ppmag

Reputation: 75

I'm using terraformer to import my existing AWS infrastructure. It's much more flexible than terraforming and has no issues mentioned in answers.

Upvotes: 2

ydaetskcoR
ydaetskcoR

Reputation: 56997

While this doesn't technically answer your question I would strongly advise not to try and import an entire existing AWS account into Terraform in a single way even if it was possible.

If you look at any Terraform best practices an awful lot of it comes down to minimising blast radius of things so only things that make sense to be changed at the same time as each other are ever applied at the same time. Charity Majors wrote up a good blog post about this and the impact it had when that wasn't the case.

Any tool that would mass import things (eg terraforming) is just going to dump everything in a single state file. Which, as mentioned before, is a bad idea.

While it sounds laborious I'd recommend that you being your migration to Terraform more carefully and methodically. In general I'd probably say that only new infrastructure should use Terraform, utilising Terraform's data sources to look up existing things such as VPC IDs that already exist.

Once you feel comfortable with using Terraform and structuring your infrastructure code and state files in a particular way you can then begin to think about how you would map your existing infrastructure code into Terraform state files etc and begin manually importing specific resources as necessary.

Doing things this way also allows you to find your feet with Terraform a bit better and understand its limitations and strengths while also working out how your team and/or CI will work together (eg remote state and state file locking and orchestration) without tripping over each other or causing potentially crippling state issues.

Upvotes: 3

Related Questions