![]() ![]() We currently use a mix of our own IP addresses and others provided by third parties (namely Amazon Web Services). Used for in-product integration with the Slack ecosystem. Used to track errors and failures in product experiences. Used to test, evaluate and control the delivery of new product experiences. Used for Cookie Consent requests as mandated by Privacy and Data Protection laws. Google Hosted Libraries content distribution network for open-source JavaScript libraries used by some Atlassian products. Google Hosted Libraries Content Delivery Network Used by some Atlassian products to display generic or public avatars. Wordpress/Gravatar Content Delivery Network Used by almost all Atlassian products to accelerate content delivery to browsers. Wss:// by almost all Atlassian products to deliver real-time events in-product, such as live updates to ticket statues, pages and notifications.Īmazon Web Services Content Delivery Network Please refer to the AWS IP range JSON file for the IP range for the AWS region ap-south-1. Wss://Īll traffic originating from the Hong Kong Datacenter environment will have one of the following source IP addresses: Please refer to the AWS IP range JSON file for the IP range for the AWS region ap-east-1. Wss://Īll traffic originating from the Capetown Datacenter environment will have one of the following source IP addresses: Please refer to the AWS IP range JSON file for the IP range for the AWS region af-south-1. Wss://Īll traffic originating from the London Datacenter environment will have one of the following source IP addresses: Please refer to the AWS IP range JSON file for the IP range for the AWS region eu-west-2. Wss://Īll traffic originating from the Frankfurt Datacenter environment will have one of the following source IP addresses: Please refer to the AWS IP range JSON file for the IP range for the AWS region eu-central-1. Wss://Īll traffic originating from the Sao Paolo Datacenter environment will have one of the following source IP addresses: Please refer to the AWS IP range JSON file for the IP ranges for the sa-east-1 region.ĪppDynamics will provide a unique set of IP addresses at the time of provisioning the Controller Tenant within AWS. See the CloudFront IP ranges for the possible IP addresses used for the AppDynamics CDN.ĪppDynamics OpenTelemetry Service (SaaS Controller) Wss://Īll traffic originating from the Oregon Datacenter environment will have one of the following source IP addresses:ĪppDynamics Content Delivery Network (CDN)ĪppDynamics uses Amazon CloudFront for the CDN. Please refer to the AWS IP range JSON file for the IP ranges for the us-west-2 region. Please contact your account team or support team if you have any questions. This change needs to be made before May 27th, 2022, otherwise EUM data will be lost (including Mobile and Browser RUM) for any applications being monitored which sit behind the firewall. If your organization currently utilizes firewall rules based on static IP ranges, you will need to update them to add the domain to the allowlist instead. This upgrade is required to improve the scalability of the cloud infrastructure used by the AppDynamics EUM solution. As part of a critical infrastructure upgrade, AppDynamics will be deprecating support for static IP ranges for the PDX/Oregon SaaS EUM collector on May 27th, 2022.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |