chat/protected/vendor/aws/aws-sdk-php/.changes/3.38.0

[
    {
        "type": "bugfix",
        "category": "Rds",
        "description": "Update PresignUrlMiddleware to take an optional require_different_region, default false, for providing presigned urls only if the source and destination regions differ. Require this for RdsClient operations that use the middleware."
    },
    {
        "type": "feature",
        "category": "S3",
        "description": "Adds the S3EncryptionClient with CBC and GCM support. Uses pluggable strategies for handling a MetadataEnvelope in conjunction with a MaterialsProvider. Supports putObject[Async] and getObject[Async] operations."
    },
    {
        "type": "api-change",
        "category": "ApplicationAutoScaling",
        "description": "Application Auto Scaling customers are now able to schedule adjustments to their MinCapacity and MaxCapacity, which makes it possible to pre-provision adequate capacity for anticipated demand and then reduce the provisioned capacity as demand lulls."
    },
    {
        "type": "api-change",
        "category": "EC2",
        "description": "AWS PrivateLink for Amazon Services - Customers can now privately access Amazon services from their Amazon Virtual Private Cloud (VPC), without using public IPs, and without requiring the traffic to traverse across the Internet."
    },
    {
        "type": "enhancement",
        "category": "S3",
        "description": "Updates several S3 endpoints."
    },
    {
        "type": "enhancement",
        "category": "Batch",
        "description": "Documentation updates for AWS Batch."
    },
    {
        "type": "api-change",
        "category": "ElastiCache",
        "description": "This release adds online resharding for ElastiCache for Redis offering, providing the ability to add and remove shards from a running cluster. Developers can now dynamically scale-out or scale-in their Redis cluster workloads to adapt to changes in demand. ElastiCache will resize the cluster by adding or removing shards and redistribute hash slots uniformly across the new shard configuration, all while the cluster continues to stay online and serves requests."
    }
]