Script 'mail_helper' called by obssrc
Hello community,
here is the log from the commit of package python-boto3 for openSUSE:Factory
checked in at 2022-01-07 12:45:02
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-boto3 (Old)
and /work/SRC/openSUSE:Factory/.python-boto3.new.1896 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-boto3"
Fri Jan 7 12:45:02 2022 rev:60 rq:944077 version:1.20.28
Changes:
--------
--- /work/SRC/openSUSE:Factory/python-boto3/python-boto3.changes
2021-12-18 20:30:02.506235738 +0100
+++ /work/SRC/openSUSE:Factory/.python-boto3.new.1896/python-boto3.changes
2022-01-07 12:45:41.463816702 +0100
@@ -1,0 +2,71 @@
+Wed Jan 5 16:05:52 UTC 2022 - John Paul Adrian Glaubitz
<adrian.glaub...@suse.com>
+
+- Update to version 1.20.28
+ * api-change:``rekognition``: [``botocore``] This release introduces a new
field
+ IndexFacesModelVersion, which is the version of the face detect and
storage model that was used
+ when indexing the face vector.
+ * api-change:``s3``: [``botocore``] Minor doc-based updates based on
feedback bugs received.
+ * enhancement:JSONFileCache: [``botocore``] Add support for __delitem__ in
JSONFileCache
+ * api-change:``s3control``: [``botocore``] Documentation updates for the
renaming of Glacier to
+ Glacier Flexible Retrieval.
+- from version 1.20.27
+ * api-change:``sagemaker``: [``botocore``] The release allows users to pass
pipeline definitions as
+ Amazon S3 locations and control the pipeline execution concurrency using
ParallelismConfiguration.
+ It also adds support of EMR jobs as pipeline steps.
+ * api-change:``rds``: [``botocore``] Multiple doc-only updates for
Relational Database Service (RDS)
+ * api-change:``mediaconvert``: [``botocore``] AWS Elemental MediaConvert SDK
has added strength
+ levels to the Sharpness Filter and now permits OGG files to be specified
as sidecar audio inputs.
+ * api-change:``greengrassv2``: [``botocore``] This release adds the API
operations to manage the
+ Greengrass role associated with your account and to manage the core device
connectivity
+ information. Greengrass V2 customers can now depend solely on Greengrass
V2 SDK for all the API
+ operations needed to manage their fleets.
+ * api-change:``detective``: [``botocore``] Added and updated API operations
to support the
+ Detective integration with AWS Organizations. New actions are used to
manage the delegated
+ administrator account and the integration configuration.
+- from version 1.20.26
+ * api-change:``nimble``: [``botocore``] Amazon Nimble Studio adds support
for users to upload files
+ during a streaming session using NICE DCV native client or browser.
+ * api-change:``chime-sdk-messaging``: [``botocore``] The Amazon Chime SDK
now supports updating
+ message attributes via channel flows
+ * api-change:``imagebuilder``: [``botocore``] Added a note to infrastructure
configuration actions
+ and data types concerning delivery of Image Builder event messages to
encrypted SNS topics. The key
+ that's used to encrypt the SNS topic must reside in the account that Image
Builder runs under.
+ * api-change:``workmail``: [``botocore``] This release allows customers to
change their email
+ monitoring configuration in Amazon WorkMail.
+ * api-change:``transfer``: [``botocore``] Property for Transfer Family used
with the FTPS protocol.
+ TLS Session Resumption provides a mechanism to resume or share a
negotiated secret key between the
+ control and data connection for an FTPS session.
+ * api-change:``lookoutmetrics``: [``botocore``] This release adds support
for Causal Relationships.
+ Added new ListAnomalyGroupRelatedMetrics API operation and
InterMetricImpactDetails API data type
+ * api-change:``mediaconnect``: [``botocore``] You can now use the
Fujitsu-QoS protocol for your
+ MediaConnect sources and outputs to transport content to and from Fujitsu
devices.
+ * api-change:``qldb``: [``botocore``] Amazon QLDB now supports journal
exports in JSON and Ion
+ Binary formats. This release adds an optional OutputFormat parameter to
the ExportJournalToS3 API.
+- from version 1.20.25
+ * api-change:``customer-profiles``: [``botocore``] This release adds an
optional parameter,
+ ObjectTypeNames to the PutIntegration API to support multiple object types
per integration option.
+ Besides, this release introduces Standard Order Objects which contain data
from third party systems
+ and each order object belongs to a specific profile.
+ * api-change:``sagemaker``: [``botocore``] This release adds a new
ContentType field in
+ AutoMLChannel for SageMaker CreateAutoMLJob InputDataConfig.
+ * api-change:``forecast``: [``botocore``] Adds ForecastDimensions field to
the
+ DescribeAutoPredictorResponse
+ * api-change:``securityhub``: [``botocore``] Added new resource details
objects to ASFF, including
+ resources for Firewall, and RuleGroup, FirewallPolicy Added additional
details for
+ AutoScalingGroup, LaunchConfiguration, and S3 buckets.
+ * api-change:``location``: [``botocore``] Making PricingPlan optional as
part of create resource
+ API.
+ * api-change:``redshift``: [``botocore``] This release adds API support for
managed Redshift
+ datashares. Customers can now interact with a Redshift datashare that is
managed by a different
+ service, such as AWS Data Exchange.
+ * api-change:``apigateway``: [``botocore``] Documentation updates for Amazon
API Gateway
+ * api-change:``devops-guru``: [``botocore``] Adds Tags support to
+ DescribeOrganizationResourceCollectionHealth
+ * api-change:``imagebuilder``: [``botocore``] This release adds support for
importing and exporting
+ VM Images as part of the Image Creation workflow via EC2 VM Import/Export.
+ * api-change:``datasync``: [``botocore``] AWS DataSync now supports FSx
Lustre Locations.
+ * api-change:``finspace-data``: [``botocore``] Make dataset description
optional and allow s3
+ export for dataviews
+- Update BuildRequires and Requires from setup.py
+
+-------------------------------------------------------------------
Old:
----
1.20.24.tar.gz
New:
----
1.20.28.tar.gz
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ python-boto3.spec ++++++
--- /var/tmp/diff_new_pack.FaJMzJ/_old 2022-01-07 12:45:41.963817049 +0100
+++ /var/tmp/diff_new_pack.FaJMzJ/_new 2022-01-07 12:45:41.963817049 +0100
@@ -19,7 +19,7 @@
%{?!python_module:%define python_module() python-%{**} python3-%{**}}
%define skip_python2 1
Name: python-boto3
-Version: 1.20.24
+Version: 1.20.28
Release: 0
Summary: Amazon Web Services Library
License: Apache-2.0
@@ -27,7 +27,7 @@
Source: https://github.com/boto/boto3/archive/%{version}.tar.gz
# Related test dependencies
BuildRequires: %{python_module botocore < 1.24.0}
-BuildRequires: %{python_module botocore >= 1.23.24}
+BuildRequires: %{python_module botocore >= 1.23.28}
BuildRequires: %{python_module mock}
BuildRequires: %{python_module pytest >= 6.2.5}
BuildRequires: %{python_module s3transfer < 0.6.0}
@@ -37,7 +37,7 @@
BuildRequires: fdupes
BuildRequires: python-rpm-macros
Requires: python-botocore < 1.24.0
-Requires: python-botocore >= 1.23.24
+Requires: python-botocore >= 1.23.28
Requires: python-jmespath < 1.0.0
Requires: python-jmespath >= 0.7.1
Requires: python-s3transfer < 0.6.0
++++++ 1.20.24.tar.gz -> 1.20.28.tar.gz ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/boto3-1.20.24/.changes/1.20.25.json
new/boto3-1.20.28/.changes/1.20.25.json
--- old/boto3-1.20.24/.changes/1.20.25.json 1970-01-01 01:00:00.000000000
+0100
+++ new/boto3-1.20.28/.changes/1.20.25.json 2022-01-04 20:09:14.000000000
+0100
@@ -0,0 +1,57 @@
+[
+ {
+ "category": "``customer-profiles``",
+ "description": "[``botocore``] This release adds an optional parameter,
ObjectTypeNames to the PutIntegration API to support multiple object types per
integration option. Besides, this release introduces Standard Order Objects
which contain data from third party systems and each order object belongs to a
specific profile.",
+ "type": "api-change"
+ },
+ {
+ "category": "``sagemaker``",
+ "description": "[``botocore``] This release adds a new ContentType field
in AutoMLChannel for SageMaker CreateAutoMLJob InputDataConfig.",
+ "type": "api-change"
+ },
+ {
+ "category": "``forecast``",
+ "description": "[``botocore``] Adds ForecastDimensions field to the
DescribeAutoPredictorResponse",
+ "type": "api-change"
+ },
+ {
+ "category": "``securityhub``",
+ "description": "[``botocore``] Added new resource details objects to ASFF,
including resources for Firewall, and RuleGroup, FirewallPolicy Added
additional details for AutoScalingGroup, LaunchConfiguration, and S3 buckets.",
+ "type": "api-change"
+ },
+ {
+ "category": "``location``",
+ "description": "[``botocore``] Making PricingPlan optional as part of
create resource API.",
+ "type": "api-change"
+ },
+ {
+ "category": "``redshift``",
+ "description": "[``botocore``] This release adds API support for managed
Redshift datashares. Customers can now interact with a Redshift datashare that
is managed by a different service, such as AWS Data Exchange.",
+ "type": "api-change"
+ },
+ {
+ "category": "``apigateway``",
+ "description": "[``botocore``] Documentation updates for Amazon API
Gateway",
+ "type": "api-change"
+ },
+ {
+ "category": "``devops-guru``",
+ "description": "[``botocore``] Adds Tags support to
DescribeOrganizationResourceCollectionHealth",
+ "type": "api-change"
+ },
+ {
+ "category": "``imagebuilder``",
+ "description": "[``botocore``] This release adds support for importing and
exporting VM Images as part of the Image Creation workflow via EC2 VM
Import/Export.",
+ "type": "api-change"
+ },
+ {
+ "category": "``datasync``",
+ "description": "[``botocore``] AWS DataSync now supports FSx Lustre
Locations.",
+ "type": "api-change"
+ },
+ {
+ "category": "``finspace-data``",
+ "description": "[``botocore``] Make dataset description optional and allow
s3 export for dataviews",
+ "type": "api-change"
+ }
+]
\ No newline at end of file
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/boto3-1.20.24/.changes/1.20.26.json
new/boto3-1.20.28/.changes/1.20.26.json
--- old/boto3-1.20.24/.changes/1.20.26.json 1970-01-01 01:00:00.000000000
+0100
+++ new/boto3-1.20.28/.changes/1.20.26.json 2022-01-04 20:09:14.000000000
+0100
@@ -0,0 +1,42 @@
+[
+ {
+ "category": "``nimble``",
+ "description": "[``botocore``] Amazon Nimble Studio adds support for users
to upload files during a streaming session using NICE DCV native client or
browser.",
+ "type": "api-change"
+ },
+ {
+ "category": "``chime-sdk-messaging``",
+ "description": "[``botocore``] The Amazon Chime SDK now supports updating
message attributes via channel flows",
+ "type": "api-change"
+ },
+ {
+ "category": "``imagebuilder``",
+ "description": "[``botocore``] Added a note to infrastructure
configuration actions and data types concerning delivery of Image Builder event
messages to encrypted SNS topics. The key that's used to encrypt the SNS topic
must reside in the account that Image Builder runs under.",
+ "type": "api-change"
+ },
+ {
+ "category": "``workmail``",
+ "description": "[``botocore``] This release allows customers to change
their email monitoring configuration in Amazon WorkMail.",
+ "type": "api-change"
+ },
+ {
+ "category": "``transfer``",
+ "description": "[``botocore``] Property for Transfer Family used with the
FTPS protocol. TLS Session Resumption provides a mechanism to resume or share a
negotiated secret key between the control and data connection for an FTPS
session.",
+ "type": "api-change"
+ },
+ {
+ "category": "``lookoutmetrics``",
+ "description": "[``botocore``] This release adds support for Causal
Relationships. Added new ListAnomalyGroupRelatedMetrics API operation and
InterMetricImpactDetails API data type",
+ "type": "api-change"
+ },
+ {
+ "category": "``mediaconnect``",
+ "description": "[``botocore``] You can now use the Fujitsu-QoS protocol
for your MediaConnect sources and outputs to transport content to and from
Fujitsu devices.",
+ "type": "api-change"
+ },
+ {
+ "category": "``qldb``",
+ "description": "[``botocore``] Amazon QLDB now supports journal exports in
JSON and Ion Binary formats. This release adds an optional OutputFormat
parameter to the ExportJournalToS3 API.",
+ "type": "api-change"
+ }
+]
\ No newline at end of file
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/boto3-1.20.24/.changes/1.20.27.json
new/boto3-1.20.28/.changes/1.20.27.json
--- old/boto3-1.20.24/.changes/1.20.27.json 1970-01-01 01:00:00.000000000
+0100
+++ new/boto3-1.20.28/.changes/1.20.27.json 2022-01-04 20:09:14.000000000
+0100
@@ -0,0 +1,27 @@
+[
+ {
+ "category": "``sagemaker``",
+ "description": "[``botocore``] The release allows users to pass pipeline
definitions as Amazon S3 locations and control the pipeline execution
concurrency using ParallelismConfiguration. It also adds support of EMR jobs as
pipeline steps.",
+ "type": "api-change"
+ },
+ {
+ "category": "``rds``",
+ "description": "[``botocore``] Multiple doc-only updates for Relational
Database Service (RDS)",
+ "type": "api-change"
+ },
+ {
+ "category": "``mediaconvert``",
+ "description": "[``botocore``] AWS Elemental MediaConvert SDK has added
strength levels to the Sharpness Filter and now permits OGG files to be
specified as sidecar audio inputs.",
+ "type": "api-change"
+ },
+ {
+ "category": "``greengrassv2``",
+ "description": "[``botocore``] This release adds the API operations to
manage the Greengrass role associated with your account and to manage the core
device connectivity information. Greengrass V2 customers can now depend solely
on Greengrass V2 SDK for all the API operations needed to manage their fleets.",
+ "type": "api-change"
+ },
+ {
+ "category": "``detective``",
+ "description": "[``botocore``] Added and updated API operations to support
the Detective integration with AWS Organizations. New actions are used to
manage the delegated administrator account and the integration configuration.",
+ "type": "api-change"
+ }
+]
\ No newline at end of file
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/boto3-1.20.24/.changes/1.20.28.json
new/boto3-1.20.28/.changes/1.20.28.json
--- old/boto3-1.20.24/.changes/1.20.28.json 1970-01-01 01:00:00.000000000
+0100
+++ new/boto3-1.20.28/.changes/1.20.28.json 2022-01-04 20:09:14.000000000
+0100
@@ -0,0 +1,22 @@
+[
+ {
+ "category": "``rekognition``",
+ "description": "[``botocore``] This release introduces a new field
IndexFacesModelVersion, which is the version of the face detect and storage
model that was used when indexing the face vector.",
+ "type": "api-change"
+ },
+ {
+ "category": "``s3``",
+ "description": "[``botocore``] Minor doc-based updates based on feedback
bugs received.",
+ "type": "api-change"
+ },
+ {
+ "category": "JSONFileCache",
+ "description": "[``botocore``] Add support for __delitem__ in
JSONFileCache",
+ "type": "enhancement"
+ },
+ {
+ "category": "``s3control``",
+ "description": "[``botocore``] Documentation updates for the renaming of
Glacier to Glacier Flexible Retrieval.",
+ "type": "api-change"
+ }
+]
\ No newline at end of file
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/boto3-1.20.24/CHANGELOG.rst
new/boto3-1.20.28/CHANGELOG.rst
--- old/boto3-1.20.24/CHANGELOG.rst 2021-12-13 21:09:36.000000000 +0100
+++ new/boto3-1.20.28/CHANGELOG.rst 2022-01-04 20:09:14.000000000 +0100
@@ -2,6 +2,54 @@
CHANGELOG
=========
+1.20.28
+=======
+
+* api-change:``rekognition``: [``botocore``] This release introduces a new
field IndexFacesModelVersion, which is the version of the face detect and
storage model that was used when indexing the face vector.
+* api-change:``s3``: [``botocore``] Minor doc-based updates based on feedback
bugs received.
+* enhancement:JSONFileCache: [``botocore``] Add support for __delitem__ in
JSONFileCache
+* api-change:``s3control``: [``botocore``] Documentation updates for the
renaming of Glacier to Glacier Flexible Retrieval.
+
+
+1.20.27
+=======
+
+* api-change:``sagemaker``: [``botocore``] The release allows users to pass
pipeline definitions as Amazon S3 locations and control the pipeline execution
concurrency using ParallelismConfiguration. It also adds support of EMR jobs as
pipeline steps.
+* api-change:``rds``: [``botocore``] Multiple doc-only updates for Relational
Database Service (RDS)
+* api-change:``mediaconvert``: [``botocore``] AWS Elemental MediaConvert SDK
has added strength levels to the Sharpness Filter and now permits OGG files to
be specified as sidecar audio inputs.
+* api-change:``greengrassv2``: [``botocore``] This release adds the API
operations to manage the Greengrass role associated with your account and to
manage the core device connectivity information. Greengrass V2 customers can
now depend solely on Greengrass V2 SDK for all the API operations needed to
manage their fleets.
+* api-change:``detective``: [``botocore``] Added and updated API operations to
support the Detective integration with AWS Organizations. New actions are used
to manage the delegated administrator account and the integration configuration.
+
+
+1.20.26
+=======
+
+* api-change:``nimble``: [``botocore``] Amazon Nimble Studio adds support for
users to upload files during a streaming session using NICE DCV native client
or browser.
+* api-change:``chime-sdk-messaging``: [``botocore``] The Amazon Chime SDK now
supports updating message attributes via channel flows
+* api-change:``imagebuilder``: [``botocore``] Added a note to infrastructure
configuration actions and data types concerning delivery of Image Builder event
messages to encrypted SNS topics. The key that's used to encrypt the SNS topic
must reside in the account that Image Builder runs under.
+* api-change:``workmail``: [``botocore``] This release allows customers to
change their email monitoring configuration in Amazon WorkMail.
+* api-change:``transfer``: [``botocore``] Property for Transfer Family used
with the FTPS protocol. TLS Session Resumption provides a mechanism to resume
or share a negotiated secret key between the control and data connection for an
FTPS session.
+* api-change:``lookoutmetrics``: [``botocore``] This release adds support for
Causal Relationships. Added new ListAnomalyGroupRelatedMetrics API operation
and InterMetricImpactDetails API data type
+* api-change:``mediaconnect``: [``botocore``] You can now use the Fujitsu-QoS
protocol for your MediaConnect sources and outputs to transport content to and
from Fujitsu devices.
+* api-change:``qldb``: [``botocore``] Amazon QLDB now supports journal exports
in JSON and Ion Binary formats. This release adds an optional OutputFormat
parameter to the ExportJournalToS3 API.
+
+
+1.20.25
+=======
+
+* api-change:``customer-profiles``: [``botocore``] This release adds an
optional parameter, ObjectTypeNames to the PutIntegration API to support
multiple object types per integration option. Besides, this release introduces
Standard Order Objects which contain data from third party systems and each
order object belongs to a specific profile.
+* api-change:``sagemaker``: [``botocore``] This release adds a new ContentType
field in AutoMLChannel for SageMaker CreateAutoMLJob InputDataConfig.
+* api-change:``forecast``: [``botocore``] Adds ForecastDimensions field to the
DescribeAutoPredictorResponse
+* api-change:``securityhub``: [``botocore``] Added new resource details
objects to ASFF, including resources for Firewall, and RuleGroup,
FirewallPolicy Added additional details for AutoScalingGroup,
LaunchConfiguration, and S3 buckets.
+* api-change:``location``: [``botocore``] Making PricingPlan optional as part
of create resource API.
+* api-change:``redshift``: [``botocore``] This release adds API support for
managed Redshift datashares. Customers can now interact with a Redshift
datashare that is managed by a different service, such as AWS Data Exchange.
+* api-change:``apigateway``: [``botocore``] Documentation updates for Amazon
API Gateway
+* api-change:``devops-guru``: [``botocore``] Adds Tags support to
DescribeOrganizationResourceCollectionHealth
+* api-change:``imagebuilder``: [``botocore``] This release adds support for
importing and exporting VM Images as part of the Image Creation workflow via
EC2 VM Import/Export.
+* api-change:``datasync``: [``botocore``] AWS DataSync now supports FSx Lustre
Locations.
+* api-change:``finspace-data``: [``botocore``] Make dataset description
optional and allow s3 export for dataviews
+
+
1.20.24
=======
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/boto3-1.20.24/boto3/__init__.py
new/boto3-1.20.28/boto3/__init__.py
--- old/boto3-1.20.24/boto3/__init__.py 2021-12-13 21:09:36.000000000 +0100
+++ new/boto3-1.20.28/boto3/__init__.py 2022-01-04 20:09:14.000000000 +0100
@@ -18,7 +18,7 @@
__author__ = 'Amazon Web Services'
-__version__ = '1.20.24'
+__version__ = '1.20.28'
# The default Boto3 session; autoloaded when needed.
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/boto3-1.20.24/docs/source/guide/index.rst
new/boto3-1.20.28/docs/source/guide/index.rst
--- old/boto3-1.20.24/docs/source/guide/index.rst 2021-12-13
21:09:36.000000000 +0100
+++ new/boto3-1.20.28/docs/source/guide/index.rst 2022-01-04
20:09:14.000000000 +0100
@@ -40,7 +40,6 @@
:maxdepth: 1
cloud9
- sdk-metrics
Migrations
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/boto3-1.20.24/docs/source/guide/sdk-metrics.rst
new/boto3-1.20.28/docs/source/guide/sdk-metrics.rst
--- old/boto3-1.20.24/docs/source/guide/sdk-metrics.rst 2021-12-13
21:09:36.000000000 +0100
+++ new/boto3-1.20.28/docs/source/guide/sdk-metrics.rst 1970-01-01
01:00:00.000000000 +0100
@@ -1,271 +0,0 @@
-.. _guide_sdk-metrics:
-
-SDK metrics
-===========
-
-AWS SDK Metrics for Enterprise Support (SDK Metrics) enables Enterprise
customers to collect metrics from AWS SDKs on their hosts and clients shared
with
-AWS Enterprise Support. SDK Metrics provides information that helps speed up
detection and diagnosis of issues occurring in connections
-to AWS services for AWS Enterprise Support customers.
-
-As telemetry is collected on each host, it is relayed via UDP to 127.0.0.1
(aka localhost), where the CloudWatch agent aggregates the data and sends it
-to the SDK Metrics service. Therefore, to receive metrics, you must add the
CloudWatch agent to your instance.
-
-The following steps to set up SDK Metrics pertain to an Amazon EC2 instance
running Amazon Linux for a client application that is using the AWS SDK for
Python.
-SDK Metrics is also available for your production environments if you enable
it while configuring the AWS SDK for Python.
-
-To utilize SDK Metrics, run the latest version of the CloudWatch agent. Learn
how to
-`Configure the CloudWatch Agent for SDK Metrics
<https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Agent-SDK-Metrics.html>`__
in the Amazon CloudWatch User Guide.
-
-To set up SDK Metrics with the AWS SDK for Python, follow these instructions:
-
-#. Create an application with an AWS SDK for Python client to use an AWS
service.
-#. Host your project on an Amazon EC2 instance or in your local environment.
-#. Install and use the latest version of Boto3 (AWS SDK for Python).
-#. Install and configure a CloudWatch agent on an EC2 instance or in your
local environment as described in the `Amazon CloudWatch User Guide
<https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Agent-SDK-Metrics.html>`__
.
-#. Authorize SDK Metrics to collect and send metrics as described in the
`Amazon CloudWatch User Guide
<https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Agent-SDK-Metrics.html>`__
..
-#. :ref:`csm-enable-agent`.
-
-
-For more information, see the following:
-
-* :ref:`csm-update-agent`
-* :ref:`csm-disable-agent`
-
-
-.. _csm-enable-agent:
-
-Enable SDK metrics
-------------------
-
-By default, SDK Metrics is turned off, and the port is set to 31000. The
following are the default parameters.
-
-Enabling SDK Metrics is independent of configuring your credentials to use an
AWS service.
-
-You can enable SDK Metrics by setting environment variables or by using the
AWS Shared config file.
-
-Option 1: Set environment variables
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-If :code:`AWS_CSM_ENABLED` is not set, the SDK checks the
:code:`AWS_DEFAULT_PROFILE` profile to determine if SDK Metrics is enabled. By
default this is set to ``false``.
-
-To turn on SDK Metrics, add the following to your environmental variables.
-
-.. code-block:: shell
-
- export AWS_CSM_ENABLED=true
-
-:ref:`Other configuration settings<csm-update-agent>` are available.
-
-Note: Enabling SDK Metrics does not configure your credentials to use an AWS
service.
-
-
-Option 2: AWS shared config file
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-If no CSM configuration is found in the environment variables, the SDK looks
for your default AWS profile field. If :code:`AWS_DEFAULT_PROFILE` is set to
something other than default, update that profile. To enable SDK Metrics, add
:code:`csm_enabled` to the shared config file located at :file:`~/.aws/config`.
-
-.. code-block:: ini
-
- [default]
- csm_enabled = true
-
- [profile aws_csm]
- csm_enabled = true
-
-:ref:`Other configuration settings<csm-update-agent>` are available.
-
-Note: Enabling SDK Metrics is independent from configuring your credentials to
use an AWS service. You can use a different profile to authenticate.
-
-.. _csm-update-agent:
-
-Update a CloudWatch agent
--------------------------
-
-To make changes to the port, you need to set the values and then restart any
AWS jobs that are currently active.
-
-Option 1: Set environment variables
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Most services use the default port. But if your service requires a unique port
ID, add ``AWS_CSM_PORT=[port_number]``, to the host's environment variables.
-
-.. code-block:: shell
-
- export AWS_CSM_ENABLED=true
- export AWS_CSM_PORT=1234
-
-
-Option 2: AWS shared config file
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Most services use the default port. But if your service requires a
-unique port ID, add ``csm_port = [port_number]`` to ``~/.aws/config``.
-
-.. code-block:: ini
-
- [default]
- csm_enabled = false
- csm_port = 1234
-
- [profile aws_csm]
- csm_enabled = false
- csm_port = 1234
-
-Restart SDK metrics
-~~~~~~~~~~~~~~~~~~~
-
-To restart a job, run the following commands.
-
-.. code-block:: shell
-
- amazon-cloudwatch-agent-ctl ???a stop;
- amazon-cloudwatch-agent-ctl ???a start;
-
-
-.. _csm-disable-agent:
-
-Disable SDK metrics
---------------------
-
-To turn off SDK Metrics, remove ``csm_enabled`` from your environment
variables, or in your AWS Shared config file located at :file:`~/.aws/config`.
-Then restart your CloudWatch agent so that the changes can take effect.
-
-**Environment Variables**
-
-Remove ``AWS_CSM_ENABLED`` from your environment variables or set it to false.
-
-.. code-block:: shell
-
- unset AWS_CSM_ENABLED
-
-
-**AWS Shared Config File**
-
-Remove ``csm_enabled`` from the profiles in your AWS Shared config file
located at :file:`~/.aws/config`.
-
-.. note:: Environment variables override the AWS Shared config file. If SDK
Metrics is enabled in the environment variables, the SDK Metrics remain enabled.
-
-To explicitly opt-out of SDK Metrics set ``csm_enabled`` to false.
-
-.. code-block:: ini
-
- [default]
- csm_enabled = false
-
- [profile aws_csm]
- csm_enabled = false
-
-To disable SDK Metrics, use the following command to stop CloudWatch agent.
-
-.. code-block:: shell
-
- sudo amazon-cloudwatch-agent-ctl -a stop &&
- echo "Done"
-
-If you are using other CloudWatch features, restart CloudWatch Agent with the
following command.
-
-.. code-block:: shell
-
- amazon-cloudwatch-agent-ctl ???a start;
-
-
-Restart SDK metrics
-~~~~~~~~~~~~~~~~~~~
-
-To restart a SDK Metrics job, run the following commands.
-
-.. code-block:: shell
-
- amazon-cloudwatch-agent-ctl ???a stop;
- amazon-cloudwatch-agent-ctl ???a start;
-
-Definitions for SDK metrics
----------------------------
-
-You can use the following descriptions of SDK Metrics to interpret your
results. In general, these metrics are available for review
-with your Technical Account Manager during regular business reviews. AWS
Support resources and your Technical Account Manager
-should have access to SDK Metrics data to help you resolve cases, but if you
discover data that is confusing or unexpected, but
-doesn???t seem to be negatively impacting your applications??? performance, it
is best to review that data during scheduled
-business reviews.
-
-.. list-table::
- :widths: 1 2
- :header-rows: 1
-
- * - Metric:
- - CallCount
-
- * - Definition
- - Total number of successful or failed API calls from your code to AWS
services
-
- * - How to use it
- - Use it as a baseline to correlate with other metrics like errors or
throttling.
-
-
-.. list-table::
- :widths: 1 2
- :header-rows: 1
-
- * - Metric:
- - ClientErrorCount
-
- * - Definition
- - Number of API calls that fail with client errors (4xx HTTP response
codes). *Examples: Throttling, Access denied, S3 bucket does not exist, and
Invalid parameter value.*
-
- * - How to use it
- - Except in certain cases related to throttling (ex. when throttling
occurs due to a limit that needs to be increased) this metric can indicate
something in your application that needs to be fixed.
-
-
-.. list-table::
- :widths: 1 2
- :header-rows: 1
-
- * - Metric:
- - ConnectionErrorCount
-
- * - Definition
- - Number of API calls that fail because of errors connecting to the
service. These can be caused by network issues between the customer application
and AWS services including load balancers, DNS failures, transit providers. In
some cases, AWS issues may result in this error.
-
- * - How to use it
- - Use this metric to determine whether issues are specific to your
application or are caused by your infrastructure and/or network. High
ConnectionErrorCount could also indicate short timeout values for API calls.
-
-
-.. list-table::
- :widths: 1 2
- :header-rows: 1
-
- * - Metric:
- - ThrottleCount
-
- * - Definition
- - Number of API calls that fail due to throttling by AWS services.
-
- * - How to use it
- - Use this metric to assess if your application has reached throttle
limits, as well as to determine the cause of retries and application latency.
Consider distributing calls over a window instead of batching your calls.
-
-
-.. list-table::
- :widths: 1 2
- :header-rows: 1
-
- * - Metric:
- - ServerErrorCount
-
- * - Definition
- - Number of API calls that fail due to server errors (5xx HTTP response
codes) from AWS Services. These are typically caused by AWS services.
-
- * - How to use it
- - Determine cause of SDK retries or latency. This metric will not always
indicate that AWS services are at fault, as some AWS teams classify latency as
an HTTP 503 response.
-
-.. list-table::
- :widths: 1 2
- :header-rows: 1
-
- * - Metric:
- - EndToEndLatency
-
- * - Definition
- - Total time for your application to make a call using the AWS SDK,
inclusive of retries. In other words, regardless of whether it is successful
after several attempts, or as soon as a call fails due to an unretriable error.
-
- * - How to use it
- - Determine how AWS API calls contribute to your application???s overall
latency. Higher than expected latency may be caused by issues with network,
firewall, or other configuration settings, or by latency that occurs as a
result of SDK retries.
-
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/boto3-1.20.24/setup.cfg new/boto3-1.20.28/setup.cfg
--- old/boto3-1.20.24/setup.cfg 2021-12-13 21:09:36.000000000 +0100
+++ new/boto3-1.20.28/setup.cfg 2022-01-04 20:09:14.000000000 +0100
@@ -3,7 +3,7 @@
[metadata]
requires_dist =
- botocore>=1.23.24,<1.24.0
+ botocore>=1.23.28,<1.24.0
jmespath>=0.7.1,<1.0.0
s3transfer>=0.5.0,<0.6.0
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/boto3-1.20.24/setup.py new/boto3-1.20.28/setup.py
--- old/boto3-1.20.24/setup.py 2021-12-13 21:09:36.000000000 +0100
+++ new/boto3-1.20.28/setup.py 2022-01-04 20:09:14.000000000 +0100
@@ -13,7 +13,7 @@
requires = [
- 'botocore>=1.23.24,<1.24.0',
+ 'botocore>=1.23.28,<1.24.0',
'jmespath>=0.7.1,<1.0.0',
's3transfer>=0.5.0,<0.6.0'
]
