AWS IAM
1)AWS IAM attributes:
a) Users/Groups/Promissions
b) Roles/Fed Users
c) Cloud Trial
d) Integration (IAM <-> AD)
e) Compliance
f) Automation
2)Inline policy
3) security scheme
MFA token
-> Time-Based Ohe-Time Password (TOTP)
virtual MFA device uses a software app that generates six-digit auth. codes are compatible with the TOTP standard, as deseribed inRFC 6238
4) Instance profile
-is a container for a IAM role that you can use to pass role inf. to an EC2 instance when the instance stars.
5) The signature Version 4 - signing process describes how to add auth. inf. to AWS requests. For security , most request to AWS must be signed with an access key (Access Key ID (AKI) and Secret Access Key (SAK)). If you use the AWS CLI or one of the SDK, those tools automaticly sigh request for you based on credentials that you specify when you configure the tools. However, if you make direct HTTP or HTTPS calls to AWS, you must sign the requests yourself.
a) Users/Groups/Promissions
b) Roles/Fed Users
c) Cloud Trial
d) Integration (IAM <-> AD)
e) Compliance
f) Automation
2)Inline policy
3) security scheme
MFA token
-> Time-Based Ohe-Time Password (TOTP)
virtual MFA device uses a software app that generates six-digit auth. codes are compatible with the TOTP standard, as deseribed inRFC 6238
4) Instance profile
-is a container for a IAM role that you can use to pass role inf. to an EC2 instance when the instance stars.
5) The signature Version 4 - signing process describes how to add auth. inf. to AWS requests. For security , most request to AWS must be signed with an access key (Access Key ID (AKI) and Secret Access Key (SAK)). If you use the AWS CLI or one of the SDK, those tools automaticly sigh request for you based on credentials that you specify when you configure the tools. However, if you make direct HTTP or HTTPS calls to AWS, you must sign the requests yourself.
Komentarze
Prześlij komentarz