05-24-2024 03:50 PM - edited 05-24-2024 03:53 PM
My customers has observed that all of a sudden they were unable to access AWS Sagemaker service from their AWS console. Observed that that firewall was blocking this traffic and customer has to add application "amazon-sagemaker" explicitly in their configuration for it to work. There was no change from their end. Has there any changes from Palo side which caused this issue?
05-26-2024 12:06 AM
Hello @lavatechno
Palo Alto has released in content update: 8852-8753 Applications Content Release Notes several new App-IDs. Amazon-bedrock and amazon-sagemaker were among them. Both of them were previously identified as amazon-aws-console, ssl, web-browsing, therefore this has likely cased the issue you described after Firewall has installed this content update.
Kind Regards
Pavel
05-26-2024 12:06 AM
Hello @lavatechno
Palo Alto has released in content update: 8852-8753 Applications Content Release Notes several new App-IDs. Amazon-bedrock and amazon-sagemaker were among them. Both of them were previously identified as amazon-aws-console, ssl, web-browsing, therefore this has likely cased the issue you described after Firewall has installed this content update.
Kind Regards
Pavel
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
