Closed
Bug 1445609
Opened 6 years ago
Closed 5 years ago
Planned AWS Maintenance for VPN and EC2 Instance
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Infrastructure & Operations Graveyard
CIDuty
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dlabici, Unassigned)
Details
Based on the Scheduled Changes inside AWS Dashboard we will have 3 planned maintenances, listed below: VPN ======= Region: us-east-1 Service: vpn-f6709d9f // vpn-c149afa8 Maintenance window: (Start) March 22, 2018 at 10:01:00 AM UTC+2 (End) March 22, 2018 at 2:01:00 PM UTC+2 Region: us-west-2 Service: vpn-8cd57592 Maintenance window: (Start) March 16, 2018 at 10:01:00 AM UTC+2 (End) March 16, 2018 at 2:01:00 PM UTC+2 EC2 ======= Region: us-east-1 Machine: i-0dc6a56a Maintenance window: (Start) March 26, 2018 at 3:00:00 AM UTC+3 (End) March 26, 2018 at 5:00:00 AM UTC+3
Comment 1•6 years ago
|
||
Adding the following VPN maintenances to all of the above: vpn-f6709d9f vpn-c149afa8 (Start)March 22, 2018 at 4:01 AM EDT (End) March 22, 2018 at 8:01 AM EDT
Comment 2•6 years ago
|
||
Adding the following VPN maintenances to all of the above: vpn-a16a87c8 (Start) April 5, 2018 at 4:01 AM EDT (End) April 5, 2018 at 8:01 AM EDT
Comment 3•6 years ago
|
||
Adding other 3 new planned maintenances: EC2 ===== Region: us-east-1 Service: i-c080592f Maintenance window: April 19, for 2 hours starting at 2018-04-19 02:00:00 UTC UTC Region: us-east-1 Service: i-2bcf189d Maintenance window: April 19, for 2 hours starting at 2018-04-19 14:00:00 UTC UTC VPN ===== Region: us-west-2 Service: vpn-5e8a2940 Maintenance window: (Start) April 20, 2018 at 1:01 AM EDT (End) April 20, 2018 at 7:01 AM EDT
Reporter | ||
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Comment 4•6 years ago
|
||
Adding the following EC2 maintenances in the us-west-2 region: Event: i-51edb55d Availability Zone us-west-2a Event type system-reboot Event status Scheduled Description Scheduled reboot Start time May 18, 2018 at 6:01:00 PM UTC+3 End time May 18, 2018 at 8:01:00 PM UTC+3 Event: i-0ef3ab02 Availability Zone us-west-2a Event type system-reboot Event status Scheduled Description Scheduled reboot Start time May 18, 2018 at 9:16:00 PM UTC+3 End time May 18, 2018 at 11:16:00 PM UTC+3
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•6 years ago
|
Product: Release Engineering → Infrastructure & Operations
Comment 5•6 years ago
|
||
Adding the following VPN endpoint maintenances in us-west-2 region: Between May 24, 2018 at 4:01 AM EDT and May 24, 2018 at 9:01 AM EDT, there will be 5 hours of maintenance on the Amazon VPN endpoint with the IP address: 205.251.233.122. vpn-5e8a2940 vpn-0525f61b
Comment 6•6 years ago
|
||
Adding the following VPN connection scheduled for planned maintenance in the us-east-1 region: (Start) May 27, 2018 at 11:01 PM EDT (End) May 28, 2018 at 3:01 AM EDT VPN Connections: vpn-f6709d9f vpn-a16a87c8
Updated•6 years ago
|
Status: REOPENED → RESOLVED
Closed: 6 years ago → 6 years ago
Resolution: --- → FIXED
Comment 7•6 years ago
|
||
Adding the following EC2 instances which is scheduled for maintenance on 2018-07-27 for 2 hours starting at 2018-07-27 22:00:00 UTC. During this time, the following instances in the us-west-2 region will be unavailable and then rebooted: i-41f3ab4d
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 8•6 years ago
|
||
Adding the following EC2 instances which is scheduled for maintenance on 2018-08-01 for 2 hours starting at 2018-08-01 08:00:00 UTC. During this time, the following instances in the us-west-2 region will be unavailable and then rebooted: i-bcaf7653
Comment 9•6 years ago
|
||
Adding the following EC2 instances which is scheduled for maintenance on 2018-08-01 for 2 hours starting at 2018-08-01 12:00:00 UTC. During this time, the following instances in the us-west-1 region will be unavailable and then rebooted: i-128a647c
Comment 10•6 years ago
|
||
The following EC2 instances which is scheduled for maintenance on 2018-08-02 for 2 hours starting at 2018-08-02 18:00:00 UTC. During this time, the following instances in the us-east-1 region will be unavailable and then rebooted: i-1a456087
Comment 11•6 years ago
|
||
One or more of your Amazon EC2 instances is scheduled for maintenance on 2018-08-27 for 2 hours starting at 2018-08-27 10:00:00 UTC. During this time, the instances associated with this event in the us-west-2 region will be unavailable and then rebooted. i-c1e3bbcd
Comment 12•6 years ago
|
||
For the date 2018-08-29 there will be two scheduled maintenances : region : us-east-1 instance : i-a1a67f4e Status : Upcoming Start time August 29, 2018 at 1:00:00 PM UTC+3 End time August 29, 2018 at 3:00:00 PM UTC+3 --------------------------------------- region : us-west-2 instance : i-2a0619f2 Status : Upcoming Start time August 29, 2018 at 5:00:00 PM UTC+3 End time August 29, 2018 at 7:00:00 PM UTC+3
Comment 13•6 years ago
|
||
For the date 2018-08-30 there will be a scheduled maintenance : region : us-east-1 instance : i-dbec6934 Status : Upcoming Start time August 30, 2018 at 3:00:00 PM UTC+3 End time August 30, 2018 at 5:00:00 PM UTC+3
Comment 14•6 years ago
|
||
For the date 2018-08-30 there will be a planned vpn maintenance : region : us-west-1 service : vpn-41045a04 // vpn-34164871 // vpn-b6cb99f3 Status : Upcoming Start time August 30, 2018 at 12:01:00 PM UTC+3 End time August 30, 2018 at 4:01:00 PM UTC+3
Comment 15•6 years ago
|
||
For the date 2018-09-13 there will be a planned vpn maintenance : region : us-west-2 service : vpn-8cd57592 Status : Upcoming Start time September 13, 2018 at 12:01:00 PM UTC+3 End time September 13, 2018 at 4:01:00 PM UTC+3
Comment 16•5 years ago
|
||
this bug was for tracking aws maintenance on ec2 and vpn. Currently, this isn't tracked any longer and I think the bug can be closed. If it will be needed in the future, we will re-open it.
Status: REOPENED → RESOLVED
Closed: 6 years ago → 5 years ago
Resolution: --- → FIXED
Updated•4 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•