Hi, welcome to this Azure cost management video which focuses
on setting up connector for AWS. Setting up connector for AWS
allows you to monitor and control your Azure in AWS spend
together in Azure cost management. The complete setup
is done in a few quick steps which include creating the cost
in usage report, setting up the role and policy which provides
Azure cost management with access as well as permissions.
Providing organization API access in cost Explorer, API
access and finally setting up the connection in Azure Cost
Management. First, we'll start by setting up AWS cost and
usage report. First, sign into the EWS management console and
open the billing and cost management console, which can be
found by searching billing in the field and services bar.
Once in the billing and cost management dashboard, click on
the cost and usage reports on the left in the Navigation Pane.
Click on the create report
button. Fill in the desired
report name. Take note of this name as it is needed when
configuring the connection in Azure Cost Management. Check the
box under additional report details and ensure the boxes
checked under data refresh
settings. Click the next button.
The next screen covers delivery options. Start with configuring
the S3 bucket by clicking on configure. In the popup screen
there are two steps. Step one, either choose from an already
existing bucket or create a new S3 bucket. Copy and remember the
bucket name as it will be important when setting up policy
and permissions later in Azure Cost Management. I'm selecting an
already existing S3 bucket. However the process to create a
new bucket is straightforward.
Back in the delivery options page, type the
report path prefix that you want to be added to
the name of your report.
Choose hourly for time granularity. Choose create new
report version under report versioning. If you wish, you can
enable report data integration for Amazon's other products. For
compression, select GZIP, select next, review the content and
update any selections needed. Click review and complete.
Now that we created our Cost and Usage Report or CUR,
Let's setup role in policy, to provide Azure cost
management with access permissions to collect the CUR
CSV files from the S3 bucket. We will also need the
organization API access to get the account names in cost
Explorer. API access to enrich the cost data. We will
set up the new role in policy, using the new search
wizard in services. Search you're not already signed
into your AWS console do so now and select services from
the top left of the page.
And click into it on the left side of the Navigation
Pane, select rolls.
Click it and select create rolls, select another AWS
account button which is the 2nd selection in the top. In account
ID. Enter 432263259397. Make sure to enter in the number
exactly as this is Azure Cost Management account ID and is
necessary for your account to be linked in Azure Cost Management.
Under options, click the box Require external ID.
In external ID enter an external ID which is a shared passcode
between the AWS roll, and Azure Cost Management, the same
external ID is also used in the new connector page and cost
management. The external ID should be a strong password
including uppercase, lowercase letters, numbers and symbols.
Do not change the selection for required MFA, it
should remain cleared. Click next permissions.
On this page, click create policy at the top of the page, a
new browser tab will open where you can start creating a new
policy. Here, let's set up the policy in the visual editor
tab, click choose a service. Type cost and usage report and
you'll be able to click into it under access level in read,
select, describe report definitions, then go down and
click add additional permissions. Again. select
choose services here select type in S3, Click S3 under
access level, click the carrot for lists and select list
bucket.
Next, click the carrot for read.
Quick get object.
Next, under resources, click the carrot and you will be given the
option to add ARN under bucket. Click on that and here we will
put in the name of the S3 bucket used to undermine.
Then click add.
Next, under object click add ARN
again. Here, add the bucket name and under object name add any.
Click add, click add additional permissions. Next we're going to
configure cost Explorer
permissions. Click in to Choose a Service again. Start typing
cost Explorer Services.
You click into it once. It shows up under manual actions, select
All Cost Explorer Service
actions. Next, we're adding organization permissions again.
Click, choose a service. Start
typing organization. Click into it when it shows up here, select
access level, lists,
List accounts. Next, click Review
Policy. On the review policy page name the new policy.
Add a description if needed and check to make sure you entered
the correct information. Then click create policy.
Go back to the previous tab.
And refresh the page.
Click Next permissions.
And search for your policy.
Select the policy.
Click next tax, add any tags needed and Click Review. Name
your new role.
Add a description if needed, ensure the account number is
correct. The correct policy is added and click create role.
We are now ready to connect AWS in Azure Cost Management,
navigate to cost management and
billing. Cost management.
And click on connector for AWS which at the time of this
recording is under preview.
Click the ad at the top of the page to create a new connector
on the create in AWS connector page, type a display name to
name your connector. Optionally, select the default management
group where it will store all discovered linked accounts. This
can be set up later. Please note that all tenants may not have
management groups configured. Under the billing section.
Select the subscription associated with all discovered
linked accounts. There is a 90 day free trial for the
connectors for AWS functionality in Azure Cost
Management. After this period you will be charged 1% of AWS
costs under management.
Click next. Enter the role ARN. It's the value that you used
when you set up the role in AWS. If you are unsure how to find
this, sign into your AWS console, click into services.
IAM rolls on the left. Search for the role you created, click into
it and the ARN is at the top of the page. Enter the external ID.
It's the value that you used when you set up your roles in AWS,
Enter the report name that you created in AWS. Click next.
Finally, review and click
create. And there you have it. We created an AWS connector,
allowing you to connect your AWS usage. The report is
available starting within 24 hours of the date that you
created a report on the reports page. The billing in Cost
Management Console. After the delivery starts. AWS updates
the AWS cost in usage report files at least once a
day. Thank you for watching and please see our other videos in
the Azure Cost Management Channel of YouTube for other
Azure Cost Management related videos.