Amazon. com Help Keep Me Signed In Checkbox

Error 502 Ray ID: 5243d4fe580ec3e3 • 2019-10-11 21:12:24 UTC

Bad gateway

Cloudflare

What happened?

The web server reported a bad gateway error.

What can I do?

Please try again in a few minutes.

Cloudflare Ray ID: 5243d4fe580ec3e3 • Your IP : 93.84.193.174 • Performance & security by Cloudflare

Question Info

Hello! I am an Independent Advisor, I would love to help you out!

Is this happening in outlook. com?

If so, sometimes the cached login session will expire and you will need to log back in with the email and password. However, you can make this last quite a while before needing to do so.

When you login, on the page that asks for your password there should be a checkbox to "keep me signed in". Make sure you have that checked and if you use the same browser and computer it should keep you signed in for quite a while, unless you clear your cache, browsing data, etc of the browser.

I attached a screenshot of what it should look like. If you are signing into the outlook desktop application there should also be a similar window and checkbox.

I hope this helps!

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

"Keep Me Signed In" Checkbox

If this is a personal device that you don’t share with others, we recommend that you check the "Keep me signed in" box. This will keep you signed in to your Amazon account on this device, so you’ll be asked to sign in less frequently. To make sure that your account remains safe, we may still occasionally ask you to confirm your identity – for example, by entering your password, or responding to a message on your mobile device.

To prevent others from accessing your Amazon account, we strongly recommend you don't use this feature on devices and computers that are shared with other people.

Was this information helpful?

Thank you for your feedback.

Please select what best describes the information:

Thanks! While we're unable to respond directly to your feedback, we'll use this information to improve our online Help.

Amazon Web Services IAM Part 4 – Sign-in credentials and MFA

In this part of IAM series, I will explain how to create sign-in credentials and configuring Multi-Factor Authentication. If we want our IAM users connect AWS services via console, we have to assign a password to them. And also by configuring MFA, we can add an extra security layer. MFA can also be used for controlling access to AWS API’s.

Let’s start with sign-in credentials.

As you see “User_admin” user have no credentials right now.

When we click “Manage_Password” , we can assign an auto-generated or custom password to our user.

I will use a auto-generated password. I can copy my password or download the credentials.

Before configuring MFA, we will test our user password. For IAM users, the sign-in URL is presented on the IAM dashboard.

If I open “https://1305xxxxxxxx. signin. aws. amazon. com/console” url, I will be able to access console with my IAM users. If you want to login as root account again, you can click “Sign-in using root account credentials” link.

Now I will login with my “User_admin” user and I can access the console with the permissions granted (In previous posts, we had denied the “start_instances” action to User_admin).

Let’s try to start “saltmaster” instance.

As expected, user couldn’t start the instance. If you want to use IAM and with the console access, it is better to provide a user friendly url. Again in dashboard screen by clicking “Create account alias”, we can create a user friendly url. I used “wekanban” as my account alias.

This seems better!

As you know it is a security practice to rotate your passwords. You can keep, change (auto-generated or custom) or remove the password of an IAM user.

So it is time to configuring MFA. We can configure MFA with a virtual or a hardware device. AWS provides different devices as here in this link. I will use Google authenticator in my example.

When we click “Manage MFA Device” , we have to select either virtual or hardware device.

I’ve already installed Google authenticator so I can continue.

I open the Google authenticator on my device and select “scan barcode”.

I scan the QR code and the device generates the authentication codes for me

I enter the codes and continue.

And MFA is configured now. We can test it and see the result.

Again I open my https://wekanban. signin. aws. amazon. com/console url. I check the “I have an MFA Token” checkbox and use my virtual hardware generated code.

I can successfully logged in the AWS console. Remember that, if you try to login without MFA code, you can not login and console warns you as “Your authentication information was incorrect.

Please try again”.

In the next posts, I will explain Roles, Identity Providers and Password Policy.

If you have any question or comment please feel free to write and don’t forget to share please.

AWS Cloud & DevOps Consultant, AWS Certified Solutions Architect, AWS Community Hero