3.74.0 4.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657
  1. [
  2. {
  3. "type": "api-change",
  4. "category": "AppSync",
  5. "description": "AWS AppSync now supports: 1. Pipeline Resolvers - Enables execution of one or more operations against multiple data sources in order, on a single GraphQL field. This allows orchestration of actions by composing code into a single Resolver, or share code across Resolvers. 2. Aurora Serverless Data Source - Built-in resolver for executing GraphQL operations with the new Aurora Serverless Data API, including connection management functionality."
  6. },
  7. {
  8. "type": "feature",
  9. "category": "RDSDataService",
  10. "description": "The RDS Data API Beta is available for the MySQL-compatible edition of Amazon Aurora Serverless in the US East (N. Virginia) Region. This API enables you to easily access Aurora Serverless with web services-based applications including AWS Lambda and AWS AppSync."
  11. },
  12. {
  13. "type": "api-change",
  14. "category": "XRay",
  15. "description": "Groups build upon X-Ray filter expressions to allow for fine tuning trace summaries and service graph results. You can configure groups by using the AWS X-Ray console or by using the CreateGroup API. The addition of groups has extended the available request fields to the GetServiceGraph API. You can now specify a group name or group ARN to retrieve its service graph."
  16. },
  17. {
  18. "type": "api-change",
  19. "category": "CloudFront",
  20. "description": "With Origin Failover capability in CloudFront, you can setup two origins for your distributions - primary and secondary, such that your content is served from your secondary origin if CloudFront detects that your primary origin is unavailable. These origins can be any combination of AWS origins or non-AWS custom HTTP origins. For example, you can have two Amazon S3 buckets that serve as your origin that you independently upload your content to. If an object that CloudFront requests from your primary bucket is not present or if connection to your primary bucket times-out, CloudFront will request the object from your secondary bucket. So, you can configure CloudFront to trigger a failover in response to either HTTP 4xx or 5xx status codes."
  21. },
  22. {
  23. "type": "feature",
  24. "category": "QuickSight",
  25. "description": "Amazon QuickSight is a fully managed, serverless, cloud business intelligence system that allows you to extend data and insights to every user in your organization. The first release of APIs for Amazon QuickSight introduces embedding and user\/group management capabilities. The get-dashboard-embed-url API allows you to obtain an authenticated dashboard URL that can be embedded in application domains whitelisted for QuickSight dashboard embedding. User APIs allow you to programmatically expand and manage your QuickSight deployments while group APIs allow easier permissions management for resources within QuickSight."
  26. },
  27. {
  28. "type": "api-change",
  29. "category": "CloudWatch",
  30. "description": "Amazon CloudWatch now supports alarms on metric math expressions."
  31. },
  32. {
  33. "type": "enhancement",
  34. "category": "Redshift",
  35. "description": "Documentation updates for redshift"
  36. },
  37. {
  38. "type": "api-change",
  39. "category": "DeviceFarm",
  40. "description": "Disabling device filters"
  41. },
  42. {
  43. "type": "api-change",
  44. "category": "SSM",
  45. "description": "AWS Systems Manager Distributor helps you securely distribute and install software packages."
  46. },
  47. {
  48. "type": "api-change",
  49. "category": "MediaLive",
  50. "description": "You can now include the media playlist(s) from both pipelines in the HLS master manifest for seamless failover."
  51. },
  52. {
  53. "type": "api-change",
  54. "category": "AutoScalingPlans",
  55. "description": "In this release, AWS Auto Scaling adds three features: 1) Predictive scaling for EC2 Auto Scaling, which analyzes your application workload history to forecast future capacity requirements, 2) an option to replace existing scaling policies that are associated with the resources in your scaling plan, and 3) an option that allows you to use predictive scaling with or without your plan's dynamic scaling feature."
  56. }
  57. ]