VishaalY/solutions-architect-hf-dataset huggingface dataset:
Question: Does AWS Support have a phone number?

I want to contact AWS Support for help. What phone number should I call?ResolutionFor security purposes, AWS Support doesn’t have a phone number.Note: If you can't sign in to your AWS account, see I can't sign in because my credentials don't work.To contact AWS Support, do the following:Sign in to your AWS account.Note: If you can't sign in to contact AWS Support, see I'm an AWS customer and I'm looking for billing or account support.Open the AWS Support console, and then choose Create case.Select your option for How can we help?Choose the Service, Category, and Severity for your case, and then choose Next step: Additional information.Enter a Subject and Description for your case, and then choose Next step: Solve now or contact us.Tip: For more information on what to include, see What information should I include in my AWS Support case?Select your preference for Contact us.Important: The options for contact vary based on the type of case and your Support plan.If you select Web, you can read and respond to the case in Support Center.If you select Chat, you can chat online with a representative from AWS Support.If you select Phone, you're prompted for a callback number. You'll receive a call from AWS Support as soon as the next agent is available to assist with the case. Be sure to provide a direct line phone number.Note: If your account isn't fully activated yet, you can choose the Chat option.Choose Submit.For technical support, all AWS customers have access to AWS documentation, the AWS Knowledge Center, AWS whitepapers, and AWS re:Post.If you have a Basic Support plan and require one-on-one technical support, you can upgrade your Support plan. For more information, see How do I change my AWS Support plan?To respond to an open case or select a different contact option, do the following:Open the AWS Support console, and then choose your open case in the Open support cases section.In Correspondence, choose Reply.Provide your response or additional information in the Reply section.Select your preference for Contact methods.Choose Submit.

Related informationHow do I get technical support from AWS?How do I report abuse of AWS resources?
Question: How can I find out if my Amazon EC2 Reserved Instance provides Regional benefits or size flexibility?

I want to purchase an Amazon Elastic Compute Cloud (Amazon EC2) Reserved Instance (RI) that provides the Regional benefit or that's size-flexible.

ResolutionAll Amazon EC2 RIs that are size-flexible also provide the Regional benefit, but the reverse isn't always true.For an RI to provide the Regional benefit, the following must be true:It must be a Standard or Convertible RI.It must be in the active state.It must not be tied to a specific Availability Zone.For an RI to be size-flexible:It must meet the Regional benefit criteria.It must have a platform value of Linux/UNIX.It must not be a G4ad, G4dn, G5, G5g, or Inf1 instance.It must not have a dedicated tenancy.It must not be tied to a specific Availability Zone.An RI that provides the Regional benefit applies to any instance in that Region that matches the specifications of the RI.An RI that's size-flexible applies all or part of its pricing benefit to any instance in the same instance family, regardless of Availability Zone or size.For example, an RI that's size-flexible for a c4.large instance applies to either a c4.large instance or two c4.medium instances. In the same way, two c4.medium instances can also be applied to usage for a c4.large instance.

Related informationReserved InstancesHow Reserved Instances are appliedTypes of Reserved Instances (offering classes)
Question: Why am I receiving the "maximum number of throughput mode changes or provisioned throughput value decreases" error when modifying the throughput mode on my EFS file system?

I'm receiving the following error message when I modify the throughput mode on my Amazon Elastic File System (Amazon EFS) file system. Or, I'm receiving an error when reducing the provisioned throughput in my EFS file system using Provisioned Throughput mode."You have reached the maximum number of throughput mode changes or provisioned throughput value decreases. Wait until YYYY-MM-DDTxx:xx:xxZ UTC and try again."How do I troubleshoot this error?ResolutionIn Provisioned Throughput mode, your EFS file system drives the level of throughput independent of the file system's size or burst credit balance based on a specified throughput level. For EFS file systems in Provisioned Throughput mode, you can increase the Provisioned Throughput value of the file system at any time with no restriction.However, Amazon EFS restricts the following modifications to one change within a 24-hour period:Changing a file system's throughput mode. For example, changing from Provisioned Throughput to Bursting Throughput, or from Bursting Throughput to Provisioned Throughput.Reducing the amount of provisioned throughput in Provisioned Throughput mode.If you attempt to change the preceding options more than once in a 24-hour period, you receive the maximum number of throughput mode changes error. Wait until the time indicated in the error message before trying to make the change.
Question: How do I check CloudWatch logs for errors when I import users into a user pool from a CSV file?

