New answers tagged

0

This is shown in the Hashicorp tutorial - "a new version of the lambda function. The suggestion there is to point to a different zipfile in S3. I suppose in your case, the filename either needs to change, or the file contents need to change. The suggestion from the tutorial is to use a variable for the filename, associated with the version of the ...


0

I saw this elegant, low tech method to test Terraform suggested by apparentlymart in a GitHub issue thread. It's not a appropriate for every situation but it's great for verifying module logic. Create a root module that includes the module under test and verifies the under-test outputs. Here is a simple example using two files: main.tf that will run the ...


1

Did you try to use remote state storage like S3? Also you can use Terraform Cloud to organzie workflow and have the shared state.


1

Your default security groups and newly created security groups include default rules that do not enable you to access your instance from the Internet. Add this: resource "aws_security_group" "allow-ssh" { vpc_id = "${aws_vpc.vpc.id}" ingress { from_port = 0 to_port = 22 protocol = "tcp" } } Then add the line vpc_security_group_ids = [...


0

You can have two approaches: Assume the role that has access to the AWS bucket. Assume this role in every account (don't forget to set up trust relationship). This is your approach. I think the issue might be some objects (state files) were created in a different way. Other culprit can be an account-specific KMS key that is used to create the objects. Don't ...


3

If I am understanding your question correctly, what you are describing sounds like a perfect use case for SSM. You can store your RDS password as a secure string parameter encrypted by KMS, then reference it in you terraform file as a data source with decryption. With this method, you only have to reference your decrypted password, and never directly store ...


Top 50 recent answers are included