Add known STS endpoint for il-central-1

[greedy52]

Comes from support shift where a customer enables the new region.

Using github.com/aws/aws-sdk-go v1.44.333 for github.com/nklaassen/sts-endpoints

However, for the long term, we should consider generating the STS endpoints from the SDK by code, instead of hard-coding in a slice.

[tigrato]

Can we replace the generator with SDK based data or adding a ci step that prevents the drift even for older versions

[reedloden]

Can we replace the generator with SDK based data or adding a ci step that prevents the drift even for older versions

https://docs.aws.amazon.com/sdk-for-go/api/aws/endpoints/ (v1 only)

[greedy52]

Can we replace the generator with SDK based data or adding a ci step that prevents the drift even for older versions

https://docs.aws.amazon.com/sdk-for-go/api/aws/endpoints/ (v1 only)

Yes, we do something similar here:

teleport/lib/config/fileconf.go

Lines 497 to 506 in 1efd30a

	// awsRegions returns the list of all regions available on every aws partition.
	// It is used to validate the AWSMatcher.Regions values.
	func awsRegions() []string {
	var regions []string
	partitions := endpoints.DefaultPartitions()
	for _, partition := range partitions {
	regions = append(regions, maps.Keys(partition.Regions())...)
	}
	return regions
	}

And in Nic's separate repo https://github.com/nklaassen/sts-endpoints

Can we replace the generator with SDK based data or adding a ci step that prevents the drift even for older versions

Let me do that in a separate PR as an alternative.

[public-teleport-github-review-bot]

@greedy52 See the table below for backport results.

Branch	Result
branch/v12	Create PR
branch/v13	Create PR
branch/v14	Create PR