The AWS Management Console is a browser-based graphical interface for accessing and managing AWS services. It exposes most AWS API functionality without requiring you to write API requests. The AWS CLI, SDKs, and infrastructure blueprints provide other ways to work with AWS. section 1.7.1 section 1.8.2 section 1.7
The console is a practical starting point for exploring services and setting up development or test infrastructure. Sign in at https://console.aws.amazon.com after creating an AWS account. The illustrated first sign-in uses Root User, the account email address, and its password. section 1.7.1 section 1.8.1 section 1.8.2
Use the top navigation bar to find your way around:
- Open Services or Search to find a service; use the AWS dashboard for an account overview. section 1.8.2
- Check Region before creating resources. The examples here use N. Virginia (us-east-1) unless stated otherwise. section 1.8.2 section 2.1
- Use Notifications for AWS alerts, Help for support, Account for account management, and Terminal for browser-based access to cloud resources. section 1.8.2
The navigation-bar figure locates the service search, region selector, and account controls used in console tasks. section 1.8.2
Create a WordPress proof of concept
Select N. Virginia, open CloudFormation through Services or Search, and choose Create Stack → With New Resources (Standard). Supply the prepared S3 template URL, name the stack wordpress, and set a unique WordpressAdminPassword. CloudFormation then creates the load balancer, database, filesystem, firewall rules, and web servers specified by the template; the console is the entry point, not a replacement for the template. section 2.1
Watch costs while experimenting: enable Free Tier usage alerts in billing preferences, then find Budgets through the console search and create a monthly cost budget with email alerts for actual and forecasted spending. An alert notifies you when its threshold is reached; it is not described as stopping resources. For another hands-on task, the console can create a Lambda website health check manually before moving to automated deployment. section 1.9 section 6.2
