Your AWS account ID and its alias

By Ashwin Venugopal -

 




Find Your AWS Account ID

The following methods might help you in this:
  • Finding your account ID using the console- You can select Support and then Support Center (in the navigation bar) where your currently signed-in 12 digit account number appears in the navigation pane.

  • Finding your account ID using the AWS CLI- The command aws sts get-caller-identity can be used to view your user ID, account ID, and user ARN.

  • Finding your account ID using the API- The API GetCallerIdentity can help in viewing the of your user ID, account ID, and user ARN. 

About Account Aliases

An account alias can be easily created if you want to change the sign-in page's URL (which is by default AWS account ID),  into your company's name or any other friendly identifier. As you can see, your sign-in page URL looks like this👇by default:

https://Your_Account_ID.signin.aws.amazon.com/console/

And if you want to create an AWS account alias, then, your sign-in page URL may look like the following example:

https:// Your_Account_Alias.signin.aws.amazon.com/console/

However, your original URL will also remain active and can be used even after creating your AWS account alias.

Note: Don't use your web browser's "bookmark this page feature" , instead type the sign-in URL manually in the bookmark entry in order to create a bookmark for your account sign-in page.

Creating, Deleting, & Listing an AWS Account Alias

The AWS Management console, the IAM API, or the command line interface can help in creating as well as deleting of your AWS account alias.

Consideration
  1. AWS account can have only one alias because any new alias will tend to overwrite the previous alias and its connected URL will also stop working.
  2. The account alias should be unique across all the Amazon Web Services products containing only digits, lower case letters, and hyphens.

Creating, Editing, & Deleting Aliases (console)

  1. First of all, you have to sign-in to the AWS Management Console and open the IAM console at https://console.aws.amazon,com/iam/.
  2. Now, select Dashboard on the navigation pane.
  3. Look for the Account Alias and choose Create in the AWS Account section. Choose Edit for an already created alias.
  4. After typing the desired name, you can select Save Changes.
  5. You can also select Delete near the Account Alias in order to remove the alias and the sign-in URL will automatically revert to using your AWS account ID.

Creating. Deleting, & Listing Aliases (AWS CLI)

  1. To create an alias for your AWS Management Console sign-in page URL, you can run aws iam create-account-alias command.
  2. The AWS account ID alias can be deleted by running the aws iam delete-account-alias command.
  3. The alias can be displayed by running aws iam list-account-aliases command.

Creating, Deleting, & Listing Aliases (AWS API)

  1. The alias can be easily created by calling the CreateAccountAlias operation.
  2. Similarly, the alias can be simply deleted by calling the DeleteAccountAlias operation.
  3. The alias ca be displayed by calling the ListAccountAliases operation.

















































Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning...
Read more