Skip to content

Latest commit

 

History

History
 
 

ec2

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
README.md
README.md
 
 
sc-ec2-linux-apache-nokey.json
sc-ec2-linux-apache-nokey.json
 
 
sc-ec2-linux-apache-simple.json
sc-ec2-linux-apache-simple.json
 
 
sc-ec2-linux-nginx-nokey.json
sc-ec2-linux-nginx-nokey.json
 
 
sc-ec2-linux-nginx-simple.json
sc-ec2-linux-nginx-simple.json
 
 
sc-ec2-linux-ra.json
sc-ec2-linux-ra.json
 
 
sc-ec2-ra-architecture.png
sc-ec2-ra-architecture.png
 
 
sc-ec2-windows-ra.json
sc-ec2-windows-ra.json
 
 
sc-portfolio-ec2.json
sc-portfolio-ec2.json
 
 
sc-portfolio-ec2VPC.json
sc-portfolio-ec2VPC.json
 
 
sc-portfolio-ec2demo.json
sc-portfolio-ec2demo.json
 
 
sc-product-ec2-demowebserver.json
sc-product-ec2-demowebserver.json
 
 
sc-product-ec2-linux.json
sc-product-ec2-linux.json
 
 
sc-product-ec2-webserver.json
sc-product-ec2-webserver.json
 
 
sc-product-ec2-windows.json
sc-product-ec2-windows.json
 
 
sc-tagoptions.json
sc-tagoptions.json
 
 

README.md

AWS Service Catalog EC2 Reference architecture

This reference architecture creates an AWS Service Catalog Portfolio called "Service Catalog EC2 Reference Architecture" with associated products. The AWS Service Catalog Product references cloudformation templates for the Amazon EC2 Linux and Windows instances which can be lauched by end users through AWS Service Catalog. The AWS Service Catalog EC2 product creates either an Aamzon Linux or Microsoft Windows EC2 instance in the VPC and Subnets selected by the end user. A Amazon Simple Systems Manager patch baseline, maintenance window and task are created to allow for automated patching of the Aamzon Linux and Microsoft Windows operating systems. The Portfolio also includes a Linux webserver Product with either Apache or NGINX versions.

Install

Launch the EC2 portfolio stack:
CreateStack
* If you have already run the VPC template, then you will put the output.LaunchRoleName from the completed LaunchConstraintRole stack in the LaunchRoleName field (default is SCEC2LaunchRole).

Install from your own S3 bucket

  1. clone this git repo:
    git clone [email protected]:aws-samples/aws-service-catalog-reference-architectures.git
  2. Copy everything in the repo to an S3 bucket:
    cd aws-service-catalog-reference-architectures
    aws s3 cp . s3://[YOUR-BUCKET-NAME-HERE] --exclude "*" --include "*.json" --include "*.yml" --recursive
  3. In the AWS CloudFormation console choose "Create Stack" and supply the Portfolio S3 url:
    https://s3.amazonaws.com/[YOUR-BUCKET-NAME-HERE]/ec2/sc-portfolio-ec2.json
  4. If this is the first portfolio you are creating, then leave LaunchRoleName blank to allow CloudFormation to create the launchconstraint role for you.
    • If you have already run the VPC template, then you will put the output.LaunchRoleName from the completed LaunchConstraintRole stack in the LaunchRoleName field (default is SCEC2LaunchRole).
  5. Set the LinkedRole1 and LinkedRole2 parameters to any additional end user roles you may want to link to the Portfolio.
  6. Set the CreateEndUsers parameter to No if you have already run a Portfolio stack from this repo (ServiceCatalogEndusers already exists).
  7. Change the RepoRootURL parameter to your bucket's root url:
    https://s3.amazonaws.com/[YOUR-BUCKET-NAME-HERE]/

EC2 Architecture with Amazon Linux and Microsoft Windows instances

sc-ec2-ra-architecture.png