If your organization does not restrict inbound network traffic from Elastic Cloud towards your environment, there is no impact to you and you do not need to make any changes.
If your organization does restrict inbound network traffic and has not yet allowed the above IP addresses after our previous announcement, you will need to update any relevant IP-based rules or firewall rules in your environments to include the above IPs before October 26th. Failure to do so may result in traffic from Elastic Cloud towards your environments being blocked by your firewalls.
If you have any questions, please feel free to contact our support team (email@example.com) for guidance or assistance.
Posted Oct 19, 2023 - 15:35 UTC
This scheduled maintenance affected: AWS N. Virginia (us-east-1) (Elasticsearch connectivity: AWS us-east-1, Kibana connectivity: AWS us-east-1, APM connectivity: AWS us-east-1, App Search connectivity: AWS us-east-1, Enterprise Search connectivity: AWS us-east-1).