ReadMeFeed / Community knowledge
EC2, Lambda, EKS, S3 and resilient AWS architectures.
ImportError: cannot import name 'docevents' from 'botocore.docs.bcdoc' (/python3.7/site-packages/botocore/docs/bcdoc/ init .py) Traceback (most recent call last): File "/root/.pyenv/versions/3.7.6/bin/aws", line 19, in <module> import awscli.clidriver File "/root/.pyenv/versions/3.7.6/lib/python3.7/site-packages/awscli/clidriver.py", line 36, in <mo
I understand that Next.js is a Node.js framework that requires server capabilities and therefore, using it for server-side rendering (SSR) could not be hosted on an S3 instance only. However, does that mean that the only alternative is to host the entire app on an EC2 instance, which is significantly more expensive, or is there another midway solution?
I have two accounts - Account A and Account B. In account A, I have a policy with a user from account B can interact with Account A. I have a repository in both accounts. Account B doesn't have a policy set ( Not sure if I need a policy for Account A to interact with it). My question is how do I push ecr images from Account A into Account B. I would like a c
I was working on uploading and downloading a file to S3 bucket using pre-signed URLs.I came across these two methods generate_presigned_url('put_object') and generate_presigned_post . What is the difference between these two methods? # upload a file to a bucket with generate_presigned_url with put object s3_client.generate_presigned_url('put_object', Params=
Background:- I have a gateway account( with no permissions) in which users are created and in order to access aws resources we use roles having admin access. config file [profile gateway] region = ap-southeast-1 output = json [profile DA] region = ap-south-1 output = json role_arn = arn:aws:iam::xxxxxxxxxxxxx:role/jatin mfa_serial = arn:aws:iam::xxxxxxxxxx:m
We have a EKS setup provisioned where we use a Cloud Native Buildpacks based Tekton Pipeline our PipelineRuns are stuck and pending forever without getting a Pod resource. We created a PersistentVolumeClaim like this: apiVersion: v1 kind: PersistentVolumeClaim metadata: name: buildpacks-source-pvc spec: accessModes: - ReadWriteOnce resources: requests: stora
I am looking to make use of the native import/export that comes with ES6. I am using Serverless Containers within AWS Lambda. I have my Dockerfile which looks like this: FROM public.ecr.aws/lambda/nodejs:14 COPY app ./ RUN npm install CMD [ "app.handler" ] I then have an app directory with my application code. The app.js code looks like this: import { succes
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
commented · 05 Jun 2025, 04:07 UTC
answered · 06 Mar 2025, 23:56 UTC
docker
python
kubernetes