Skip to content

Commit 369b6a2

Browse files
committed
Update services based on release-2025-10-28 of AWS Go SDK
Reference: https://github.com/aws/aws-sdk-go-v2/releases/tag/release-2025-10-28
1 parent 150d83b commit 369b6a2

File tree

11 files changed

+1148
-268
lines changed

11 files changed

+1148
-268
lines changed

.latest-tag-aws-sdk-go

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
release-2025-10-27
1+
release-2025-10-28

lib/aws/generated/application_signals.ex

Lines changed: 45 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -1079,6 +1079,17 @@ defmodule AWS.ApplicationSignals do
10791079

10801080
@typedoc """
10811081
1082+
## Example:
1083+
1084+
canary_entity() :: %{
1085+
"CanaryName" => [String.t() | atom()]
1086+
}
1087+
1088+
"""
1089+
@type canary_entity() :: %{(String.t() | atom()) => any()}
1090+
1091+
@typedoc """
1092+
10821093
## Example:
10831094
10841095
list_audit_findings_output() :: %{
@@ -1581,10 +1592,14 @@ defmodule AWS.ApplicationSignals do
15811592
end
15821593

15831594
@doc """
1584-
Deletes the grouping configuration for this account.
1595+
Deletes a grouping configuration that defines how services are grouped and
1596+
organized in Application Signals.
1597+
1598+
Once deleted, services will no longer be grouped according to the specified
1599+
configuration rules.
15851600
1586-
This removes all custom grouping attribute definitions that were previously
1587-
configured.
1601+
This operation is irreversible. After deletion, you must recreate the grouping
1602+
configuration if you want to restore the same grouping behavior.
15881603
"""
15891604
@spec delete_grouping_configuration(map(), %{}, list()) ::
15901605
{:ok, delete_grouping_configuration_output(), any()}
@@ -1700,13 +1715,14 @@ defmodule AWS.ApplicationSignals do
17001715
end
17011716

17021717
@doc """
1703-
Returns a list of audit findings that provide automated analysis of service
1704-
behavior and root cause analysis.
1718+
Retrieves a list of audit findings for Application Signals resources.
17051719
1706-
These findings help identify the most significant observations about your
1707-
services, including performance issues, anomalies, and potential problems. The
1708-
findings are generated using heuristic algorithms based on established
1709-
troubleshooting patterns.
1720+
Audit findings identify potential issues, misconfigurations, or compliance
1721+
violations in your observability setup.
1722+
1723+
You can filter findings by time range, auditor type, and target resources to
1724+
focus on specific areas of concern. This operation supports pagination for large
1725+
result sets.
17101726
"""
17111727
@spec list_audit_findings(map(), list_audit_findings_input(), list()) ::
17121728
{:ok, list_audit_findings_output(), any()}
@@ -1741,11 +1757,14 @@ defmodule AWS.ApplicationSignals do
17411757
end
17421758

17431759
@doc """
1744-
Returns the current grouping configuration for this account, including all
1745-
custom grouping attribute definitions that have been configured.
1760+
Retrieves the available grouping attribute definitions that can be used to
1761+
create grouping configurations.
17461762
1747-
These definitions determine how services are logically grouped based on
1748-
telemetry attributes, Amazon Web Services tags, or predefined mappings.
1763+
These definitions specify the attributes and rules available for organizing
1764+
services.
1765+
1766+
Use this operation to discover what grouping options are available before
1767+
creating or updating grouping configurations.
17491768
"""
17501769
@spec list_grouping_attribute_definitions(
17511770
map(),
@@ -1988,11 +2007,15 @@ defmodule AWS.ApplicationSignals do
19882007
end
19892008

19902009
@doc """
1991-
Returns information about the last deployment and other change states of
1992-
services.
2010+
Retrieves the current state information for services monitored by Application
2011+
Signals.
2012+
2013+
Service states include health status, recent change events, and other
2014+
operational metadata.
19932015
1994-
This API provides visibility into recent changes that may have affected service
1995-
performance, helping with troubleshooting and change correlation.
2016+
You can filter results by time range, AWS account, and service attributes to
2017+
focus on specific services or time periods. This operation supports pagination
2018+
and can include data from linked accounts.
19962019
"""
19972020
@spec list_service_states(map(), list_service_states_input(), list()) ::
19982021
{:ok, list_service_states_output(), any()}
@@ -2130,13 +2153,12 @@ defmodule AWS.ApplicationSignals do
21302153
end
21312154

21322155
@doc """
2133-
Creates or updates the grouping configuration for this account.
2156+
Creates or updates a grouping configuration that defines how services are
2157+
organized and grouped in Application Signals dashboards and service maps.
21342158
2135-
This operation allows you to define custom grouping attributes that determine
2136-
how services are logically grouped based on telemetry attributes, Amazon Web
2137-
Services tags, or predefined mappings. These grouping attributes can then be
2138-
used to organize and filter services in the Application Signals console and
2139-
APIs.
2159+
Grouping configurations allow you to logically organize services based on
2160+
attributes such as environment, team ownership, or business function, making it
2161+
easier to monitor and manage related services together.
21402162
"""
21412163
@spec put_grouping_configuration(map(), put_grouping_configuration_input(), list()) ::
21422164
{:ok, put_grouping_configuration_output(), any()}

lib/aws/generated/ec2.ex

Lines changed: 99 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4098,6 +4098,21 @@ defmodule AWS.EC2 do
40984098

40994099
@typedoc """
41004100

