Pre-Deployment Steps - Standardized Architecture for PCI DSS on the AWS Cloud

Pre-Deployment Steps

Before you deploy the PCI DSS Quick Start templates, follow the instructions in this section to confirm that your account is set up correctly:

  • Review the service quotas and service usage of your AWS account and request increases if required, to ensure that there is available capacity to launch resources in your account.

  • Ensure that your AWS account is set up with at least one SSH key pair (but preferably two separate key pairs) in the AWS Region where you plan to deploy, for use with the bastion login host and other Amazon EC2 hosts.

  • Ensure that you have manually set up AWS Config in the AWS Config console, if you are deploying into an AWS Region where AWS Config is available. AWS Config is currently available only in the Regions listed on the endpoints and quotas webpage.

Review AWS Service Quotas

To review and (if necessary) increase service quotas for the resources you need for the PCI Quick Start deployment, you use the Service Quotas console and the Amazon EC2 console. You’ll need the resources specified in the Technical Requirements table.

Use the Service Quotas console to view the existing service quotas for Amazon VPC, IAM groups, and IAM roles within your account, and ensure that there is availability to deploy additional resources:

  1. Open the Service Quotas console at!/.

  2. In the navigation pane, choose AWS services.

  3. On the AWS services page, scroll through the list of services until you find the service that you want to check, and then choose that service.

  4. Scroll through the service quota names and compare the AWS default quota value column to the Applied quota value column, to ensure that you can allocate the following without exceeding the default quota in the AWS Region you will deploy this Quick Start into (US East (N. Virginia) Region is recommended):

    • Two (2) more VPCs

    • Six (6) more IAM groups

    • Five (5) more IAM roles

      If an increase is needed, you can choose the quota name, and then choose Request quota increase to open the Request quota increase form.

Create Amazon EC2 Key Pairs

Make sure that at least one Amazon EC2 key pair exists within your AWS account in the Region you are planning to deploy the Quick Start in.

  1. Open the Amazon EC2 console at

  2. Use the Region selector in the navigation bar to choose the AWS Region where you plan to deploy.

  3. In the navigation pane, under Network & Security, choose Key Pairs.

  4. In the key pair list, verify that at least one available key pair (but preferably two available key pairs) exist and make note of the key pair name or names. You’ll need to provide a key pair name for the parameters pEC2KeyPairBastion (for bastion host login access) and pEC2KeyPair (for all other Amazon EC2 host login access) when you launch the Quick Start. Although you can use the same key pair for both parameters, we recommend that you use a different key pair for each.

    If you want to create a new key pair, choose Create Key Pair. For additional information, see the Amazon EC2 documentation.


Creating a key pair

    Figure 6: Creating a key pair


If you’re deploying the Quick Start for testing or proof of concept, we recommend that you create a new key pair instead of specifying a key pair that’s already being used by a production instance.

Set up AWS Config

If AWS Config has not yet been initialized in the Region where you are deploying this Quick Start, follow the steps below in the Region where you are planning to deploy the Quick Start.

  1. Open the AWS Config console at

  2. Use the Region selector in the navigation bar to choose the AWS Region where you plan to deploy.

  3. In the AWS Config console, choose Get Started (or Get Started Now).

    Figure 7: AWS Config console

  4. On the Set up AWS Config screen, you may leave all default values in place, or make modifications as you see fit, and then choose Continue.

    Figure 8: AWS Config setup screen

  5. On the next screen, you are prompted to select rules for AWS Config. The centralized logging template deploys rules for your environment and you can add more rules, or remove rules, as you see fit. Choose Skip to proceed.

    Figure 9: Skip AWS Config rules selection

  6. On the Review screen, you review settings and confirm setup of AWS Config. To finish setup, choose Confirm.