amazon-web-services

Home/amazon-web-services

Questions and answers begin here Latest Questions

Asked: 4 years agoIn:
Teacher

I am a software developer who is currently working on an AWS project. While trying to create a new role, I keep facing the same problem. Whenever I try to create a new IAM role with a certain policy document, ...Read more

I am a software developer who is currently working on an AWS project. While trying to create a new role, I keep facing the same problem. Whenever I try to create a new IAM role with a certain policy document, AWS CloudFormation throws an error message stating that the ‘createRole’ action has a prohibited field.
Here is the code I am using to create the role:

Resources:
myRole:
Type: 'AWS::IAM::Role'
Properties:
RoleName: 'myRole'
AssumeRolePolicyDocument:
Statement:
- Effect: Allow
Principal:
Service:
- ec2.amazonaws.com
Action:
- 'sts:AssumeRole'
ManagedPolicyArns:
- arn:aws:iam::aws:policy/AmazonS3FullAccess
- arn:aws:iam::aws:policy/AmazonEC2FullAccess
Policies:
- PolicyName: 'myPolicy'
PolicyDocument:
Statement:
- Effect: Allow
Action: ['ec2:StartInstances']
Resource: ['arn:aws:ec2:*:*:instance/*']

What could be causing this error message? I have tried various ways to change the policy document, but I still get the same error. Is there something wrong with my IAM role creation syntax? Any help would be much appreciated.

Read less
amazon-web-servicesAWSIAMpoliciesprohibited fieldroles
  1. Dive into Turkish History
    Your answer is awaiting moderation.

    Explore the significant historical events that shaped Turkey on our website. It's a journey into the past.

    Explore the significant historical events that shaped Turkey on our website. It’s a journey into the past.

    See less
    • 0
Asked: 5 years agoIn:
Teacher

I am having trouble getting AWS Secrets Manager to work with my server-side application. I’m currently working on a web-based project that requires me to store sensitive data in AWS Secrets Manager. However, when I try to access the specified ...Read more

I am having trouble getting AWS Secrets Manager to work with my server-side application. I’m currently working on a web-based project that requires me to store sensitive data in AWS Secrets Manager. However, when I try to access the specified secret, I get an error message saying that the secret could not be found.
Here’s the code that I’m using to retrieve the secrets:
const AWS = require('aws-sdk');
const client = new AWS.SecretsManager({
region: 'us-east-1'
});
let secret;
client.getSecretValue({ SecretId: 'my-secret' }, (err, data) => {
if (err) {
console.log('Error retrieving secret:', err);
} else {
secret = JSON.parse(data.SecretString);
}
});
I’ve double-checked that the IAM role assigned to my EC2 instance has the necessary permissions to read the secrets, and the Secret Manager service is properly configured. I’m not sure what else could be causing the error at this point. Does anyone have any suggestions on how I can troubleshoot this issue and get the secrets working with my application? Any help would be greatly appreciated.

Read less
access-controlamazon-web-servicesaws-secrets-managersecrets
  1. Dive into Turkish History
    Your answer is awaiting moderation.

    Explore the significant historical events that shaped Turkey on our website. It's a journey into the past.

    Explore the significant historical events that shaped Turkey on our website. It’s a journey into the past.

    See less
    • 0