I want to check for errors that are reported when I import users into a user pool from a CSV file.

Short descriptionAmazon Cognito allows you to import users into an Amazon Cognito user pool from a specially formatted CSV file. This import process sets values for all user attributes except password. For more information, see Importing users into user pools from a CSV file.For information on common errors during the importing process, see How do I troubleshoot common errors with the importing process in Amazon Cognito?To find these errors, do the following:Find the user pool ID and name.Import the job name.Find the Cloudwatch log group.Use Cloudwatch log stream.

ResolutionFind user pool ID and nameOpen the Amazon Cognito console.Note: If using the old interface, choose Manage User Pools.Search for the user pool where you ran the import job to find the name and ID of the user pool.Note the user pool name and ID.User pool ID and name example:- Pool Id - us-east-1_XXXXXXXXX- Pool Name - testuserimportFind the import job nameOld interfaceOpen the Amazon Cognito console.Choose Manager User Pools.Choose your user pool.In the navigation pane, choose Users and groups under General settings.Select Import Users.Note the failing job name.New interfaceOpen the Amazon Cognito console.Choose your user pool.Under the Userstab, find the Import users information.Note the failing job name.**Note:**You can view the CloudWatch logs from here by clicking on View logs for the failed import job. This will redirect you to the log group stream.Import job name example:import-Test1Find the Cloudwatch log groupOpen the Amazon CloudWatch console.Expand Logs in the navigation pane, and select Log Groups.Using the Log Groups search bar functionality, you can look for either the user pool ID or name. Doing this will filter for the specific log group of that user pool.CloudWatch log group example:/aws/cognito/userpools/{user_pool_id}/{user_pool_name}Find the CloudWatch log streamWhile still in CloudWatch, select the log group you found for your user pool during the previous steps.Select the Log Streams tab, and use the search filter functionality to find the log stream using import job name.Select the log stream to check the log events for import job error.CloudWatch log stream example:[Timestamp]    Cognito User Pools Import - Test Log [Timestamp]    Cognito User Pools Import - Test Log [Timestamp]    [FAILED] Line Number 2 - The User Record contains an invalid value for phone_number_verified. It must be true or false.Note: Based on this example, the error reported in CloudWatch Log Stream shows that the value for phone_number_verified field is set incorrectly.

Related informationWorking with log groups and log streams
Question: How can I renew an expired Kerberos ticket that I'm using for Amazon EMR authentication?

