VishaalY/solutions-architect-hf-dataset huggingface dataset:
Question: How do I truncate the sys.aud$ table on my Amazon RDS DB instance that is running Oracle?

How do I truncate the sys.aud$ table on my Amazon Relational Database Service (Amazon RDS) DB instance that is running Oracle?ResolutionTo truncate thesys.aud$ table, run the following command as the master user:SQL> exec rdsadmin.rdsadmin_master_util.truncate_sys_aud_table;If the procedure is successful, you receive output similar to the following:PL/SQL procedure successfully completed.SQL> select count(*) from sys.aud$; COUNT(*)----------         0Note: Truncating the table requires that your RDS DB instance can run the TRUNCATE_SYS_AUD_TABLE procedure as a master user. Oracle versions 12.1.0.2.v2 and 11.2.0.4.v6, as well as subsequent versions, support this operation.If the preceding command is unsuccessful, contact AWS Support for assistance. To determine what kind of assistance AWS Support needs to provide, run the following commands and then note their output:1.    Run the following command to determine if the TRUNCATE_SYS_AUD_TABLE procedure is available on your RDS DB instance:SQL> desc rdsadmin.rdsadmin_master_utilIf your RDS DB instance has theTRUNCATE_SYS_AUD_TABLE procedure, then you receive output similar to the following:FUNCTION IS_DML_ENABLED RETURNS BOOLEANPROCEDURE TRUNCATE_SYS_AUD_TABLEPROCEDURE TRUNCATE_SYS_FGA_LOG_TABLE2.    Run the following command to determine if theRDS_MASTER_ROLE role is available on your RDS DB instance:SQL> select role from dba_roles where role='RDS_MASTER_ROLE';If the RDS_MASTER_ROLE role is available on your RDS DB instance, then you receive output similar to the following:ROLE--------------------------------------------RDS_MASTER_ROLE3.    Run the following command to verify that the master user has permissions to run the TRUNCATE_SYS_AUD_TABLE procedure:SQL> select granted_role, grantee, admin_option from dba_role_privs where granted_role='RDS_MASTER_ROLE';If the master user has permissions to run the TRUNCATE_SYS_AUD_TABLE procedure, then you receive output similar to the following:GRANTED_ROLE         GRANTEE              ADM-------------------- -------------------- ---RDS_MASTER_ROLE      SYS                  YESRDS_MASTER_ROLE      MASTER_USER          NORelated informationOracle on Amazon RDSCommon DBA tasks for Oracle DB instances
Question: How can I disable public access for an AWS DMS replication DB instance?

How can I disable public access for an AWS Database Migration Service (AWS DMS) replication instance?Short descriptionAn AWS DMS replication instance can have one public IP address and one private IP address, just like an Amazon Elastic Compute Cloud (Amazon EC2) instance that has a public IP address.To use a public IP address, choose the Publicly accessible option when you create your replication instance. Or specify the --publicly-accessible option when you create the replication instance using the AWS Command Line Interface (AWS CLI).If you uncheck (disable) the box for Publicly accessible, then the replication instance has only a private IP address. As a result, the replication instance can communicate with a host that is in the same Amazon Virtual Private Cloud (Amazon VPC) and that can communicate with the private IP address. Or the replication instance can communicate with a host that is connected privately, for example, by VPN, VPC peering, or AWS Direct Connect.After you create the replication instance, you can't modify the Publicly accessible option.

ResolutionNote: If you receive errors when running AWS CLI commands, make sure that you’re using the most recent version of the AWS CLI.To disable public access to your replication instance, delete the replication instance and then recreate it. Before you can delete a replication instance, you must delete all the tasks that use the replication instance.Instead of recreating the replication instance, you can change the subnets that are in the subnet group that is associated with the replication instance to private subnets. A private subnet is a subnet that isn't routed to an internet gateway. Instances in a private subnet can't communicate with a public IP address, even if they have a public IP address. For more information, see Setting up a network for a replication instance.

Related informationWorking with an AWS DMS replication instance
Question: How do I sign up for an AWS Support plan?

