After you create IAM users and passwords for each, users can sign in to the AWS Management Console for your AWS account with a special URL.
By default, the sign-in URL for your account includes your account ID. You can create a unique sign-in URL for your account so that the URL includes a name instead of an account ID. For more information, see Your AWS Account ID and Its Alias.
The sign-in endpoint follows this pattern:
https://<em class="replaceable"><code class=""><span class="">AWS</span>-account-<span class="">ID</span>-<span class="">or</span>-<span class="">alias</span></code></em>.signin.aws.amazon.com/console
You can find the sign-in URL for an account on the IAM console dashboard.
You can also sign in at the following endpoint and enter the account ID or alias manually, instead of it being embedded in the URL:
<a href="http://docs.aws.amazon.com/IAM/latest/UserGuide/getting-started_how-users-sign-in.html" target="_blank">https://signin.aws.amazon.com/console</a>
To create a bookmark for your account’s unique sign-in page in your web browser, you should manually enter your account’s sign-in URL in the bookmark entry. Don’t use your web browser’s “bookmark this page” feature.
IAM users in your account have access only to the AWS resources that you specify in the policy that is attached to the user or to an IAM group that the user belongs to. To work in the console, users must have permissions to perform the actions that the console performs, such as listing and creating AWS resources. For more information, see Access Management and Example Policies for Administering AWS Resources.
If your organization has an existing identity system, you might want to create a single sign-on (SSO) option that gives users access to the AWS Management Console for your account without requiring them to have an IAM user identity and without requiring them to sign in separately to your organization’s site and to AWS. For more information, see Creating a URL that Enables Federated Users to Access the AWS Management Console (Custom Federation Broker).
Logging sign-in details in CloudTrail
If you enable CloudTrail to log sign-in events to your logs, you need to be aware of how CloudTrail chooses where to log the events.
- If your users sign-in directly to a console, they are redirected to either a global or a regional sign-in endpoint, based on whether the selected service console supports regions. For example, the main console home page supports regions, so if you sign in to the following URL:
you are redirected to a regional sign-in endpoint such as
https://us-east-1.signin.aws.amazon.com, resulting in a regional CloudTrail log entry in the user’s region’s log:
On the other hand, the Amazon S3 console does not support regions, so if you sign in to the following URL1https://alias.signin.aws.amazon.com/console/s3
AWS redirects you to the global sign-in endpoint at
https://signin.aws.amazon.com, resulting in a global CloudTrail log entry.
- You can manually request a certain regional sign-in endpoint by signing in to the region-enabled main console home page using a URL syntax like the following:
AWS redirects you to the
ap-southeast-1regional sign-in endpoint and results in a regional CloudTrail log event.
For more information about CloudTrail and IAM, see Logging IAM Events with AWS CloudTrail .
If users need programmatic access to work with your account, you can create an access key pair (an access key ID and a secret access key) for each user, as described in Creating, Modifying, and Viewing Access Keys (AWS Management Console).