VishaalY/solutions-architect-hf-dataset huggingface dataset:
Question: How can I update the WorkSpace image in a custom bundle?

I want to update the application installed in the Amazon WorkSpaces image associated with a custom WorkSpaces bundle. How can I do this?ResolutionYou can update an existing custom WorkSpaces bundle by:Modifying the WorkSpace that is based on the bundle.Creating an image from the WorkSpace.Updating the bundle with the new image.You can then launch new WorkSpaces using the updated bundle.For a detailed tutorial, see Update a custom WorkSpaces bundle.
Question: How can I resolve the error "Unknown dataset URI pattern: dataset" when exporting Amazon RDS data to Amazon S3 in Parquet format using Sqoop?

I'm trying to use an Amazon EMR cluster to export Amazon Relational Database Service (Amazon RDS) data to Amazon Simple Storage Service (Amazon S3) in Apache Parquet format using Apache Sqoop. I'm using the --as-parquetfile parameter, but I keep getting this error:"Check that JARs for s3a datasets are on the class path org.kitesdk.data.DatasetNotFoundException: Unknown dataset URI pattern: dataset."Short descriptionThis error affects Sqoop version 1.4.7. To resolve the error, download and install the kite-data-s3-1.1.0.jar.

ResolutionNote: The following solution was tested on Amazon EMR release version 5.34.0 and Sqoop version 1.4.7.1.    Connect to the master node using SSH.2.    Use wget to download the kite-data-s3-1.1.0.jar:[hadoop@ip-xxx-xx-xx-x]$ wget https://repo1.maven.org/maven2/org/kitesdk/kite-data-s3/1.1.0/kite-data-s3-1.1.0.jar3.    Confirm that the downloaded file is the correct size (1.7 MB):[hadoop@ip-xxx-xx-xx-x]$ du -h1.7M     /usr/lib/sqoop/lib/kite-data-s3-1.1.0.jar4.    Move the JAR to the Sqoop library directory ( /usr/lib/sqoop/lib/):sudo cp kite-data-s3-1.1.0.jar /usr/lib/sqoop/lib/5.    Grant permission on the JAR:sudo chmod 755 kite-data-s3-1.1.0.jar6.    Use the s3n connector to import the jar. If you use the s3 connector, you get the Unknown dataset URI pattern: dataset error.sqoop import --connect jdbc:mysql://mysql.cdfqbesrukqe.eu-west-1.rds.amazonaws.com:8193/dev --username admin -P --table hist_root --target-dir "s3n://awsexamplebucket/sqoop_parquet/demo" --as-parquetfile -m 2 --split-by identifiers -- --schema onwatchFor more information about the Kite SDK dataset URI, see Dataset, view, and repository URIs.
Question: I can't sign in because my credentials don't work

I tried to sign in, but the credentials I used didn't work.

ResolutionThe following scenarios often cause problems with account credentials:You forgot the credentials for the account.You accidentally use the incorrect credentials to sign in. For example, you use the credentials for the wrong account or AWS Identity and Access Management (IAM) identity.An authorized user changed the credentials. For example, your account administrator updated your IAM credentials.Recovering a forgotten passwordTo recover a password, you must know the email address or account number that's associated with the account. You must also have access to the email address to receive an email with instructions on how to reset the password.For instructions, see How do I recover a lost or forgotten AWS password?Finding the email address for an accountCheck any email addresses you might have used to open an AWS account. Most account-related correspondence from AWS comes from no-reply-aws@amazon.com. If you find correspondence like this, then the email address is probably associated with an AWS account.Ask other members of your team, organization, or family. If someone you know created the account, then they can help you get access.Recovering IAM credentialsContact your account administrator. Your account administrator sets the credentials for each IAM entity on the account.Some IAM identities can update their own passwords. For more information, see How an IAM user changes their own password.Note: AWS Support can't discuss the details of any AWS account other than the account that you're signed in to. AWS Support can't change the credentials associated with an account for any reason.For more information, see Troubleshooting sign-in issues.Receiving account supportIf the previous methods don't work and you still can't access your account, then contact AWS Support with the Amazon Web Services Support form.

Related informationWhat do I do if I receive an error when entering the CAPTCHA to sign in to my AWS account?AWS security credentialsManaging user passwords in AWSHow do I remove a lost or broken MFA device from my AWS account?
Question: How do I include my dedicated IP address as part of my default IP pool on Amazon SES?