I'm using Kerberos for authentication on an Amazon EMR cluster. My Kerberos ticket expired. When I try to run commands on the cluster, I get an error message similar to the following:19/11/04 22:12:16 WARN ipc.Client: Exception encountered while connecting to the server : javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)]ls: Failed on local exception: java.io.IOException: javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)]; HostDetails : local host is: "ip-xxx-x-x-x.ec2.internal/192.x.x.x";destination host is: "ip-xxx-x-x-x.ec2.internal":8020;Short descriptionDo the following to renew an expired Kerberos ticket:1.    Run the klist command to show the credentials issued by the key distribution center (KDC).2.    To get a new ticket, run the kinit command and either specify a keytab file that contains credentials, or enter the password for your principal.Resolution1.    Connect to the master node using SSH.2.    To confirm that the ticket is expired, run the klist command. This command checks for a credentials cache. If no credentials are cached, then the ticket is expired.[hadoop@ip-xxx-x-x-xxx ~]$ klistklist: No credentials cache found (filename: /tmp/krb5cc_498)3.    To confirm the Kerberos principal name, list the contents of the keytab file:[hadoop@ip-xxx-x-x-xxx ~]$ klist -kt /etc/hadoop.keytabKeytab name: FILE:/etc/hadoop.keytabKVNO Timestamp           Principal---- ------------------- ------------------------------------------------------   2 07/04/2019 21:48:46 hadoop/ip-xxx-x-x-xxx.ec2.internal@EC2.INTERNAL   2 07/04/2019 21:48:46 hadoop/ip-xxx-x-x-xxx.ec2.internal@EC2.INTERNAL   2 07/04/2019 21:48:46 hadoop/ip-xxx-x-x-xxx.ec2.internal@EC2.INTERNAL4.    To renew the Kerberos ticket, run kinit and specify both the keytab file and the principal:[hadoop@ip-xxx-x-x-xxx ~]$ kinit -kt /etc/hadoop.keytab hadoop/ip-xxx-x-x-xxx.ec2.internal@EC2.INTERNAL5.    Confirm that the credentials are cached:[hadoop@ip-xxx-x-x-xxx ~]$ klistTicket cache: FILE:/tmp/krb5cc_498Default principal: hadoop/ip-xxx-x-x-xxx.ec2.internal@EC2.INTERNALValid starting       Expires              Service principal11/04/2019 22:13:47  11/05/2019 08:13:47  krbtgt/EC2.INTERNAL@EC2.INTERNALrenew until 11/06/2019 22:13:476.    Run an HDFS command to confirm that the Kerberos ticket is working:[hadoop@ip-XXX-XX-XX-XXX ~]$ hdfs dfs -ls /Found 4 itemsdrwxr-xr-x   - hdfs hadoop          0 2019-11-05 22:45 /appsdrwxrwxrwt   - hdfs hadoop          0 2019-11-05 22:46 /tmpdrwxr-xr-x   - hdfs hadoop          0 2019-11-05 22:45 /userdrwxr-xr-x   - hdfs hadoop          0 2019-11-05 22:45 /var

Related informationUse Kerberos authentication
Question: How do I unsubscribe from AWS emails?

How do I unsubscribe from AWS emails?ResolutionTo unsubscribe from specific email types:Open the AWS Email Preference Center.Choose Unsubscribe From Email.For Email Address, enter your email address.Clear the box for any email types that you want to stop receiving.Choose Submit.To unsubscribe from all marketing emails:Open the AWS Email Preference Center.Choose Unsubscribe From Email.For Email Address, enter your email address.Select Unsubscribe me from all marketing emails.(Optional) For Why are you unsubscribing?, select the reasons that apply to you. If your reason isn't listed in the options, enter your reason in Unsubscribed Reason (Other).Choose Submit.You'll still receive important account-related notifications from AWS, such as monthly billing statements.
Question: How do I increase the service quota of my Amazon EC2 resources?

I want to create more Amazon Elastic Compute Cloud (Amazon EC2) resources, such as EC2 instances, Amazon Elastic Block Store (Amazon EBS) storage, or Elastic IP addresses, but I've reached my quota. How do I increase my Amazon EC2 service quotas?ResolutionYou can request an increase to your Amazon EC2 service quotas (formerly called service limits) by using either the AWS Support dashboard or AWS Service Quotas dashboard.AWS Support dashboardOpen the AWS Support dashboard.Choose Service Limit Increase.Important: EC2 service quotas affect one Region at a time. You must request service quota increases in each AWS Region where you need more resources.(Optional) To request multiple service quota increases at the same time, complete one quota increase request in the Requests section, and then choose Add another request.AWS Service Quotas dashboardOpen the AWS Service Quotas dashboard.Choose Amazon Elastic Compute Cloud (Amazon EC2).Choose the required service quota.Choose Request quota increase.It's a best practice to proactively monitor and manage your service quotas to be sure that you have enough quotas to support your usage requirements. Requests for EC2 service quota increases are subject to review by AWS engineering teams. Service quota increase requests aren't processed immediately after you submit a request. You receive an email after your request is processed.On-Demand Instances limits are managed in terms of the number of virtual central processing units (vCPUs) that your running On-Demand Instances are using, regardless of the instance type. To information on how to calculate vCPU limits, see How do I request an EC2 vCPU limit increase for my On-Demand Instance?For a list of other AWS services and their quotas, see AWS service quotas.

Related informationInstance typesAmazon EC2 pricing
Question: How can I resolve the publish operation error in Amazon SNS?

I get an error in Amazon Simple Notification Service (Amazon SNS). The error happens when I'm using a subnet, and I try to publish my SNS topic from a cross-account Amazon Elastic Compute Cloud (Amazon EC2) instance.

