VishaalY/solutions-architect-hf-dataset huggingface dataset:
Question: How do I troubleshoot outbound caller ID issues in Amazon Connect?

In Amazon Connect, my caller ID isn't displaying as expected when making outbound calls.

Short descriptionYou can specify either a caller ID name or a caller ID number in your Amazon Connect instance. You can set a caller ID name or number in queue or by using the Call phone number block. For more information, see How to specify a custom caller ID number using a Call phone number block.Important: If you're using the Call phone number block, then you can set the custom caller ID number. However, to use this in your Amazon Connect instance you must first activate the custom caller ID in the block. To activate a custom caller ID, you must create a support case. If the instance isn't activated, then you can't set the custom caller ID in the block.

ResolutionOutbound caller ID as a nameIt's a best practice to register your outbound caller ID name and phone number in a CNAM database for US and Canada numbers. To register your US-based phone number and company name in the CNAM database of the Amazon Connect carrier, you must create a support case.Note: Amazon Web Services (AWS) offers the functionality of configuring a display name for outbound calls. However, AWS can't guarantee that the same caller ID is shown to the recipient of the call.Outbound caller ID as a numberTo troubleshoot outbound caller IDs as a number, consider the following:Make sure that the queue and contact flow where the outbound caller ID is set is correctly associated with the agent. If caller ID is set in the queue, then verify that the agent is assigned to the routing profile that's set for the caller ID.If you're setting the caller ID in queue settings and the Call phone number block, then the call phone number block takes priority. If you didn't define the call phone number block, then the caller ID in queue settings are considered. For more information, see Set up outbound caller ID.Note: The caller ID display number is offered on a best effort basis and isn't guaranteed. However, when setting the caller ID in the queue, make sure to select the DID numbers that are configured in the Amazon Connect instance. If a TFN number is selected, then the caller ID might be flagged as a SPAM call by the telecom regulators. For more information, see Set up outbound caller ID.
Question: Why am I seeing an Emergent Snapshot or my snapshot running after my backup window is closed for my RDS for SQL Server instance?

Why am I seeing an Emergent Snapshot or my snapshot running after my backup window is closed for my Amazon Relational Database Service (RDS) for SQL Server instance?Short descriptionAn Emergent Snapshot is an automatic as-needed backup taken by Amazon RDS due to the following:Restoring or creating a new database with SIMPLE recovery model.Modifying recovery model from FULL to SIMPLE/bulk-logged in both single and Multi-Availability Zone (AZ) instances.For Point in Time Recovery (PiTR), RDS uploads transaction log backups every five minutes for DB instances to Amazon Simple Storage Service (Amazon S3). When RDS doesn't take transactional log backups successfully, an Emergent Snapshot is triggered by RDS to mitigate problems during PiTR.After instance patching is complete, RDS triggers an Emergent Snapshot to safeguard the instance.You can back up your Amazon RDS instances using one of the following methods:Manually back up your DB instance by creating a DB snapshot. For more information, see creating a DB snapshot.Automatically back up your DB instance by making sure automated backups are turned on. Amazon RDS creates and saves automated backups during the backup window of your DB instance.When manually or automatically backing up your DB instance, an event "Backing up DB instance" is logged in RDS Events. Automated backups occur daily during the preferred backup window. Also, observing an event "Emergent Snapshot Request: Databases found to still be awaiting snapshot" in RDS events creates an automatic ad-hoc backup. This automatic ad-hoc backup occurs outside the instance backup window.Note: An Emergent Snapshot is normal and is an expected behavior.

ResolutionTo identify the reason for Emergent Snapshot, review the SQL Server engine logs:Open the Amazon RDS console.In the navigation pane, choose Databases.Choose the name of the DB instance that has the log file that you want to view.Choose the Logs & events tab.Scroll down to the Logs section.(Optional) Enter a search term to filter your results.Choose the log that you want to view, then choose View.Review the Amazon RDS for SQL Server logs, which are logged immediately before the Emergent Snapshot, to identify messages similar to the following:BACKUP failed to complete the command BACKUP LOG Test_Database. Check the backup application log for detailed messages.Setting database option RECOVERY to SIMPLE for database 'Test_Database'Restore is complete on database 'Test_Database'.  The database is now available.Starting up database 'Test_Database'.The Amazon RDS for SQL server logs indicate log backup failures and changes of a database recovery model to SIMPLE. They also indicate new databases restored on an instance or new databases created.To identify instances that have been patched, review RDS Events to look for an event similar to "Applying off-line patches to DB instance".
Question: How can I mount an Amazon EFS volume to an instance in my Elastic Beanstalk environment?

I want to mount an Amazon Elastic File System (Amazon EFS) volume to an Amazon Elastic Compute Cloud (Amazon EC2) instance in my AWS Elastic Beanstalk environment.

Short descriptionIn an Elastic Beanstalk environment, you can use Amazon EFS to create a shared directory that stores files that are uploaded or modified by your application's users. Your application can treat a mounted Amazon EFS volume as local storage. Therefore, you don't have to change your application code to scale up to multiple instances.To mount an Amazon EFS volume to an Amazon EC2 instance in your Elastic Beanstalk environment, you must include configuration files in your source code.Resolution1.    Create an Amazon EFS file system, and then note the Amazon EFS ID and security group ID.2.    To allow connections, edit the security group rules for the file system. The rules must allow inbound connections on port 2049 (Network File System or NFS) from the security group for instances in your Elastic Beanstalk environment.3.    Update the instance security group to allow outbound connections on port 2049 to the Amazon EFS security group.Note: The Amazon EFS security group must allow inbound connections when you mount the mount targets of one subnet on an environment in a different subnet. That is, it must allow inbound connections on port 2049 from your Amazon Virtual Private Cloud (Amazon VPC) CIDR.4.    In the root of your application bundle, create a directory named .ebextensions.5.    Add a formatted configuration file (YAML or JSON) to your directory.Important: Add the file system ID in the configuration file. Replace FILE_SYSTEM_ID: {"Ref" : "FileSystem"} with FILE_SYSTEM_ID: fs-xxxxxxxx. The configuration file includes a script that mounts the Amazon EFS file system to the instance during deployment.6.    Deploy the source code that includes the configuration file from step 5 to your Elastic Beanstalk application.7.    To confirm that your Amazon EFS volume is mounted to your instance on your specified mount path, run the following command:df -HRelated informationMounting EFS file systemsUsing Elastic Beanstalk with Amazon Elastic File SystemSecurity in Amazon EFS
Question: How do I set up the AWS CLI so that I can work with an Amazon DynamoDB table on Amazon EC2?

I want to configure the AWS Command Line Interface (AWS CLI) to work with Amazon DynamoDB tables on Amazon Elastic Compute Cloud (Amazon EC2).

ResolutionCreate an AWS Identity and Access Management (IAM) roleTo create an IAM role, do the following:For Select type of trusted entity, choose AWS service, and then choose EC2.For Attach permissions policies, choose AmazonDynamoDBFullAccess.Note: Follow the security best practice of granting least privilege to perform a task.Attach the IAM role to an Amazon EC2 instance1.    Launch an EC2 instance using an Amazon Linux Amazon Machine Image (AMI). Linux AMIs come with the AWS CLI installed.2.    On the Configure Instance Details page, in the IAM role drop-down list, select the IAM role that you created earlier. Be sure that the subnet that you select is accessible from the internet.3.    On the Configure Security Group page, be sure that you select a security group that allows SSH access from your IP address.Connect to the instance using SSH1.    Connect to your Linux instance using SSH.2.    After you're connected, run the yum update command to be sure that the software packages on the instance are up to date.Configure the AWS CLI1.    Run the aws configure command.2.    When prompted for an AWS Access Key ID and AWS Secret Access Key, press Enter. You don't need to provide keys because you're using an instance IAM role to connect with an AWS service.3.    When prompted for Default region name, enter the Region where your DynamoDB tables are located. For example, ap-northeast-3. For a list of Region names, see Service endpoints.4.    When prompted for Default output format, press Enter.5.    Run the list-tables command to confirm that you can run DynamoDB commands on the AWS CLI.Note: If you receive errors when running AWS CLI commands, make sure that you’re using the most recent version of the AWS CLI.