I have dedicated IP addresses on Amazon Simple Email Service (Amazon SES). How can I send my emails using a dedicated IP address from my default IP address pool?ResolutionIf you haven't assigned a dedicated IP address to an IP pool, then the dedicated IP address is already included in the default IP pool (named ses-default-dedicated-pool). Additionally, if you don't specify an IP pool in your configuration set, then Amazon SES uses one of the dedicated IP addresses from ses-default-dedicated-pool.To modify an existing configuration set to explicitly specify the use of ses-default-dedicated-pool, follow these steps:Open the Amazon SES console.From the navigation pane, under Email Sending, choose Configuration Sets.Choose the configuration set that you want to associate with ses-default-dedicated-pool.Choose the Sending IP Pool tab. Then, for Pool name, select ses-default-dedicated-pool.Choose Finish.Note the following important considerations for using a configuration set and dedicated IP addresses:For a configuration set to apply to emails, you must pass the name of the configuration set in the email headers. For more information, see Specifying a Configuration Set When You Send Email.It's a best practice to attach the default IP pool to the configuration set only after the dedicated IP addresses are warmed up. Amazon SES automatically warms up your dedicated IP addresses by gradually increasing the number of emails sent from the IP addresses. Or, you can also choose to disable the automatic warm-up process so that you can manually warm up your IP addresses. While the dedicated IP addresses are warming up, avoid sending emails explicitly using the default IP pool associated with a configuration set. This impacts the warm-up process and can result in ISPs throttling emails coming from those IP addresses.Related InformationAssigning an IP Pool to an Existing Configuration Set
Question: How do I monitor my Amazon OpenSearch Service cluster using CloudWatch alarms?