I'd like to speak with AWS support engineers about my resources. How do I sign up for an AWS Support plan?ResolutionTo sign up for an AWS Support plan, you must sign in with:AWS account root user credentials-or-AWS Identity and Access Management (IAM) user credentials with access permissions for AWS Support plans. For more information, see Manage access for AWS Support Plans.To sign up for an AWS Support plan, do the following:Open AWS Support Plans.(Optional) On the Support Plans page, compare the Support plans. For pricing information, see AWS Support Plan pricing.Under AWS Support pricing example, choose See examples, and then choose one of the Support plan options to see the estimated cost.Choose Review downgrade or Review upgrade for the plan that you want. Important: If you have an Enterprise On-Ramp or Enterprise Support plan, on the Change plan confirmation dialog box, choose Contact us, fill in the form, and then choose Submit.For Change plan confirmation, expand the support items to see the features included with the plan.Under Pricing, you can view the projected one-time charges for the new Support plan.Choose Accept and agree.If the Support plan that you choose has a monthly cost associated with it, then your payment method is automatically charged the prorated monthly cost according to the days remaining in the current month. When this charge is processed, your AWS Support subscription is activated within a few hours.To learn about the benefits and costs of the available AWS Support plans, visit AWS Support.

Related informationHow do I change my AWS Support plan?
Question: Why can't I delete my snapshot in Amazon Redshift?

I'm trying to delete a snapshot of my Amazon Redshift cluster. However, I receive an error message indicating that my snapshot is accessible by another AWS account. How do I resolve this?Short descriptionIf you're trying to delete a snapshot that shares access with another AWS account, you might encounter the following error message:"Cannot delete the snapshot- xxx-xxx-xxx because other accounts still have access to it."To resolve this error message, remove the shared access from the AWS account that created the cluster snapshot in Amazon Redshift. Then, delete your cluster snapshot.

ResolutionTo delete a shared cluster snapshot using the Amazon Redshift console, perform the following steps:1.    Sign in to the AWS Management Console with the AWS account that created the cluster snapshot.2.    Open the Amazon Redshift console.3.    From Clusters, choose the snapshot that you want to delete.4.    Choose Actions.5.    Choose Manage Access to view the access settings for your cluster.6.    Choose Remove Account to delete the shared access of your cluster snapshot.7.    Delete your cluster snapshot.To delete a shared cluster snapshot using the AWS Command Line Interface (AWS CLI), perform the following steps:Note: If you receive errors when running AWS CLI commands, make sure that you’re using the most recent AWS CLI version.1.    Revoke the shared snapshot access using the revoke-snapshot-access command:aws redshift revoke-snapshot-access --snapshot-id my-snapshot-id --account-with-restore-access <AWS-account-id-with-access>2.    Delete your Amazon Redshift cluster snapshot using the delete-cluster-snapshot command:aws redshift delete-cluster-snapshot --snapshot-identifier my-snapshot-id
Question: How do I find out if my Amazon EC2 Reserved Instances are being fully used?

I've purchased some Amazon Elastic Compute Cloud (Amazon EC2) Reserved Instances for my account, and I'd like to be sure that I'm getting the maximum benefit from them. How do I find out if my Reserved Instances (RIs) are being fully utilized?ResolutionTo see the billing hours that are covered by your Amazon EC2 RIs, do the following:Open the Billing and Cost Management console.Choose Bills in the navigation pane.You can view the charges for different services in the Details section.Expand the Elastic Compute Cloud section and the AWS Region to view the billing information about your RIs.You can view the Reserved Instance types and billing hours for your RIs.You can use Cost Explorer reports or Amazon EC2 usage reports to understand more about the utilization of your Reserved Instances. You can use the RI Utilization and RI Coverage reports in Cost Explorer to:Track the number of RI hours used against the number of RI hours purchasedTrack the number of hours covered by RIs against the On Demand hours in the tableTrack the number of RI hours that you have reserved but did not useFor information on how to use Cost Explorer to view your RI utilization and coverage, see How can I use Cost Explorer to analyze my spending and usage?Related informationCreating Cost and Usage ReportsUnderstanding your reservations with Cost ExplorerHow Reserved Instances are applied
Question: How can I stop Route 53 health check requests that are sent to my application?