4101+
## Example:
4102+
4103+
describe_capacity_reservation_topology_request() :: %{
4104+
optional("CapacityReservationIds") => list(String.t() | atom()),
4105+
optional("DryRun") => boolean(),
4106+
optional("Filters") => list(filter()),
4107+
optional("MaxResults") => integer(),
4108+
optional("NextToken") => String.t() | atom()
4109+
}
4110+
4111+
"""
4112+
@type describe_capacity_reservation_topology_request() :: %{(String.t() | atom()) => any()}
4113+
4114+
@typedoc """
4115+
41014116
## Example:
41024117

41034118
launch_template_license_configuration() :: %{
@@ -13969,6 +13984,24 @@ defmodule AWS.EC2 do
1396913984

1397013985
@typedoc """
1397113986

13987+
## Example:
13988+
13989+
capacity_reservation_topology() :: %{
13990+
"AvailabilityZone" => String.t() | atom(),
13991+
"AvailabilityZoneId" => String.t() | atom(),
13992+
"CapacityBlockId" => String.t() | atom(),
13993+
"CapacityReservationId" => String.t() | atom(),
13994+
"GroupName" => String.t() | atom(),
13995+
"InstanceType" => String.t() | atom(),
13996+
"NetworkNodes" => list(String.t() | atom()),
13997+
"State" => String.t() | atom()
13998+
}
13999+
14000+
"""
14001+
@type capacity_reservation_topology() :: %{(String.t() | atom()) => any()}
14002+
14003+
@typedoc """
14004+
1397214005
## Example:
1397314006

1397414007
reject_capacity_reservation_billing_ownership_result() :: %{
@@ -16381,6 +16414,18 @@ defmodule AWS.EC2 do
1638116414

1638216415
@typedoc """
1638316416

16417+
## Example:
16418+
16419+
describe_capacity_reservation_topology_result() :: %{
16420+
"CapacityReservations" => list(capacity_reservation_topology()),
16421+
"NextToken" => String.t() | atom()
16422+
}
16423+
16424+
"""
16425+
@type describe_capacity_reservation_topology_result() :: %{(String.t() | atom()) => any()}
16426+
16427+
@typedoc """
16428+
1638416429
## Example:
1638516430

1638616431
attribute_value() :: %{
@@ -37303,6 +37348,54 @@ defmodule AWS.EC2 do
3730337348
Request.request_post(client, meta, "DescribeCapacityReservationFleets", input, options)
3730437349
end
3730537350

37351+
@doc """
37352+
Describes a tree-based hierarchy that represents the physical host placement of
37353+
your
37354+
pending or active Capacity Reservations within an Availability Zone or Local
37355+
Zone.
37356+
37357+
You
37358+
can use this information to determine the relative proximity of your capacity
37359+
within the
37360+
Amazon Web Services network before it is launched and use this information to
37361+
allocate capacity
37362+
together to support your tightly coupled workloads.
37363+
37364+
Capacity Reservation topology is supported for specific instance types only. For
37365+
more
37366+
information, see [Prerequisites for Amazon EC2 instance
37367+
topology](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-topology-prerequisites.html)
37368+
in the
37369+
*Amazon EC2 User Guide*.
37370+
37371+
The Amazon EC2 API follows an eventual consistency model due to the
37372+
distributed nature of the system supporting it. As a result, when you call the
37373+
DescribeCapacityReservationTopology API command immediately after launching
37374+
instances, the response might return a `null` value for
37375+
`capacityBlockId` because the data might not have fully propagated
37376+
across all subsystems. For more information, see [Eventual consistency in the Amazon EC2
37377+
API](https://docs.aws.amazon.com/ec2/latest/devguide/eventual-consistency.html)
37378+
in the *Amazon EC2 Developer
37379+
Guide*.
37380+
37381+
For more information, see [Amazon EC2 topology](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-topology.html)
37382+
in
37383+
the *Amazon EC2 User Guide*.
37384+
"""
37385+
@spec describe_capacity_reservation_topology(
37386+
map(),
37387+
describe_capacity_reservation_topology_request(),
37388+
list()
37389+
) ::
37390+
{:ok, describe_capacity_reservation_topology_result(), any()}
37391+
| {:error, {:unexpected_response, any()}}
37392+
| {:error, term()}
37393+
def describe_capacity_reservation_topology(%Client{} = client, input, options \\ []) do
37394+
meta = metadata()
37395+
37396+
Request.request_post(client, meta, "DescribeCapacityReservationTopology", input, options)
37397+
end
37398+
3730637399
@doc """
3730737400
Describes one or more of your Capacity Reservations.
3730837401

@@ -38312,10 +38405,10 @@ defmodule AWS.EC2 do
3831238405

3831338406
Instance topology is supported for specific instance types only. For more
3831438407
information,
38315-
see [
38316-
Prerequisites for Amazon EC2 instance
38408+
see [Prerequisites for Amazon EC2 instance
3831738409
topology](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-topology-prerequisites.html)
38318-
in the *Amazon EC2 User Guide*.
38410+
in the
38411+
*Amazon EC2 User Guide*.
3831938412

3832038413
The Amazon EC2 API follows an eventual consistency model due to the
3832138414
distributed nature of the system supporting it. As a result, when you call the
@@ -38327,8 +38420,9 @@ defmodule AWS.EC2 do
3832738420
in the *Amazon EC2 Developer
3832838421
Guide*.
3832938422

38330-
For more information, see [Amazon EC2 instance topology](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-topology.html)
38331-
in the *Amazon EC2 User Guide*.
38423+
For more information, see [Amazon EC2 topology](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-topology.html)
38424+
in
38425+
the *Amazon EC2 User Guide*.
3833238426
"""
3833338427
@spec describe_instance_topology(map(), describe_instance_topology_request(), list()) ::
3833438428
{:ok, describe_instance_topology_result(), any()}

lib/aws/generated/ecs.ex

Lines changed: 79 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -816,7 +816,9 @@ defmodule AWS.ECS do
816816
service_revision_summary() :: %{
817817
"arn" => String.t() | atom(),
818818
"pendingTaskCount" => integer(),
819+
"requestedProductionTrafficWeight" => float(),
819820
"requestedTaskCount" => integer(),
821+
"requestedTestTrafficWeight" => float(),
820822
"runningTaskCount" => integer()
821823
}
822824
@@ -836,6 +838,18 @@ defmodule AWS.ECS do
836838

837839
@typedoc """
838840
841+
## Example:
842+
843+
linear_configuration() :: %{
844+
"stepBakeTimeInMinutes" => integer(),
845+
"stepPercent" => float()
846+
}
847+
848+
"""
849+
@type linear_configuration() :: %{(String.t() | atom()) => any()}
850+
851+
@typedoc """
852+
839853
## Example:
840854
841855
service_not_found_exception() :: %{
@@ -1241,8 +1255,10 @@ defmodule AWS.ECS do
12411255
deployment_configuration() :: %{
12421256
"alarms" => deployment_alarms(),
12431257
"bakeTimeInMinutes" => integer(),
1258+
"canaryConfiguration" => canary_configuration(),
12441259
"deploymentCircuitBreaker" => deployment_circuit_breaker(),
12451260
"lifecycleHooks" => list(deployment_lifecycle_hook()),
1261+
"linearConfiguration" => linear_configuration(),
12461262
"maximumPercent" => integer(),
12471263
"minimumHealthyPercent" => integer(),
12481264
"strategy" => list(any())
@@ -2500,6 +2516,18 @@ defmodule AWS.ECS do
25002516

25012517
@typedoc """
25022518
2519+
## Example:
2520+
2521+
canary_configuration() :: %{
2522+
"canaryBakeTimeInMinutes" => integer(),
2523+
"canaryPercent" => float()
2524+
}
2525+
2526+
"""
2527+
@type canary_configuration() :: %{(String.t() | atom()) => any()}
2528+
2529+
@typedoc """
2530+
25032531
## Example:
25042532
25052533
submit_container_state_change_response() :: %{
@@ -4594,6 +4622,57 @@ defmodule AWS.ECS do
45944622
service uses Application Load Balancer, Network Load Balancer, or Service
45954623
Connect
45964624
4625+
*
4626+
4627+
`LINEAR`: A *linear* deployment strategy (`LINEAR`) gradually shifts traffic
4628+
from the current production environment to a new environment in equal percentage
4629+
increments over a specified time period. With Amazon ECS linear deployments, you
4630+
can control the pace of traffic shifting and validate new service revisions with
4631+
increasing amounts of production traffic.
4632+
4633+
Linear deployments are best suited for the following scenarios:
4634+
4635+
*
4636+
Gradual validation: When you want to gradually validate your new service version
4637+
with increasing traffic
4638+
4639+
*
4640+
Performance monitoring: When you need time to monitor metrics and performance
4641+
during the deployment
4642+
4643+
*
4644+
Risk minimization: When you want to minimize risk by exposing the new version to
4645+
production traffic incrementally
4646+
4647+
*
4648+
Load balancer requirement: When your service uses Application Load Balancer,
4649+
Network Load Balancer, or Service Connect
4650+
4651+
*
4652+
4653+
`CANARY`: A *canary* deployment strategy (`CANARY`) shifts a small percentage of
4654+
traffic to the new service revision first, then shifts the remaining traffic all
4655+
at once after a specified time period. This allows you to test the new version
4656+
with a subset of users before full deployment.
4657+
4658+
Canary deployments are best suited for the following scenarios:
4659+
4660+
*
4661+
Feature testing: When you want to test new features with a small subset of users
4662+
before full rollout
4663+
4664+
*
4665+
Production validation: When you need to validate performance and functionality
4666+
with real production traffic
4667+
4668+
*
4669+
Blast radius control: When you want to minimize blast radius if issues are
4670+
discovered in the new version
4671+
4672+
*
4673+
Load balancer requirement: When your service uses Application Load Balancer,
4674+
Network Load Balancer, or Service Connect
4675+
45974676
*
45984677
External
45994678

0 commit comments

Comments
 (0)