How can I improve Amazon Web Services performance without guessing?
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
ReadMeFeed / Community knowledge
EC2, Lambda, EKS, S3 and resilient AWS architectures.
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
I launched a new Amazon Linux 2 instance. I tried connecting to the instance via the EC2 instance connect option under the Connect -> EC2 Instance Connect (browser-based SSH connection) option in the Management Console. I get the error: There was a problem setting up the instance connection An internal error has occurred within the remote server, and the
The documentations of how to use SageMaker estimators are scattered around, sometimes obsolete, incorrect. Is there a one stop location which gives the comprehensive views of how to use SageMaker SDK Estimator to train and save models?
When you are running multiple CloudFormation stacks within the same region, you are able to share references across stacks using CloudFormation Outputs However, outputs cannot be used for cross region references as that documentation highlights. You can't create cross-stack references across regions. You can use the intrinsic function Fn::ImportValue to impo
I am following the proposed solution by Trivikr for adding support for s3.getSignedUrl api which is not currently available in newer v3. I am trying to make a signed url for getting an object from bucket. Just for convenience, the code is being added below: const { S3, GetObjectCommand } = require("@aws-sdk/client-s3"); // 1.0.0-gamma.2 version const { S3Req
I'm working with CDK/CloudFormation and recently started getting this error when attempting to create a new stack: The maximum number of addresses has been reached. Looking in the AWS Management Console, there is a limit of 40 VPC IP addresses and there are exactly 40 in the list - but some of these have neither an Associated Instance ID nor an Association I
The plan was to get data from aws data exchange, move it to an s3 bucket then query it by aws athena for a data api. Everything works, just feels a bit slow. No matter the dataset nor the query I can't get below 2 second in athena response time. Which is a lot for an API. I checked the best practices but seems that those are also above 2 sec. So my question:
A fictional application reads most objects under an allowed prefix. A newer object returns AccessDenied. The newer object uses a different customer-managed KMS key. The bucket policy appears unchanged. Which evidence would distinguish S3 access from encryption-key access?
The same intended role can read an object from an approved diagnostic session, while a service running through an S3 VPC endpoint receives 403. The team has checked the role and bucket policy but has not reviewed the endpoint policy. How should the differing request paths be compared?