We released new features for our dashboard "Orbiter". The Orbiter now offers the possibilty to list all existing snapshots of a database instance. Further the public ip address of the bastion host is shown in the Orbiter.
By clicking the snapshots button all snapshots will be displayed in a separeted pop-up.
The pop-up shows all available snapshots with additional information about them, including the important time of creation. By clicking the relevant snapshot identifier a new view will be displayed.
This view provides the ability to copy the restore command for the specific snapshot. This command has to be run on the bastion host to create a new database beside the exisiting to access the restored data.
The Orbiter now shows the public ip address of the bastion host. There is a link to our knowledge base, which discribes how to connect via ssh to the environment, too.
With the release of Tideways 5, our customers now have the opportunity to use the new features of Tideways 5 to monitor the performance of their applications and to debug them on their server.
Tideways 5 now offers a more detailed view of the metrics:
Analyse traces to find long lasting querys and which component is involved:
If you already use Tideways and would like to upgrade to version 5, then you can contact our support and upgrade them.
For questions about Tideways, please contact our customer service at https://support.root360.cloud
Find more information about Tideways 5 on https://tideways.com/profiler/...
capturing more data in monitoring mode
always capture the total performance of SQL, HTTP, Redis, Memcache, File I/O and other downstream services for monitoring purposes
simpler and better transaction naming
As we rolled out our cloud management CLI suite 'r3'  almost a year ago, we are deprecating the old legacy commands for deploying customer code into our infrastructure.
This affects the following commands:
Starting today those commands will deploy the code and always return code 250 and a deprecation message when the deploy was successful.
You should switch to the r3-command to deploy your code  by 27th September 2018. After this date the mentioned commands will be removed.
root360 Cloud Management CLI Suite r3
Default Deployment: How deployment via CLI is working
Docker (ECS) Deployment: root360 Container Platform Deployment
Due to a security patch the deploy script deploy.py is deprecated since today. Please check your deployment processes.
In the night between 1:39 AM UTC and 1:49 AM UTC AWS experienced network connectivity issues for some instances in a single Availability Zone in the EU-CENTRAL-1 Region. This may have affected your availability during this period.
We have reviewed the components and do not see any malfunction of currently running instances. The issues has been resolved by AWS at 2:34 AM UTC officially.
If you have further issues which may be related to this outage, please get back to us at https://support.root360.cloud/
11:04 fixed time in post
Currently we have no possibility to receive and send messages via email@example.com and our ticket system. We are already in contact with the provider of our ticket system. We apologize for this circumstance and keep you up to date.
14:15 - problems are resolved
We've updated the root360 Dashboard with new features that allow our customers to get even more information about their environments. See our new features below.
We now offer our customers 14 days to look back in their metric graphs.
We have now given our customers the opportunity to see triggered CloudWatch alerts in the orbiter.
Our customers now see the set alarm thresholds in the graph and when they have been exceeded.
Always well informed on the way. Our dashboard now has a responsive design, allowing our customers to keep track of their environment from any device.
Get in touch with our root360 Dashboard at https://my.root360.cloud/dashb...
If your not registered yet, please contact us at https://support.root360.cloud
extension of the time period from max. 6 hours to max. 14 days backwards
added alarm threshold to graphs
see alarms for every single service
To increase security for our customers, we have increased security for SSH connections by disabling weak encryption, key exchange protocols, and MAC algorithms.
AWS has announced that as of August 1, 2018, support for the MySQL minor engine versions 5.6.27 and 5.6.29 will be discontinued.
Beginning on July 25, 2018 at 0:00 UTC, all RDS DB instances running MySQL 5.6.27 or 5.6.29 will be automatically upgraded to the latest minor version during the next maintenance window specified for each instance. Any instances still running one of these versions on August 1, 2018 at 0:00 UTC will be upgraded immediately. Once this completes, any instance restored from a snapshot of the deprecated version will automatically and immediately be upgraded to a currently supported version.
We will contact the relevant customers and, if necessary, schedule maintenance together. During maintenance, downtime can be expected.
We noticed some DNS problems occurring while accessing some websites. The problems aren't located at AWS only.
We will keep you updated.
15:00 AWS also confirmed DNS resolution errors using third party DNS resolvers 184.108.40.206 / 220.127.116.11
15:30 AWS resolved the issues
In order to prevent outage and security alerts caused by a penetration or vulnerability test, we require to announce this kind of automated test 3 business days before. We will also forward this information to AWS to ensure no actions will be taken during the test. Please note that only tests are allowed which are compliant to the AWS acceptable use policy and AWS penetration tests rules.
See our form https://root360.atlassian.net/...
Currently the npm installation fails on our environments due to an internal npm failure. We are working on a patch right now.
14:30 The patch for the broken npm was now rolled out in our environments, which fixes the npm installation issues.
We've noticed an increased amount of errors in deployments that use Bitbucket.org.
We are in contact with Bitbucket.org to locate the cause.
We'll keep you posted here.
11:30 Our tests show that the regions Ireland and USA are not affected by this issue.
13:00 Bitbucket confirmed an issue of the connection between there data centers causing this issue
see https://status.bitbucket.org/ for current status on Bitbuckets side
13:45 Bitbucket found the cause with their network vendor and are working to solve it
17:00 issue was solved by Bitbucket and there network vendor; our tests confirm that the issue is solved
The newly discovered ability to exploit publicly available memcaches for DDoS attacks is now even easier with ready-made tools. Nevertheless, it is not possible to misuse memcaches used in Root360 infrastructures because they are securely located in the application network and are not publicly accessible. Further information can be found in our Quickstart.
Between 23:41 CET and 23:56 CET some EC2 instances experienced elevated DNS resolution errors in the EU-CENTRAL-1 and EU-WEST-1 Region. As a result of this, some AWS services experienced elevated errors and increased latency. The issue has been resolved and the service is operating normally.