Validate policy effectiveness

Validate the effectiveness of the policy by creating an EC2 instance with a volume type of io1

  1. Click on the name of the currently logged-in user.

    • Click Sign out.

  2. Click Log back in

CostGovernance

  1. At IAM user name enter the user we created (testuser).
    • At Password enter the password we have set up (Testuser123).
    • Click Sign in.

CostGovernance

If you failed to log in, please check the user and password information created in the previous steps. Also, make sure you use the correct AWS account ID when logging in.

  1. Click the search box, and click EC2 to go to the management interface of the EC2 service.

  2. Click Launch instance, then click Launch instance.

CostGovernance

  1. At Name enter testserver

CostGovernance

  1. Scroll down, click on instance type t2.micro.

CostGovernance

  1. In the search box, enter t3.
    • Click to select instance type t3.nano.

CostGovernance

  1. At Key pair name, click in the Select box.
    • Select **Proceed without a key pair (Not recommended)

CostGovernance

We will need key pair to be able to make a connection to the EC2 instance. In this lab, we just want to check the service permissions so we won’t need to connect to the EC2 instance.

  1. Scroll down to Configure storage.
    • Click Add new volume.

CostGovernance

  1. Click gp3.
    • Click Provisioned IOPS SSD (io1) to change the volume type to io1.
    • Click Launch instance.

CostGovernance

  1. We will see that launching an instance with volume type io1 will fail. CostGovernance

Try creating a server with volume type gp3

  1. Click Edit instance config.

CostGovernance

  1. Scroll down, click io1.
    • Click General purpose SSD(gp3) to convert the volume type to gp3.
    • Click Launch instance.

CostGovernance

  1. So we have successfully created EC2 instance with instance type t3.nano and volume type gp3.

CostGovernance

Delete the created testserver

  1. Click View all instances.

CostGovernance

  1. At the list of EC2 instances.

    • Click to select testserver.

  2. Click Instance state.

    • Click Terminate instance to proceed to delete the virtual server testserver.
    • Click Terminate to confirm.

  3. Make sure you delete the instance successfully, avoiding unexpected costs.

CostGovernance

In this step, we have successfully created 1 EC2 instance with instance type of t3.nano and volume type of gp3 (forbid users from creating volume type of io1). The next step is to clean up resources.