xuwang / aws-terraform Goto Github PK

Just change the CLUSTER_NAME variable from the default "coreos-cluster" at the top of Makefile is not enough. "coreos-cluster" is hard-coded in other places, which makes the cluster creation to fail.

Would be nice to not have to confirm Y/N for applying each terraform state, especially when deploying a new environment.

Currently under each build/<resource> directory, absolute symlinks are used to reference Terraform output variables from other resources. I think relative links should be used instead to avoid broken links if the build directory is pushed to a central repository and later is checked out by other team members.

Add Cloudtrail module.

Taint aws_s3_bucket_object doesn't trigger cloud-config user data update, because the source file name doesn't change.

I wanted to create a vpc with subnets and an etcd cluster in the Frankfurt region but it fails because only 2 availability zones exist and terraform always tries to create 3 subnets.
I manually solved this by deleting all references to subnet_2 in my local copy but I think it would be cool to have a general switch as there are regions with 2, 3 and 4 availability zones.

See: https://github.com/jsonmaur/aws-regions

This happens during bootstrapping due to git pull cannot verify host-key.

I tried using this project in the Frankfurt datacenter but it fails while fetching the cloud-config and initial-cluster because this datacenter uses the newer AWS4 authorization:

cat ${workDir}/cloud-config.yaml 
<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>InvalidRequest</Code><Message>The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.</Message><RequestId>26B794E2DF6DBB38</RequestId><HostId>1MUzjCurL7ZI8zEi5D/fNUUrSdRo7WMJnrH/I+ujSuPogkuHIOJztpzXWQQ9diOlwE5xQYb1Rrw=</HostId></Error>

The code no longer runs with Terraform 0.7.0 because of #7103. Migrate code is necessary for 0.7.0.

To make it less possible to conflict with other keyparis. I will work on a PR.

To support signature version 4.

Should be able to do this with data.aws_availability_zones.

The script uses curl -s http://169.254.169.254/latest/dynamic/instance-identity/document | grep -Eo '([[:digit:]]{12})' to generate AWS accountId, but in rare cases when an instance id contains consecutive 12 digits, the accountId generated would have two numbers which is complete bogus, causing the bootstrap to fail.

The repo currently works with 0.6.x but not 0.7.x due to some incompatibilities.