I want to monitor my Amazon OpenSearch Service cluster for stability issues. How can I effectively monitor my cluster?ResolutionImportant: Different versions of Elasticsearch use different thread pools to process calls to the _index API.Elasticsearch versions 1.5 and 2.3 use the index thread pool.Elasticsearch versions 5.x, 6.0, and 6.2 use the bulk thread pool. (Currently, the OpenSearch Service console doesn't include a graph for the bulk thread pool.)Elasticsearch versions 6.3 and later use the write thread pool.To monitor the health of your OpenSearch Service cluster, set the recommended Amazon CloudWatch alarms and the following OpenSearch Service cluster metric alarms:MasterReachableFromNodeKibanaHealthyNodesDiskQueueDepthThreadpoolIndexQueueThreadpoolSearchQueueYou can configure your OpenSearch Service metric alarms like this:MasterReachableFromNode:Statistic = MaximumValue = ‘=0’Frequency = 1 periodPeriod = 1 minuteIssue: Leader node is down.KibanaHealthyNodes:Statistic = AverageValue = ‘=0’Frequency = 1 periodPeriod = 1 minuteIssue: Indicates that the kibana index is unhealthy.DiskQueueDepth:Statistic = AverageValue = ‘>=100'Frequency = 1 periodPeriod = 5 minutesIssue: Disk Queue Depth is the number of I/O requests that are queued at a time against the storage. This could indicate a surge in requests or Amazon EBS throttling, resulting in increased latency.ThreadpoolIndexQueue and ThreadpoolSearchQueue:Statistic = MaximumValue = ‘>=20’Frequency = 1 periodPeriod = 1 minuteIssue: Indicates that there are requests getting queued up, which can be rejected. To verify the request status, check the CPU Utilization and Threadpool Index or Search rejects.To set up an Amazon CloudWatch alarm for your OpenSearch Service cluster, perform the following steps:1.    Open the Amazon CloudWatch console.2.    Go to the Alarm tab.3.    Choose Create Alarm.4.    Choose Select Metric.5.    Choose ES for your metric.6.    Select Per-Domain and Per-Client Metrics.7.    Select a metric and choose Next.8.    Configure the following settings for your Amazon CloudWatch alarm:Statistic = MaximumPeriod to 1 minuteThreshold type = StaticAlarm condition = Greater than or equal toThreshold value = 19.    Choose the Additional configuration tab.10.    Update the following configuration settings:Datapoints to alarm = Frequency stated aboveMissing data treatment = Treat missing data as ignore (maintain the alarm state)11.    Choose Next.12.    Choose the action that you want your alarm to take, and choose Next.13.    Set a name for your alarm, and then choose Next.14.    Choose Create Alarm.Note: If the alarm is triggered for CPUUtilization or JVMMemoryPressure, check your Amazon CloudWatch metrics to see if there's a spike coinciding with incoming requests. In particular, monitor these Amazon CloudWatch metrics: IndexingRate, SearchRate, and OpenSearchRequests.

Related informationClusterBlockExceptionUsing Amazon CloudWatch alarms
Question: How can I use AWS DMS to migrate data to Amazon S3 in Parquet format?

How can I use AWS Database Migration Service (AWS DMS) to migrate data in Apache Parquet (.parquet) format to Amazon Simple Storage Service (Amazon S3)?ResolutionNote: If you receive errors when running AWS Command Line Interface (AWS CLI) commands, make sure that you’re using the most recent AWS CLI version.You can use AWS DMS to migrate data to an S3 bucket in Apache Parquet format if you use replication 3.1.3 or a more recent version. The default Parquet version is Parquet 1.0.1.    Create a target Amazon SE endpoint from the AWS DMS Console, and then add an extra connection attribute (ECA), as follows. Also, check the other extra connection attributes that you can use for storing parquet objects in an S3 target.dataFormat=parquet;Or, create a target Amazon S3 endpoint using the create-endpoint command in the AWS Command Line Interface (AWS CLI):aws dms create-endpoint --endpoint-identifier s3-target-parque --engine-name s3 --endpoint-type target --s3-settings '{"ServiceAccessRoleArn": <IAM role ARN for S3 endpoint>, "BucketName": <S3 bucket name to migrate to>, "DataFormat": "parquet"}'2.    Use the following extra connection attribute to specify the Parquet version of output file:parquetVersion=PARQUET_2_0;3.    Run the describe-endpoints command to see if the S3 endpoint that you created has the S3 setting DataFormat or the extra connection attribute dataFormat set to "parquet". To check the S3 setting DataFormat, run a command similar to the following:aws dms describe-endpoints --filters Name=endpoint-arn,Values=<S3 target endpoint ARN> --query "Endpoints[].S3Settings.DataFormat"[    "parquet"]4.    If the value of the DataFormat parameter is CSV, then recreate the endpoint.5.    After you have the output in Parquet format, you can parse the output file by installing the Apache Parquet command line tool:pip install parquet-cli --user6.    Then, inspect the file format:parq LOAD00000001.parquet  # Metadata  <pyarrow._parquet.FileMetaData object at 0x10e948aa0>  created_by: AWS  num_columns: 2  num_rows: 2  num_row_groups: 1  format_version: 1.0  serialized_size: 1697.    Finally, print the file content:parq LOAD00000001.parquet --head   i        c0  1  insert11  2  insert2Related informationUsing Amazon S3 as a target for AWS Database Migration Service
Question: Why are properly functioning Amazon ECS tasks registered to ELB marked as unhealthy and replaced?

Elastic Load Balancing (ELB) is repeatedly flagging properly functioning Amazon Elastic Container Service (Amazon ECS) tasks as unhealthy. These incorrectly flagged tasks are stopped, and then new tasks are started instead.

Short descriptionSome Amazon ECS tasks have several dependencies and lengthy bootstrapping processes that can exceed the ELB health check grace period, even when functioning as intended. When Amazon ECS tasks don't respond to ELB health checks within the grace period, they're flagged as unhealthy. To increase the health check grace period for your service, complete the following steps.To troubleshoot ECS tasks failing an Application Load Balancer health check, see How can I get my Amazon ECS tasks running using the Amazon EC2 launch type to pass the Application Load Balancer health check in Amazon ECS?ResolutionIf no grace period is configured, then the service scheduler immediately replaces any targets marked as unhealthy. Change the grace period to allow more time for your Amazon ECS tasks to complete their processes and pass the health check.Note: To change the grace period, use the earlier version of the ECS console. To change to the earlier version of the console, toggle off New ECS Experience at the top of the navigation pane. Then, complete the following steps.Open the AWS Management Console.In the navigation bar, choose Services, and then select ECS from the list.Select your service from the Service Name list.Choose Update.Choose Next step.On the Step 2: Configure network page, change the Health check grace period to an appropriate time period for your service. The maximum time period is 2,147,483,647 seconds.Caution: To prevent delayed replacement of legitimately unhealthy Amazon ECS tasks, carefully estimate the required grace period for your lengthiest tasks. When setting your grace period, consider all relevant factors, such as bootstrap time and time to pull container images.Choose Next step, and then choose Update Service.You can also use these ways to increase the grace period:Use the HealthCheckGracePeriodSeconds parameter defined in the AWS::ECS::Service resource in AWS CloudFormation.Run the UpdateService command in the AWS Command Line Interface (AWS CLI), and increase the --health-check-grace-period-seconds value.

Related informationAmazon ECS adds ELB health check grace period
Question: How do I manage the clock source for EC2 instances running Linux?

How can I determine the clock source used by an Amazon Elastic Compute Cloud (Amazon EC2) instance running Linux, and how can I change it?Short descriptionBy using an SSH client, you can find the current clock source, list the available clock sources, or change the clock source.Note: There are many clock sources available for Hardware Virtual Machine (HVM) instances, such as Xen, Time Stamp Counter (TSC), High Precision Event Time (HPET), or Advanced Configuration and Power Interface Specification (ACPI). For EC2 instances launched on the AWS Xen Hypervisor, it's a best practice to use the tsc clock source. Other EC2 instance types, such as C5 or M5, use the AWS Nitro Hypervisor. The recommended clock source for the AWS Nitro Hypervisor is kvm-clock.Note: AWS Graviton2 processors use arch_sys_counter as the clock source.

ResolutionTo find the clock sourceOpen an SSH client into your EC2 instance, and then run the following commands to find the current and available clock sources.To find the currently set clock source, list the contents of the current_clocksource file:cat /sys/devices/system/clocksource/clocksource0/current_clocksourcexenTo list the available clock sources, list the contents of the available_clocksource file:cat /sys/devices/system/clocksource/clocksource0/available_clocksourcexen tsc hpet acpi_pmTo set the current clock source to a different value1.    Run bash as a superuser to override the current_clocksource:sudo bash -c 'echo tsc > /sys/devices/system/clocksource/clocksource0/current_clocksource'2.    Run the dmesg command to view the kernel messages:dmesg | lessIf the override was successful, this message appears:clocksource: Switched to clocksource tscNote: Rebooting the system causes the Linux kernel to reset the clock source.To permanently set the clock sourceTo permanently set the clock source, set the source in the system boot loader:1.    Set clocksource in the kernel command line parameter.For example, if you use grub2 and you want to set the clock source to "tsc", open /etc/default/grub in an editor. Then, add clocksource=tsc tsc=reliable for the GRUB_CMDLINE_LINUX option:GRUB_CMDLINE_LINUX="console=tty0 crashkernel=auto console=ttyS0,115200 clocksource=tsc tsc=reliable"2.    Generate the grub.cfg file:grub2-mkconfig -o /boot/grub2/grub.cfg

Related informationSet the time for your Linux instance
Question: How do I change domain ownership or other domain information in Route 53?

I want to change the ownership of my domain, update contact information, or troubleshoot a domain name change operation in Amazon Route 53.

ResolutionChange the domain ownerFor some domains, you can update the owner by changing the person or organization information listed for the domain. You can also update the contact information for the domain.For more information see Updating the contact information and ownership for a domain.Change ownership of a TLDWhen you change the owner of a domain, the registries for some TLDs require special processing. For these domains, submit a change of domain ownership form to AWS Support.For more information, see TLDs that require special processing to change the owner.Update ownership of multiple domains in a bulk updateTo update ownership for multiple domains to a different user, create a custom script listing all of the domain names that you want to update. Then, run the update-domain-contact AWS Command Line Interface (AWS CLI) command. Pass the script through the JSON file listed in the following example:aws route53domains update-domain-contact \    --region us-east-1 \    --cli-input-json file://C:\temp\update-domain-contact.jsonNote: If you receive errors when running AWS CLI commands, make sure that you're using the most recent version of the AWS CLI.TroubleshootingThe domain ownership email is sent to an inactive or nonexistent contactIf the domain verification email is sent to a contact that's no longer active, then the ownership change becomes stuck in the Pending status. Or, if the email is incorrect, then the change is stuck in the Domain ownership change in progress status. To resolve these issues, complete the following steps:Cancel the CHANGE_DOMAIN_OWNER operation by contacting AWS Support.After AWS Support cancels the operation, update the email address of your domain to the correct email address.Restart the CHANGE_DOMAIN_OWNER operation.

Related informationWho is the owner of a domain?
Question: How do I move my Amazon Redshift provisioned cluster from one VPC to another VPC?

I want to move an Amazon Redshift cluster from one Amazon Virtual Private Cloud (Amazon VPC) to another VPC.

Short descriptionTo move an Amazon Redshift provisioned cluster from one VPC to another:Confirm the AWS Identity and Access Management (IAM) roles and configuration details of the source cluster.Create a cluster subnet group.Take a snapshot of the source cluster.Restore the cluster to the new cluster subnet group.Associate the IAM roles.

ResolutionNote: Be sure to stop writes to the original cluster during the migration. Otherwise, some data might not be backed up to the new cluster.Confirm the IAM rolesOpen the Amazon Redshift console, and then choose CLUSTERS on the navigation pane.Select the Amazon Redshift cluster that you want to move.At the top of the page, choose the Actions dropdown list, and then choose Manage IAM roles.Note the IAM roles that are associated with your cluster. You'll associate these roles with the new cluster later.Create a cluster subnet groupCreate a cluster subnet group. For VPC, choose the ID of the VPC that you want to migrate the cluster to, and then add any associated subnets.Take a manual snapshot of the source clusterCreate a manual snapshot. For Cluster identifier, choose the cluster that you want to migrate.Restore the cluster to the new cluster subnet groupChoose the snapshot that you created, choose Restore from snapshot, and then choose Restore to provisioned cluster.Configure the properties of the new cluster. By default, Amazon Redshift automatically selects the same properties as the source cluster. Be sure that these properties are different from the source cluster:Cluster identifier  Virtual private cloud (VPC): the VPC that you want to migrate the cluster toChoose Restore.Associate the IAM rolesOn the navigation pane, choose CLUSTERS, and then choose the new cluster.Choose the Actions drop-down list, and then choose Manage IAM roles.From Available IAM roles, choose the roles that are associated with the source cluster.Choose Add IAM role, and then choose Done.After the snapshot is restored and the new cluster status changes to Available, follow these steps:Rename the old cluster (for example, "oldcluster-1").Rename the new cluster to the original cluster name (for example, "cluster-1").Resume write operations to the cluster from client applications.Delete the old cluster.

Related informationManaging clusters in a VPCWhy can't I access a VPC to launch my Amazon Redshift cluster?How do I copy an Amazon Redshift provisioned cluster to a different AWS account?
Question: How do I terminate instances in my AWS Marketplace subscription and cancel the subscription?

I want to delete the instances that are launched with my AWS Marketplace subscription and cancel the subscription.

Short descriptionHere are a few things to keep in mind while canceling your software subscription:It's a best practice to terminate all the instances associated with your software subscription before you cancel your subscription.If you cancel a subscription to a software product without terminating all running instances of the software, then you're charged for any software usage. You might also incur infrastructure related charges related to using the product.After you cancel the software subscription, you can no longer start new instances of the software, either from AWS Marketplace console or the Amazon Elastic Compute Cloud (Amazon EC2) console. If the subscription that you're canceling is for a product with a monthly fee, then you're charged a prorated amount of the monthly fee on your next bill.

ResolutionTerminate the instancesTo terminate instances in a software subscription, do the following:Sign in to the AWS Marketplace console.Choose Manage subscriptions.On the Manage subscriptions page, choose Manage next to the software subscription that you want to cancel.Choose Actions, and then choose View instances.Confirm the AWS Regions where the instances are running.Terminate all the instances from the Amazon EC2 console. For more information, see How do I delete or terminate EC2 resources?Cancel the software subscriptionAfter you terminate all the instances associated with your AWS Marketplace subscription, you can cancel the subscription by doing the following:On the Manage subscriptions page, choose Manage next to the software subscription that you want to cancel.Choose Actions, and then choose Cancel subscription.Select the check box to acknowledge that running instances are charged to your account, and then choose Yes, cancel subscription.

Related informationHow do I sell an Amazon EC2 Reserved Instance on the EC2 Reserved Instance Marketplace?