Related informationUsing the AWS CLI with DynamoDB
Question: How do I change the VPC for an Amazon RDS DB instance?

How can I move my Amazon Relational Database Service (Amazon RDS) DB instance from an existing Amazon Virtual Private Cloud (Amazon VPC) to a new VPC?Short descriptionTo move an Amazon RDS DB instance to a new VPC, you must change its subnet group. Before you move the RDS DB instance to a new network, configure the new VPC. This configuration includes the security group inbound rules, the subnet group, and the route tables. When you change the VPC for a DB instance, the instance reboots when it moves from one network to another. Because the DB instance isn't accessible while it's being moved, change the VPC during a planned change window that is outside the RDS weekly maintenance window.You can't change the VPC for a DB instance if:The DB instance is in multiple Availability Zones (AZs). Convert the DB instance to a single AZ, and then convert it back to a Multi-AZ DB instance after moving to the new VPC. For more information about converting instances, see High availability (Multi-AZ) for Amazon RDS. Note: You can't change a DB subnet group to a Multi-AZ configuration. By default, the Amazon Aurora storage is Multi-AZ—even for a single instance—so you can't modify the VPC for Amazon Aurora. For more information, see How can I change the VPC of an Amazon Aurora for MySQL or PostgreSQL cluster?The DB instance is a read replica or has read replicas. Remove the read replicas, and then add read replicas after the DB instance is moved to the new VPC.The subnet group created in the target VPC doesn't have subnets from the AZ where the source database is running. If the AZs are different, then the operation fails.

ResolutionOpen the Amazon RDS console.From the navigation pane, choose Subnet Groups from the navigation pane.Choose Create DB Subnet Group.Enter the subnet name, description, and VPC ID, and then choose the subnets needed for the DB instance.Choose Create.From the navigation pane, choose Databases.Select the DB instance, and then choose Modify.From the Connectivity section, select the Subnet Group associated with the new VPC. Then, choose the appropriate Security Group for that VPC.Choose Continue, and then choose Apply Immediately.Note: If you don't choose Apply Immediately, then Amazon RDS modifies the VPC during the next maintenance window.Review the details on the Modify DB Instance page, and then choose Modify DB Instance.This task can take several minutes to complete. You can confirm that the subnet is changed by selecting the instance and then navigating to the configuration details page. This shows that the subnet group is updated and the status is Complete. You can also open the RDS console and then choose Events in the left navigation pane. Confirm that the process moved the DB instance to the target VPC.

Related informationWorking with a DB instance in a VPCVPCs and subnets
Question: How do I provide feedback on or report errors in AWS documentation?

I noticed something that's incorrect in AWS documentation, or I have a suggestion for improving it.

ResolutionAWS updates the AWS Documentation pages at docs.aws.amazon.com in response to feedback. Choose the Provide feedback button on any page on docs.amazon.com, and enter your detailed feedback.AWS also updates articles in the AWS Knowledge Center in response to feedback. To provide feedback to AWS on a Knowledge Center article, choose the Submit feedback or Let us know button on the article page.

Related informationAWS Documentation
Question: How can I revoke my ACM public certificate?

How can I revoke an AWS Certificate Manager (ACM) public certificate?Short descriptionIf you no longer need your ACM public certificate, you can delete the certificate. If you need to revoke your ACM public certificate for compliance reasons, AWS Support can do this on your behalf. Important: Revoked ACM public certificates can't be used again with the same serial number.