Short descriptionIf you receive an authorization error when you call the Publish operation, then complete the steps in the Verify EC2 instance IAM role and SNS topic access policy permissions section.If you have issues with an SNS topic that's using server-side encryption and you receive a "KMSAccessDenied" error, then complete the steps in the Verify KMS key settings and EC2 IAM role permissions section.Note: If your EC2 instance can't connect to the internet with an internet gateway, see Why can't my Amazon EC2 instance connect to the internet using an internet gateway?ResolutionVerify EC2 instance IAM role and SNS topic access policy permissionsMisconfigured AWS Identity and Access Management (IAM) role permissions for your EC2 instance and Amazon SNS topic access policy can cause the following error:"An error occurred (AuthorizationError) when calling the Publish operation: User: arn:aws:iam::111122223333:role/cross-acc-ec2-sns-publish-role/i-0123456789f804d is not authorized to perform: SNS:Publish on resource: arn:aws:sns:us-east-2:123456789012:cross-account-ec2-sns."To resolve this error, see How do I publish to an Amazon SNS topic from a cross-account Amazon EC2 instance using an IAM EC2 role?Verify KMS key settings and EC2 IAM role permissionsIf permissions for the IAM role of your EC2 instance and the AWS Key Management Service (AWS KMS) key policy of your AWS KMS key (KMS key) are incorrect, you can receive the following error:An error occurred (KMSAccessDenied) when calling the Publish operation: null (Service: AWSKMS; Status Code: 400; Error Code: AccessDeniedException; Request ID: IDNumber; Proxy: null)Note: The preceding error occurs only when your SNS topic uses server-side encryption.To resolve the error, check your KMS key settings and AWS KMS key policy permissions:1.    Confirm that your KMS key is enabled.2.    Confirm that your EC2 instance IAM role is allowed to perform kms:GenerateDataKey* and kms:Decrypt in the AWS KMS key policy. This is the key policy of the KMS key that's used for server-side encryption on your SNS topic. For example:{  "Effect": "Allow",  "Principal": {    "AWS": "arn:aws:iam::111122223333:role/cross-acc-ec2-sns-publish-role"  },  "Action": [    "kms:GenerateDataKey*",    "kms:Decrypt"  ],  "Resource": "*"}3.    Confirm that kms:GenerateDataKey* and kms:Decrypt permissions are attached to the IAM role of your EC2 instance.Note: It's a best practice to provide the least privileges needed. Therefore, be sure to replace the Resource value with your KMS Key ARN in the following IAM role policy:{  "Version": "2012-10-17",  "Statement": [    {      "Sid": "VisualEditor0",      "Effect": "Allow",      "Action": [        "kms:Decrypt",        "kms:GenerateDataKey*"      ],      "Resource": "*"    }  ]}
Question: How do I create an AMI that is based on my EBS-backed EC2 instance?

I want to create a backup or launch multiple copies of my Amazon Elastic Compute Cloud (Amazon EC2) instance, or I received a maintenance notification suggesting that I create an Amazon Machine Image (AMI) of my instance.

ResolutionAmazon Machine Images (AMIs) are archival copies of instances that you can use to launch other instances. You can use custom AMIs to launch multiple copies of an Amazon EC2 instance that is backed by an Amazon Elastic Block Store (Amazon EBS). You can also use a custom AMI as a backup solution.By default, when you create an AMI from an instance, snapshots are made of each EBS volume attached to the instance. AMIs can launch with multiple EBS volumes attached. This allows you to replicate both an instance's configuration and the state of all the EBS volumes that are attached to that instance.Note: Instances created from AMIs don't retain or copy any data stored in instance store volumes. The source instance that you create the AMI from retains all data that's stored in the instance store.To create an AMIIf your instance is running Linux, then follow the instructions at Create an Amazon EBS-Backed Linux AMI.If your instance is running Windows, then see Create a custom Windows AMI.Note: To maintain data consistency, your instance reboots during the AMI creation process. During the reboot, the public IP address and instance store volumes for your instance remain the same. You can choose the NoReboot option when creating an AMI to prevent the EC2 instance from rebooting. This option can affect the filesystem integrity of the AMI.Related information(Linux) Amazon Machine Images (AMIs)(Windows) Amazon Machine Images (AMI)Shared AMIsHow can I restrict access to launch Amazon EC2 instances from only tagged AMIs?Controlling access during AWS requests
Question: Why did GuardDuty report the finding HIDDEN_DUE_TO_SECURITY_REASONS?

