Santosh Baruah's questions

In our scenario, We're running into an issue with our SPF records in route53. We are receiving SPF Too Many DNS Lookups because we are using multiple mail services. Is there a way to resolve this? I saw one thread stating to run a look up on the domains and include them by IP but that doesn't seem too stable of a solution. Another said to us PTR but that seems like the same path. Is there a better way you know of that we could achieve this?

"Error! 15 DNS lookups required to evaluate the SPF record. The maximum is 10."

v=spf1 ip4:52.209.21.221 include:spf1.abc.com include:spf2.abc.com ~all

We have 7 mailing platforms which is causing too many DNS lookups.

spf1.abc.com    -
    
"v=spf1 include:_spf.salesforce.com include:spf.protection.outlook.com include:mail.zendesk.com ~all"

spf2.abc.com    -
    
"v=spf1 include:amazonses.com include:sendgrid.net include:abc-com.spf.smtp25.com include:_spf.google.com ~all"

Is this modification will help

"v=spf1 ip4:52.209.21.221 include:spf1.abc.com -all"

Do we need to go with SPF flattening technique, how can we achieve that can anyone advise me on this?

My root volume won't expand to the size the EC2 console shows we've set the drive to. The C:\ should be 1.5 TB but only shows as 50 GB. The option to expand the volume isn't present in the disk management.

seems that drive C cannot be able to extend due to a partition recovery is in between drive C and the free space

Do I need to delete recovery partition or alternative solution is there . Could anyone guide me how to resolve this?

How should I unmount a drive well ensuring it wont be deleted? We want to move

vol-0de12fb88020aa624
from i-0b727a35caea24013 
to i-0dff0911c0ebf45f9

I want to move the volume, do not want copy files from one EBS volume to another EBS volume ?? How fast can unmounting result in deleting of the volume? can anyone advice me with the best way for this ?

In my production Environment I'm observing a sporadic issue where pages are taking a long time to load. In the error logs we are seeing:

PHP Fatal error:  Maximum execution time of 30 seconds exceeded

The affected line is where a session is being created for the user.

The directories are physical. There are +3.5 million files in the directory. The trash collection is set for 31 days for sessions in PHP.

Could you advise on what issues we might be running into and how to resolve them?

Possible solutions I thought of:
Increase provisioned IOPS on the drive
Clear session data every X days
Change scaling policy so if number of sessions on any server goes above X number we spin up a 
new server
Change instance type of our production servers
Move session data elsewhere 
store session data in DB
AWS API GateWay
elastic caching

Could anyone advise on what issues?

I'm wondering specifically is there way to migrate Centos6.3 server from Rackspace to AWS cloud, Server image is 268.92 GB Uncompressed.

I've done the sync processes before and it didn't work so I wanted to spin up the exact same instance. I also tried the newer libraries of the platform we are running but it failed.

This is essentially what i need to run https://github.com/knmnyn/ParsCit. Is there's another way to get that running on the dev machine to updated the repo on? can anyone Help me with this?

In Listeners Load Balancer, Can it make sense to push all the listening rules into one rule? In our settings Currently, all are looking at the host header for a non-HTTPS connection and redirecting to the provided host with an HTTPS connection. Is there is a limit to the number of host rules or if separating them outperform better.?can you please suggest .

example:

1.arn...3e0bb           IF                                       THEN
                        host is abc.com OR xyz.com               Redirect to https://#{host}:443/#{path}?#{query}
                                                                 status code HTTP_301

I'm facing the issue of occasional emails being queued when sending through SES. This can be seen in the dynamodb. what might be the possible way and how to avoid this ?

In my aws env requests are hanging at the ALB for some reason. I haven't been able to identify a cause yet aside from Cache hanging requests there and possibly the session write being left open causing it to wait. what might be the possible reason for of it ,Are there other diagnostic tools for recommendation to add into the stack to try to debug this issue?