Tagging fips endpoint resolves to a domain that doesn't exist

未关闭
#3,395 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
50/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
aws, php
领域
cloud

调研方向

Reproduce with the PHP snippet using Aws\Sdk with use_fips_endpoint set to true in us-gov-west-1, then trace how createResourceGroupsTaggingAPI() resolves its endpoint for the tagging service. Compare the tagging service's FIPS endpoint metadata with a service that resolves correctly in GovCloud, and check whether the endpoint should be corrected or rejected explicitly. Done means GetResources targets a resolvable FIPS host or fails with a clear unsupported-endpoint error, with a test covering the GovCloud FIPS case.

由索引模型根据 Issue 内容生成。

描述

bug p2 queued service-api
Describe the bug

In for govcloud regions with AWS_USE_FIPS_ENDPOINT=true the following urls are resolved:

This leads to errors like:

Error executing "GetResources" on "https://tagging-fips.us-gov-west-1.amazonaws.com/"; AWS HTTP error: cURL error 6: Could not resolve host: tagging-fips.us-gov-west-1.amazonaws.com (see https://curl.se/libcurl/c/libcurl-errors.html) for https://tagging-fips.us-gov-west-1.amazonaws.com/

Regression Issue
  • Select this option if this issue appears to be a regression.
Expected Behavior

I expect the domain that it uses to have a DNS entry that routes to the fips compliant service

Current Behavior

A domain that is actually routed should be returned.

Reproduction Steps
$sdk = new Aws\Sdk([
    'region' => 'us-gov-west-1',
    'use_fips_endpoint' => true, // or AWS_USE_FIPS_ENDPOINT=true
    ...
]);
$sdk->createResourceGroupsTaggingAPI()->getResources();
Possible Solution

Add a dns entry for the fips tagging API, or throw an exception if there is no fips tagging API.

Additional Information/Context

No response

SDK version used

3.402.2

Environment details (Version of PHP (php -v)? OS name and version, etc.)

PHP 8.5, environment independent

主要语言
PHP
星标
6.2k
派生
1.3k
平均合并
4 天 15 小时
30 天内合并 PR
21

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

aws/aws-sdk-php 的其他 Issue

查看 aws/aws-sdk-php 的全部 Issue

相似的 Issue

更多 PHP Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。