Work in progress - please report any issues you find.

This utility 'AWS to Terraform' (aws2tf) reads an AWS Account and generates all the required terraform configuration files (.tf) from each of the composite AWS resources

It also imports the terraform state using a

"terraform import ...." command

And finally runs a

"terraform plan ." command

There should hopefully be no subsequent additions or deletions reported by the terraform plan command as all the approriate terraform configuration files will have have automatically been created.

• The tool is written for the bash shell script & Python3 and has been tested on macOS
• AWS cli (V1) version 1.17.4 or higher needs to be installed and you need a login with at least "Read" priviledges
• terraform version v0.12.25 or higher needs to be installed
• jq version 1.6 or higher

Running the tool in your local shell (bash) required these steps:

1. Unzip or clone this git repo into an empty directory
2. login to the AWS cli (aws configure)
3. run the tool

To generate the terraform files for an account and stop after a "terraform validate":

./aws2tf.sh -v yes

terraform validate
Success! The configuration is valid.

Or there may be some kind of error as trying to test everyone's AWS combinations in advance isn't possible.

If you happen to find one of these errors please open an issue here and paste in the error and it will get fixed.

Once the validation is ok you can use the tool in anger to not only generate the terraform files (-v yes) but also import the resources and perform a terraform plan (see below)

To generate the terraform files for an entire AWS account, import the resourcs and perform a terraform plan:

./aws2tf.sh 

To include AWS account Policies and Roles:

./aws2tf.sh -p yes

To generate the terraform files for an EKS cluster named "mycluster"

./aws2tf.sh -t eks -i mycluster

To get all the VPC related resources in a particular VPC

./aws2tf.sh -t vpc -i vpc-xxxxxxxxx

To use a specific region and profile

./aws2tf.sh -t vpc -i vpc-xxxxxxxxx -r eu-west-1 -p default

To use the fast forward option correctly you'll need a good understanding of terraform resource dependancies to ensure you avoid any depenacy errors.

Be patient - lots of output is given as aws2tf:

• Loops through each provider
• Creates the requited *.tf configuration files in the "generated" directory
• Performs the necessary 'terraform import' commands
• And finally runs a 'terraform plan'

The following terraform resource types are supported by this tool at this time:

• aws_athena_named_query

• aws_autoscaling_group

• aws_directory_service_directory

• aws_ec2_client_vpn_endpoint
• aws_ec2_client_vpn_network_association
• aws_ec2_transit_gateway
• aws_ec2_transit_gateway_route_table
• aws_ec2_transit_gateway_vpc_attachment
• aws_eip
• aws_instance
• aws_launch_template

• aws_ecs_capacity_provider (tbd)
• aws_ecs_cluster
• aws_ecs_service
• aws_ecs_task_definition

• aws_eks_cluster
• aws_eks_fargate_profile
• aws_eks_node_group

• aws_lb
• aws_lb_listener
• aws_lb_target_group

• aws_glue_job

• aws_iam_instance_profile
• aws_iam_policy
• aws_iam_role
• aws_iam_role_policy
• aws_iam_role_policy_attachment

• aws_resource_group

• aws_db_instance

• aws_route53_zone

• aws_s3_access_point
• aws_s3_bucket
• aws_s3_bucket_policy

• aws_service_discovery_private_dns_namespace

• aws_customer_gateway
• aws_internet_gateway
• aws_nat_gateway
• aws_network_interface
• aws_network_interface_attachment
• aws_route_table
• aws_route_table_association
• aws_subnet
• aws_security_group
• aws_vpc
• aws_vpc_ipv4_cidr_block_association
• aws_vpc_endpoint
• aws_vpc_dhcp_options
• aws_vpc_peering_connection
• aws_vpn_connection

• PaaS databases and other missing providers (feel free to contribute !)
• ongoing better EKS support as EKS evolves
• Other terraform providers as terraform supports

It can take a lot of time to loop around everything in large accounts, in particular the importing of the resources.

Can fail if your login doesn't have acccess to KMS

Can fail if your login/SPN doesn't have acccess to the KMS used for encryption.