You can now use the latest LTS version of Java with Azure Functions.
Generally Available: Durable Functions support for Java
Durable Functions make it easy to orchestrate stateful workflows as-code in a serverless environment.
Generally available: Static Web Apps Diagnostics
You can now access guided troubleshooting information related to specific issues detected within your Azure Static Web Apps service configuration.
Public preview: New UX for the AKS DevX Extension for Visual Studio Code
Easily containerize non-container applications using Draft.
Generally Available: Kubernetes 1.25 support in AKS
You can now benefit from Kubernetes 1.25 enhancements in AKS.
Azure SQL—General availability updates for mid-December 2022
General availability enhancements and updates released for Azure SQL in mid-December 2022.
New – Bring ML Models Built Anywhere into Amazon SageMaker Canvas and Generate Predictions
Amazon SageMaker Canvas provides business analysts with a visual interface to solve business problems using machine learning (ML) without writing a single line of code. Since we introduced SageMaker Canvas in 2021, many users have asked us for an enhanced, seamless collaboration experience that enables data scientists to share trained models with their business analysts with a few simple clicks.
Today, I’m excited to announce that you can now bring ML models built anywhere into SageMaker Canvas and generate predictions.
New – Bring Your Own Model into SageMaker Canvas
As a data scientist or ML practitioner, you can now seamlessly share models built anywhere, within or outside Amazon SageMaker, with your business teams. This removes the heavy lifting for your engineering teams to build a separate tool or user interface to share ML models and collaborate between the different parts of your organization. As a business analyst, you can now leverage ML models shared by your data scientists within minutes to generate predictions.
Let me show you how this works in practice!
In this example, I share an ML model that has been trained to identify customers that are potentially at risk of churning with my marketing analyst. First, I register the model in the SageMaker model registry. SageMaker model registry lets you catalog models and manage model versions. I create a model group called 2022-customer-churn-model-group
and then select Create model version to register my model.
To register your model, provide the location of the inference image in Amazon ECR, as well as the location of your model.tar.gz
file in Amazon S3. You can also add model endpoint recommendations and additional model information. Once you’ve registered your model, select the model version and select Share.
You can now choose the SageMaker Canvas user profile(s) within the same SageMaker domain you want to share your model with. Then, provide additional model details, such as information about training and validation datasets, the ML problem type, and model output information. You can also add a note for the SageMaker Canvas users you share the model with.
Similarly, you can now also share models trained in SageMaker Autopilot and models available in SageMaker JumpStart with SageMaker Canvas users.
The business analysts will receive an in-app notification in SageMaker Canvas that a model has been shared with them, along with any notes you added.
My marketing analyst can now open, analyze, and start using the model to generate ML predictions in SageMaker Canvas.
Select Batch prediction to generate ML predictions for an entire dataset or Single prediction to create predictions for a single input. You can download the results in a .csv file.
New – Improved Model Sharing and Collaboration from SageMaker Canvas with SageMaker Studio Users
We also improved the sharing and collaboration capabilities from SageMaker Canvas with data science and ML teams. As a business analyst, you can now select which SageMaker Studio user profile(s) you want to share your standard-build models with.
Your data scientists or ML practitioners will receive a similar in-app notification in SageMaker Studio once a model has been shared with them, along with any notes from you. In addition to just reviewing the model, SageMaker Studio users can now also, if needed, update the data transformations in SageMaker Data Wrangler, retrain the model in SageMaker Autopilot, and share back the updated model. SageMaker Studio users can also recommend an alternate model from the list of models in SageMaker Autopilot.
Once SageMaker Studio users share back a model, you receive another notification in SageMaker Canvas that an updated model has been shared back with you. This collaboration between business analysts and data scientists will help democratize ML across organizations by bringing transparency to automated decisions, building trust, and accelerating ML deployments.
Now Available
The enhanced, seamless collaboration capabilities for Amazon SageMaker Canvas, including the ability to bring your ML models built anywhere, are available today in all AWS Regions where SageMaker Canvas is available with no changes to the existing SageMaker Canvas pricing.
Start collaborating and bring your ML model to Amazon SageMaker Canvas today!
— Antje
Heads-Up: Amazon S3 Security Changes Are Coming in April of 2023
Starting in April of 2023 we will be making two changes to Amazon Simple Storage Service (Amazon S3) to put our latest best practices for bucket security into effect automatically. The changes will begin to go into effect in April and will be rolled out to all AWS Regions within weeks.
Once the changes are in effect for a target Region, all newly created buckets in the Region will by default have S3 Block Public Access enabled and access control lists (ACLs) disabled. Both of these options are already console defaults and have long been recommended as best practices. The options will become the default for buckets that are created using the S3 API, S3 CLI, the AWS SDKs, or AWS CloudFormation templates.
As a bit of history, S3 buckets and objects have always been private by default. We added Block Public Access in 2018 and the ability to disable ACLs in 2021 in order to give you more control, and have long been recommending the use of AWS Identity and Access Management (IAM) policies as a modern and more flexible alternative.
In light of this change, we recommend a deliberate and thoughtful approach to the creation of new buckets that rely on public buckets or ACLs, and believe that most applications do not need either one. If your application turns out to be one that does, then you will need to make the changes that I outline below (be sure to review your code, scripts, AWS CloudFormation templates, and any other automation).
What’s Changing
Let’s take a closer look at the changes that we are making:
S3 Block Public Access – All four of the bucket-level settings described in this post will be enabled for newly created buckets:
A subsequent attempt to set a bucket policy or an access point policy that grants public access will be rejected with a 403 Access Denied error. If you need public access for a new bucket you can create it as usual and then delete the public access block by calling DeletePublicAccessBlock
(you will need s3:PutBucketPublicAccessBlock permission in order to call this function; read Block Public Access to learn more about the functions and the permissions).
ACLs Disabled – The Bucket owner enforced setting will be enabled for newly created buckets, making bucket ACLs and object ACLs ineffective, and ensuring that the bucket owner is the object owner no matter who uploads the object. If you want to enable ACLs for a bucket, you can set the ObjectOwnership
parameter to ObjectWriter
in your CreateBucket
request or you can call DeleteBucketOwnershipControls
after you create the bucket. You will need s3:PutBucketOwnershipControls permission in order to use the parameter or to call the function; read Controlling Ownership of Objects and Creating a Bucket to learn more.
Stay Tuned
We will publish an initial What’s New post when we start to deploy this change and another one when the deployment has reached all AWS Regions. You can also run your own tests to detect the change in behavior.
— Jeff
Facet Enhancements for Cloud Search
What’s changing
- Faceting support for integer type fields, such as priority levels for support tickets or the number of pages in a document
- Out of the box Faceting support for document size, document creation, and custom date fields
- New default reserved operators for document size and created date fields
- Simplified Query API response with filters being directly provided in the response
Getting started
- Admins and developers: See our developer documentation for more information about using new facet enhancements
- End users: There is no end user action required. You will automatically see new filter options once your admin has configured them
Rollout pace
- This feature is available now for all users.
Availability
- Available to Google Cloud Search Customers