Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS Backup vault cannot be seen using FIPS endpoint #22573

Closed
JohnRattz opened this issue Jan 13, 2022 · 4 comments · Fixed by #38057
Closed

AWS Backup vault cannot be seen using FIPS endpoint #22573

JohnRattz opened this issue Jan 13, 2022 · 4 comments · Fixed by #38057
Assignees
Labels
bug Addresses a defect in current functionality. fips Pertains to the Federal Information Processing Standard (FIPS). service/backup Issues and PRs that pertain to the backup service.
Milestone

Comments

@JohnRattz
Copy link

JohnRattz commented Jan 13, 2022

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

Terraform v1.0.11 (running from a Terraform Enterprise instance in us-gov-west-1)
on linux_amd64
AWS provider v3.71.0

Affected Resource(s)

  • aws_backup_vault

Terraform Configuration Files

locals {
  aws_region = "us-gov-west-1"
}

provider "aws" {

  region = local.aws_region

  endpoints {
    backup = "backup-fips.us-gov-west-1.amazonaws.com"
    kms = "kms-fips.us-gov-west-1.amazonaws.com"
    efs = "elasticfilesystem-fips.us-gov-west-1.amazonaws.com"
    iam = "iam.us-gov.amazonaws.com"
    autoscaling = "autoscaling.us-gov-west-1.amazonaws.com"
    ecs = "ecs-fips.us-gov-west-1.amazonaws.com"
    elb = "elasticloadbalancing.us-gov-west-1.amazonaws.com"
    cloudwatch = "monitoring.us-gov-west-1.amazonaws.com"
    lambda = "lambda-fips.us-gov-west-1.amazonaws.com"
  } 
}

resource "aws_backup_vault" "backup" {
  name = "backup"
}

Debug Output

GitHub Gist

Expected Behavior

The AWS Backup vault should be found by terraform plan.

Actual Behavior

The following error occurs:

│ Error: error reading Backup Vault (backup): InvalidSignatureException: 
│       status code: 403, request id: e6ef79ce-5dad-4ca4-855c-3e765419fab7
...

Steps to Reproduce

  1. Run terraform apply with the backup endpoint line commented to create the backup vault resource.
  2. Uncomment the backup endpoint line and run terraform plan.

Important Factoids

We are using FIPS enabled endpoints for services.

The command aws backup describe-backup-vault --backup-vault-name jenkins --endpoint-url https://backup-fips.us-gov-west-1.amazonaws.com finds the vault, though the provider does not using the same FIPS endpoint.

References

@github-actions github-actions bot added needs-triage Waiting for first response or review from a maintainer. service/backup Issues and PRs that pertain to the backup service. labels Jan 13, 2022
@justinretzolk justinretzolk added bug Addresses a defect in current functionality. fips Pertains to the Federal Information Processing Standard (FIPS). and removed needs-triage Waiting for first response or review from a maintainer. labels Jan 13, 2022
@gdavison
Copy link
Contributor

gdavison commented Feb 3, 2023

I see that you're using version 3.71 of the AWS Provider, which was released on 6 January 2022. Version 4.0, released 10 February 2022, had enhancements to FIPS support. Have you tried this with a more up-to-date version of the provider?

Please be aware of the upgrade guide when trying with version 4.x

@gdavison gdavison self-assigned this Feb 3, 2023
@gdavison gdavison added the waiting-response Maintainers are waiting on response from community or contributor. label Feb 3, 2023
Copy link

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

@github-actions github-actions bot added this to the v5.55.0 milestone Jun 20, 2024
@terraform-aws-provider terraform-aws-provider bot removed the waiting-response Maintainers are waiting on response from community or contributor. label Jun 20, 2024
Copy link

This functionality has been released in v5.55.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. fips Pertains to the Federal Information Processing Standard (FIPS). service/backup Issues and PRs that pertain to the backup service.
Projects
None yet
3 participants