How can I stop Amazon Route 53 health check requests that are sent to my application?Short descriptionYou can configure Route 53 health checks against any public resource. If your application is receiving health check requests from Route 53 when you haven't configured health checks on your application, the cause might be:A health check was mistakenly configured against your application by another customer.A health check was configured from your account for testing purposes but wasn't deleted when testing was complete.A health check was configured against another customer's public AWS resources. However, the IP addresses of those resources were reassigned to your AWS resources. In this scenario, the health check was configured on the reassigned IP addresses. If the health check was based on domain names, the requests were sent due to DNS caching.The Elastic Load Balancing service updated its public IP addresses due to scaling, and the IP addresses were reassigned to your load balancer.

ResolutionTo stop unwanted health checks requests from Route 53:Find the ID of the unwanted health check by reviewing your application logs. For more information, see How can I identify and resolve unwanted health checks from Route 53?Contact AWS. If you have an AWS Support plan, create a support case. If you don't have an AWS Support plan, complete the Stop unwanted Amazon Route 53 health checks form. In both scenarios, be sure to include the health check ID that you found in step 1.(Optional) Block the health check IP address ranges in your firewall. To find the IP address ranges for each AWS Region used by the Route 53 health check service, see the IP ranges JSON file. In the JSON file, search for "ROUTE53_HEALTHCHECKS". For more information, see Configuring router and firewall rules for Amazon Route 53 health checks.
Question: How do I organize my AWS resources?

I want to organize my AWS resources so that I can manage them as a group.

ResolutionYou can use AWS Resource Groups to organize and manage your AWS resources that are in the same AWS Region. With Resource Groups, you can automate tasks, such as applying security patches and updates, on a group of AWS resources at the same time.To create AWS CloudFormation stack-based Resource Groups, see Create an AWS CloudFormation stack-based group.To create tag-based Resource Groups, see Build a tag-based query and create a group.You can add tags to most of your resources to help identify and sort your resources within your organization. You can add these tags when you create or edit your AWS resources. Also, you can add tags to supported resources using Tag Editor.You can also access Resource Groups by opening the AWS Systems Manager console, and then choosing Resource Groups & Tag Editor from the navigation pane.

Related informationResources you can use with AWS Resource Groups and Tag EditorAmazon Resource Names (ARNs)
Question: I enabled public access on my bucket's ACL using the Amazon S3 console. Is my bucket open to everyone?

I used the Amazon Simple Storage Service (Amazon S3) console to update my bucket's access control list (ACL) to allow public access. Can anyone access my bucket?ResolutionEven if you enable all available ACL options in the Amazon S3 console, the ACL alone won't allow everyone to download objects from your bucket. However, depending on which option you select, any user could perform these actions:If you select List objects for the Everyone group, then anyone can get a list of objects that are in the bucket.If you select Write objects, then anyone can upload, overwrite, or delete objects that are in the bucket.If you select Read bucket permissions, then anyone can view the bucket's ACL.If you select Write bucket permissions, then anyone can change the bucket's ACL.For more information, see What permissions can I grant?To prevent any accidental change to public access on a bucket's ACL, you can configure public access settings for the bucket. If you select Block new public ACLs and uploading public objects, then users can't add new public ACLs or upload public objects to the bucket. If you select Remove public access granted through public ACLs, then all existing or new public access granted by ACLs is respectively overridden or denied.Important: Granting cross-account access through bucket and object ACLs doesn't work for buckets that have S3 Object Ownership set to Bucket Owner Enforced. In most cases, ACLs aren't required to grant permissions to objects and buckets. Instead, use AWS Identity Access and Management (IAM) policies and S3 bucket policies to grant permissions to objects and buckets.

Related informationUsing Amazon S3 Block Public AccessManaging access with ACLs
Question: Why am I seeing "Error" in the Access field for some buckets in the Amazon S3 console?

