Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Oct 26, 2023 - 09:00 UTC
Scheduled
We previously communicated that additional egress public IP addresses were planned to be added in the Elastic Cloud AWS us-east-1 region. These IP addresses are now deployed and active.
Starting on October 26th, we will begin to shift larger portions of network traffic to use these new egress public IP addresses.
What's Changing?
Starting on October 26th, we will begin sending network traffic from the Elastic Cloud AWS us-east-1 region towards the public internet through this full list of outbound IP addresses:
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 (support@elastic.co) 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).