Getting started with Application Cost Profiler
AWS Application Cost Profiler helps you get cost information about your AWS resources by reporting resource usage by tenant, rather than for the resource as a whole. A tenant can be a user, a group of users, or a project. Make sure that you can identify your resource usage by the tenant you choose. To get cost reports about tenant usage, you configure a report and send usage data to Application Cost Profiler. This section discusses the prerequisites that you must complete before you use Application Cost Profiler.
Topics
Sign up for an AWS account
If you do not have an AWS account, complete the following steps to create one.
To sign up for an AWS account
Follow the online instructions.
Part of the sign-up procedure involves receiving a phone call and entering a verification code on the phone keypad.
When you sign up for an AWS account, an AWS account root user is created. The root user has access to all AWS services and resources in the account. As a security best practice, assign administrative access to an administrative user, and use only the root user to perform tasks that require root user access.
AWS sends you a confirmation email after the sign-up process is
complete. At any time, you can view your current account activity and manage your account by
going to https://aws.amazon.com/
Create an administrative user
After you sign up for an AWS account, create an administrative user so that you don't use the root user for everyday tasks.
Secure your AWS account root user
-
Sign in to the AWS Management Console
as the account owner by choosing Root user and entering your AWS account email address. On the next page, enter your password. For help signing in by using root user, see Signing in as the root user in the AWS Sign-In User Guide.
-
Turn on multi-factor authentication (MFA) for your root user.
For instructions, see Enable a virtual MFA device for your AWS account root user (console) in the IAM User Guide.
Create an administrative user
-
For your daily administrative tasks, grant administrative access to an administrative user in AWS IAM Identity Center (successor to AWS Single Sign-On).
For instructions, see Getting started in the AWS IAM Identity Center (successor to AWS Single Sign-On) User Guide.
Sign in as the administrative user
-
To sign in with your IAM Identity Center user, use the sign-in URL that was sent to your email address when you created the IAM Identity Center user.
For help signing in using an IAM Identity Center user, see Signing in to the AWS access portal in the AWS Sign-In User Guide.
Grant programmatic access
Users need programmatic access if they want to interact with AWS outside of the AWS Management Console. The way to grant programmatic access depends on the type of user that's accessing AWS:
-
If you manage identities in IAM Identity Center, the AWS APIs require a profile, and the AWS Command Line Interface requires a profile or an environment variable.
-
If you have IAM users, the AWS APIs and the AWS Command Line Interface require access keys. Whenever possible, create temporary credentials that consist of an access key ID, a secret access key, and a security token that indicates when the credentials expire.
To grant users programmatic access, choose one of the following options.
| Which user needs programmatic access? | To | By |
|---|---|---|
|
Workforce identity (Users managed in IAM Identity Center) |
Use short-term credentials to sign programmatic requests to the AWS CLI or AWS APIs (directly or by using the AWS SDKs). |
Following the instructions for the interface that you want to use:
|
| IAM | Use short-term credentials to sign programmatic requests to the AWS CLI or AWS APIs (directly or by using the AWS SDKs). | Following the instructions in Using temporary credentials with AWS resources in the IAM User Guide. |
| IAM | Use long-term credentials to sign programmatic requests to the AWS CLI or AWS APIs
(directly or by using the AWS SDKs). (Not recommended) |
Following the instructions in Managing access keys for IAM users in the IAM User Guide. |
Application Cost Profiler specific prerequisites
Before you get started with Application Cost Profiler, you must complete the following prerequisites:
-
Enable Cost Explorer
Enable AWS Cost Explorer for your AWS account. Setting up an account with Cost Explorer can take up to 24 hours. You must complete Cost Explorer setup before Application Cost Profiler can generate your daily and monthly reports.
For more information, see Enabling Cost Explorer in the AWS Billing and Cost Management User Guide.
-
Create S3 buckets
Create at least two Amazon Simple Storage Service (Amazon S3) buckets. Application Cost Profiler uses one S3 bucket to provide reports to you. You use the other S3 bucket to upload usage data to Application Cost Profiler. Typically, you only need one S3 bucket to upload usage data. However, you might want to have more than one S3 bucket so that you can keep usage for different services in separate S3 buckets with different permissions, if needed for your security. You must give Application Cost Profiler permissions to these S3 buckets.
For more information about setting up the Amazon S3 buckets for Application Cost Profiler, see Setting up Amazon S3 buckets for Application Cost Profiler.
-
Enable tags
To report usage by tag, rather than by resource, you must enable those tags in the AWS Billing and Cost Management console.
For more information about activating AWS generated tags, see Activating the AWS-Generated Cost Allocation Tags in the AWS Billing and Cost Management User Guide. For more information about activating user-defined tags, see Activating User-Defined Cost Allocation Tags in the AWS Billing and Cost Management User Guide.
Next steps
After you complete these prerequisites, you can:
-
Configure your report and send usage data to Application Cost Profiler. For more information, see Creating your report.
-
Get and analyze your generated reports. For more information, see Using Application Cost Profiler reports.
