Validate policy effectiveness

Validate the effectiveness of the policy by creating an EC2 instance other than the T3 family.

  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, 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. At Key pair name, click in 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. Click Launch Instance.

CostGovernance

In this step, we tried to create 1 EC2 instance with instance type of t2.micro and this EC2 instance creation failed because we only have permission to create instances belonging to T3 family.

CostGovernance

Try creating a server with T3 family

  1. Click Edit instance config.

CostGovernance

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

CostGovernance

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

CostGovernance

  1. Check Instance type has changed to t3.micro.
    • Click Launch instance.

CostGovernance

  1. So we have successfully created EC2 instance with instance type t3.micro.

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 an EC2 instance with instance type t3.micro. In the next section, we will try to limit the creation of an instance with a specified size.