ResolutionSubmit a request to AWS Support to revoke the public certificateFollow the instructions to create a support case in the Support Center of the AWS Management Console.For emailed validated certificates, an email that looks similar to the following is sent to three registered addresses in WHOIS and the five common domain name addresses:Amazon Trust Services has been requested to revoke the followingcertificate. If you requested this revocation, please respond to thisemail with I approve.Domain: <DOMAIN>AWS account ID: <AWS Account ID>AWS Region name: <REGION>Certificate identifier: <CERTIFICATE IDENTIFIER>Sincerely,Amazon Trust ServicesFor DNS validated certificates, you might be contacted by AWS Support to add a unique TXT record in the DNS database to verify domain ownership.After receiving the requested information and domain ownership is confirmed, AWS Support revokes the public certificate.Verify that the ACM public certificate is revoked with OpenSSLNote: If you receive errors when running OpenSSL commands, make sure that you’re using the most recent OpenSSL version.1.    Get the certificate file information for your domain and save the output to a .pem file:$ openssl s_client -connect example.com:443 2>&1 < /dev/null | sed -n '/-----BEGIN/,/-----END/p' > example.pem2.    Check if the certificate has an Online Certificate Status Protocol (OCSP) URI:$ openssl x509 -noout -ocsp_uri -in example.pemOutput:http://ocsp.rootca1.amazontrust.com3.    Capture the certificate chain:$ openssl s_client -connect example.com:443 -showcerts 2>&1 < /dev/null4.    Save the .pem file.5.    Send an OCSP request similar to the following:openssl ocsp -issuer chain.pem -cert example.pem -url http://ocsp.rootca1.amazontrust.comOutput:Response verify OKexample.pem: revokedThis Update: Apr 9 03:02:45 2014 GMTNext Update: Apr 10 03:02:45 2014 GMTRevocation Time: Mar 25 15:45:55 2014 GMTIn the output, note that the response is revoked.

Related informationBest practices
Question: How do I connect my Amazon SageMaker Studio notebook with an Amazon Redshift cluster?

I want to connect my Amazon SageMaker Studio notebook with an Amazon Redshift cluster.

ResolutionPublicly accessible clusterIf the Redshift cluster is publicly accessible, then you can access the cluster from either of the following:A SageMaker domain launched with public internet only and no Amazon Virtual Private Cloud (Amazon VPC) accessA SageMaker Studio domain launched in an Amazon VPCIf the Redshift cluster is in a different VPC, then configure a VPC peering connection to make sure that Studio can access the cluster.Private clusterIf the Redshift cluster is private, then you can access the cluster only through a SageMaker Studio domain launched in an Amazon VPC. If the cluster is in a different VPC, configure a VPC peering connection to make sure that Studio can access the cluster.Additional requirementsBe sure that the following requirements are met for both types of clusters:The security group attached to the SageMaker Studio allows outbound traffic to ephemeral ports. When a Studio client connects to a Redshift server, a random port from the ephemeral port range (1024-65535) becomes the client's source port.The security group attached to the Redshift cluster allows inbound connection from the security group attached to the SageMaker Studio domain on port 5439.If you configured custom DNS, verify that the DNS server used by the Studio VPC can resolve the hostname of the Redshift cluster.

Related informationConnect to an external data sourceUsing the Amazon Redshift data API to interact from an Amazon SageMaker Jupyter notebookRead the Docs documentation for Ingest data with Redshift
Question: How can I resolve an “Access Error” after configuring my VPC flow log?

After I configure my virtual private cloud (VPC) flow log, I receive an "Access Error."Short descriptionIf you have a permissions issue when you configure your VPC flow log, then you see the following error:"Access Error. The IAM role for your flow logs does not have sufficient permissions to send logs to the CloudWatch log group."The following scenarios commonly cause this error:The Identity and Access Management (IAM) role for your flow log doesn't have permission to publish flow log records to the Amazon CloudWatch log group.The IAM role doesn't have a trust relationship with the flow logs service.The trust relationship doesn't specify the flow logs service as the principal.

ResolutionThe IAM role for your flow log doesn't have permission to publish flow log records to the CloudWatch log groupThe IAM role that's associated with your flow log must have sufficient permissions to publish flow logs to the specified log group in CloudWatch Logs. The IAM role must belong to your AWS account. Make sure that the IAM role has the following permissions:{  "Version": "2012-10-17",  "Statement": [    {      "Effect": "Allow",      "Action": [        "logs:CreateLogGroup",        "logs:CreateLogStream",        "logs:PutLogEvents",        "logs:DescribeLogGroups",        "logs:DescribeLogStreams"      ],      "Resource": "*"    }  ]}The IAM role doesn't have a trust relationship with the flow logs serviceMake sure that your role has a trust relationship that allows the flow logs service to assume the role:1.    Log in to the IAM console.2.    Select Roles.3.    Select VPC-Flow-Logs.4.    Select Trust relationships.5.    Select Edit trust policy.6.    Delete the current code in this section, and then enter the following policy:{  "Version": "2012-10-17",  "Statement": [    {      "Effect": "Allow",      "Principal": {        "Service": "vpc-flow-logs.amazonaws.com"      },      "Action": "sts:AssumeRole"    }  ]}7.    Select Update policy.Trust relationships give you control over what services are allowed to assume roles. In this example, the relationship allows the VPC Flow Logs service to assume the role.The trust relationship doesn't specify the flow logs service as the PrincipalMake sure that the trust relationship specifies the flow logs service as the Principal:{  "Version": "2012-10-17",  "Statement": [    {      "Effect": "Allow",      "Principal": {        "Service": "vpc-flow-logs.amazonaws.com"      },      "Action": "sts:AssumeRole"    }  ]}Related informationIAM role for publishing flow logs to CloudWatch LogsTroubleshoot VPC flow logs
Question: How do I resolve errors when issuing a new ACM-PCA certificate?

I tried requesting a new private end-entity certificate or subordinate CA for AWS Certificate Manager (ACM) and the request failed.

Short descriptionTo troubleshoot failed private certificate requests, check the following:The pathLenConstraint parameter of the issuing certificate authority.The status of the issuing certificate authority.The signing algorithm family of the issuing certificate authority.The validity period of the requested certificate.AWS Identity and Access Management (IAM) permissions.

ResolutionThe "pathLenConstraint" parameter of the issuing certificate authorityCreating a CA with a path length greater than or equal to the path length of its issuing CA certificate returns a ValidationException error. Make sure that the pathLenConstraint for issuing an ACM subordinate CA is less than the path length of the issuing CA.The status of the issuing certificate authorityIssuing a new PCA certificate using the IssueCertificate API with an expired a CA (which isn't in Active status) returns a InvalidStateException failure code.If the signing CA is expired, make sure that you renew it first before issuing new subordinate CA certificates or ACM private certificates.The signing algorithm family of the issuing certificate authorityThe AWS Management Console doesn't support issuing private ECDSA certificates, and so the issuing CA is unavailable. This occurs even if an ECDSA private subordinate certificate authority was already created. You can use the IssueCertificate API call and specify the ECDSA variant with the --signing-algorithm flag.The validity period of the requested certificateCertificates issued and managed by ACM (those certificates that ACM generates the private key for) have a validity period of 13 months (395 days).For ACM Private CA, you can use the IssueCertificate API to apply any validity period. However, if you specify the certificate validity period longer than the issuing certificate authority, the certificate issuance fails.It's a best practice to set the CA certificate validity period to a value that's two to five times as large as the period of child or end-entity certificates. For more information, see Choosing validity periods.IAM permissionsPrivate certificates issued with IAM identities must have the required permissions, or the request fails with an "AccessDenied" error. It's a best practice to grant your IAM identities permission to issue private certificates while adhering to the principle of granting least privilege.For more information, see Identity and Access Management for AWS Certificate Manager Private Certificate Authority.