Data from region ap-southeast-5 is not being fetched

[agoyburu]

Describe the bug
Plugin is not fetching data from new region ap-southeast-5

Steampipe version (steampipe -v)
Example: v1.0.0

Plugin version (steampipe plugin list)
Example: v1.4.0

To reproduce
Create any resource in region ap-southeast-5 and try to fetch it using steampipe.

Expected behavior
The resource should be present in the result.

Additional context
Region ap-southeast-5 was made available last September so it is kind of new.

Querying select * from aws_region; shows the region as opted-in but still no data is being retrieved from there.

I've also tried using that region exclusively but that didn't work either:

connection "aws_default" {
  plugin = "aws"
  # `regions` defines the list of regions that Steampipe should target for
  # each query. API calls are made to multiple regions in parallel. The regions
  # list may include wildcards (e.g. *, us-*, us-??st-1).
  # If `regions` is not specified, Steampipe will target the `default_region`
  # only.
  regions = ["ap-southeast-5"] # All regions

[ParthaI]

Hi @agoyburu,

Sorry to hear that you’re encountering this issue.

After investigating, I’ve identified the root cause of why resources for the ap-southeast-5 region are not being retrieved. Here are my findings:

• The region ap-southeast-5 was officially made generally available (GA) on August 21, 2024.
• Our AWS plugin is designed to make API calls based on the region configured in the aws.spc file.
• The plugin relies on AWS SDK V1 to fetch the list of supported regions for services.
• However, AWS SDK V1 is in maintenance mode and will reach its end-of-life on July 31, 2025. For details, see the announcement: AWS SDK V1 End-of-Life.
• When fetching the supported region list for the service, the ap-southeast-5 region is categorized as unsupported because it hasn’t been added to the list in AWS SDK V1.
• We currently have an open issue to remove support for AWS SDK V1 from the plugin. Once this transition is complete, the issue should be resolved, as ap-southeast-5 is already supported in AWS SDK V2.

Thanks, and I hope this clarifies the situation!

[agoyburu]

Hi @ParthaI, thanks for replying.

Do you know when this will be worked on?

[ParthaI]

Sorry, @agoyburu, we don’t have an ETA for this issue yet. It’s on our to-do list, and we’ll update you as soon as we begin working on it. Thank you for your patience!