New answers tagged

1

The error message here is telling you that you are not allowed to enable MFADelete without having an authenticated token with mfa. Meaning the executing principal must have logged in with MFA. essentially the API call on the cli would be something like this aws --profile my_profile s3api put-bucket-versioning --bucket bucket-name --versioning configuration '...


0

In our terraform pipeline we use the aws cli command to assume a role and get the credential variables, the EC2 instance for the pipeline worker is using a profile which can assume the role. creds=$(aws sts assume-role --role-arn ${ROLE_ARN} --role-session-name tf-pipeline | jq -r '.Credentials') export AWS_ACCESS_KEY_ID=$(echo $creds | jq -r '.AccessKeyId') ...


0

If the vendor is going to change the Cloudformation template often or if the Terraform resources don't need to interact with the Cloudformation resource then it's fine to deploy the Cloudformation stack with Terraform. If both of these things are false you might want to migrate the resources to Terraform. If one is false and the other is true you should ...


0

No sense. As Occam's razor principle says - "entities should not be multiplied without necessity". So, two entities for one task is too much.


0

Initially, I though no it does not make sense to use Terraform to create the infra structure to run Cloud Formation script to do create resources you can do using Terraform. If you are experience in Terraform and use it for your other infrastructure, it does not make sense to introduce another way of doing it, The only reason I could see to create the Cloud ...


2

I figured it out. The stub resource has to have a provider that is configured with the proper AWS region. All these security groups were in us-west-2. You need this: resource "aws_security_group" "rds-launch-wizard-2" { provider = aws.us_west_2 } instead of this: resource "aws_security_group" "rds-launch-wizard-2" {} ...


Top 50 recent answers are included