This forum provides solutions for aws developers for their issues.It provides solutions for aws elastic ip, ec2 instance, public ip,route53 pricing, load balancers in aws,Orchestration, ebs,, lambda, installing mongodb on ubuntu etc.

Saturday 8 April 2017

not authorized to perform: route53:ChangeResourceRecordSets on resource:

{ [AccessDenied: User: arn:aws:iam::902816437957:user/SrinivasNidadavolu is not authorized to perform: route53:ChangeResourceRecordSets on resource: arn:aws:route53:::hostedzone/Z4MNS19SVTW6HWE]
  message: 'User: arn:aws:iam::902816437957:user/SrinivasNidadavolu is not authorized to perform: route53:ChangeResourceRecordSets on resource: arn:aws:route53:::hostedzone/Z4MNS19SVTW6HWE',
  code: 'AccessDenied',
  time: Sun Apr 09 2017 14:54:04 GMT+0800 (Malay Peninsula Standard Time),
  requestId: '320f74e1-1cf1-11e7-b82f-d7cbe814b865',
  statusCode: 403,
  retryable: false,
  retryDelay: 49.57547772210091 }


Solution :

Go to IAM in AWS Console
IAM Resources    - Users: 1

steps:
1.click on the user

2. add Add inline policy
      Policy Generator - Select

You need to add inline policy to the user


1.Select Route 53,
2. ChangeResourceRecords
3. ARN is  arn:aws:route53:::hostedzone/M148QEXAMPUE9J    - us your hostzone


Friday 7 April 2017

Instance does not have a volume attached at root (/dev/sda1)

Error starting instances
Invalid value 'i-07a7ac5708cbb15' for instanceId. Instance does not have a volume attached at root (/dev/sda1)



Solution:

Whenever you attach the Volume, set parameter :


Device: /dev/sda1

Labels

Online Training

Your Name :
Your Email: (required)
Your Message: (required)

Powered by Blogger.

Recent Posts

Find Us On Facebook

Popular Posts