Release notes
Back to All

Jun 8, 2023 — Security Connector 3.5.0 now available

almost 2 years ago by lruaware@akamai.com

Security Connector 3.5.0 is now available for download or upgrade. You can now deploy Security Connector on the Amazon Web Services (AWS) and Microsoft Azure cloud platforms.

When deploying Security Connector on these platforms, you do not need to download the Security Connector image file in Enterprise Center.

  • For Azure, the Security Connector image file is available in the Azure Marketplace.
  • For AWS, you must contact your ​​Akamai​​ representative to have ​​Akamai​​ share the image file to your AWS account as a Community AMI.

For instructions on setting up Security Connector on Azure or AWS, see Deploy Security Connector.

The following issues or limitations have been resolved in this update:

  • Direct-to-origin failover setting for HTTP Forwarder dropped domains configured for bypass if they were in other lists with a conflicting policy action. This issue has been resolved. Requests to these domains are now directed to the origin.
  • Unnecessary PII logging setting in Security Connector. This setting has been removed from Security Connector. By default, the user’s encrypted internal IP address is reported in ​SIA​ reports.
  • Domains configured in the Local Bypass Settings (Clients & Connectors > Local Bypass Settings) were dropped if they could only be resolved by the local DNS server. This issue has been resolved. This traffic is now directed to the origin.
  • IP addresses or CIDRs configured in the Local Bypass Settings were not supported by Security Connector. This issue has been resolved. IP addresses or CIDRs in the Local Bypass Setting now bypass Security Connector and are directed to the origin.
  • A BPDU filter was previously required on a VMware ESXi host to prevent a denial-of-service scenario. This issue has been resolved.
  • In certain situations, HTTP Forwarder failover did not work properly. Make sure you configure your local or corporate DNS server as the Security Connector DNS name server. The Security Connector DNS name servers act as fallback servers if ​SIA​ is in an unhealthy state. As a result, you should not configure the ​SIA​ DNS servers as the Security Connector DNS name servers.