 The service catalog introduced in OpenShift 3.6 has been expanded through a partnership with Amazon. Now the service catalog offers the ability to directly provision native AWS services and then easily use them with your OpenShift applications. End users interact with a series of simple dialogues to configure the options for the service being provisioned. Ultimately, service credentials are stored as OpenShift Secrets in the same project as the deployed service. Multiple services, as well as multiple instances of the same type of service, may be deployed into the same OpenShift project. Amazon has provided different service plans for its services, which enable and disable different service options such as high availability. Service Secrets store both endpoint connection information as well as access credentials. Here, we quickly deploy a complex multi-component microservices application from a single CLI input. The inventory microservice requires both a database and a message topic to function properly, and the front end is gracefully failing. We can easily inject access credentials from the secret into an application with just a few clicks. As credential information is injected, OpenShift automatically takes care of restarting the application instance so that this information becomes available. Credentials can be injected both as standard system environment variables or have their contents injected as a file inside of the container. Now that the credentials are available, the inventory microservice becomes available itself. The application can now store its data in Amazon RDS and send notifications via Amazon SNS.