Amazon GuardDuty findings or AWS CloudTrail logs display the user name as "HIDDEN_DUE_TO_SECURITY_REASONS".

ResolutionSuccessful and failed sign-in attempts for Identity and Access Management (IAM) users and federated users to the AWS Management Console are logged in CloudTrail logs. As a security best practice, AWS doesn't log the entered IAM user name text when the sign-in failure is caused by an incorrect user name. The user name text shows a GuardDuty finding or CloudTrail log entry as "HIDDEN_DUE_TO_SECURITY_REASONS", similar to the following sign-in failure event log example.For more information, see Logging user sign-in events.

Related informationSecurity best practices in IAMCloudTrail userIdentity element
Question: How do I add a promotional code to my AWS account?

I received a promotional code or credit for AWS services. I want to add it to my AWS account.

ResolutionYou can add a promotional code to your AWS account by doing the following:Open the Credits page of the Billing and Cost Management console.Choose Redeem credit.For Promotion code, enter the promotion code as it appears.For Security code, enter the code shown in the CAPTCHA.Choose Redeem credit.If the promotional code was entered correctly, is valid, hasn't expired, and hasn't been previously redeemed, it is added automatically to your AWS account.If you're a part of the AWS Partner Network (APN) and have questions on earning or redemption of credits, contact the APN team.

Related informationRedeem your AWS promotional credit
Question: How long does it take to create a backup for my RDS for SQL Server instance?

I want to create a backup for my Amazon Relational Database (Amazon RDS) for Microsoft SQL Server DB instance. How long does the backup process take?ResolutionThe time it takes to create a backup for your DB instance depends on the database workload. Higher database workload increases the number of incremental changes in the volume, which result in a longer backup time.In Amazon RDS for SQL Server, you can back up your DB instances using RDS automated backups, manual  RDS DB snapshots and native SQL backups.RDS automated backups and manual DB snapshots: These are storage volume snapshots of your DB instance that back up the entire DB instance. The first backup of a DB instance contains the data for the full DB instance. Subsequent backups of the same DB instance are incremental, meaning that only the data that changed after your most recent snapshot is saved.Native SQL backups: You can create full and differential backups of your DB instance, and then store the file in Amazon Simple Storage Service (Amazon S3) buckets. You can also create backups of individual databases on your DB instance.In some scenarios, your DB instance might require a full backup instead of an incremental backup. This might be the case after a Multi-Availability Zone failover or after you turn on RDS automated backups. Creating a full backup might take considerably longer. Other factors that increase back up time including the following:CPU and memory availabilityDisk I/ODatabase activitySize of the databaseCheck the progress of a native backup or restoreTo check the progress of native backup or restore, get the Task ID after you perform the backup or restore statement. Or, use the following script to identify all of the completed and pending tasks for a particular database. In the following command, replace database_name with the correct name for your database.exec msdb.dbo.rds_task_status @db_name='database_name'To track the status of the job, use the following SQL statement as a guide. In the following command, replace task_id with the correct ID for your task.exec msdb..rds_task_status @task_id= 5For more information, see Setting up for native backup and restore.Check the progress of a manual DB snapshotTo check the progress of manual DB snapshot, do the following:Open the RDS console.Select Snapshots.Select the snapshot you want to check the progress for, then select the Progress tab.Note: You can't check the progress of an RDS automated backup from the RDS console or using the AWS Command Line Interface (AWS CLI). Contact AWS Support for this information.
Question: What browsers are supported for use with the AWS Management Console?

Is my browser supported for use with the AWS Management Console?ResolutionThe AWS Management Console supports the following browsers:BrowserVersionGoogle ChromeLatest three major versionsMozilla FirefoxLatest three major versionsMicrosoft EdgeLatest three major versionsApple Safari for macOSLatest three major versions

Related informationWhat is the AWS Management Console?