I'm using the Amazon Simple Storage Service (Amazon S3) console to view buckets. Why am I seeing "Error" in the Access field for certain buckets?ResolutionThe bucket list view in the Amazon S3 console includes an Access column that provides information about public access to each bucket. To see the Access value, the AWS Identity and Access Management (IAM) user or role using the console must have the following permissions to each bucket:s3:GetAccountPublicAccessBlocks3:GetBucketPublicAccessBlocks3:GetBucketPolicyStatuss3:GetBucketAcls3:ListAccessPointsIf the IAM identity (user or role) doesn't have the required permissions, then the identity sees "Error" in the Access field. This is also true if the identity explicitly is denied access to the required permissions.To allow an IAM identity to see Access values in the Amazon S3 console, add the required permissions to the user's or role's policy.Note: Because of eventual consistency, a bucket that recently was deleted might appear in the console with "Error" in the Access field. To confirm that a bucket was deleted, check the AWS CloudTrail event history for DeleteBucket events.
Question: How can I get my AWS::ECS::Service resources out of UPDATE_IN_PROGRESS or UPDATE_ROLLBACK_IN_PROGRESS status?

My AWS CloudFormation stack update to the AWS::ECS::Service resource got stuck in UPDATE_IN_PROGRESS or UPDATE_ROLLBACK_IN_PROGRESS status. I want to stabilize the stack and get my service to launch new tasks.

Short descriptionYour Amazon Elastic Container Service (Amazon ECS) service can get stuck in UPDATE_IN_PROGRESS or UPDATE_ROLLBACK_IN_PROGRESS status when the service fails to launch tasks.Here are some common reasons why an Amazon ECS service can fail to launch new tasks:Container image issuesA lack of necessary resources for launching tasksA health check failure on a load balancerInstance configuration or Amazon ECS container agent issuesAn Amazon ECS service that fails to launch tasks causes AWS CloudFormation to get stuck in UPDATE_IN_PROGRESS status. Then, AWS CloudFormation waits for several hours before rolling back to a previous configuration. If the issue that's causing stack failure continues during stack rollback to a previous configuration, then the stack gets stuck in UPDATE_ROLLBACK_IN_PROGRESS status. Finally, the stack changes to UPDATE_ROLLBACK_FAILED status.It can take the AWS CloudFormation stack several hours to stabilize. To stabilize your stack more quickly, complete the following steps.Important: The following resolution is intended to help you stabilize an AWS CloudFormation stack quickly without waiting for the stack to time out. The resolution isn't intended for production environments, as the Amazon ECS service is out of sync with the known state of AWS CloudFormation. To sync resources between your Amazon ECS service and the AWS CloudFormation stack, you must perform an error-free update on the stack.

ResolutionChange the desired task count of the Amazon ECS serviceOpen the Amazon ECS console.Choose your cluster.Select the service, and then choose Update.Set Number of tasks to 0, and then save the configuration.Identify why the Amazon ECS service can't launch new tasksOpen the Amazon ECS console.Choose your cluster.Select the service, and then choose Events.Note: The Events section displays the reason why your service didn't stabilize.Choose a solution based on the issue that you identified:Your task failed Elastic Load Balancing (ELB) health checks.A container marked as essential for the task definition exited or died.You can't place a task because your container instance didn't meet the necessary requirements.You receive a "cannot pull container image" error.
Question: How can I access my Amazon SES logs?

I send emails using Amazon Simple Email Service (Amazon SES), and I want to get logs or notifications for bounces, complaints, delivery, failures, or rejections.

Short descriptionTo get logs or notifications about your email-sending events on Amazon SES, use one of the following mechanisms:Email feedback forwardingAmazon Simple Notification Service (Amazon SNS) topic for event notificationsConfiguration set to publish email-sending events to Amazon SNS, Amazon CloudWatch, Amazon Pinpoint, or Amazon Kinesis Data FirehoseNote: These mechanisms don't provide logs for emails that you sent before you implemented the mechanism.

ResolutionUse email feedback forwardingBy default, Amazon SES sends you a notification when a message that you send bounces or gets a complaint. The destination that you check for the bounce or complaint notifications depends on your email-sending operation. For more information, see Email feedback forwarding destination.If you de-activated email feedback forwarding, then you can re-activate feedback forwarding using the Amazon SES console.Use an Amazon SNS topic to send event notificationsYou can use an Amazon SNS topic for notifications about Amazon SES email delivery, bounces, or complaints.Follow these steps to configure an Amazon SNS topic for Amazon SES events:Create an Amazon SNS topic.Subscribe an endpoint (such as an email address) to receive notifications from the Amazon SNS topic.Configure your Amazon SES verified identity (domain or email address) to send event notifications to the Amazon SNS topic that you created. You can do this using either the Amazon SES console or the Amazon SES API.After you configure an Amazon SNS topic for Amazon SES event notifications, you receive notifications at the endpoint that you subscribed to the topic. For more information on the details in the notifications, see Amazon SNS notification contents for Amazon SES and Amazon SNS notification examples for Amazon SES.Note: Amazon SES doesn't support FIFO type topics.Use a configuration set to publish email-sending events to Amazon SNS, CloudWatch, Amazon Pinpoint, or Kinesis Data FirehoseUse an Amazon SES configuration set that publishes events to get information about the following outcomes:SendsRejectsHard bouncesComplaintsDeliveriesDelivery delaysSubscriptionsOpensClicksRendering failuresFor details about each outcome, see Event publishing terminology.To create the configuration set, first specify the event destination, and then specify the parameters for the events that you want to publish. For step-by-step instructions, see Setting up Amazon SES event publishing.Make sure that you configure your email-sending method to pass the name of the configuration set in the headers of your emails. This is required for Amazon SES to apply the configuration set to your emails. For more information, see Specifying a configuration set when you send email. You can also assign a default configuration set to the verified identity that's used as the From/Source address. Then, messages that you send from this identity automatically use the assigned default configuration set.
Question: How can I configure automatic scaling in Amazon EMR?

I want to use Amazon Elastic Compute Cloud (Amazon EC2) Auto Scaling on an Amazon EMR cluster.

Short descriptionAmazon EMR versions 5.30.0, 6.1.0, and later: Use Amazon EMR managed scaling. Or, use automatic scaling with a custom policy for instance groups.Amazon EMR versions 4.0.0-5.29.0 and 6.0.0: Use automatic scaling with a custom policy for instance groups.

ResolutionAmazon EMR versions 5.30.0, 6.1.0, and laterIf you're using Amazon EMR 5.30.0, 6.1.0, or later versions, then you have two options for automatic scaling: turn on Amazon EMR managed scaling to automatically increase or decrease the number of instances or units in your cluster based on workload. Or, use automatic scaling with a custom policy for instance groups, as explained in the following section.Amazon EMR versions 4.0.0 and laterFollow the steps at Using automatic scaling with a custom policy for instance groups. For information about the Amazon CloudWatch metrics that you can use for automatic scaling in Amazon EMR, see Monitor metrics with CloudWatch. The following are two commonly used metrics for automatic scaling:YarnMemoryAvailablePercentage: This is the percentage of remaining memory that's available for YARN.ContainerPendingRatio: This is the ratio of pending containers to allocated containers. You can use this metric to scale a cluster based on container-allocation behavior for varied loads. This is useful for performance tuning.To confirm that the scaling policy is attached to the instance group, choose Events from the navigation pane.Check for automatic scaling policy events.

Related informationScaling cluster resources
Question: How do I increase Amazon WorkSpaces quotas?

I want to increase my service quota for Amazon WorkSpaces. How can I do this?Short descriptionAmazon WorkSpaces-based resources in your AWS account have default quotas (also known as service limits). For more information, see Amazon WorkSpaces quotas.

ResolutionTo request a quota increase, do the following:Open the WorkSpaces Limits form.Select the Region.Select the Limit type you're requesting a quota increase for. For example, Max WorkSpaces.Note: Graphics and Graphics Pro bundles are supported in the following Regions: US East (N. Virginia), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Sydney), Asia Pacific (Tokyo), and Asia Pacific (Singapore). You can request quota increases for Graphics and Graphics Pro in these Regions only.Enter the New Limit Value.Select Add another request to enter another increase request for the same limit type.Enter the Use Case Description explaining why you're requesting a limit increase.Note: Request for more than 200 WorkSpaces or more than 20 Graphics/Graphics Pro WorkSpaces require additional information. Make sure you answer the additional questions listed within the request form in your use case description.Enter Contact options.Select Submit.

Related informationTroubleshoot WorkSpaces issues