At Mercury we have been utilizing Azure DevOps for our CI/CD process and have seen the implementation of Pipelines change and continuously improve. In this series I’ll be walking through setting up an end to end pipeline using multi-stage pipelines in YAML
What We're Writing
Having 4, 6, 12, or even more accounts with individual invoices, billing methods, support contracts, reserved instance pools, and everything else that comes along would be enough to drive anyone crazy. Luckily, AWS offers a great solution that is easy to set up and manage.
Recovering from a production site outage during peak hours can be a daunting task. While everyone wants a 100% uptime, it can be near impossible because of things out of our hands. However, we can plan for these potential outages and architect the application and infrastructure to allow for a quick recovery.
In the second installment of our multi-part post on using multiple AWS accounts in your organization we’re going deeper into the technical side of creating cross-account roles for IAM authentication.
Considered to be best practices in AWS, as well as one of the most popular ways to fully maximize the potential of AWS, is to utilize multiple accounts. Accounts can be set up as either per-organization, per-department, or even per-application and can be utilized to logically and physically separate any resources to fit your organization’s needs. This, combined with master-account billing and properly utilizing Tags, can allow you to be as separate, yet collected, as you see fit.
Feature flags are a powerful tool with many uses, they should be thoughtfully considered as a development tool. Feature Flags allow developers to achieve continuous deployment and clients see great value in the speed at which issues can be resolved.