Created
October 12, 2023 20:32
-
-
Save howdoicomputer/601137636cdc079799e1c2c7daee2b64 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[howdoicomputer@framework:~/workspace/aws-cdktf-example]$ cdktf deploy | |
aws-cdktf-example Initializing the backend... | |
aws-cdktf-example | |
Successfully configured the backend "remote"! Terraform will automatically | |
use this backend unless the backend configuration changes. | |
aws-cdktf-example Initializing provider plugins... | |
- Finding hashicorp/aws versions matching "5.20.1"... | |
aws-cdktf-example - Installing hashicorp/aws v5.20.1... | |
aws-cdktf-example - Installed hashicorp/aws v5.20.1 (signed by HashiCorp) | |
Terraform has created a lock file .terraform.lock.hcl to record the provider | |
selections it made above. Include this file in your version control repository | |
so that Terraform can guarantee to make the same selections by default when | |
you run "terraform init" in the future. | |
Terraform has been successfully initialized! | |
You may now begin working with Terraform. Try running "terraform plan" to see | |
any changes that are required for your infrastructure. All Terraform commands | |
should now work. | |
If you ever set or change modules or backend configuration for Terraform, | |
rerun this command to reinitialize your working directory. If you forget, other | |
commands will detect it and remind you to do so if necessary. | |
aws-cdktf-example - Fetching hashicorp/aws 5.20.1 for linux_amd64... | |
aws-cdktf-example - Retrieved hashicorp/aws 5.20.1 for linux_amd64 (signed by HashiCorp) | |
- Obtained hashicorp/aws checksums for linux_amd64; All checksums for this platform were already tracked in the lock file | |
aws-cdktf-example Success! Terraform has validated the lock file and found no need for changes. | |
aws-cdktf-example Running apply in the remote backend. Output will stream here. Pressing Ctrl-C | |
will cancel the remote apply if it's still pending. If the apply started it | |
will stop streaming the logs, but will not stop the apply running remotely. | |
Preparing the remote apply... | |
aws-cdktf-example To view this run in a browser, visit: | |
https://app.terraform.io/app/howdoicomputer/example-infrastructure/runs/run-ZJAVYsCJ3MESEzUF | |
aws-cdktf-example Waiting for the plan to start... | |
aws-cdktf-example Terraform v1.6.1 | |
on linux_amd64 | |
Initializing plugins and modules... | |
aws-cdktf-example Planning failed. Terraform encountered an error while generating this plan. | |
╷ | |
│ Error: No valid credential sources found | |
│ | |
│ with provider["registry.terraform.io/hashicorp/aws"], | |
│ on cdk.tf.json line 24, in provider.aws[0]: | |
│ 24: } | |
│ | |
│ Please see https://registry.terraform.io/providers/hashicorp/aws | |
│ for more information about providing credentials. | |
│ | |
│ Error: failed to refresh cached credentials, no EC2 IMDS role found, | |
│ operation error ec2imds: GetMetadata, request canceled, context deadline | |
│ exceeded | |
│ | |
╵ | |
aws-cdktf-example Operation failed: failed running terraform plan (exit 1) | |
0 Stacks deploying 1 Stack done 0 Stacks waiting | |
Invoking Terraform CLI failed with exit code 1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment