This is a step by step guide on how to set up SSO for Amazon Web Services (AWS) Identity and Access Management (IAM) on Okta.

Essentially by federating Okta to Amazon Web Services (AWS) Identity and Access Management (IAM) accounts, end users get single sign on access to all their assigned AWS roles with their Okta credentials.

Such that when users sign into AWS from Okta, they are automatically logged into their assigned AWS role on AWS. 

I have been testing Google Cloud and AWS, so I recently decided to stop all my Amazon services so I can focus on testing on one cloud computing hosting provider. I decided I will test on Google as I like their BigQuery features.

So I scaled down all my Amazon AWS (Amazon Web Services) instances and found that I was still getting charged by AWS.

What I received was a bill, I logged into AWS and found that I needed to disable my Elastic IP address that I had set on AWS.

As I knew I had already disabled the instances itself (and in each region - be sure to check that!). But the instance still had an Elastic IP address associated and set up with it. So I didn't realise it right now, but I was still using another paid feature, so that was what was causing that charge on my credit card was for in the following month.

Well, here is the example details that I saw when I logged into my AWS account.