We are going to perform the following steps:
For this workshop, we are using the same account as both the hub and spoke for simplicity; in a multi-account setup, products that are created in a hub account could be provisioned in multiple spoke accounts.
Here are the steps you need to follow to “Provision the control”
Navigate to the ServiceCatalogPuppet CodeCommit repository again
Click on manifest.yaml
Append the following snippet to the end of the main input field:
Now that we have written the manifest file we are ready to commit it.
Using a good / unique commit message will help you understand what is going on later.
The YAML we pasted in the previous step told the framework to perform the following actions:
Once you have made your changes the ServiceCatalogPuppet Pipeline should have run. If you were quick may still be running. If it has not yet started feel free to the hit the Release change button.
Once it has completed it should show the Source, Generate and Deploy stages in green to indicate they have completed successfully:
If this is failing please raise your hand for some assistance
Once you have verified the pipeline has run you can go to Service Catalog provisioned products to view your provisioned product. Please note when you arrive at the provisioned product page you will need to select account from the filter by drop down in the top right:
If you cannot see your product please raise your hand for some assistance
You have now successfully provisioned a product
To see the AWS Config rule enabled, navigate to AWS Config rules. Once there you should see the following: