AWS Service Catalog customers

The main benefit of the AWS Service Catalog to Genesys is self-service. Engineers can select a product that creates a virtual machine preloaded with all the troubleshooting tools needed in a matter of minutes. When no longer needed, they can delete it and start a new one in no time. The AWS Service Catalog is an excellent service as it allows us to lock all services that we do not need and focus on the services that our engineers do need. When an engineer launches a product from the AWS Service Catalog, we use the Infrastructure as Code to build the resource; it locates the proper Amazon golden images, adds the newly created VM to the Microsoft Domain during the creation, applies all the group policies and security access to the virtual machine. After a few minutes, the EC2 is showing and ready to log on with their domain account. To create a domain account, we again utilized the AWS Service Catalog and created two products that integrate with the Microsoft Domain controller. Once selected, the engineer can type the username and password they desire, and once submitted, their account is created. These two products dropped our support case count by 93% and saved us multiple hours of unplanned work during our sprint cycles.

To save more time and effort within our environment, we also automated the shutdown of machines based on idle time as there are very rare occurrences when a test machine needs to be running 24/7. When an engineer needs to work on their test machine, they can turn it on in a matter of minutes.

Our DevOps team uses AWS Service Catalog to provision a wide range of AWS resources, including EC2 and RDS. This enables our teams to maintain and update our application stacks across multiple AWS accounts. With AWS Service Catalog AppRegistry integrated into our applications, we are also able to keep track of our Cloud resources and store valuable metadata for each application. This complements our resource tagging strategy and improves our operational teams’ efficiency. Our project teams are able to glance at Application Manager to identify which resources our applications are using and their associated costs.

We started using AWS Service Catalog AppRegistry in 2020 to register our applications and their metadata. The combined power of AWS Service Catalog and AWS Service Catalog’s tagging enforcement capabilities now helps us to track our cloud resources and their associations with different business processes. We also proudly participated in beta for Principal Name Sharing, a new capability/ feature of AWS Service Catalog. Principal Name Sharing will simplify how we distribute cloud patterns, so we look forward to using it further.

AWS Service Catalog enables Dish Networks to take a product centric approach towards how we are building on AWS instead of treating infrastructure builds as bespoke patterns. For cloud engineers and administrators, Service Catalog provides infrastructure in the form of product offerings that provide reusability, consistency, and standards enforcement.  For end users such as developers, they are empowered to provision infrastructure resources via self-service easily and at scale. By removing cloud engineering and operations teams as a bottleneck for infrastructure creation, builds that routinely took months are now completed in hours to days. AWS Service Catalog allows us to do more with less time and resources

Service Catalog helps us meet our objective to enable builders to go from concept to cloud in under 6-hours, while raising the bar on engineering rigor. We have provided a developer first methodology that allows teams to move quickly, and helps us achieve self-service governance at scale.

We implemented AWS Organizations and AWS Service Catalog to help us deploy and manage over 200 AWS accounts with ease. We have benefitted greatly by having an automated account provisioning pipeline that executes within a few minutes and produces a fully managed, compliant AWS account. We also deployed AWS CloudTrail to meet requirement for compliance and auditing and introduced AWS Config for compliance validation. With CloudTrail and AWS Config, we can adhere to BP security controls for auditing compliance.

AWS Service Catalog helps us create environments quickly by eliminating continuous manual authorizations and stabilizing our costs for future research and development. In addition, Service Catalog helps us remain compliant by putting guardrails in place, which impact what technology can be used in a self-service environment, as well as who can use the technology. As a result, we gain faster and frequent code delivery, saved costs, and the opportunity to experiment with different technologies and configurations.

Building each environment from the ground up typically took two skilled engineers two to three weeks… Using AWS Service Catalog means we can deploy a full-featured Miner environment in about 45 minutes. It’s one-click simple. Each deployment has tested and proven security and networking configurations, so engineers don’t have to worry about those things."

Our product can be tested quickly with the correct environments, but creating and starting these environments can be time consuming. And catering for changes over time can also be challenging. Therefore, our goal has been to move towards an automated process of provisioning an AWS environment and deploying software on it, using infrastructure as a code. We implemented CloudFormation and Service Catalog so that the DevOps team can automate the creation of internal AWS environments for development and testing environments. We then use CloudWatch to get a better overview of what is happening in our configurations, which is of great importance. These services have helped us find a way to innovate faster while maintaining control over our AWS infrastructure.

We use Cloud Formation and Service Catalog to automatically provision a number of resources, including Config, Systems Manager, AWS Budgets, and CloudWatch. As a result, every client we onboard is configured according to the well-architecture framework. With these services, we have found a way to achieve secure management at scale, establish end-to-end IT lifecycle management, and gain operational visibility. With CloudFormation, we can configure a set of standard templates based on best practices, which can be implemented for each client and each account. With CloudWatch and Budgets, we can easily visualize important metrics, which leads to reduced costs. We use Config and CloudWatch to continuously monitor workloads, which reduces operational overheard. We are relieved that our teams and our customers no longer have to pick between business agility and governance.

Our customers rely on Logicworks to design, build, and deploy reliable infrastructure that meets high security, availability, and performance standards. By using Service Catalog, we have been able to dramatically simplify the process of creating or replicating AWS environments, enabling our customers to offer their teams self-service options for standard configurations. By providing them with services through AWS Service Catalog, they can improve time-to-production and reduce stress on in-house IT teams with the assurance that baseline security configurations are maintained.