L1 Terminal Fault Security Patching
Scheduled Maintenance Report for Aptible
Completed
All databases in shared-tenancy environments have now been restarted.

At this point, all shared-tenancy environments have been protected against this L1 Terminal Fault vulnerability. Depending on our continued investigation into the impacts of L1TF, we may schedule additional maintenance for dedicated environments, but for now, this maintenance is complete.
Posted 6 months ago. Aug 16, 2018 - 19:30 EDT
Update
Most database containers have now been restarted on patched instances. Some containers must still be restarted; we apologize for the delay, but we expect that all containers should be restarted by 8:00pm EDT. We'll update this status page once all databases have been restarted.
Posted 6 months ago. Aug 16, 2018 - 18:53 EDT
Update
Continuing with our remediation efforts, we will be replacing all database instances in shared-tenancy stacks. In order to perform this operation, it will be necessary to restart all database containers running in shared environments. We will be completing all such restart operations between 3:00pm and 6:00pm EDT today, August 16. These operations will cause up to approximately 60 seconds of downtime for each database container running in a shared environment.
Posted 6 months ago. Aug 16, 2018 - 14:16 EDT
Update
All app containers in shared environments have now been restarted on new instances running Linux kernel versions patched against L1TF. In addition, all build and bastion instances for shared stacks have been replaced with new, patched instances
Posted 6 months ago. Aug 15, 2018 - 22:07 EDT
In progress
We've begun the process of restarting app containers on shared environments, in order to relaunch them on patched instances.
Posted 6 months ago. Aug 15, 2018 - 19:15 EDT
Scheduled
Yesterday, a new speculative execution attack affecting Intel processors was announced, named "L1 Terminal Fault" (L1TF) by Intel, and nicknamed "Foreshadow" by the security community.

In order to ensure that customer environments are protected against this vulnerability, our Reliability Team is beginning the process of re-launching customer containers and utility services (e.g., build instances, ephemeral SSH servers) on new EC2 instances that have been updated to the latest Linux kernel, which contains the Page Table Entry (PTE) Inversion mitigation against this L1TF attack.

To begin, the most vulnerable instances will be replaced — i.e., instances in shared environments where arbitrary code may be run. These include:

* App instances
* Build instances (where Docker images are built)
* Bastion instances (where ephemeral `aptible ssh` containers run)

The replacement operation should incur no downtime for your apps, but will require that we run `aptible restart` (a zero downtime operation) on each app in your shared environments.

We will continue to update this status page as we proceed with the patching process.

Here are a few relevant links to learn more about this vulnerability:
* https://foreshadowattack.eu/
* https://www.redhat.com/en/blog/understanding-l1-terminal-fault-aka-foreshadow-what-you-need-know
* https://www.kernel.org/doc/html/latest/admin-guide/l1tf.html
Posted 6 months ago. Aug 15, 2018 - 14:11 EDT