terraform-provider-aws | Terraform AWS provider | Infrastructure Automation library

 by   hashicorp Go Version: v5.4.0 License: MPL-2.0

kandi X-RAY | terraform-provider-aws Summary

kandi X-RAY | terraform-provider-aws Summary

terraform-provider-aws is a Go library typically used in Devops, Infrastructure Automation, Terraform applications. terraform-provider-aws has no bugs, it has no vulnerabilities, it has a Weak Copyleft License and it has medium support. You can download it from GitHub.

Terraform AWS provider

            kandi-support Support

              terraform-provider-aws has a medium active ecosystem.
              It has 8633 star(s) with 8068 fork(s). There are 453 watchers for this library.
              There were 10 major release(s) in the last 12 months.
              There are 3741 open issues and 12057 have been closed. On average issues are closed in 377 days. There are 361 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of terraform-provider-aws is v5.4.0

            kandi-Quality Quality

              terraform-provider-aws has 0 bugs and 0 code smells.

            kandi-Security Security

              terraform-provider-aws has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              terraform-provider-aws code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              terraform-provider-aws is licensed under the MPL-2.0 License. This license is Weak Copyleft.
              Weak Copyleft licenses have some restrictions, but you can use them in commercial projects.

            kandi-Reuse Reuse

              terraform-provider-aws releases are available to install and integrate.
              It has 957920 lines of code, 30469 functions and 3789 files.
              It has high code complexity. Code complexity directly impacts maintainability of the code.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of terraform-provider-aws
            Get all kandi verified functions for this library.

            terraform-provider-aws Key Features

            No Key Features are available at this moment for terraform-provider-aws.

            terraform-provider-aws Examples and Code Snippets

            No Code Snippets are available at this moment for terraform-provider-aws.

            Community Discussions


            how can i create S3 Lifecycle configuration using Terraform?
            Asked 2022-Mar-07 at 06:06

            I tried to use newer_noncurrent_versions in S3 Lifecycle.

            In Terraform 4.3.0, lifecycle was released.

            However, when applying on Terraform cloud, an error saying to use Lifecycle V2 occurred.

            Is my code the problem? Is it a terraform provider problem?

            Terraform CLI and Terraform AWS Provider Version ...


            Answered 2022-Mar-07 at 06:06

            Your are missing filter in the rule:

            Source https://stackoverflow.com/questions/71376827


            Deploying API Gateway and Lambda Integration using Terraform
            Asked 2022-Feb-22 at 21:17

            I am trying to create Lambda function using Terraform. There is no permission issue.



            Answered 2022-Feb-22 at 21:17

            I was able to successfully create the lambda function and IAM role resources;

            Source https://stackoverflow.com/questions/71127495


            why does 'terraform plan' fail due to my timezone not set to automatic?
            Asked 2022-Feb-14 at 17:24

            I had issue



            Answered 2022-Feb-14 at 17:24

            The hashicorp/aws provider must send requests to the AWS API that are signed using the AWS Signature Version 4 algorithm.

            One of the goals of the AWS signing scheme is to minimize the time window that a compromised signature couuld be reused by an attacker. To achieve that, the signature scheme includes a timestamp when the signature was created and the remote system requires that the timestamp be within 15 minutes of the request time as understood by the remote system.

            The official documentation describes this as follows, at the time I'm writing this:

            • Protect against reuse of the signed portions of the request – The signed portions (using AWS Signatures) of requests are valid within 15 minutes of the timestamp in the request. An unauthorized party who has access to a signed request can modify the unsigned portions of the request without affecting the request's validity in the 15 minute window. Because of this, we recommend that you maximize protection by signing request headers and body, making HTTPS requests to Amazon S3, and by using the s3:x-amz-content-sha256 condition key (see Amazon S3 Signature Version 4 Authentication Specific Policy Keys) in AWS policies to require users to sign Amazon S3 request bodies.

            If your local system has an incorrect system time or if your system believes its local time to be in a different timezone than you are actually working in then the AWS SDK (which the Terraform AWS provider is built with) will generate a timestamp outside of the allowed 15 minute window, and so your request will fail. This would be true of any request to AWS APIs using this standard signature scheme, whether made by Terraform's AWS provider or by any other AWS-integrated tool.

            In order for requests to succeed your system must be able to generate a correct UTC-referenced timestamp. In order for that to be true, it must have both a correct time and – if you are using an operating system like Windows where the system time is stored in local time rather than UTC – a correct configuration of your system time's offset from UTC so that the SDK can convert to a UTC timestamp as the AWS API requires.

            Source https://stackoverflow.com/questions/71114463


            terraform ecs/CreateCapacityProvider request 500
            Asked 2022-Jan-10 at 21:33

            I am getting the following error while trying to create an ECS cluster, at the capacity provider creation phase.



            Answered 2022-Jan-06 at 21:49

            I fixed this by creating the cluster without capacity provider first then modifying it to have one.

            Source https://stackoverflow.com/questions/70597037


            Provided region_name '"$region"' doesn't match a supported format for Windows (CMD)
            Asked 2022-Jan-08 at 07:27

            I am trying to deploy ECS using Terraform and it's throwing the above error while I am Provisioning the ECR this is happening. It tried removing the double quotes, then enabled trace for troubleshooting. I tried updating to the latest version of terraform as well (v 1.1.2)

            Here is the code chunk from main.tf file



            Answered 2022-Jan-04 at 23:34


            A ${ ... } sequence is an interpolation in Terraform's configuration language, which evaluates the expression given between the markers. Unix shells typically use $..

            As per the official documentation, the command is evaluated in a shell, and can use environment variables or Terraform variables. So, basically, what you are trying to achieve should work fundamentally.

            I did a quick test and I was able to successfully apply that locally:

            with double quotes

            Source https://stackoverflow.com/questions/70547172


            Terraform getting stuck when running on Jenkins
            Asked 2021-Dec-07 at 16:26

            I'm using terraform with aws:

            • Terraform v0.14.8
            • provider registry.terraform.io/hashicorp/archive v2.2.0
            • provider registry.terraform.io/hashicorp/aws v3.55.0

            Current behavior:

            • On my local machine it works fine.
            • On local docker, that is used by Jenkins it's working fine
            • On Jenkins with same docker on US-WEST-2 working fine but,
            • On Jenkins with same docker on EU-CENTRAL-1 get stuck. In debug mode, I get:

            2021-08-24T20:16:08.901Z [INFO] plugin.terraform-provider-aws_v3.55.0_x5: 2021/08/24 20:16:08 [DEBUG] [aws-sdk-go] DEBUG: Send Request lambda/GetLayerVersion failed, attempt 25/25, error RequestError: send request failed caused by: Get "https://lambda.eu-central-1.amazonaws.com/2018-10-31/layers/awswrangler/versions/2": dial tcp i/o timeout: timestamp=2021-08-24T20:16:08.901Z 2021/08/24 20:16:08 [TRACE] vertex "module.key_rotation.aws_lambda_layer_version.lambda_layer": visit complete 2021/08/24 20:16:08 [TRACE] vertex "module.key_rotation.aws_lambda_layer_version.lambda_layer": dynamic subgraph encountered errors 2021/08/24 20:16:08 [TRACE] vertex "module.key_rotation.aws_lambda_layer_version.lambda_layer": visit complete 2021/08/24 20:16:08 [TRACE] vertex "module.key_rotation.aws_lambda_layer_version.lambda_layer (expand)": dynamic subgraph encountered errors 2021/08/24 20:16:08 [TRACE] vertex "module.key_rotation.aws_lambda_layer_version.lambda_layer (expand)": visit complete 2021/08/24 20:16:08 [TRACE] dag/walk: upstream of "module.key_rotation.aws_lambda_function.sync_apps_db_lambda_function (expand)" errored, so skipping 2021/08/24 20:16:08 [TRACE] dag/walk: upstream of "module.key_rotation.aws_lambda_function.cleanup_lambda_function (expand)" errored, so skipping 2021/08/24 20:16:08 [TRACE] dag/walk: upstream of "module.key_rotation.aws_lambda_function.check_application_keys_lambda_function (expand)" errored, so skipping 2021/08/24 20:16:08 [TRACE] dag/walk: upstream of "module.key_rotation.aws_cloudwatch_event_target.event_target_lambda (expand)" errored, so skipping 2021/08/24 20:16:08 [TRACE] dag/walk: upstream of "module.key_rotation.aws_lambda_permission.allow_cloudwatch_to_call_cleaner_lambda (expand)" errored, so skipping 2021/08/24 20:16:08 [TRACE] dag/walk: upstream of "module.key_rotation.aws_lambda_permission.allow_cloudwatch_to_call_lambda (expand)" errored, so skipping 2021/08/24 20:16:08 [TRACE] dag/walk: upstream of "module.key_rotation.aws_cloudwatch_event_target.event_target_cleaner_lambda (expand)" errored, so skipping 2021/08/24 20:16:08 [TRACE] dag/walk: upstream of "module.key_rotation (close)" errored, so skipping 2021/08/24 20:16:08 [TRACE] dag/walk: upstream of "provider["registry.terraform.io/hashicorp/aws"] (close)" errored, so skipping 2021/08/24 20:16:08 [TRACE] dag/walk: upstream of "meta.count-boundary (EachMode fixup)" errored, so skipping 2021/08/24 20:16:08 [TRACE] dag/walk: upstream of "root" errored, so skipping

            Seems like it's related to lambda upload.

            I tryied:

            • update terraform to latest
            • destroy everithing
            • removing all the states also from S3

            same result.



            Answered 2021-Aug-26 at 22:36

            I think the root cause of your issue is this:

            Get "https://lambda.eu-central-1.amazonaws.com/2018-10-31/layers/awswrangler/versions/2": dial tcp i/o timeout

            Why the terraform binary can't connect to the eu-central-1 endpoint of the Lambda service is impossible to say based on the information you provided.

            You don't say where or how Jenkins is deployed. I assume in some container on AWS?

            It could be a temporary network glitch or for some reason connectivity to eu-central-1 is blocked from your Jenkins deployment.

            Have you retried after a few hours?

            Are you able to reproduce this behaviour consistenly?

            Source https://stackoverflow.com/questions/68938564


            aws_caller_identity for two providers inside a module
            Asked 2021-Nov-19 at 23:09

            I am facing an issue trying to get the account id of an aws provider that is not the provider where the resource will be deployed. This is my scenario:

            main.tf (root directory)



            Answered 2021-Nov-19 at 23:09

            Following Hashicorp documentation, the main.tf file of the child (asdf) module should be:

            Source https://stackoverflow.com/questions/70033429


            Can't execute neither user_data script, nor remote-exec with connection block while launching ec2 instance with terraform cloud [aws-provider]
            Asked 2021-Oct-01 at 09:02

            I have created a aws infrastructure with network acls, security group, subnets, etc [code attached at the bottom]. in the free tier. I have also established ssh connection with my ec2 instance and I can also download manually packages when logged to the instance.

            However, since I want to fully utilize Terraform, I would like to pre-install some stuff while Terraform creates the instance.

            The commands I want to execute are quite simple (install jdk, python, docker),



            Answered 2021-Oct-01 at 09:02

            I run your code in my sandbox env, and the remote-exec works. I had to make some changes for it to work and even to run your code (region, ami, security groups, ...). So you can have a look at the modified code and take it from there. But the code below works for me without any issues.

            Source https://stackoverflow.com/questions/69397558


            How can I test terraform import in acceptance tests?
            Asked 2021-Sep-01 at 08:22

            I found this article about testing tf import in acceptance tests:



            Answered 2021-Sep-01 at 08:22

            Your setup for testing import is correct. Adding steps with ImportState and ImportStateVerify should be enough.

            Testing import is implemented in terraform-provider-sdk testStepNewImportState function. How it works:

            1. Previous step applies terraform config using testcase workdir and state.
            2. If next step sets ImportState to true, use ResourceName to grab resource id from testcase state (or use ImportStateIdFunc or ImportStateId if they are set for this step).
            3. Create empty workdir, initialize new empty state, and import resource given resource name and id from previous step. There would be no conflicts since this is a separate empty state.
            4. If ImportStateVerify is true, compare resource states from previous step and import step, they should be identical.
            5. If ImportStateCheck function is set, use this function for custom state validation. This can be used in case if direct state comparison will be not valid.
            6. Discard temporary workdir.

            Source https://stackoverflow.com/questions/68824711


            TerraForm: deploying EC2 instances without starting them
            Asked 2021-Jul-13 at 04:37

            I want to deploy my infrastructure in different AWS environments (dev, prod, qa).

            That deployment creates a few EC2 instances from a custom AMI. When deployed, instances are in the "running" state. I understand this seems to be related to some constraint in the EC2 API. However, I don't necessarily want my instances started, depending on context. Sometimes, I just want the instances to be created, and they will be started later on. I guess this is a quite common scenario.

            Reading the few related issues/requests on Hashicorp's github, makes me think so:

            There must be some TerraForm based solution which doesn't require to rely on AWS CLI / CDK or lambda, right? Something in the TerraForm script that, for example, would stop the instance right after its creation.

            My google foo didn't help me much here. Any help / suggestion for dealing with that scenario is welcome.



            Answered 2021-Jul-10 at 12:53

            Provisioning a new instance automatically puts it in a 'started' state.

            As Marcin suggested, you can use user data scripts, here's some psuedo user data script. For you to figure out the actual implementation ;)

            Source https://stackoverflow.com/questions/68325428

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network


            No vulnerabilities reported

            Install terraform-provider-aws

            You can download it from GitHub.


            Full, comprehensive documentation is available on the Terraform website:.
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
          • HTTPS


          • CLI

            gh repo clone hashicorp/terraform-provider-aws

          • sshUrl


          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link

            Consider Popular Infrastructure Automation Libraries


            by hashicorp


            by saltstack


            by pulumi


            by GoogleCloudPlatform

            Try Top Libraries by hashicorp


            by hashicorpGo


            by hashicorpGo


            by hashicorpGo


            by hashicorpRuby


            by hashicorpGo