Name: aws-service-catalog-reference-architectures
Owner: AWS Samples
Description: AWS Service Catalog Reference Architectures
Created: 2018-03-19 16:17:54.0
Updated: 2018-05-09 22:57:36.0
Pushed: 2018-05-09 22:57:35.0
Homepage: null
Size: 9984
Language: Python
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
Copyright 2018 Amazon.com, Inc. or its affiliates. All Rights Reserved.
Licensed under the Apache License, Version 2.0 (the “License”). You may not use this file except in compliance with the License. A copy of the License is located at
http://www.apache.org/licenses/LICENSE-2.0
or in the “license” file accompanying this file. This file is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
AWS Service Catalog allows you to centrally manage these commonly deployed IT services, and helps you achieve consistent governance and meet your compliance requirements, while enabling users to quickly deploy only the approved IT services they need. For more Information on AWS Service Catalog, see documentation
Many organizations are looking for sample products that they can distribute to their IAM users for a specific use-case. The AWS Service Catalog Reference blueprints are sample products distributed via this GitHub repository that demonstrate specific use-cases around specific AWS Services. Note that these products have been tested in US-EAST-1 region.
To give you an example, the Amazon EC2 use case shows how an organization can leverage the AWS Service Catalog to provide Amazon Elastic Compute (EC2) instances and AWS Systems Manager (SSM)-based patching for testing and integration. Currently GitHub repository contains following reference blueprints:
Note - Before you distribute the CloudFormation template to your organization, review the template and ensure that it is doing what you want it to do. Check IAM permissions, Deletion policies, update stack behavior, other aspects of the template, and ensure that they are as per your expectations and processes. These sample CloudFormation templates may need updates before you can use them in production.
Each Blueprint comes with a detailed walkthrough guide that includes step-by-step instructions on how to set up the Service Catalog Blueprint.
AWS CLI configured to point to point to the region in which you want to create the reference blueprint components within AWS Service Catalog.
Access to a system with permissions to execute a python script. The script utilizes “boto3” and “random” modules.
Here is the list of commands to be executed from terminal -
Download reference blueprint
r ~/Downloads/sc-ra
/Downloads/sc-ra
clone https://github.com/aws-samples/aws-service-catalog-reference-architectures
Change to appropriate Reference blueprint directory, these instructions show how to create VPC Service Catalog product. However instructions remain identical for all reference blueprint modules.
pc
You can execute ls -l if you are using linux terminal to see files available.
l
r--r-- 1 username staff #### Mar 12 16:07 README.md
r-xr-x 1 username staff #### Mar 12 15:19 sc-vpc-ra-setup.py
r--r-- 1 username staff ##### Mar 12 16:10 sc-vpc-ra.json
r--r-- 1 username staff ##### Mar 12 16:00 sc-vpc-ra.yml
r--r-- 1 username staff ###### Mar 12 17:53 sc-vpc-ra-architecture-multi-az.png
Set execute permissions on an appropriate python setup script
d +x sc-vpc-ra-setup.py
Verify whether your CLI is configured for appropriate region. Note that the script will create an AWS Service Catalog product along with corresponding portfolio.
~/.aws/config
ault]
on = us-east-2
Execute the setup script
re you execute the script, review and revisit the parameters defined in the python script.
-vpc-ra-setup.py
Once you execute python script, an AWS Service Catalog portfolio containing reference blueprint product will be created. However, if you want to set up the portfolio manually, you can do so using AWS Service Catalog console.
Once you have set up the portfolio, you would need to grant end-users access. To know more about how to grant access, see documentation
Once access has been provided to one or more end users, the reference blueprint product can be lauched. To know more about how to launch AWS Service Catalog product, see documentation
The following AWS team members have provided guidance, code review and other assistance throughout the design of this reference blueprint.