Chapter 8 - Security and Compliance Flashcards
What protection Aws Shield provide?
- Block common attack patterns, such as SQL injection or cross-site scripting
- Protection against Distributed Denial of Service (DDoS) attacks
- Protection against In-Transit data spoofing Protection against EC2 hacking
- Protection against encryption key loss
- Block common attack patterns, such as SQL injection or cross-site scripting
- Protection against Distributed Denial of Service (DDoS) attacks
- Protection against In-Transit data spoofing Protection against EC2 hacking
- Protection against encryption key loss
What is difference between AWS Shield Standard and AWS Shield Advanced? Choose 2.
- AWS Shield Standard provides protection for all AWS customers against common and most frequently occurring infrastructure (layer 3 and 4) attacks like SYN/UDP floods, reflection attacks.
- AWS Shield Advanced provides protection for all AWS customers against common and most frequently occurring infrastructure (layer 3 and 4) attacks like SYN/UDP floods, reflection attacks.
- AWS Shield Standard provides enhanced protections for your applications running on protected Amazon EC2, Elastic Load Balancing (ELB), Amazon CloudFront, AWS Global Accelerator, and Route 53 resources against more sophisticated and larger attacks.
- AWS Shield Advanced provides enhanced protections for your applications running on protected Amazon EC2, Elastic Load Balancing (ELB), Amazon CloudFront, AWS Global Accelerator, and Route 53 resources against more sophisticated and larger attacks.
- AWS Shield Standard provides protection for all AWS customers against common and most frequently occurring infrastructure (layer 3 and 4) attacks like SYN/UDP floods, reflection attacks.
- AWS Shield Advanced provides protection for all AWS customers against common and most frequently occurring infrastructure (layer 3 and 4) attacks like SYN/UDP floods, reflection attacks.
- AWS Shield Standard provides enhanced protections for your applications running on protected Amazon EC2, Elastic Load Balancing (ELB), Amazon CloudFront, AWS Global Accelerator, and Route 53 resources against more sophisticated and larger attacks.
- AWS Shield Advanced provides enhanced protections for your applications running on protected Amazon EC2, Elastic Load Balancing (ELB), Amazon CloudFront, AWS Global Accelerator, and Route 53 resources against more sophisticated and larger attacks.
Which AWS service lets you monitor the HTTP and HTTPS requests that are forwarded to an Amazon API Gateway, Amazon CloudFront or an Application Load Balancer and gives you control over which traffic to allow or block to your web applications by defining customizable web security rules?
- AWS Shield
- AWS Cloudtrail
- AWS Cloudwatch
- AWS WAF
- AWS Shield
- AWS Cloudtrail
- AWS Cloudwatch
- AWS WAF
What are the different conditions you can define in AWS WAF to watch for in web requests? Choose 4.
- Cross-site scripting: Scripts that are likely to be malicious. Attackers embed scripts that can exploit vulnerabilities in web applications.
- IP addresses or address ranges, country or geographical location that requests originate from.
- Length of specified parts of the request, such as the query string. Strings that appear in the request.
- User credentials authentication.
- SQL injection: SQL code that is likely to be malicious. Attackers try to extract data from your database by embedding malicious SQL code in a web request.
- Cross-site scripting: Scripts that are likely to be malicious. Attackers embed scripts that can exploit vulnerabilities in web applications.
- IP addresses or address ranges, country or geographical location that requests originate from.
- Length of specified parts of the request, such as the query string. Strings that appear in the request.
- User credentials authentication.
- SQL injection: SQL code that is likely to be malicious. Attackers try to extract data from your database by embedding malicious SQL code in a web request.
Which Amazon service offers threat detection that enables you to continuously monitor and protect your AWS accounts and workloads by continuously analyzing streams of meta-data generated from your account and network activity found in AWS CloudTrail Events, Amazon VPC Flow Logs, and DNS Logs?
- AWS WAF
- AWS Shield
- Amazon GuardDuty
- Amazon Macie
- AWS WAF
- AWS Shield
- Amazon GuardDuty
- Amazon Macie
What is Rate-based Rule in AWS WAF? Choose 2.
- Allows you to specify the number of web requests that are allowed by a client IP in a trailing, continuously updated, 15 minute period.
- Allows you to specify the number of web requests that are allowed by a client IP in a trailing, continuously updated, 5 minute period.
- If an IP address breaches the configured limit, new requests will be blocked until the request rate falls below the configured threshold.
- If an IP address breaches the configured limit, new requests will be blocked for 5 minutes.
- Allows you to specify the number of web requests that are allowed by a client IP in a trailing, continuously updated, 15 minute period.
- Allows you to specify the number of web requests that are allowed by a client IP in a trailing, continuously updated, 5 minute period.
- If an IP address breaches the configured limit, new requests will be blocked until the request rate falls below the configured threshold.
- If an IP address breaches the configured limit, new requests will be blocked for 5 minutes.
What is AWS security shared responsibility model? Choose 3.
- Security of the cloud – AWS is responsible for protecting the infrastructure that runs AWS services in the AWS Cloud. This infrastructure is composed of the hardware, software, networking, and facilities that run AWS Cloud services.
- AWS compliance programs doesn’t includes testing by third party auditors who verify the effectiveness of security.
- Security in the cloud – Your responsibility is determined by the AWS service that you use. This determines the amount of configuration work the customer must perform as part of their security responsibilities.
- Security in the cloud -You are also responsible for other factors including the sensitivity of your data, your organization’s requirements, and applicable laws and regulations.
- Security of the cloud – AWS is responsible for protecting the infrastructure that runs AWS services in the AWS Cloud. This infrastructure is composed of the hardware, software, networking, and facilities that run AWS Cloud services.
- AWS compliance programs doesn’t includes testing by third party auditors who verify the effectiveness of security.
- Security in the cloud – Your responsibility is determined by the AWS service that you use. This determines the amount of configuration work the customer must perform as part of their security responsibilities.
- Security in the cloud -You are also responsible for other factors including the sensitivity of your data, your organization’s requirements, and applicable laws and regulations.
What are the different types of policy types available in AWS? Choose 6.
- Identity-based policies
- Certificate based policies
- Resource-based policies
- Permissions boundaries
- User Policies
- Organizations SCPs
- Access control lists (ACLs)
- Session policies
- Identity-based policies
- Certificate based policies
- Resource-based policies
- Permissions boundaries
- User Policies
- Organizations SCPs
- Access control lists (ACLs)
- Session policies
Based on recent pattern of brute attack on your web site, you have analyzed that the requests come from 192.0.2.44 and they contain the value BadBot in the User-Agent header. You just don’t want to block the ip-address but want to block it only when there is more than 1000 requests from the ip in a duration of 5 minutes. How can you set up this rule?
- Create a rate based rule in AWS Shield
- Create a rate based rule in AWS Firewall Manager
- Create a rate based rule in AWS WAF
- Create a rate based rule in EC2
- Create a rate based rule in AWS Shield
- Create a rate based rule in AWS Firewall Manager
- Create a rate based rule in AWS WAF
- Create a rate based rule in EC2
How can you use WAF Rate-based rule to limit access to certain parts of your web login page? Choose from following rate-based rule configuration: String match Condition settings:
- The “Part of the request to filter” on is URI.
- The “Match Type” is Starts with.
- A “Value to match” is login
- Rate limit setting:
- A Rate limit of 1000. IP match Condition settings:
- Specify the IPv4 address 192.0.2.44/32.
- 1,2,3,4
- 13,4,5
- 3,4,5
- 2,3,4,5
- 1,2,3,4
- 13,4,5
- 3,4,5
- 2,3,4,5
Which AWS service simplifies your AWS WAF, AWS Shield Advanced, and Amazon VPC security group’s administration and maintenance tasks across multiple accounts and resources?
- AWS System Manager
- AWS Trusted Advisor
- AWS Firewall Manager
- AWS Security
- AWS System Manager
- AWS Trusted Advisor
- AWS Firewall Manager
- AWS Security
Which AWS Directory Service is a Microsoft Active Directory compatible directory that is powered by Samba 4 and hosted on the AWS cloud?
- AWS Managed Microsoft AD
- AD Connector
- Amazon Cloud Directory
- Simple AD
- AWS Managed Microsoft AD
- AD Connector
- Amazon Cloud Directory
- Simple AD
Which AWS Directory Service provides an easy way to connect compatible AWS applications to your existing on-premises Microsoft Active Directory?
- AWS Managed Microsoft AD
- AD Connector
- Amazon Cloud Directory
- Amazon Cognito
- AWS Managed Microsoft AD
- AD Connector
- Amazon Cloud Directory
- Amazon Cognito
Which AWS Directory Service is best choice if you have more than 5,000 users and need a trust relationship set up between an AWS hosted directory and your on-premises directories?
- AWS Managed Microsoft AD
- AD Connector
- Amazon Cloud Directory
- Simple AD
- AWS Managed Microsoft AD
- AD Connector
- Amazon Cloud Directory
- Simple AD
Your company has around 3000 users and want to use Microsoft Active Directory compatible features to manage their EC2 instances running Windows and other AWS applications such as Amazon workspaces, Amazon Workdocs or Amazon WorkMail. You don’t want to set a trust relationship with on-premise AD. Which AWS service will you use?
- AWS Managed Microsoft AD
- AD Connector
- Amazon Cloud Directory
- Simple AD
- AWS Managed Microsoft AD
- AD Connector
- Amazon Cloud Directory
- Simple AD
How is web identity federation i.e. providing access to externally authenticated users supported in AWS? Choose 3.
- Using Amazon Cognito as an identity broker which does much of the federation work.
- If you are creating a mobile app or web-based app it blocks users who have Login with Amazon, Facebook, Google, or any OpenID Connect (OIDC) compatible identity provider.
- You can create a mobile app or web-based app that can let users identify themselves through an Internet identity provider like Login with Amazon, Facebook, Google, or any OpenID Connect (OIDC) compatible identity provider, the app can use federation to access AWS.
- Using Web Identity Federation API Operations for Mobile Apps.
- Using Amazon Cognito as an identity broker which does much of the federation work.
- If you are creating a mobile app or web-based app it blocks users who have Login with Amazon, Facebook, Google, or any OpenID Connect (OIDC) compatible identity provider.
- You can create a mobile app or web-based app that can let users identify themselves through an Internet identity provider like Login with Amazon, Facebook, Google, or any OpenID Connect (OIDC) compatible identity provider, the app can use federation to access AWS.
- Using Web Identity Federation API Operations for Mobile Apps.
What are IAM Identity-based and Resource-based Policies? Choose 2.
- Identity-based policies are permissions policies that you attach to an IAM identity, such as an IAM user, group, or role.
- Resource-based policies are permissions policies that you attach to a resource such as an Amazon S3 bucket or an IAM role trust policy.
- Identity-based policies are permissions policies that you attach to an IAM identity, such an Amazon S3 bucket or an IAM role trust policy.
- Resource-based policies are permissions policies that you attach to a resource such as an IAM user, group, or role.
- Identity-based policies are permissions policies that you attach to an IAM identity, such as an IAM user, group, or role.
- Resource-based policies are permissions policies that you attach to a resource such as an Amazon S3 bucket or an IAM role trust policy.
- Identity-based policies are permissions policies that you attach to an IAM identity, such an Amazon S3 bucket or an IAM role trust policy.
- Resource-based policies are permissions policies that you attach to a resource such as an IAM user, group, or role.
How many types of IAM Identity Managed policies are there? Choose 2.
- Inline policies
- AWS managed policies
- Resource-based policies
- Customer managed policies
- Inline policies
- AWS managed policies
- Resource-based policies
- Customer managed policies
What is a principal in AWS IAM terms? Choose 2.
- A person that uses the AWS account root user, an IAM user, or an IAM role to sign in and make requests to AWS.
- An application that uses the AWS account root user, an IAM user, or an IAM role to sign in and make requests to AWS.
- An encryption API that uses the AWS account root user, an IAM user, or an IAM role to sign in and make requests to AWS.
- A replication service that uses the AWS account root user, an IAM user, or an IAM role to sign in and make requests to AWS.
- A person that uses the AWS account root user, an IAM user, or an IAM role to sign in and make requests to AWS.
- An application that uses the AWS account root user, an IAM user, or an IAM role to sign in and make requests to AWS.
- An encryption API that uses the AWS account root user, an IAM user, or an IAM role to sign in and make requests to AWS.
- A replication service that uses the AWS account root user, an IAM user, or an IAM role to sign in and make requests to AWS.
Choose IAM best practices which should be followed? Choose 4.
- Use Roles for Applications That Run on Amazon EC2 Instances
- Share user credentials to delegate permissions
- Use Roles to Delegate Permissions
- Enable MFA for Privileged Users
- Do Not Share Access Keys
- Store access keys in your application configuration file
- Use Roles for Applications That Run on Amazon EC2 Instances
- Share user credentials to delegate permissions
- Use Roles to Delegate Permissions
- Enable MFA for Privileged Users
- Do Not Share Access Keys
- Store access keys in your application configuration file
What are the scenarios when you should create an IAM ‘user’ instead of a ‘role’? Choose 3.
- You’re creating an application that runs on an Amazon Elastic Compute Cloud (Amazon EC2) instance and that application makes requests to other AWS resources.
- You created an AWS account and you’re the only person who works in your account.
- Other people in your group need to work in your AWS account, and your group is using no other identity mechanism.
- You want to use the command-line interface (CLI) to work with AWS.
- Users in your company are authenticated in your corporate network and want to be able to use AWS without having to sign in again.
- You’re creating an application that runs on an Amazon Elastic Compute Cloud (Amazon EC2) instance and that application makes requests to other AWS resources.
- You created an AWS account and you’re the only person who works in your account.
- Other people in your group need to work in your AWS account, and your group is using no other identity mechanism.
- You want to use the command-line interface (CLI) to work with AWS.
- Users in your company are authenticated in your corporate network and want to be able to use AWS without having to sign in again.
An IAM user with administrator permissions is not the same thing as the AWS account root user.
- True
- False
- True
- False
What are the different ways to access AWS depending on user credentials? Choose 4.
- Access Keys
- Console password
- SSH keys for use with CodeCommit
- Server Certificate
- Telnet Putty
- Access Keys
- Console password
- SSH keys for use with CodeCommit
- Server Certificate
- Telnet Putty
Which statements are true about IAM users? Choose 4.
- By default, a brand new IAM user has no permissions to do anything.
- You could use an ARN to specify the user as a Principal in an IAM policy. Arn: aws: iam: account-ID-without-hyphens: user/James.
- By default, a brand new IAM user has administrator permissions to do anything.
- Each IAM user can be associated with more than one AWS account.
- An IAM user can represent a person or an application that uses its credentials to make AWS requests.
- Each IAM user is associated with one and only one AWS account.
- By default, a brand new IAM user has no permissions to do anything.
- You could use an ARN to specify the user as a Principal in an IAM policy. Arn: aws: iam: account-ID-without-hyphens: user/James.
- By default, a brand new IAM user has administrator permissions to do anything.
- Each IAM user can be associated with more than one AWS account.
- An IAM user can represent a person or an application that uses its credentials to make AWS requests.
- Each IAM user is associated with one and only one AWS account.
What signature versions are supported by AWS? Choose 2.
- Signature Version 1
- Signature Version 2
- Signature Version 3
- Signature Version 4
- Signature Version 5
- Signature Version 1
- Signature Version 2
- Signature Version 3
- Signature Version 4
- Signature Version 5
Choose ways you can change the permissions for an IAM user in your AWS account?
- By changing its group memberships
- By copying permissions from an existing user
- By attaching policies directly to a user
- By setting a permissions boundary
- All of the above
- By changing its group memberships
- By copying permissions from an existing user
- By attaching policies directly to a user
- By setting a permissions boundary
- All of the above
Which statements are true for IAM groups? Choose 3.
- A group can contain many users, and a user can belong to multiple groups.
- Groups can’t be nested; they can contain only users, not other groups.
- Groups can be nested; they can contain only users, not other groups.
- There’s no default group that automatically includes all users in the AWS account. If you want to have a group like that, you need to create it and assign each new user to it.
- Groups can’t be nested; they can contain only roles, not other groups.
- A group can contain many roles, and a role can belong to multiple groups.
- A group can contain many users, and a user can belong to multiple groups.
- Groups can’t be nested; they can contain only users, not other groups.
- Groups can be nested; they can contain only users, not other groups.
- There’s no default group that automatically includes all users in the AWS account. If you want to have a group like that, you need to create it and assign each new user to it.
- Groups can’t be nested; they can contain only roles, not other groups.
- A group can contain many roles, and a role can belong to multiple groups.
A group is not truly an “identity” in IAM because it cannot be identified as a Principal in a permission policy. It is simply a way to attach policies to multiple users at one time.
- True
- False
- True
- False
An IAM role is not an IAM identity that you can create in your account that has specific permissions.
- True
- False
- True
- False
Roles can be used by the following.
- An IAM user in the same AWS account as the role.
- An IAM user in a different AWS account than the role.
- A web service offered by AWS such as Amazon Elastic Compute Cloud (Amazon EC2).
- An external user authenticated by an external identity provider (IdP) service that is compatible with SAML 2.0 or OpenID Connect, or a custom-built identity broker.
- All of the above.
- An IAM user in the same AWS account as the role.
- An IAM user in a different AWS account than the role.
- A web service offered by AWS such as Amazon Elastic Compute Cloud (Amazon EC2).
- An external user authenticated by an external identity provider (IdP) service that is compatible with SAML 2.0 or OpenID Connect, or a custom-built identity broker.
- All of the above.
Delegation of a role involves setting up a trust between the account that owns the resource (the trusting account), and the account that contains the users that need to access the resource (the trusted account). The trusted and trusting accounts can be any of the following. Choose 3:
- The same account.
- It can never be in two accounts owned by different organization.
- Separate accounts that are both under your organization’s control.
- Two accounts owned by different organizations.
- The same account.
- It can never be in two accounts owned by different organization.
- Separate accounts that are both under your organization’s control.
- Two accounts owned by different organizations.
Assuming that for a live web application you are maintaining two AWS accounts to isolate development and production environment. Development account users are assigned to two IAM groups of Testers and Developers. Some of the users in development account belonging to Developer user group will require access to production environment. What steps you will take to leverage IAM Roles so that some of the users in the Developer group in development account environment will have cross account access to production account environment? Choose 3.
- In the production account use IAM to create a role in that account and defines a trust policy that specifies the development account as a Principal. Also defines a permissions policy for the role that specifies which role users have read and write permissions to AWS resources.
- Share the account number and name of the role (for AWS console users) or the Amazon Resource Name (ARN) (for AWS CLI or AWS API access) to Development environment users for whom you want to give access.
- Create separate identities and passwords in each environment for users who work in both accounts.
- In the development account grant specific required members of the Developers group permission to switch to the role. This is done by granting the Developers group permission to call the AWS Security Token Service (AWS STS) AssumeRole API for the role created in production account.
- In the production account use IAM to create a role in that account and defines a trust policy that specifies the development account as a Principal. Also defines a permissions policy for the role that specifies which role users have read and write permissions to AWS resources.
- Share the account number and name of the role (for AWS console users) or the Amazon Resource Name (ARN) (for AWS CLI or AWS API access) to Development environment users for whom you want to give access.
- Create separate identities and passwords in each environment for users who work in both accounts.
- In the development account grant specific required members of the Developers group permission to switch to the role. This is done by granting the Developers group permission to call the AWS Security Token Service (AWS STS) AssumeRole API for the role created in production account.
You have VPC where you have web server instances in public subnet and database servers in the private subnet. There is an Application Load Balancer in the front listening at port 80 mapped to web server instances in public subnet. You are also leveraging Cloudfront for low latency and high transfer speeds for your end user. How can you minimize the impact of a DDoS attack or brute force attack from one ip address on your application? You want to ensure that attack requests should not reach your web server instances? Choose 2.
- On discovering attack update the web server instance security group to block access to ip address/es.
- Use AWS Shield together with AWS WAF rules to create a comprehensive DDoS attack mitigation strategy.
- Have your web server instances in private subnet.
- Add CloudFront IP addresses to your security groups to ensure ELB only responds to requests that are served by CloudFront (and therefore inspected by AWS WAF).
- On discovering attack update the web server instance security group to block access to ip address/es.
- Use AWS Shield together with AWS WAF rules to create a comprehensive DDoS attack mitigation strategy.
- Have your web server instances in private subnet.
- Add CloudFront IP addresses to your security groups to ensure ELB only responds to requests that are served by CloudFront (and therefore inspected by AWS WAF).
What are the features of IAM user access keys? Choose 3.
- Access keys are long-term credentials for an IAM user or the AWS account root user.
- You can use access keys to sign programmatic requests to the AWS CLI or AWS API (directly or using the AWS SDK).
- You must use either the access key ID or secret access key to authenticate your requests.
- Access keys consist of two parts: an access key ID and a secret access.
- Access keys are long-term credentials for an IAM user or the AWS account root user.
- You can use access keys to sign programmatic requests to the AWS CLI or AWS API (directly or using the AWS SDK).
- You must use either the access key ID or secret access key to authenticate your requests.
- Access keys consist of two parts: an access key ID and a secret access.
Your company first project in AWS cloud is an internal web application to be used by employees only. You want to provide single sign on where employee can use their existing corporate sign on identities. You don’t want to a have separate user management module in the new application which will require your employees to have a separate authentication userid/password. Essentially this will enable your employees to have single sign on to new web application using existing corporate identities. You found that AWS supports this by way of user federation for authenticating using existing corporate identities. Which of the following consideration have to be kept in mind to use this user federation feature? Choose 3.
- Existing corporate Identity Provider should be compatible with Security Assertion Markup Language 2.0 (SAML 2.0) to provide single-sign on (SSO) access.
- If your corporate Identity Provider is Microsoft Active Directory Federation Service (AD FS), you cannot configure SSO.
- If your corporate Identity Provider is Microsoft Active Directory Federation Service (AD FS), you can configure SSO.
- If your corporate directory is not compatible with SAML 2.0, you can create an identity broker application to provide single-sign on (SSO) access to the AWS for your users.
- If your corporate directory is not compatible with SAML 2.0, you cannot create an identity broker application to provide single-sign on (SSO) access to the AWS Management Console for your users.
- Existing corporate Identity Provider should be compatible with Security Assertion Markup Language 2.0 (SAML 2.0) to provide single-sign on (SSO) access.
- If your corporate Identity Provider is Microsoft Active Directory Federation Service (AD FS), you cannot configure SSO.
- If your corporate Identity Provider is Microsoft Active Directory Federation Service (AD FS), you can configure SSO.
- If your corporate directory is not compatible with SAML 2.0, you can create an identity broker application to provide single-sign on (SSO) access to the AWS for your users.
- If your corporate directory is not compatible with SAML 2.0, you cannot create an identity broker application to provide single-sign on (SSO) access to the AWS Management Console for your users.
You are planning to use a third party product to monitor your AWS accounts and its resources for optimization. To enable this you are planning to use roles to delegate access to them. What information third party must provide to you to create a role that they can assume? Choose 3.
- The third party’s AWS account ID which you will specify as the principal when you define the trust policy for the role.
- The third party’s AWS account root user id which you will specify as the principal when you define the trust policy for the role.
- An external ID to uniquely associate with the role. You will specify this ID when you define the trust policy for the role. The third party then must provide this ID when they assume the role.
- The access keys of third party account to uniquely associate with the role. You will specify these keys when you define the trust policy for the role. The third party then must provide these keys when they assume the role.
- The permissions that the third party requires to work with your AWS resources. You must specify these permissions when defining the role’s permission policy
- The third party’s AWS account ID which you will specify as the principal when you define the trust policy for the role.
- The third party’s AWS account root user id which you will specify as the principal when you define the trust policy for the role.
- An external ID to uniquely associate with the role. You will specify this ID when you define the trust policy for the role. The third party then must provide this ID when they assume the role.
- The access keys of third party account to uniquely associate with the role. You will specify these keys when you define the trust policy for the role. The third party then must provide these keys when they assume the role.
- The permissions that the third party requires to work with your AWS resources. You must specify these permissions when defining the role’s permission policy
What are the scenarios when you should create an IAM ‘role’ instead of a ‘user’? Choose 3.
- You’re creating an application that runs on an Amazon Elastic Compute Cloud (Amazon EC2) instance and that application makes requests to other AWS resources.
- You created an AWS account and you’re the only person who works in your account.
- Other people in your group need to work in your AWS account, and your group is using no other identity mechanism.
- You want to use the command-line interface (CLI) to work with AWS.
- Users in your company are authenticated in your corporate network and want to be able to use AWS without having to sign in again.
- You’re creating an app that runs on a mobile phone and that makes requests to AWS.
- You’re creating an application that runs on an Amazon Elastic Compute Cloud (Amazon EC2) instance and that application makes requests to other AWS resources.
- You created an AWS account and you’re the only person who works in your account.
- Other people in your group need to work in your AWS account, and your group is using no other identity mechanism.
- You want to use the command-line interface (CLI) to work with AWS.
- Users in your company are authenticated in your corporate network and want to be able to use AWS without having to sign in again.
- You’re creating an app that runs on a mobile phone and that makes requests to AWS.
What are the best practices for managing IAM user access keys? Choose 4.
- Remove (or Don’t Generate) Account Access Key.
- Use Temporary Security Credentials (IAM Roles) Instead of Long-Term Access Keys
- Don’t embed access keys directly into code.
- Rotate access keys periodically.
- Embed access keys directly into code for better security.
- Remove (or Don’t Generate) Account Access Key.
- Use Temporary Security Credentials (IAM Roles) Instead of Long-Term Access Keys
- Don’t embed access keys directly into code.
- Rotate access keys periodically.
- Embed access keys directly into code for better security.