AWS is enabling teams to address application weaknesses with the introduction of the AWS Fault Injection Simulator at is virtual AWS re:Invent 2020 conference this week. The simulator is a chaos engineering tool expected to be generally available in 2021.

According to the company, the new offering will come packed with pre-built templates for creating the desired disruptions whether that’s for server latency or database errors. It also contains controls and guardrails such as automatically rolling back or stopping the experiment if certain conditions are met. Then teams can quickly roll back to the pre-experiment state.

Teams will also have access to a range of fine-grained controls during the experiments to gradually or simultaneously impair how different resources perform in a production environment as it is scaled up, according to AWS in a post.

“With a few clicks in the console, teams can run complex scenarios with common distributed system failures happening in parallel or building sequentially over time, enabling them to create the real world conditions necessary to find hidden weaknesses,” AWS explained on its website.

AWS explained the new offering will be especially useful for simulating game days by creating the high-traffic conditions, a new launch or for integration right into continuous delivery pipelines so that teams can repeatedly test the impact of faults in the SDLC.

Fault Injection Simulator can be used to generate tests in many AWS services such as AWS services, such as Amazon EC2, Amazon EKS, Amazon ECS, and Amazon RDS.

At GitLab, we are focused on improving developer productivity and satisfaction. And GitLab 13.6 has all the right ingredients to help you achieve all that and more! We hope that you find these top features, and the 60+ new features and improvements packed in this release, useful.

Improved ease of use and automation for efficiency
To make it easy for you to get started with GitLab CI/CD with Amazon Web Services (AWS), Auto DevOps has now been extended to support AWS, so you can now Auto-Deploy to Amazon EC2 using Auto DevOps without using Kubernetes (as previously required by Auto DevOps).

Docker Hub has enforced rate limits on docker pull requests. We have mitigated the impact for our SaaS and self-hosted users and have shared ways to monitor the limits with Prometheus in your environments. We want all our users to stay safe with their CI/CD pipelines and Kubernetes clusters. We are moving the Dependency Proxy to Core available for everyone.

Listening to the community’s feedback to have a more descriptive default branch, Group owners now have more flexibility in configuring a custom default initial branch name for new repositories as opposed to the master branch. Speaking of defaults, the Static Site Editor can use a default merge request template across a project, reducing the need to navigate to the merge request after submission to update the description.

Improved visibility for faster decision making
You cannot fix what you cannot find. With 13.6, we’ve made improvements to several dashboards and reports to aid you with faster decision making.

With the code quality severity included within the merge request and the Full Code Quality Report, you can now quickly determine which code quality violations are critical to resolve before merging. Thanks for the community contribution with Code Quality Report, Vicken Simonian!

We’ve made updates to the Project Security Dashboard to include the results of the latest run pipeline security scan and also a dynamic vulnerability trend chart to help you stay on top of the real time and historical vulnerability trends. We’ve also added the fuzz testing results in the merge request along with the other security results and improved the readability of this report by adding the source file name and line number to help you quickly find the exact crash location and fix it.

GitLab Self Managed Administrators can now see their organization’s usage trends for popular features such as users, projects, groups, issues, and pipelines over the last 12 months.

Improved extensibility for a seamless workflow
We aim to play well with other popular tools you may be using in your environment so that you have a seamless experience, even when you use only a few parts of GitLab. With 13.6, to enable easy access and collaboration from within VS Code, we’ve improved our extension with VS Code to insert Snippets, view and comment on merge requests and issues directly from VS Code rather than switching to the GitLab interface.

GitLab integrations can now be configured at a group level in addition to instance and project level – helping group owners manage integrations with ease.To enable you to grow beyond the 10GB per project storage limit, we recently introduced an add-on to purchase additional storage for your group or personal name space. In addition to Dependency Proxy, we’ve also moved Tracing to Core as part of this release.

These are just a few highlights from the many new features and performance improvements described below. If you’d like to preview what’s coming in next month’s release, check out our Upcoming Releases page as well as our 13.7 release kick off video series where the Product Managers highlight key features coming in the next release.